<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="fedregister.xsl"?>
<FEDREG xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="FRMergedXML.xsd">
    <VOL>72</VOL>
    <NO>71</NO>
    <DATE>Friday, April 13, 2007</DATE>
    <UNITNAME>Contents</UNITNAME>
    <CNTNTS>
        <AGCY>
            <EAR>Agricultural</EAR>
            <PRTPAGE P="iii"/>
            <HD>Agricultural Marketing Service</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency information collection activities; proposals, submissions, and approvals, </DOC>
                    <PGS>18620</PGS>
                    <FRDOCBP T="13APN1.sgm" D="0">E7-7039</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Agriculture</EAR>
            <HD>Agriculture Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Agricultural Marketing Service</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Animal and Plant Health Inspection Service</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Farm Service Agency</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Forest Service</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Rural Housing Service</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>Animal</EAR>
            <HD>Animal and Plant Health Inspection Service</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency information collection activities; proposals, submissions, and approvals, </DOC>
                    <PGS>18620-18622</PGS>
                    <FRDOCBP T="13APN1.sgm" D="1">E7-7042</FRDOCBP>
                    <FRDOCBP T="13APN1.sgm" D="1">E7-7044</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Army</EAR>
            <HD>Army Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Engineers Corps</P>
            </SEE>
        </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>Centers</EAR>
            <HD>Centers for Medicare &amp; Medicaid Services</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency information collection activities; proposals, submissions, and approvals, </DOC>
                    <PGS>18658-18659</PGS>
                    <FRDOCBP T="13APN1.sgm" D="1">E7-6990</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Coast Guard</EAR>
            <HD>Coast Guard</HD>
            <CAT>
                <HD>RULES</HD>
                <SJ>Ports and waterways safety; regulated navigation areas, safety zones, security zones, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Intracoastal Waterway, Treasure Island, FL, </SJDOC>
                    <PGS>18585-18587</PGS>
                    <FRDOCBP T="13APR1.sgm" D="2">E7-7073</FRDOCBP>
                </SJDENT>
            </CAT>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Meetings:</SJ>
                <SJDENT>
                    <SJDOC>National Maritime Security Advisory Committee, </SJDOC>
                    <PGS>18664-18665</PGS>
                    <FRDOCBP T="13APN1.sgm" D="1">E7-7072</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Commerce</EAR>
            <HD>Commerce Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Economics and Statistics Administration</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> International Trade Administration</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> National Institute of Standards and Technology</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> National Oceanic and Atmospheric Administration</P>
            </SEE>
        </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>18626-18627</PGS>
                    <FRDOCBP T="13APN1.sgm" D="1">E7-7057</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Customs</EAR>
            <HD>Customs and Border Protection Bureau</HD>
            <CAT>
                <HD>RULES</HD>
                <DOCENT>
                    <DOC>Automated Commercial Environment Truck Manifest System; advance electronic truck cargo information requirement, </DOC>
                    <PGS>18574-18575</PGS>
                    <FRDOCBP T="13APR1.sgm" D="1">E7-6908</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Defense</EAR>
            <HD>Defense Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Engineers Corps</P>
            </SEE>
            <CAT>
                <HD>RULES</HD>
                <DOCENT>
                    <DOC>Privacy Act; implementation, </DOC>
                    <PGS>18758-18790</PGS>
                    <FRDOCBP T="13APR2.sgm" D="32">E7-6118</FRDOCBP>
                </DOCENT>
            </CAT>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Freedom of Information Act; implementation:</SJ>
                <SJDENT>
                    <SJDOC>Central Contractor Registration database; access requests, </SJDOC>
                    <PGS>18637-18640</PGS>
                    <FRDOCBP T="13APN1.sgm" D="3">E7-7010</FRDOCBP>
                </SJDENT>
                <SJ>Meetings:</SJ>
                <SJDENT>
                    <SJDOC>Employer Support of the Guard and Reserve Advisory Board, </SJDOC>
                    <PGS>18640</PGS>
                    <FRDOCBP T="13APN1.sgm" D="0">07-1829</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Drug</EAR>
            <HD>Drug Enforcement Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency information collection activities; proposals, submissions, and approvals, </DOC>
                    <PGS>18668-18669</PGS>
                    <FRDOCBP T="13APN1.sgm" D="1">E7-7080</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Economics</EAR>
            <HD>Economics and Statistics Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Reports and guidance documents; availability, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Business innovation; measurement and its impact on U.S. economy; comment request, </SJDOC>
                    <PGS>18627-18628</PGS>
                    <FRDOCBP T="13APN1.sgm" D="1">07-1827</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Energy</EAR>
            <HD>Energy Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Federal Energy Regulatory Commission</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>Engineers</EAR>
            <HD>Engineers Corps</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Environmental statements; notice of intent:</SJ>
                <SJDENT>
                    <SJDOC>Duval County, FL; Jacksonville Harbor navigation study; general reevaluation report, </SJDOC>
                    <PGS>18641</PGS>
                    <FRDOCBP T="13APN1.sgm" D="0">07-1835</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Mississippi River-Gulf Outlet 3-D Project, LA, </SJDOC>
                    <PGS>18641-18643</PGS>
                    <FRDOCBP T="13APN1.sgm" D="2">E7-7086</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>EPA</EAR>
            <HD>Environmental Protection Agency</HD>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <SJ>Air quality implementation plans; approval and promulgation; various States; air quality planning purposes; designation of areas:</SJ>
                <SJDENT>
                    <SJDOC>Virginia, </SJDOC>
                    <PGS>18602-18614</PGS>
                    <FRDOCBP T="13APP1.sgm" D="12">E7-7017</FRDOCBP>
                </SJDENT>
            </CAT>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Environmental statements; availability, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Agency comment availability, </SJDOC>
                    <PGS>18643</PGS>
                    <FRDOCBP T="13APN1.sgm" D="0">E7-7022</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Agency weekly receipts, </SJDOC>
                    <PGS>18644</PGS>
                    <FRDOCBP T="13APN1.sgm" D="0">E7-7021</FRDOCBP>
                </SJDENT>
                <SJ>Meetings:</SJ>
                <SJDENT>
                    <SJDOC>Association of American Pesticide Control Officials/State FIFRA Issues Research and Evaluation Group, </SJDOC>
                    <PGS>18644-18645</PGS>
                    <FRDOCBP T="13APN1.sgm" D="1">E7-6945</FRDOCBP>
                </SJDENT>
                <SJ>Pesticide registration, cancellation, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Propiconazole, etc., </SJDOC>
                    <PGS>18645-18651</PGS>
                    <FRDOCBP T="13APN1.sgm" D="6">E7-7019</FRDOCBP>
                </SJDENT>
                <SJ>Superfund; response and remedial actions, proposed settlements, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Continental Steel Corp. Site, IN, </SJDOC>
                    <PGS>18651</PGS>
                    <FRDOCBP T="13APN1.sgm" D="0">E7-7016</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Executive</EAR>
            <HD>Executive Office of the President</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Presidential Documents</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>Farm</EAR>
            <HD>Farm Service Agency</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Environmental statements; availability, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Hurricane Tree Assistance Program, </SJDOC>
                    <PGS>18622-18623</PGS>
                    <FRDOCBP T="13APN1.sgm" D="1">E7-6993</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>FAA</EAR>
            <HD>Federal Aviation Administration</HD>
            <CAT>
                <HD>RULES</HD>
                <SJ>Airworthiness directives:</SJ>
                <SJDENT>
                    <SJDOC>Airbus, </SJDOC>
                    <PGS>18563-18565</PGS>
                    <FRDOCBP T="13APR1.sgm" D="2">E7-6931</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <PRTPAGE P="iv"/>
                    <SJDOC>British Aerospace Regional Aircraft, </SJDOC>
                    <PGS>18565-18566</PGS>
                    <FRDOCBP T="13APR1.sgm" D="1">E7-6913</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Latinoamericana de Aviacion S.A., </SJDOC>
                    <PGS>18566-18568</PGS>
                    <FRDOCBP T="13APR1.sgm" D="2">E7-6929</FRDOCBP>
                </SJDENT>
                <DOCENT>
                    <DOC>Class E Airspace, </DOC>
                    <PGS>18568-18569</PGS>
                    <FRDOCBP T="13APR1.sgm" D="1">07-1812</FRDOCBP>
                </DOCENT>
            </CAT>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <SJ>Airworthiness directives:</SJ>
                <SJDENT>
                    <SJDOC>Diamond Aircraft Industries GmbH, </SJDOC>
                    <PGS>18698-18602</PGS>
                    <FRDOCBP T="13APP1.sgm" D="2">E7-7049</FRDOCBP>
                    <FRDOCBP T="13APP1.sgm" D="2">E7-7050</FRDOCBP>
                </SJDENT>
                <SJ>Airworthiness standards:</SJ>
                <SUBSJ>Special conditions—</SUBSJ>
                <SSJDENT>
                    <SUBSJDOC>Boeing Model 787-8 airplane, </SUBSJDOC>
                    <PGS>18597-18598</PGS>
                    <FRDOCBP T="13APP1.sgm" D="1">E7-7065</FRDOCBP>
                </SSJDENT>
            </CAT>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Airport noise compatibility program:</SJ>
                <SJDENT>
                    <SJDOC>Alexandria International Airport, LA, </SJDOC>
                    <PGS>18723-18724</PGS>
                    <FRDOCBP T="13APN1.sgm" D="1">07-1837</FRDOCBP>
                </SJDENT>
                <SJ>Environmental statements; availability, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Fort Lauderdale-Hollywood International Airport, FL, </SJDOC>
                    <PGS>18724</PGS>
                    <FRDOCBP T="13APN1.sgm" D="0">07-1836</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Federal Emergency</EAR>
            <HD>Federal Emergency Management Agency</HD>
            <CAT>
                <HD>RULES</HD>
                <SJ>Flood elevation determinations:</SJ>
                <SJDENT>
                    <SJDOC>Various States, </SJDOC>
                    <PGS>18587-18593</PGS>
                    <FRDOCBP T="13APR1.sgm" D="6">E7-7009</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Federal Energy</EAR>
            <HD>Federal Energy Regulatory Commission</HD>
            <CAT>
                <HD>RULES</HD>
                <SJ>Electric utilities (Federal Power Act):</SJ>
                <SJDENT>
                    <SJDOC>Transmission service; preventing undue discrimination and preference, </SJDOC>
                    <PGS>18569-18572</PGS>
                    <FRDOCBP T="13APR1.sgm" D="3">E7-7000</FRDOCBP>
                </SJDENT>
                <SJ>Practice and procedure:</SJ>
                <SJDENT>
                    <SJDOC>Critical energy infrastructure information, </SJDOC>
                    <PGS>18572-18574</PGS>
                    <FRDOCBP T="13APR1.sgm" D="2">E7-7005</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Federal Highway</EAR>
            <HD>Federal Highway Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Environmental statements; notice of intent:</SJ>
                <SJDENT>
                    <SJDOC>Cidra, PR, </SJDOC>
                    <PGS>18725</PGS>
                    <FRDOCBP T="13APN1.sgm" D="0">E7-7014</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Federal Housing</EAR>
            <HD>Federal Housing Finance Board</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Federal home loan bank system:</SJ>
                <SJDENT>
                    <SJDOC>Community support review; members selected for review; list, </SJDOC>
                    <PGS>18651-18655</PGS>
                    <FRDOCBP T="13APN1.sgm" D="4">E7-6142</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Federal Motor</EAR>
            <HD>Federal Motor Carrier Safety Administration</HD>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <SJ>Motor carrier safety standards:</SJ>
                <SJDENT>
                    <SJDOC>Intermodal equipment providers, motor carriers, and drivers operating intermodal equipment; safety and maintenance requirements, </SJDOC>
                    <PGS>18615-18616</PGS>
                    <FRDOCBP T="13APP1.sgm" D="1">07-1865</FRDOCBP>
                </SJDENT>
            </CAT>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Motor carrier safety standards:</SJ>
                <SJDENT>
                    <SJDOC>Driver qualifications; vision requirement exemptions, </SJDOC>
                    <PGS>18725-18728</PGS>
                    <FRDOCBP T="13APN1.sgm" D="1">E7-6997</FRDOCBP>
                    <FRDOCBP T="13APN1.sgm" D="1">E7-6998</FRDOCBP>
                    <FRDOCBP T="13APN1.sgm" D="1">E7-6999</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Federal Railroad</EAR>
            <HD>Federal Railroad Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Exemption petitions, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Alaska Railroad Corp. et al., </SJDOC>
                    <PGS>18728</PGS>
                    <FRDOCBP T="13APN1.sgm" D="0">E7-7069</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Canadian National Railway Co., </SJDOC>
                    <PGS>18728-18729</PGS>
                    <FRDOCBP T="13APN1.sgm" D="1">E7-7068</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>SMS Lines, </SJDOC>
                    <PGS>18729</PGS>
                    <FRDOCBP T="13APN1.sgm" D="0">E7-7079</FRDOCBP>
                </SJDENT>
                <SJ>Meetings:</SJ>
                <SJDENT>
                    <SJDOC>Private highway-rail grade crossings safety, </SJDOC>
                    <PGS>18730</PGS>
                    <FRDOCBP T="13APN1.sgm" D="0">E7-7064</FRDOCBP>
                </SJDENT>
                <SJ>Traffic control systems; discontinuance or modification:</SJ>
                <SJDENT>
                    <SJDOC>BNSF Railway Co., </SJDOC>
                    <PGS>18730-18731</PGS>
                    <FRDOCBP T="13APN1.sgm" D="1">E7-7070</FRDOCBP>
                    <FRDOCBP T="13APN1.sgm" D="0">E7-7077</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>CSX Transportation, Inc., </SJDOC>
                    <PGS>18731-18732</PGS>
                    <FRDOCBP T="13APN1.sgm" D="1">E7-7059</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>CSX Transportation, Inc., et al., </SJDOC>
                    <PGS>18732</PGS>
                    <FRDOCBP T="13APN1.sgm" D="0">E7-7060</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Federal Reserve</EAR>
            <HD>Federal Reserve System</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Banks and bank holding companies:</SJ>
                <SJDENT>
                    <SJDOC>Change in bank control, </SJDOC>
                    <PGS>18655-18656</PGS>
                    <FRDOCBP T="13APN1.sgm" D="1">E7-6987</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Formations, acquisitions, and mergers, </SJDOC>
                    <FRDOCBP T="13APN1.sgm" D="0">E7-6988</FRDOCBP>
                    <PGS>18656</PGS>
                    <FRDOCBP T="13APN1.sgm" D="0">E7-7035</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Federal Transit</EAR>
            <HD>Federal Transit Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Reports and guidance documents; availability, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Title VI and Title VI-dependent guidelines for FTA recipients, </SJDOC>
                    <PGS>18732-18746</PGS>
                    <FRDOCBP T="13APN1.sgm" D="14">E7-7066</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Food</EAR>
            <HD>Food and Drug Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency information collection activities; proposals, submissions, and approvals, </DOC>
                    <PGS>18659-18660</PGS>
                    <FRDOCBP T="13APN1.sgm" D="1">E7-6983</FRDOCBP>
                </DOCENT>
                <SJ>Meetings:</SJ>
                <SJDENT>
                    <SJDOC>Supplements; chemistry, manufacturing, controls, and changes to approved marketing applications, </SJDOC>
                    <PGS>18660-18661</PGS>
                    <FRDOCBP T="13APN1.sgm" D="1">E7-6985</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Forest</EAR>
            <HD>Forest Service</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Appealable decisions; legal notice:</SJ>
                <SJDENT>
                    <SJDOC>Southern Region, </SJDOC>
                    <PGS>18623-18625</PGS>
                    <FRDOCBP T="13APN1.sgm" D="2">07-1834</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Health</EAR>
            <HD>Health and Human Services Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Centers for Medicare &amp; Medicaid Services</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Food and Drug Administration</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Health Resources and Services Administration</P>
            </SEE>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency information collection activities; proposals, submissions, and approvals, </DOC>
                    <PGS>18657-18658</PGS>
                    <FRDOCBP T="13APN1.sgm" D="0">E7-7002</FRDOCBP>
                    <FRDOCBP T="13APN1.sgm" D="0">E7-7003</FRDOCBP>
                    <FRDOCBP T="13APN1.sgm" D="0">E7-7004</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Health</EAR>
            <HD>Health Resources and Services Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency information collection activities; proposals, submissions, and approvals, </DOC>
                    <PGS>18661-18662</PGS>
                    <FRDOCBP T="13APN1.sgm" D="1">E7-6991</FRDOCBP>
                    <FRDOCBP T="13APN1.sgm" D="0">E7-6992</FRDOCBP>
                </DOCENT>
                <SJ>National Vaccine Injury Compensation Program:</SJ>
                <SJDENT>
                    <SJDOC>Petitions received; list, </SJDOC>
                    <PGS>18662-18664</PGS>
                    <FRDOCBP T="13APN1.sgm" D="2">E7-6984</FRDOCBP>
                </SJDENT>
            </CAT>
        </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>
        </AGCY>
        <AGCY>
            <EAR>Housing</EAR>
            <HD>Housing and Urban Development Department</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Grants and cooperative agreements; availability, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Homeless assistance; excess and surplus Federal properties, </SJDOC>
                    <PGS>18665</PGS>
                    <FRDOCBP T="13APN1.sgm" D="0">E7-6768</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Interior</EAR>
            <HD>Interior Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Land Management Bureau</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Minerals Management Service</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>IRS</EAR>
            <HD>Internal Revenue Service</HD>
            <CAT>
                <HD>RULES</HD>
                <SJ>Income taxes:</SJ>
                <SUBSJ>Corporate reorganizations; additional distributions guidance</SUBSJ>
                <SSJDENT>
                    <SUBSJDOC>Correction, </SUBSJDOC>
                    <PGS>18575-18576</PGS>
                    <FRDOCBP T="13APR1.sgm" D="1">E7-6979</FRDOCBP>
                </SSJDENT>
            </CAT>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency information collection activities; proposals, submissions, and approvals, </DOC>
                    <PGS>18747-18750</PGS>
                    <FRDOCBP T="13APN1.sgm" D="1">E7-6973</FRDOCBP>
                    <FRDOCBP T="13APN1.sgm" D="0">E7-6974</FRDOCBP>
                    <FRDOCBP T="13APN1.sgm" D="1">E7-6975</FRDOCBP>
                    <FRDOCBP T="13APN1.sgm" D="1">E7-6976</FRDOCBP>
                    <FRDOCBP T="13APN1.sgm" D="0">E7-6977</FRDOCBP>
                </DOCENT>
                <SJ>Committees; establishment, renewal, termination, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Internal Revenue Service Advisory Council, </SJDOC>
                    <PGS>18750-18751</PGS>
                    <FRDOCBP T="13APN1.sgm" D="1">E7-6978</FRDOCBP>
                </SJDENT>
                <SJ>Meetings:</SJ>
                <SJDENT>
                    <SJDOC>Taxpayer Advocacy Panels, </SJDOC>
                    <FRDOCBP T="13APN1.sgm" D="0">E7-6967</FRDOCBP>
                    <PGS>18751-18752</PGS>
                    <FRDOCBP T="13APN1.sgm" D="1">E7-6968</FRDOCBP>
                    <FRDOCBP T="13APN1.sgm" D="0">E7-6969</FRDOCBP>
                    <FRDOCBP T="13APN1.sgm" D="0">E7-6971</FRDOCBP>
                    <FRDOCBP T="13APN1.sgm" D="0">E7-6972</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>International</EAR>
            <PRTPAGE P="v"/>
            <HD>International Trade Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Antidumping:</SJ>
                <SUBSJ>Forged stainless steel flanges from—</SUBSJ>
                <SSJDENT>
                    <SUBSJDOC>India, </SUBSJDOC>
                    <PGS>18628-18629</PGS>
                    <FRDOCBP T="13APN1.sgm" D="1">E7-7082</FRDOCBP>
                </SSJDENT>
                <SUBSJ>Petroleum wax candles from—</SUBSJ>
                <SSJDENT>
                    <SUBSJDOC>China, </SUBSJDOC>
                    <PGS>18629-18630</PGS>
                    <FRDOCBP T="13APN1.sgm" D="1">E7-7051</FRDOCBP>
                </SSJDENT>
                <SUBSJ>Steel concrete reinforcing bar from—</SUBSJ>
                <SSJDENT>
                    <SUBSJDOC>Korea, </SUBSJDOC>
                    <PGS>18630-18632</PGS>
                    <FRDOCBP T="13APN1.sgm" D="2">E7-7084</FRDOCBP>
                </SSJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>International</EAR>
            <HD>International Trade Commission</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Meetings; Sunshine Act, </DOC>
                    <PGS>18667-18668</PGS>
                    <FRDOCBP T="13APN1.sgm" D="1">07-1868</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Justice</EAR>
            <HD>Justice Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Drug Enforcement Administration</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Justice Programs Office</P>
            </SEE>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency information collection activities; proposals, submissions, and approvals, </DOC>
                    <PGS>18668</PGS>
                    <FRDOCBP T="13APN1.sgm" D="0">07-1857</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Justice</EAR>
            <HD>Justice Programs Office</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency information collection activities; proposals, submissions, and approvals, </DOC>
                    <PGS>18669-18670</PGS>
                    <FRDOCBP T="13APN1.sgm" D="1">E7-7058</FRDOCBP>
                    <FRDOCBP T="13APN1.sgm" D="0">E7-7083</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Labor</EAR>
            <HD>Labor Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Occupational Safety and Health Administration</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Veterans Employment and Training Service</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>Land</EAR>
            <HD>Land Management Bureau</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Recreation management restrictions, etc:</SJ>
                <SJDENT>
                    <SJDOC>Nye County, NV; temporary closure to target shooting, </SJDOC>
                    <PGS>18665-18666</PGS>
                    <FRDOCBP T="13APN1.sgm" D="1">E7-7023</FRDOCBP>
                </SJDENT>
                <SJ>Survey plat filings:</SJ>
                <SJDENT>
                    <SJDOC>Nevada, </SJDOC>
                    <PGS>18666</PGS>
                    <FRDOCBP T="13APN1.sgm" D="0">E7-6981</FRDOCBP>
                </SJDENT>
                <SJ>Withdrawal and reservation of lands:</SJ>
                <SJDENT>
                    <SJDOC>Nevada, </SJDOC>
                    <PGS>18666-18667</PGS>
                    <FRDOCBP T="13APN1.sgm" D="1">E7-7200</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Legal</EAR>
            <HD>Legal Services Corporation</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Grants and cooperative agreements; availability, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Competitive grant funds (2008 CY), </SJDOC>
                    <PGS>18690</PGS>
                    <FRDOCBP T="13APN1.sgm" D="0">E7-7012</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Minerals</EAR>
            <HD>Minerals Management Service</HD>
            <CAT>
                <HD>RULES</HD>
                <SJ>Outer Continental Shelf; oil, gas, and sulphur operations:</SJ>
                <SJDENT>
                    <SJDOC>Marine mammals and threatened and endangered species protection; lessee plans and information submission requirements, </SJDOC>
                    <PGS>18577-18585</PGS>
                    <FRDOCBP T="13APR1.sgm" D="8">E7-7028</FRDOCBP>
                </SJDENT>
            </CAT>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Environmental statements; availability, etc.:</SJ>
                <SUBSJ>Western and Central Gulf of Mexico OCS—</SUBSJ>
                <SSJDENT>
                    <SUBSJDOC>Oil and gas lease sales, </SUBSJDOC>
                    <PGS>18667</PGS>
                    <FRDOCBP T="13APN1.sgm" D="0">E7-7031</FRDOCBP>
                </SSJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>National Institute</EAR>
            <HD>National Institute of Standards and Technology</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Meetings:</SJ>
                <SJDENT>
                    <SJDOC>Advanced Technology Program Advisory Committee, </SJDOC>
                    <PGS>18632</PGS>
                    <FRDOCBP T="13APN1.sgm" D="0">E7-7075</FRDOCBP>
                </SJDENT>
                <SJ>National Fire Codes:</SJ>
                <SJDENT>
                    <SJDOC>Fire safety codes and standards, </SJDOC>
                    <PGS>18632-18634</PGS>
                    <FRDOCBP T="13APN1.sgm" D="2">E7-7078</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Technical committee reports, </SJDOC>
                    <PGS>18634-18636</PGS>
                    <FRDOCBP T="13APN1.sgm" D="2">E7-7076</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>Pacific cod, </SUBSJDOC>
                    <PGS>18595-18596</PGS>
                    <FRDOCBP T="13APR1.sgm" D="1">E7-7038</FRDOCBP>
                </SSJDENT>
                <SSJDENT>
                    <SUBSJDOC>Rock sole, flathead sole, and other flatfish, </SUBSJDOC>
                    <PGS>18595</PGS>
                    <FRDOCBP T="13APR1.sgm" D="0">07-1823</FRDOCBP>
                </SSJDENT>
                <SUBSJ>Caribbean, Gulf, and South Atlantic fisheries—</SUBSJ>
                <SSJDENT>
                    <SUBSJDOC>Tilefish, </SUBSJDOC>
                    <PGS>18593-18594</PGS>
                    <FRDOCBP T="13APR1.sgm" D="1">E7-6965</FRDOCBP>
                </SSJDENT>
                <SUBSJ>Northeastern United States fisheries—</SUBSJ>
                <SSJDENT>
                    <SUBSJDOC>Atlantic mackerel, squid, and butterfish, </SUBSJDOC>
                    <PGS>18594</PGS>
                    <FRDOCBP T="13APR1.sgm" D="0">07-1824</FRDOCBP>
                </SSJDENT>
            </CAT>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <SJ>Endangered and threatened species:</SJ>
                <SUBSJ>Findings on petitions, etc.—</SUBSJ>
                <SSJDENT>
                    <SUBSJDOC>Black abalone, </SUBSJDOC>
                    <PGS>18616-18619</PGS>
                    <FRDOCBP T="13APP1.sgm" D="3">E7-6966</FRDOCBP>
                </SSJDENT>
            </CAT>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Endangered and threatened species permit applications, determinations, etc., </DOC>
                    <PGS>18636</PGS>
                    <FRDOCBP T="13APN1.sgm" D="0">E7-6970</FRDOCBP>
                </DOCENT>
                <SJ>Meetings:</SJ>
                <SJDENT>
                    <SJDOC>Gulf of Mexico Fishery Management Council, </SJDOC>
                    <PGS>18636-18637</PGS>
                    <FRDOCBP T="13APN1.sgm" D="0">E7-6995</FRDOCBP>
                    <FRDOCBP T="13APN1.sgm" D="0">E7-6996</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>National Science</EAR>
            <HD>National Science Foundation</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Meetings:</SJ>
                <SJDENT>
                    <SJDOC>International Science and Engineering Advisory Committee, </SJDOC>
                    <PGS>18690-18691</PGS>
                    <FRDOCBP T="13APN1.sgm" D="1">E7-7011</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Nuclear</EAR>
            <HD>Nuclear Regulatory Commission</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Environmental statements; availability, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Pacific Gas &amp; Electric Co., </SJDOC>
                    <PGS>18691-18692</PGS>
                    <FRDOCBP T="13APN1.sgm" D="1">E7-7074</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Occupational</EAR>
            <HD>Occupational Safety and Health Administration</HD>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <SJ>Occupational safety and health standards:</SJ>
                <SJDENT>
                    <SJDOC>Hazardous materials; explosives and blasting agents, </SJDOC>
                    <PGS>18792-18845</PGS>
                    <FRDOCBP T="13APP2.sgm" D="53">E7-6607</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Pension</EAR>
            <HD>Pension Benefit Guaranty Corporation</HD>
            <CAT>
                <HD>RULES</HD>
                <SJ>Single employer plans:</SJ>
                <SUBSJ>Allocation of assets—</SUBSJ>
                <SSJDENT>
                    <SUBSJDOC>Interest assumptions for valuing and paying benefits, </SUBSJDOC>
                    <PGS>18576-18577</PGS>
                    <FRDOCBP T="13APR1.sgm" D="1">E7-7071</FRDOCBP>
                </SSJDENT>
            </CAT>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency information collection activities; proposals, submissions, and approvals, </DOC>
                    <PGS>18692-18693</PGS>
                    <FRDOCBP T="13APN1.sgm" D="1">E7-7126</FRDOCBP>
                </DOCENT>
                <SJ>Single-employer and multiemployer plans:</SJ>
                <SJDENT>
                    <SJDOC>Interest rates and assumptions, </SJDOC>
                    <PGS>18693-18694</PGS>
                    <FRDOCBP T="13APN1.sgm" D="1">E7-7097</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Presidential</EAR>
            <HD>Presidential Documents</HD>
            <CAT>
                <HD>ADMINISTRATIVE ORDERS</HD>
                <SJ>Government agencies and employees:</SJ>
                <SJDENT>
                    <SJDOC>National Intelligence, Office of the Director of; assignment of functions relating to the information sharing environment (Memorandum of April 10, 2007), </SJDOC>
                    <PGS>18561</PGS>
                      
                    <FRDOCBP T="13APO0.sgm" D="0">07-1875</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Railroad</EAR>
            <HD>Railroad Retirement Board</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency information collection activities; proposals, submissions, and approvals, </DOC>
                    <PGS>18694</PGS>
                    <FRDOCBP T="13APN1.sgm" D="0">E7-7001</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Rural</EAR>
            <HD>Rural Housing Service</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency information collection activities; proposals, submissions, and approvals, </DOC>
                    <PGS>18625-18626</PGS>
                    <FRDOCBP T="13APN1.sgm" D="1">E7-7062</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>SEC</EAR>
            <PRTPAGE P="vi"/>
            <HD>Securities and Exchange Commission</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency information collection activities; proposals, submissions, and approvals, </DOC>
                    <PGS>18694-18695</PGS>
                    <FRDOCBP T="13APN1.sgm" D="1">E7-7006</FRDOCBP>
                </DOCENT>
                <SJ>Self-regulatory organizations; proposed rule changes:</SJ>
                <SJDENT>
                    <SJDOC>American Stock Exchange LLC, </SJDOC>
                    <PGS>18695-18700</PGS>
                    <FRDOCBP T="13APN1.sgm" D="3">E7-6960</FRDOCBP>
                    <FRDOCBP T="13APN1.sgm" D="2">E7-7054</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Chicago Stock Exchange, Inc., </SJDOC>
                    <PGS>18700-18701</PGS>
                    <FRDOCBP T="13APN1.sgm" D="1">E7-6963</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>International Securities Exchange LLC, </SJDOC>
                    <PGS>18701-18703</PGS>
                    <FRDOCBP T="13APN1.sgm" D="2">E7-6961</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>National Association of Securities Dealers, Inc., </SJDOC>
                    <PGS>18703-18707</PGS>
                    <FRDOCBP T="13APN1.sgm" D="4">E7-7008</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>New York Stock Exchange LLC, </SJDOC>
                    <PGS>18707-18716</PGS>
                    <FRDOCBP T="13APN1.sgm" D="3">E7-6962</FRDOCBP>
                    <FRDOCBP T="13APN1.sgm" D="2">E7-7055</FRDOCBP>
                    <FRDOCBP T="13APN1.sgm" D="4">E7-7056</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>NYSE Arca, Inc., </SJDOC>
                    <PGS>18716-18718</PGS>
                    <FRDOCBP T="13APN1.sgm" D="2">E7-6959</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Philadelphia Stock Exchange, Inc., </SJDOC>
                    <PGS>18718-18719</PGS>
                    <FRDOCBP T="13APN1.sgm" D="1">E7-7007</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>SBA</EAR>
            <HD>Small Business Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Disaster loan areas:</SJ>
                <SJDENT>
                    <SJDOC>Washington, </SJDOC>
                    <PGS>18719</PGS>
                    <FRDOCBP T="13APN1.sgm" D="0">E7-7029</FRDOCBP>
                </SJDENT>
                <SJ>Meetings:</SJ>
                <SJDENT>
                    <SJDOC>Audit and Financial Management Advisory Committee; canceled, </SJDOC>
                    <PGS>18719</PGS>
                    <FRDOCBP T="13APN1.sgm" D="0">E7-7030</FRDOCBP>
                </SJDENT>
            </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>
                    <FRDOCBP T="13APN1.sgm" D="0">E7-7043</FRDOCBP>
                    <PGS>18720-18722</PGS>
                    <FRDOCBP T="13APN1.sgm" D="1">E7-7045</FRDOCBP>
                    <FRDOCBP T="13APN1.sgm" D="0">E7-7046</FRDOCBP>
                    <FRDOCBP T="13APN1.sgm" D="1">E7-7047</FRDOCBP>
                </DOCENT>
                <SJ>Culturally significant objects imported for exhibition:</SJ>
                <SJDENT>
                    <SJDOC>Herculaneum Women and the Origins of Archaeology, </SJDOC>
                    <PGS>18722</PGS>
                    <FRDOCBP T="13APN1.sgm" D="0">E7-7037</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Treasures from the Hermitage and Guggenheim Collections, </SJDOC>
                    <PGS>18722</PGS>
                    <FRDOCBP T="13APN1.sgm" D="0">E7-7040</FRDOCBP>
                </SJDENT>
                <SJ>Meetings:</SJ>
                <SJDENT>
                    <SJDOC>International Telecommunication Advisory Committee, </SJDOC>
                    <PGS>18722</PGS>
                    <FRDOCBP T="13APN1.sgm" D="0">E7-7036</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>TVA</EAR>
            <HD>Tennessee Valley Authority</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency information collection activities; proposals, submissions, and approvals, </DOC>
                    <PGS>18723</PGS>
                    <FRDOCBP T="13APN1.sgm" D="0">E7-6980</FRDOCBP>
                </DOCENT>
            </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> Federal Highway Administration</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Federal Motor Carrier Safety Administration</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Federal Railroad Administration</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Federal Transit Administration</P>
            </SEE>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <SJ>Individuals with disabilities:</SJ>
                <SJDENT>
                    <SJDOC>Passenger vessels; accessibility guidelines, </SJDOC>
                    <PGS>18614-18615</PGS>
                    <FRDOCBP T="13APP1.sgm" D="1">E7-6941</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Treasury</EAR>
            <HD>Treasury Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Internal Revenue Service</P>
            </SEE>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency information collection activities; proposals, submissions, and approvals, </DOC>
                    <PGS>18746-18747</PGS>
                    <FRDOCBP T="13APN1.sgm" D="1">E7-7033</FRDOCBP>
                </DOCENT>
                <SJ>Meetings:</SJ>
                <SJDENT>
                    <SJDOC>Debt Management Advisory Committee, </SJDOC>
                    <PGS>18747</PGS>
                    <FRDOCBP T="13APN1.sgm" D="0">07-1826</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Veterans</EAR>
            <HD>Veterans Affairs Department</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Privacy Act: systems of records, </DOC>
                    <PGS>18752-18756</PGS>
                    <FRDOCBP T="13APN1.sgm" D="4">E7-6982</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Veterans</EAR>
            <HD>Veterans Employment and Training Service</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Grants and cooperative agreements; availability, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Homeless Veterans’ Reintegration Program; National Technical Assistance Center development, </SJDOC>
                    <PGS>18670-18678</PGS>
                    <FRDOCBP T="13APN1.sgm" D="8">E7-7027</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Urban and Non-Urban Homeless Veterans’ Reintegration Program (2007 PY), </SJDOC>
                    <PGS>18678-18690</PGS>
                    <FRDOCBP T="13APN1.sgm" D="12">E7-7024</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <PTS>
            <HD SOURCE="HED">Separate Parts In This Issue</HD>
            <HD>Part II</HD>
            <DOCENT>
                <DOC>Defense Department, </DOC>
                <PGS>18758-18790</PGS>
                <FRDOCBP T="13APR2.sgm" D="32">E7-6118</FRDOCBP>
            </DOCENT>
            <HD>Part III</HD>
            <DOCENT>
                <DOC>Labor Department, Occupational Safety and Health Administration, </DOC>
                <PGS>18792-18845</PGS>
                <FRDOCBP T="13APP2.sgm" D="53">E7-6607</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>72</VOL>
    <NO>71</NO>
    <DATE>Friday, April 13, 2007</DATE>
    <UNITNAME>Rules and Regulations</UNITNAME>
    <RULES>
        <RULE>
            <PREAMB>
                <PRTPAGE P="18563"/>
                <AGENCY TYPE="F">DEPARTMENT OF TRANSPORTATION </AGENCY>
                <SUBAGY>Federal Aviation Administration </SUBAGY>
                <CFR>14 CFR Part 39 </CFR>
                <DEPDOC>[Docket No. FAA-2007-27013; Directorate Identifier 2006-NM-236-AD; Amendment 39-15022; AD 2007-08-05] </DEPDOC>
                <RIN>RIN 2120-AA64 </RIN>
                <SUBJECT>Airworthiness Directives; Airbus Model A330-200, A330-300, A340-200, and A340-300 Series Airplanes </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration (FAA), Department of Transportation (DOT). </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>We are adopting a new airworthiness directive (AD) for the products listed above. This AD results from mandatory continuing airworthiness information (MCAI) issued by an airworthiness authority of another country to identify and correct an unsafe condition on an aviation product. The MCAI describes the unsafe condition as fatigue damage with a crack propagation through the fastener line of the wing shroud box bottom panel, resulting in panel detachment and potential injuries to persons on the ground. We are issuing this AD to require actions to correct the unsafe condition on these products. </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>This AD becomes effective May 18, 2007. </P>
                    <P>The Director of the Federal Register approved the incorporation by reference of certain publications listed in this AD as of May 18, 2007. </P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        You may examine the AD docket on the Internet at 
                        <E T="03">http://dms.dot.gov</E>
                         or in person at the Docket Management Facility, U.S. Department of Transportation, 400 Seventh Street, SW., Nassif Building, Room PL-401, Washington, DC. 
                    </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 98057-3356; telephone (425) 227-2797; fax (425) 227-1149. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Discussion </HD>
                <P>
                    The FAA is implementing a new process for streamlining the issuance of ADs related to MCAI. This streamlined process will allow us to adopt MCAI safety requirements in a more efficient manner and will reduce safety risks to the public. This process continues to allow all FAA AD issuance processes to meet legal, economic, Administrative Procedure Act, and 
                    <E T="04">Federal Register</E>
                     requirements. We also continue to meet our technical decision-making responsibilities to identify and correct unsafe conditions on U.S.-certificated products. 
                </P>
                <P>This AD references the MCAI and related service information that we considered in forming the engineering basis to correct the unsafe condition. The AD contains text copied from the MCAI and for this reason might not follow our plain language principles. </P>
                <P>
                    We issued a notice of proposed rulemaking (NPRM) to amend 14 CFR part 39 to include an AD that would apply to the specified products. That NPRM was published in the 
                    <E T="04">Federal Register</E>
                     on January 26, 2007 (72 FR 3771). That NPRM proposed to require performing a one-time detailed inspection of the shroud box bottom panel for cracks, fasteners missing or loose, damage, and marks; and applying all applicable corrective actions. The MCAI states that an A330 operator has reported a shroud box bottom panel missing during routine inspection. The same panel detached from an A330 aircraft during take-off, causing damages to the surrounding structure and to the Trimmable Horizontal Stabilizer (THS) tip fairing. Preliminary inspection has shown that the blind rivets used to attach the panel worked loose causing the panel to suffer fatigue damage with a crack propagation through the fastener line resulting in panel detachment. To avoid potential injuries to persons on ground, the MCAI mandates a one time detailed visual inspection of the shroud box bottom panel for cracks in the panel and for missing and loose fasteners, and repair if necessary. 
                </P>
                <HD SOURCE="HD1">Comments </HD>
                <P>We gave the public the opportunity to participate in developing this AD. We received no comments on the NPRM or on the determination of the cost to the public. </P>
                <HD SOURCE="HD1">Clarification of Service Bulletin Reference </HD>
                <P>The “Relevant Service Information” section of the NPRM, and paragraph (g) of the NPRM refer to Airbus Service Bulletin A330-57A3092, February 3, 2006, as one of the appropriate sources of service information to do the actions in the NPRM. However, in paragraph (e) of the NPRM, we inadvertently referred to Airbus Service Bulletin A330-57A3792, dated February 3, 2006. We have revised paragraph (e) of this AD accordingly. </P>
                <HD SOURCE="HD1">Conclusion </HD>
                <P>We reviewed the available data, and determined that air safety and the public interest require adopting the AD with the change described previously. We determined that this change will not increase the economic burden on any operator or increase the scope of the AD. </P>
                <HD SOURCE="HD1">Differences Between This AD and the MCAI or Service Information </HD>
                <P>We have reviewed the MCAI and related service information and, in general, agree with their substance. But we might have found it necessary to use different words from those in the MCAI to ensure the AD is clear for U.S. operators and is enforceable in a U.S. court of law. In making these changes, we do not intend to differ substantively from the information provided in the MCAI and related service information. </P>
                <P>We might also have required different actions in this AD from those in the MCAI in order to follow our FAA policies. Any such differences are described in a separate paragraph of the AD. These requirements, if any, take precedence over the actions copied from the MCAI. </P>
                <HD SOURCE="HD1">Costs of Compliance </HD>
                <P>
                    We estimate that this AD will affect 27 products of U.S. registry. We also estimate that it will take about 2 work-hours per product to comply with this AD. The average labor rate is $80 per work-hour. Based on these figures, we 
                    <PRTPAGE P="18564"/>
                    estimate the cost of this AD to the U.S. operators to be $4,320, or $160 per product. 
                </P>
                <HD SOURCE="HD1">Authority for This Rulemaking </HD>
                <P>Title 49 of the United States Code specifies the FAA's authority to issue rules on aviation safety. Subtitle I, section 106, describes the authority of the FAA Administrator. “Subtitle VII: Aviation Programs,” describes in more detail the scope of the Agency's authority. </P>
                <P>We are issuing this rulemaking under the authority described in “Subtitle VII, Part A, Subpart III, Section 44701: General requirements.” Under that section, Congress charges the FAA with promoting safe flight of civil aircraft in air commerce by prescribing regulations for practices, methods, and procedures the Administrator finds necessary for safety in air commerce. This regulation is within the scope of that authority because it addresses an unsafe condition that is likely to exist or develop on products identified in this rulemaking action. </P>
                <HD SOURCE="HD1">Regulatory Findings </HD>
                <P>We determined that this AD will not have federalism implications under Executive Order 13132. This AD will 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>
                <P>For the reasons discussed above, I certify that this AD:</P>
                <P>(1) Is not a “significant regulatory action” under Executive Order 12866; </P>
                <P>(2) Is not a “significant rule” under 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 regulatory evaluation of the estimated costs to comply with this AD and placed it in the AD Docket. </P>
                <HD SOURCE="HD1">Examining the AD Docket </HD>
                <P>
                    You may examine the AD docket on the Internet at 
                    <E T="03">http://dms.dot.gov;</E>
                     or in person at the Docket Management Facility between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays. The AD docket contains the NPRM, the regulatory evaluation, any comments received, and other information. The street address for the Docket Office (telephone (800) 647-5227) is in the 
                    <E T="02">ADDRESSES</E>
                     section. Comments will be available in the AD docket shortly after receipt. 
                </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 14 CFR Part 39 </HD>
                    <P>Air transportation, Aircraft, Aviation safety, Incorporation by reference, Safety.</P>
                </LSTSUB>
                <REGTEXT TITLE="14" PART="39">
                    <HD SOURCE="HD1">Adoption of the Amendment </HD>
                    <AMDPAR>Accordingly, under the authority delegated to me by the Administrator, the FAA amends 14 CFR part 39 as follows: </AMDPAR>
                    <PART>
                        <HD SOURCE="HED">PART 39—AIRWORTHINESS DIRECTIVES </HD>
                    </PART>
                    <AMDPAR>1. The authority citation for part 39 continues to read as follows: </AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>49 U.S.C. 106(g), 40113, 44701. </P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="14" PART="39">
                    <SECTION>
                        <SECTNO>§ 39.13 </SECTNO>
                        <SUBJECT>[Amended] </SUBJECT>
                    </SECTION>
                    <AMDPAR>2. The FAA amends § 39.13 by adding the following new AD: </AMDPAR>
                    <EXTRACT>
                        <FP SOURCE="FP-2">
                            <E T="04">2007-08-05 Airbus:</E>
                             Amendment 39-15022. Docket No. FAA-2007-27013; Directorate Identifier 2006-NM-236-AD. 
                        </FP>
                        <HD SOURCE="HD1">Effective Date </HD>
                        <P>(a) This airworthiness directive (AD) becomes effective May 18, 2007. </P>
                        <HD SOURCE="HD1">Affected ADs </HD>
                        <P>(b) None. </P>
                        <HD SOURCE="HD1">Applicability </HD>
                        <P>(c) This AD applies to Airbus Model A330-200, A330-300, A340-200, and A340-300 series airplanes, all certified models, all serial numbers, certificated in any category, on which Airbus Modification 42061 or 46077 or 53604 has been embodied in production and delivered before December 31, 2005. </P>
                        <HD SOURCE="HD1">Reason </HD>
                        <P>(d) The mandatory continuing airworthiness information (MCAI) states that an A330 operator has reported a shroud box bottom panel missing during routine inspection. The same panel detached from an A330 aircraft during take-off, causing damages to the surrounding structure and to the Trimmable Horizontal Stabilizer (THS) tip fairing. Preliminary inspection has shown that the blind rivets used to attach the panel worked loose causing the panel to suffer fatigue damage with a crack propagation through the fastener line resulting in panel detachment. To avoid potential injuries to persons on ground, the MCAI requires a one time detailed visual inspection of the shroud box bottom panel for cracks in the panel and for missing and loose fasteners, and applicable repairs. </P>
                        <HD SOURCE="HD1">Actions and Compliance </HD>
                        <P>(e) Unless already done, do the following actions. Within the threshold specified in paragraphs (e)(1) and (e)(2) of this AD and in accordance with the instructions of Airbus Service Bulletin A330-57A3092, dated February 3, 2006; or Airbus Service Bulletin A340-57A4101, dated February 3, 2006; as applicable: Perform a one-time detailed inspection of the shroud box bottom panel for cracks, fasteners missing or loose, damage, and marks; and apply all applicable corrective actions. Do applicable corrective actions before further flight. The inspections results, whatever they are, must be reported to Airbus. </P>
                        <P>(1) For Model A330 airplanes: Whichever occurs later between paragraphs (e)(1)(i) and (e)(1)(ii) of this AD. </P>
                        <P>(i) Prior to the accumulation of 1,200 flight cycles or 2,400 flight hours from the first flight of the aircraft, whichever occurs first. </P>
                        <P>(ii) Within 6 months or 1,200 flight hours, whichever occurs first, following the effective date of this AD. </P>
                        <P>(2) For Model A340-200 and A340-300 series airplanes: Whichever occurs later between paragraphs (e)(2)(i) and (e)(2)(ii) of this AD. </P>
                        <P>(i) Prior to the accumulation of 1,200 flight cycles or 4,800 flight hours from the first flight of the aircraft, whichever occurs first. </P>
                        <P>(ii) Within 6 months or 2,400 flight hours, whichever occurs first, following the effective date of this AD. </P>
                        <HD SOURCE="HD1">Other FAA AD Provisions </HD>
                        <P>(f) The following provisions also apply to this AD: </P>
                        <P>(1) Alternative Methods of Compliance (AMOCs): The Manager, International Branch, ANM-116, Transport Airplane Directorate, FAA, Attn: Tim Backman, Aerospace Engineer, 1601 Lind Avenue, SW., Renton, Washington 98057-3356, has the authority to approve AMOCs for this AD, if requested using the procedures found in 14 CFR 39.19. Before using any AMOC approved in accordance with § 39.19 on any airplane to which the AMOC applies, notify the appropriate principal inspector in the FAA Flight Standards Certificate Holding District Office. </P>
                        <P>(2) Airworthy Product: For any requirement in this AD to obtain corrective actions from a manufacturer or other source, use these actions if they are FAA-approved. Corrective actions are considered FAA-approved if they are approved by the State of Design Authority (or their delegated agent). You are required to assure the product is airworthy before it is returned to service. </P>
                        <P>(3) Reporting Requirements: For any reporting requirement in this AD, under the provisions of the Paperwork Reduction Act, the Office of Management and Budget (OMB) has approved the information collection requirements and has assigned OMB Control Number 2120-0056. </P>
                        <HD SOURCE="HD1">Related Information </HD>
                        <P>(g) Refer to MCAI European Aviation Safety Agency Airworthiness Directive 2006-0107, dated May 12, 2006, and Airbus Service Bulletins A330-57A3092 and A340-57A4101, both dated February 3, 2006, for related information. </P>
                        <HD SOURCE="HD1">Material Incorporated by Reference </HD>
                        <P>(h) You must use Airbus Service Bulletin A330-57A3092, dated February 3, 2006; or Airbus Service Bulletin A340-57A4101, dated February 3, 2006; as applicable, to do the actions required by this AD, unless the AD specifies otherwise. </P>
                        <P>
                            (1) The Director of the Federal Register approved the incorporation by reference of 
                            <PRTPAGE P="18565"/>
                            this service information under 5 U.S.C. 552(a) and 1 CFR part 51. 
                        </P>
                        <P>(2) For service information identified in this AD, contact Airbus, 1 Rond Point Maurice Bellonte, 31707 Blagnac Cedex, France. </P>
                        <P>
                            (3) You may review copies at the FAA, Transport Airplane Directorate, 1601 Lind Avenue, SW., Renton, Washington; or at the National Archives and Records Administration (NARA). For information on the availability of this material at NARA, call 202-741-6030, or go to: 
                            <E T="03">http://www.archives.gov/federal-register/cfr/ibr-locations.html.</E>
                        </P>
                    </EXTRACT>
                </REGTEXT>
                <SIG>
                    <DATED>Issued in Renton, Washington, on April 4, 2007. </DATED>
                    <NAME>Stephen P. Boyd, </NAME>
                    <TITLE>Acting Manager, Transport Airplane Directorate, Aircraft Certification Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. E7-6931 Filed 4-12-07; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4910-13-P </BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION </AGENCY>
                <SUBAGY>Federal Aviation Administration </SUBAGY>
                <CFR>14 CFR Part 39 </CFR>
                <DEPDOC>[Docket No. FAA-2007-27070 Directorate Identifier 2007-CE-003-AD; Amendment 39-15023; AD 2007-08-06] </DEPDOC>
                <RIN>RIN 2120-AA64 </RIN>
                <SUBJECT>Airworthiness Directives; British Aerospace Regional Aircraft Models HP.137 Jetstream Mk.1, Jetstream Series 200, Jetstream Series 3101, and Jetstream Model 3201 Airplanes </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration (FAA), Department of Transportation (DOT). </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>We are adopting a new airworthiness directive (AD) for the products listed above. This AD results from mandatory continuing airworthiness information (MCAI) issued by an aviation authority of another country to identify and correct an unsafe condition on an aviation product. The MCAI describes the unsafe condition as: </P>
                    <EXTRACT>
                        <P>This Airworthiness Directive * * * is published in order to maintain the structural integrity of the applicable aircraft. The Service Bulletin provides life limits for critical landing gear components. Failure of such items could lead to unsafe conditions.</P>
                    </EXTRACT>
                </SUM>
                <FP>We are issuing this AD to require actions to correct the unsafe condition on these products. </FP>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>This AD becomes effective May 18, 2007. </P>
                    <P>The Director of the Federal Register approved the incorporation by reference of certain publications listed in this AD as of May 18, 2007. </P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        You may examine the AD docket on the Internet at 
                        <E T="03">http://dms.dot.gov</E>
                         or in person at the Docket Management Facility, U.S. Department of Transportation, 400 Seventh Street, SW., Nassif Building, Room PL-401, Washington, DC. 
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Taylor Martin, Aerospace Engineer, FAA, Small Airplane Directorate, 901 Locust, Room 301, Kansas City, Missouri 64106; telephone: (816) 329-4138; fax: (816) 329-4090. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Streamlined Issuance of AD </HD>
                <P>
                    The FAA is implementing a new process for streamlining the issuance of ADs related to MCAI. The streamlined process will allow us to adopt MCAI safety requirements in a more efficient manner and will reduce safety risks to the public. This process continues to follow all FAA AD issuance processes to meet legal, economic, Administrative Procedure Act, and 
                    <E T="04">Federal Register</E>
                     requirements. We also continue to meet our technical decision-making responsibilities to identify and correct unsafe conditions on U.S.-certificated products. 
                </P>
                <P>This AD references the MCAI and related service information that we considered in forming the engineering basis to correct the unsafe condition. The AD contains text copied from the MCAI and for this reason might not follow our plain language principles. </P>
                <HD SOURCE="HD1">Discussion </HD>
                <P>
                    We issued a notice of proposed rulemaking (NPRM) to amend 14 CFR part 39 to include an AD that would apply to the specified products. That NPRM was published in the 
                    <E T="04">Federal Register</E>
                     on February 12, 2007 (72 FR 6500). That NPRM proposed to correct an unsafe condition for the specified products. The MCAI states: 
                </P>
                <EXTRACT>
                    <P>This Airworthiness Directive * * * is published in order to maintain the structural integrity of the applicable aircraft. The Service Bulletin provides life limits for critical landing gear components. Failure of such items could lead to unsafe conditions.</P>
                </EXTRACT>
                <P>The MCAI requires: </P>
                <EXTRACT>
                    <P>From the effective date of this AD, it is mandatory to comply with the requirements given in Jetstream Series 3100 and 3200 Service Bulletin 32-JA981042 Rev 5. Landing Gear—Main and Nose Landing Gears—To introduce life limitations and provide means of establishing total flight cycles since new for critical components * * *</P>
                </EXTRACT>
                <HD SOURCE="HD1">Comments </HD>
                <P>We gave the public the opportunity to participate in developing this AD. We received no comments on the NPRM or on the determination of the cost to the public. </P>
                <HD SOURCE="HD1">Conclusion </HD>
                <P>We reviewed the available data and determined that air safety and the public interest require adopting the AD as proposed. </P>
                <HD SOURCE="HD1">Differences Between This AD and the MCAI or Service Information </HD>
                <P>We have reviewed the MCAI and related service information and, in general, agree with their substance. But we might have found it necessary to use different words from those in the MCAI to ensure the AD is clear for U.S. operators and is enforceable. In making these changes, we do not intend to differ substantively from the information provided in the MCAI and related service information. </P>
                <P>
                    We might also have required different actions in this AD from those in the MCAI in order to follow FAA policies. Any such differences are highlighted in a 
                    <E T="04">Note</E>
                     within the AD. 
                </P>
                <HD SOURCE="HD1">Costs of Compliance </HD>
                <P>We estimate that this AD will affect 149 products of U.S. registry. We also estimate that it will take about 2 work-hours per product to comply with basic requirements of this AD. The average labor rate is $80 per work-hour. Based on these figures, we estimate the cost of this AD to the U.S. operators to be $23,840, or $160 per product. </P>
                <HD SOURCE="HD1">Authority for This Rulemaking </HD>
                <P>Title 49 of the United States Code specifies the FAA's authority to issue rules on aviation safety. Subtitle I, section 106, describes the authority of the FAA Administrator. “Subtitle VII: Aviation Programs,” describes in more detail the scope of the Agency's authority. </P>
                <P>We are issuing this rulemaking under the authority described in “Subtitle VII, Part A, Subpart III, Section 44701: General requirements.” Under that section, Congress charges the FAA with promoting safe flight of civil aircraft in air commerce by prescribing regulations for practices, methods, and procedures the Administrator finds necessary for safety in air commerce. This regulation is within the scope of that authority because it addresses an unsafe condition that is likely to exist or develop on products identified in this rulemaking action. </P>
                <HD SOURCE="HD1">Regulatory Findings </HD>
                <P>
                    We determined that this AD will not have federalism implications under Executive Order 13132. This AD will not have a substantial direct effect on 
                    <PRTPAGE P="18566"/>
                    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>
                <P>For the reasons discussed above, I certify this AD:</P>
                <P>(1) Is not a “significant regulatory action” under Executive Order 12866; </P>
                <P>(2) Is not a “significant rule” under 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 regulatory evaluation of the estimated costs to comply with this AD and placed it in the AD Docket. </P>
                <HD SOURCE="HD1">Examining the AD Docket </HD>
                <P>
                    You may examine the AD docket on the Internet at 
                    <E T="03">http://dms.dot.gov</E>
                    ; or in person at the Docket Management Facility between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays. The AD docket contains the NPRM, the regulatory evaluation, any comments received, and other information. The street address for the Docket Office (telephone (800) 647-5227) is in the 
                    <E T="02">ADDRESSES</E>
                     section. Comments will be available in the AD docket shortly after receipt. 
                </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 14 CFR Part 39 </HD>
                    <P>Air transportation, Aircraft, Aviation safety, Incorporation by reference, Safety.</P>
                </LSTSUB>
                <REGTEXT TITLE="14" PART="39">
                    <HD SOURCE="HD1">Adoption of the Amendment </HD>
                    <AMDPAR>Accordingly, under the authority delegated to me by the Administrator, the FAA amends 14 CFR part 39 as follows: </AMDPAR>
                    <PART>
                        <HD SOURCE="HED">PART 39—AIRWORTHINESS DIRECTIVES </HD>
                    </PART>
                    <AMDPAR>1. The authority citation for part 39 continues to read as follows: </AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>49 U.S.C. 106(g), 40113, 44701. </P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="14" PART="39">
                    <SECTION>
                        <SECTNO>§ 39.13 </SECTNO>
                        <SUBJECT>[Amended] </SUBJECT>
                    </SECTION>
                    <AMDPAR>2. The FAA amends § 39.13 by adding the following new AD: </AMDPAR>
                    <EXTRACT>
                        <FP SOURCE="FP-2">
                            <E T="04">2007-08-06 British Aerospace Regional Aircraft:</E>
                             Amendment 39-15023; Docket No. FAA-2007-27070; Directorate Identifier 2007-CE-003-AD. 
                        </FP>
                        <HD SOURCE="HD1">Effective Date </HD>
                        <P>(a) This airworthiness directive (AD) becomes effective May 18, 2007. </P>
                        <HD SOURCE="HD1">Affected ADs </HD>
                        <P>(b) None. </P>
                        <HD SOURCE="HD1">Applicability </HD>
                        <P>(c) This AD applies to Models HP.137 Jetstream Mk.1, Jetstream Series 200, Jetstream Series 3101, and Jetstream Model 3201 airplanes, all serial numbers, certificated in any category. </P>
                        <HD SOURCE="HD1">Subject </HD>
                        <P>(d) Air Transport Association of America (ATA) Code 32: Landing Gear. </P>
                        <HD SOURCE="HD1">Reason </HD>
                        <P>(e) The mandatory continuing airworthiness information (MCAI) states: </P>
                        <P>This Airworthiness Directive * * * is published in order to maintain the structural integrity of the applicable aircraft. The Service Bulletin provides life limits for critical landing gear components. Failure of such items could lead to unsafe conditions. </P>
                        <HD SOURCE="HD1">Actions and Compliance </HD>
                        <P>(f) Unless already done, within 60 days after May 18, 2007 (the effective date of this AD), comply with the requirements given in BAE Systems British Aerospace Jetstream Series 3100 and 3200 Service Bulletin 32-JA981042 Rev 5, dated November 1, 2005. </P>
                        <NOTE>
                            <HD SOURCE="HED">Note 1:</HD>
                            <P>The compliance times of this AD are presented in cycles (landings) since new (CSN). If you do not keep the total CSN, then you may multiply the total number of airplane hours time-in-service by 0.75. </P>
                        </NOTE>
                        <HD SOURCE="HD1">FAA AD Differences </HD>
                        <NOTE>
                            <HD SOURCE="HED">Note 2:</HD>
                            <P>This AD differs from the MCAI and/or service information as follows: We allow a different method for calculating the CSN of a component listed in this AD.</P>
                        </NOTE>
                        <HD SOURCE="HD1">Other FAA AD Provisions </HD>
                        <P>(g) The following provisions also apply to this AD: </P>
                        <P>(1) Alternative Methods of Compliance (AMOCs): The Manager, Standards Staff, FAA, ATTN: Taylor Martin, Aerospace Engineer, FAA, Small Airplane Directorate, 901 Locust, Room 301, Kansas City, Missouri 64106; telephone: (816) 329-4138; fax: (816) 329-4090, has the authority to approve AMOCs for this AD, if requested using the procedures found in 14 CFR 39.19. Before using any approved AMOC on any airplane to which the AMOC applies, notify your appropriate principal inspector (PI) in the FAA Flight Standards District Office (FSDO), or lacking a PI, your local FSDO. </P>
                        <P>(2) Airworthy Product: For any requirement in this AD to obtain corrective actions from a manufacturer or other source, use these actions if they are FAA-approved. Corrective actions are considered FAA-approved if they are approved by the State of Design Authority (or their delegated agent). You are required to assure the product is airworthy before it is returned to service. </P>
                        <P>
                            (3) Reporting Requirements: For any reporting requirement in this AD, under the provisions of the Paperwork Reduction Act (44 U.S.C. 3501 
                            <E T="03">et seq.</E>
                            ), the Office of Management and Budget (OMB) has approved the information collection requirements and has assigned OMB Control Number 2120-0056. 
                        </P>
                        <HD SOURCE="HD1">Related Information </HD>
                        <P>(h) Refer to MCAI European Aviation Safety Agency (EASA) AD No.: 2006-0087, dated April 18, 2006, and BAE Systems British Aerospace Jetstream Series 3100 and 3200 Service Bulletin 32-JA981042 Rev 5, dated November 1, 2005, for related information. </P>
                        <HD SOURCE="HD1">Material Incorporated by Reference </HD>
                        <P>(i) You must use BAE Systems British Aerospace Jetstream Series 3100 and 3200 Service Bulletin 32-JA981042 Rev 5, dated November 1, 2005, to do the actions required by this AD, unless the AD specifies otherwise. </P>
                        <P>(1) The Director of the Federal Register approved the incorporation by reference of this service information under 5 U.S.C. 552(a) and 1 CFR part 51. </P>
                        <P>(2) For service information identified in this AD, contact Customer Information Department, BAE Systems, Prestwick International Airport, Ayshire, KA9 2RW, Scotland; telephone: (01292) 675207; fax: (01292) 675704. </P>
                        <P>
                            (3) You may review copies at the FAA, Central Region, Office of the Regional Counsel, 901 Locust, Room 506, Kansas City, Missouri 64106; or at the National Archives and Records Administration (NARA). For information on the availability of this material at NARA, call 202-741-6030, or go to: 
                            <E T="03">http://www.archives.gov/federal-register/cfr/ibr-locations.html</E>
                            .
                        </P>
                    </EXTRACT>
                </REGTEXT>
                <SIG>
                    <DATED>Issued in Kansas City, Missouri, on April 6, 2007. </DATED>
                    <NAME>Kim Smith, </NAME>
                    <TITLE>Manager, Small Airplane Directorate, Aircraft Certification Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. E7-6913 Filed 4-12-07; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4910-13-P </BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION </AGENCY>
                <SUBAGY>Federal Aviation Administration </SUBAGY>
                <CFR>14 CFR Part 39 </CFR>
                <DEPDOC>[Docket No. FAA-2007-27109; Directorate Identifier 2007-CE-005-AD; Amendment 39-15024; AD 2007-08-07] </DEPDOC>
                <RIN>RIN 2120-AA64 </RIN>
                <SUBJECT>Airworthiness Directives; LATINOAMERICANA DE AVIACIÓN (LAVIA) S.A. (Type Certificate Data Sheets No. 2A8 and No. 2A10 Previously Held by The New Piper Aircraft, Inc.) Models PA-25, PA-25-235, and PA-25-260 Airplanes </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration (FAA), Department of Transportation (DOT). </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        We are adopting a new airworthiness directive (AD) for the products listed above. This AD results from mandatory continuing airworthiness information (MCAI) 
                        <PRTPAGE P="18567"/>
                        issued by an aviation authority of another country to identify and correct an unsafe condition on an aviation product. The MCAI references Latinoamericana de Aviación S.A. Service Bulletin No. 25/53/03, dated May 10, 2006, which describes the unsafe condition as: 
                    </P>
                    <EXTRACT>
                        <P>REAR AND FORWARD SUPPORTS OF BOTH HORIZONTAL STABILIZER MODIFICATION. It have been found on several of the affected airplanes some severe corrosion and cracks in both supports. The probable cause for those failures is the accumulation of steam or application products vapors. </P>
                    </EXTRACT>
                </SUM>
                <FP>We are issuing this AD to require actions to correct the unsafe condition on these products. </FP>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>This AD becomes effective May 18, 2007. </P>
                    <P>
                        The Director of the 
                        <E T="04">Federal Register</E>
                         approved the incorporation by reference of certain publications listed in this AD as of May 18, 2007. 
                    </P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        You may examine the AD docket on the Internet at 
                        <E T="03">http://dms.dot.gov</E>
                         or in person at the Docket Management Facility, U.S. Department of Transportation, 400 Seventh Street SW., Nassif Building, Room PL-401, Washington, DC. 
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Mr. Sarjapur Nagarajan, Aerospace Engineer, FAA, Small Airplane Directorate, 901 Locust, Room 301, Kansas City, Missouri 64106; telephone: (816) 329-4145; fax: (816) 329-4090. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Streamlined Issuance of AD </HD>
                <P>
                    The FAA is implementing a new process for streamlining the issuance of ADs related to MCAI. The streamlined process will allow us to adopt MCAI safety requirements in a more efficient manner and will reduce safety risks to the public. This process continues to follow all FAA AD issuance processes to meet legal, economic, Administrative Procedure Act, and 
                    <E T="04">Federal Register</E>
                     requirements. We also continue to meet our technical decision-making responsibilities to identify and correct unsafe conditions on U.S.-certificated products. 
                </P>
                <P>This AD references the MCAI and related service information that we considered in forming the engineering basis to correct the unsafe condition. The AD contains text copied from the MCAI and for this reason might not follow our plain language principles. </P>
                <HD SOURCE="HD1">Discussion </HD>
                <P>
                    We issued a notice of proposed rulemaking (NPRM) to amend 14 CFR part 39 to include an AD that would apply to the specified products. That NPRM was published in the 
                    <E T="04">Federal Register</E>
                     on February 14, 2007 (72 FR 6982). That NPRM proposed to require compliance with Service Bulletin No. 25/53/03 issued by Latinoamericana de Aviación S.A. in order to detect cracks, evidence of corrosion or any other anomalies on support tubes of the horizontal stabilizer. 
                </P>
                <HD SOURCE="HD1">Comments </HD>
                <P>We gave the public the opportunity to participate in developing this AD. We received no comments on the NPRM or on the determination of the cost to the public. </P>
                <HD SOURCE="HD1">Conclusion </HD>
                <P>We reviewed the available data and determined that air safety and the public interest require adopting the AD as proposed. </P>
                <HD SOURCE="HD1">Differences Between This AD and the MCAI or Service Information </HD>
                <P>We have reviewed the MCAI and related service information and, in general, agree with their substance. But we might have found it necessary to use different words from those in the MCAI to ensure the AD is clear for U.S. operators and is enforceable in a U.S. court of law. In making these changes, we do not intend to differ substantively from the information provided in the MCAI and related service information. </P>
                <P>We might also have required different actions in this AD from those in the MCAI in order to follow FAA policies. Any such differences are described in a separate paragraph of the AD. These requirements, if any, take precedence over the actions copied from the MCAI. </P>
                <HD SOURCE="HD1">Costs of Compliance </HD>
                <P>We estimate that this AD will affect 1,144 products of U.S. registry. We also estimate that it will take about 10 work-hours per product to comply with this AD. The average labor rate is $80 per work-hour. Required parts will cost about $845 per product. Where the service information lists required parts costs that are covered under warranty, we have assumed that there will be no charge for these parts. As we do not control warranty coverage for affected parties, some parties may incur costs higher than estimated here. Based on these figures, we estimate the cost of this AD to the U.S. operators to be $1,881,880, or $1,645 per product. </P>
                <HD SOURCE="HD1">Authority for This Rulemaking </HD>
                <P>Title 49 of the United States Code specifies the FAA's authority to issue rules on aviation safety. Subtitle I, section 106, describes the authority of the FAA Administrator. “Subtitle VII: Aviation Programs,” describes in more detail the scope of the Agency's authority. </P>
                <P>We are issuing this rulemaking under the authority described in “Subtitle VII, Part A, Subpart III, Section 44701: General requirements.” Under that section, Congress charges the FAA with promoting safe flight of civil aircraft in air commerce by prescribing regulations for practices, methods, and procedures the Administrator finds necessary for safety in air commerce. This regulation is within the scope of that authority because it addresses an unsafe condition that is likely to exist or develop on products identified in this rulemaking action. </P>
                <HD SOURCE="HD1">Regulatory Findings </HD>
                <P>We determined that this AD will not have federalism implications under Executive Order 13132. This AD will 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>
                <P>For the reasons discussed above, I certify this AD:</P>
                <P>(1) Is not a “significant regulatory action” under Executive Order 12866; </P>
                <P>(2) Is not a “significant rule” under 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 regulatory evaluation of the estimated costs to comply with this AD and placed it in the AD Docket. </P>
                <HD SOURCE="HD1">Examining the AD Docket </HD>
                <P>
                    You may examine the AD docket on the Internet at 
                    <E T="03">http://dms.dot.gov</E>
                    ; or in person at the Docket Management Facility between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays. The AD docket contains the NPRM, the regulatory evaluation, any comments received, and other information. The street address for the Docket Office (telephone (800) 647-5227) is in the 
                    <E T="02">ADDRESSES</E>
                     section. Comments will be available in the AD docket shortly after receipt. 
                </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 14 CFR Part 39 </HD>
                    <P>Air transportation, Aircraft, Aviation safety, Incorporation by reference, Safety.</P>
                </LSTSUB>
                <REGTEXT TITLE="14" PART="39">
                    <HD SOURCE="HD1">Adoption of the Amendment </HD>
                    <AMDPAR>
                        Accordingly, under the authority delegated to me by the Administrator, 
                        <PRTPAGE P="18568"/>
                        the FAA amends 14 CFR part 39 as follows: 
                    </AMDPAR>
                    <PART>
                        <HD SOURCE="HED">PART 39—AIRWORTHINESS DIRECTIVES </HD>
                    </PART>
                    <AMDPAR>1. The authority citation for part 39 continues to read as follows: </AMDPAR>
                    <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>
                    </SECTION>
                    <AMDPAR>2. The FAA amends § 39.13 by adding the following new AD:</AMDPAR>
                    <EXTRACT>
                        <FP SOURCE="FP-2">
                            <E T="04">2007-08-07 LATINOAMERICANA DE AVIACIÓN (LAVIA) S.A. (Type Certificate Data Sheets No. 2A8 and No. 2A10 previously held by The New Piper Aircraft, Inc.):</E>
                             Amendment 39-15024; Docket No. FAA-2007-27109; Directorate Identifier 2007-CE-005-AD. 
                        </FP>
                        <HD SOURCE="HD1">Effective Date </HD>
                        <P>(a) This airworthiness directive (AD) becomes effective May 18, 2007. </P>
                        <HD SOURCE="HD1">Affected ADs </HD>
                        <P>(b) None. </P>
                        <HD SOURCE="HD1">Applicability </HD>
                        <P>(c) This AD applies to Models PA-25, PA-25-235, and PA-25-260, all serial numbers up to LA-260-06008, certificated in any category. </P>
                        <HD SOURCE="HD1">Subject </HD>
                        <P>(d) Air Transport Association of America (ATA) Code 55: Stabilizers. </P>
                        <HD SOURCE="HD1">Reason </HD>
                        <P>(e) The mandatory continuing airworthiness information (MCAI) references Latinoamericana de Aviación S.A. Service Bulletin No. 25/53/03, dated May 10, 2006, which states: </P>
                        <P>REAR AND FORWARD SUPPORTS OF BOTH HORIZONTAL STABILIZER MODIFICATION. It has been found on several of the affected airplanes some severe corrosion and cracks in both supports. The probable cause for those failures is the accumulation of steam or application products vapors. </P>
                        <HD SOURCE="HD1">Actions and Compliance </HD>
                        <P>(f) Unless already done, do the following actions:</P>
                        <P>(1) Upon accumulating 1,500 hours time-in-service (TIS) or within the next 50 hours TIS after May 18, 2007 (the effective date of this AD), whichever occurs later, do the operations as specified in the paragraph “ACTIONS,” subparagraph “INITIAL” of Latinoamericana de Aviación S.A. Service Bulletin No. 25/53/03, dated May 10, 2006. Repetitively inspect thereafter every 100 hours TIS or 12 months, whichever occurs first, until the modification specified in paragraph “ACTIONS,” subparagraph “DEFINITIVE” of Latinoamericana de Aviación S.A. Service Bulletin No. 25/53/03, dated May 10, 2006, is done. </P>
                        <P>(2) If any evidence of cracks, signs of corrosion, or any other discrepancy is detected during any inspection required in paragraph (f)(1) of this AD, before further flight, disassemble both horizontal stabilizers and conduct a detailed inspection on the surface of both supports and take corrective action. Use paragraph “ACTIONS,” subparagraph “DEFINITIVE” of Latinoamericana de Aviación S.A. Service Bulletin No. 25/53/03, dated May 10, 2006. </P>
                        <P>(3) After incorporating the modification specified in paragraph “ACTIONS,” subparagraph “DEFINITIVE” of Latinoamericana de Aviación S.A. Service Bulletin No. 25/53/03, dated May 10, 2006, no further action is required. </P>
                        <P>(4) Upon accumulating 1,000 hours TIS after May 18, 2007 (the effective date of this AD), modify both horizontal stabilizers as specified in paragraph “ACTIONS,” subparagraph “DEFINITIVE” of Latinoamericana de Aviación S.A. Service Bulletin No. 25/53/03, dated May 10, 2006, unless already done. Incorporating this modification terminates the repetitive inspection requirement in paragraph (f)(1) of this AD. </P>
                        <P>(5) As a terminating action to the inspection requirements of this AD, the modification to both horizontal stabilizers specified in paragraph “ACTIONS,” subparagraph “DEFINITIVE” of Latinoamericana de Aviación S.A. Service Bulletin No. 25/53/03, dated May 10, 2006, may be incorporated at any time after the effective date of this AD and before the time required in paragraph (f)(4) of this AD. </P>
                        <HD SOURCE="HD1">FAA AD Differences </HD>
                        <NOTE>
                            <HD SOURCE="HED">Note:</HD>
                            <P>This AD differs from the MCAI and/or service information as follows: No differences.</P>
                        </NOTE>
                        <HD SOURCE="HD1">Other FAA AD Provisions </HD>
                        <P>(g) The following provisions also apply to this AD: </P>
                        <P>
                            (1) 
                            <E T="03">Alternative Methods of Compliance (AMOCs):</E>
                             The Manager, Standards Staff, FAA, Small Airplane Directorate, ATTN: Sarjapur Nagarajan, Aerospace Engineer, 901 Locust, Room 301, Kansas City, Missouri 64106; telephone: (816) 329-4145; fax: (816) 329-4090, has the authority to approve AMOCs for this AD, if requested using the procedures found in 14 CFR 39.19. 
                        </P>
                        <P>
                            (2) 
                            <E T="03">Airworthy Product:</E>
                             For any requirement in this AD to obtain corrective actions from a manufacturer or other source, use these actions if they are FAA-approved. Corrective actions are considered FAA-approved if they are approved by the State of Design Authority (or their delegated agent). You are required to assure the product is airworthy before it is returned to service. 
                        </P>
                        <P>
                            (3) 
                            <E T="03">Reporting Requirements:</E>
                             For any reporting requirement in this AD, under the provisions of the Paperwork Reduction Act (44 U.S.C. 3501 et.seq.), the Office of Management and Budget (OMB) has approved the information collection requirements and has assigned OMB Control Number 2120-0056. 
                        </P>
                        <HD SOURCE="HD1">Related Information </HD>
                        <P>(h) Refer to MCAI Dirección Nacional de Aeronavegabilidad AD No. RA 2006-06-01, Rev. 1 LAVIA S.A., Amendment No. 39/03-041, dated November 17, 2006; and Latinoamericana de Aviación S.A. Service Bulletin No. 25/53/03, dated May 10, 2006, for related information. </P>
                        <HD SOURCE="HD1">Material Incorporated by Reference </HD>
                        <P>(i) You must use Latinoamericana de Aviación S.A. Service Bulletin No. 25/53/03, dated May 10, 2006, to do the actions required by this AD, unless the AD specifies otherwise. </P>
                        <P>
                            (1) The Director of the 
                            <E T="04">Federal Register</E>
                             approved the incorporation by reference of this service information under 5 U.S.C. 552(a) and 1 CFR part 51. 
                        </P>
                        <P>
                            (2) For service information identified in this AD, contact Latinoamericana de Aviación S.A., Hangar No. 1 Aeropuerto “El Plumerillo” sur, Las Heras-Mendoza-Argentina—CP 5541; telephone: 0054-261-4489198; e-mail: 
                            <E T="03">laviasa@hotmail.com</E>
                            . 
                        </P>
                        <P>
                            (3) You may review copies at the FAA, Central Region, Office of the Regional Counsel, 901 Locust, Room 506, Kansas City, Missouri 64106; or at the National Archives and Records Administration (NARA). For information on the availability of this material at NARA, call 202-741-6030, or go to: 
                            <E T="03">http://www.archives.gov/federal-register/cfr/ibr-locations.html</E>
                            .
                        </P>
                    </EXTRACT>
                </REGTEXT>
                <SIG>
                    <DATED>Issued in Kansas City, Missouri, on April 6, 2007. </DATED>
                    <NAME>Kim Smith, </NAME>
                    <TITLE>Manager, Small Airplane Directorate, Aircraft Certification Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. E7-6929 Filed 4-12-07; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4910-13-P </BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <CFR>14 CFR Part 71</CFR>
                <DEPDOC>[Docket No. FAA-2006-26719; Airspace Docket No. 06-AAL-41]</DEPDOC>
                <SUBJECT>Revision of Class E Airspace; Valdez, AK</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration (FAA), DOT.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This action revises Class E airspace at Valdez, AK to provide adequate controlled airspace to contain aircraft executing Standard Instrument Approach Procedures (SIAPs). The FAA Instrument Flight Procedures Production and Maintenance Branch has drafted two new SIAPs for the Valdez Pioneer Field Airport at Valdez, AK. This rule results in the revision of Class E airspace upward from 700 feet (ft.) and 1,200 ft. above the surface at Valdez, AK.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        <E T="03">Effective Date:</E>
                         0901 UTC, July 5, 2007. The Director of the Federal Register approves this incorporation by reference action under title 1, Code of Federal Regulations, part 51, subject to the annual revision of FAA Order 
                        <PRTPAGE P="18569"/>
                        7400.9 and publication of conforming amendments.
                    </P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Gary Rolf, AAL-538G, Federal Aviation Administration, 222 West 7th Avenue, Box 14, Anchorage, AK 99513-7587; telephone number (907) 271-5898; fax: (907) 271-2850; e-mail: 
                        <E T="03">gary.ctr.rolf@faa.gov.</E>
                         Internet address: 
                        <E T="03">http://www.alaska.faa.gov/at.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">History</HD>
                <P>On Thursday, January 18, 2007, the FAA proposed to amend part 71 of the Federal Aviation Regulations (14 CFR part 71) to revise Class E airspace upward form 700 ft. and 1,200 ft. above the surface at Valdez Pioneer Field, AK (72 FR2213). The action was proposed in order to create Class E airspace sufficient in size to contain aircraft while executing two new SIAPs for the Valdez Pioneer Field Airport. The approaches are (1) Localizer Type Directional Aid (LDA)/Distance Measuring Equipment (DME)-G, Original and (2) LDA-H, Original. The LDA-G is a Special SIAP and will not be published in the U.S. Terminal Procedures (Alaska) publication. Class E controlled airspace extending upward from 700 ft. and 1,200 ft. above the surface in the Valdez, AK area is revised by this action. In the Notice of Proposed Rulemaking, the airport name was not fully articulated. The full and proper designation (Valdez Pioneer Field) is included in this rule. The location of the localizer has also been updated to reflect accurate position.</P>
                <P>Interested parties were invited to participate in this rulemaking proceeding by submitting written comments on the proposal to the FAA. No public comments have been received; thus the rule is adopted as proposed.</P>
                <P>
                    The area will be depicted on aeronautical charts for pilot reference. The coordinates for this airspace docket are based on North American Datum 83. The Class E airspace areas designated as 700/1,200 ft. transition areas are published in paragraph 6005 of FAA Order 7400.9P, 
                    <E T="03">Airspace Designations and Reporting Points,</E>
                     dated September 1, 2006, and effective September 15, 2006, which is incorporated by reference in 14 CFR 71.1. The Class E airspace designations listed in this document will be published subsequently in the Order.
                </P>
                <HD SOURCE="HD1">The Rule</HD>
                <P>This amendment to 14 CFR part 71 revises Class E airspace at the Valdez Pioneer Field Airport, Alaska. This Class E airspace is revised to accommodate aircraft executing SIAPs, and will be depicted on aeronautical charts for pilot reference. The intended effect of this rule is to provide adequate controlled airspace for IFR operations at the Valdez Pioneer Field Airport, Valdez, Alaska.</P>
                <P>The FAA has determined that this regulation only involves an established body of technical regulations for which frequent and routine amendments are necessary to keep them operationally current. It, therefore—(1) Is not a “significant regulatory action” under Executive Order 12866; (2) is not a “significant rule” under DOT Regulatory Policies and Procedures (44 FR 11034; February 26, 1979); and (3) does not warrant preparation of a regulatory evaluation as the anticipated impact is so minimal. Since this is a routine matter that will only affect air traffic procedures and air navigation, it is certified that this rule will not have a significant economic impact on a substantial number of small entities under the criteria of the Regulatory Flexibility Act.</P>
                <P>The FAA's authority to issue rules regarding aviation safety is found in Title 49 of the United States Code. Subtitle 1, Section 106 describes the authority of the FAA Administrator. Subtitle VII, Aviation Programs, describes in more detail the scope of the agency's authority.</P>
                <P>This rulemaking is promulgated under the authority described in Subtitle VII, Part A, Subpart 1, Section 40103, Sovereignty and use of airspace. Under that section, the FAA is charged with prescribing regulations to ensure the safe and efficient use of the navigable airspace. This regulation is within the scope of that authority because it creates Class E airspace sufficient in size to contain aircraft executing instrument procedures for the Valdez Pioneer Field Airport and represents the FAA's continuing effort to safely and efficiently use the navigable airspace.</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 14 CFR Part 71</HD>
                    <P>Airspace, Incorporation by reference, Navigation (air).</P>
                </LSTSUB>
                <REGTEXT TITLE="14" PART="71">
                    <HD SOURCE="HD1">Adoption of the Amendment</HD>
                    <AMDPAR>In consideration of the foregoing, the Federal Aviation Administration amends 14 CFR part 71 as follows:</AMDPAR>
                    <PART>
                        <HD SOURCE="HED">PART 71—DESIGNATION OF CLASS A, CLASS B, CLASS C, CLASS D, AND CLASS E AIRSPACE AREAS; AIRWAYS; ROUTES; AND REPORTING POINTS</HD>
                    </PART>
                    <AMDPAR>1. The authority citation for 14 CFR part 71 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>49 U.S.C. 106(g), 30103, 40120; E.O. 10854, 24 FR 9565, 3 CFR, 1959-1963 Comp., p. 389.</P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="14" PART="71">
                    <SECTION>
                        <SECTNO>§ 71.1</SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>
                        2. The incorporation by reference in 14 CFR 71.1 of Federal Aviation Administration Order 7400.9P, 
                        <E T="03">Airspace Designations and Reporting Points</E>
                        , dated September 1, 2006, and effective September 15, 2006, is amended as follows:
                    </AMDPAR>
                    <EXTRACT>
                        <STARS/>
                        <HD SOURCE="HD2">Paragraph 6005 Class E Airspace Extending Upward from 700 feet or More Above the Surface of the Earth.</HD>
                        <STARS/>
                        <HD SOURCE="HD1">AAL AK E5 Valdez, AK</HD>
                        <FP SOURCE="FP-2">Valdez Pioneer Field, AK</FP>
                        <FP SOURCE="FP1-2">(Lat. 61°08′02″ N, long. 146°14′54″ W.)</FP>
                        <FP SOURCE="FP-2">Valdez Localizer</FP>
                        <FP SOURCE="FP1-2">(Lat. 61°08′10″ N, long. 146°13′15″ W.)</FP>
                        <FP SOURCE="FP-2">Johnstone Point VORTAC</FP>
                        <FP SOURCE="FP1-2">(Lat. 60°28′51″ N, long. 146°35′58″ W.)</FP>
                        <P>That airspace extending upward from 700 feet above the surface within a 6.6-mile radius of the Valdez Pioneer Field Airport, AK, and within 3.1 miles each side of the Valdez Localizer front course extending from the 6.6-mile radius to 12.8 miles southwest of the Valdez Localizer; and that airspace extending upward from 1,200 feet above the surface within 50 miles of the Johnstone Point VORTAC, AK, extending clockwise from the Johnstone Point VORTAC, AK, 200° radial to the 076° radial.</P>
                        <STARS/>
                    </EXTRACT>
                </REGTEXT>
                <SIG>
                    <DATED>Issued in Anchorage, AK, on April 2, 2007.</DATED>
                    <NAME>Anthony M. Wylie,</NAME>
                    <TITLE>Manager, Alaska Flight Services Information Area Group.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 07-1812 Filed 4-12-07; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-13-M</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF ENERGY </AGENCY>
                <SUBAGY>Federal Energy Regulatory Commission </SUBAGY>
                <CFR>18 CFR Parts 35 and 37 </CFR>
                <DEPDOC>[Docket Nos. RM05-17-000 and RM05-25-000; Order No. 890] </DEPDOC>
                <SUBJECT>Preventing Undue Discrimination and Preference in Transmission Service </SUBJECT>
                <DATE>Issued April 6, 2007. </DATE>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Energy Regulatory Commission, DOE. </P>
                </AGY>
                <ACT>
                    <PRTPAGE P="18570"/>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule; Notice of electronic filing guidelines. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        On February 16, 2007, the Federal Energy Regulatory Commission issued  Order No. 890, which amended the regulations and the 
                        <E T="03">pro forma</E>
                         open access transmission tariff (OATT). This notice contains guidelines for the electronic submission of OATT tariffs and other information required by Order No. 890. 
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        <E T="03">Effective Date:</E>
                         These guidelines became effective on April 6, 2007. 
                    </P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P> </P>
                    <FP SOURCE="FP-1">Daniel Hedberg (Technical Information), Office of Energy Markets and Reliability, Federal Energy Regulatory Commission,  888 First Street, NE., Washington, DC 20426, (202) 502-6243. </FP>
                    <FP SOURCE="FP-1">W. Mason Emnett (Legal Information), Office of the General Counsel—Energy Markets,  Federal Energy Regulatory Commission, 888 First Street, NE., Washington, DC 20426, (202) 502-6540. </FP>
                    <FP SOURCE="FP-1">Kathleen Barrón (Legal Information), Office of the General Counsel—Energy Markets,  Federal Energy Regulatory Commission,  888 First Street, NE., Washington, DC 20426, (202) 502-6461. </FP>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Notice of Electronic Filing Guidelines for Open Access Transmission Tariffs and Related Filings Pursuant to Commission Order No. 890 and 18 CFR Part 35 and 37 </HD>
                <P>
                    On February 16, 2007, the Federal Energy Regulatory Commission issued Order No. 890,
                    <SU>1</SU>
                    <FTREF/>
                     which amends the regulations and the 
                    <E T="03">pro forma</E>
                     open access transmission tariff (OATT) to ensure that transmission services are provided on a basis that is just, reasonable and not unduly discriminatory or preferential. 
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         
                        <E T="03">Preventing Undue Discrimination and Preference in Transmission Service,</E>
                         Order No. 890, 72 FR 12266 (March 15, 2007), FERC Stats. &amp; Regs. ¶ 31,241 (2007), 
                        <E T="03">reh'g pending.</E>
                    </P>
                </FTNT>
                <P>This document contains guidelines for the electronic submission of OATT tariffs and other information required by Order No. 890. The table attached to the guidelines includes specific filing instructions and references to the pertinent paragraph(s) in Order No. 890 for each type of submission. </P>
                <P>
                    The Commission's electronic filing system can be accessed on its Web site at: 
                    <E T="03">http://www.ferc.gov/docs-filing/docs-filing.asp.</E>
                     An eRegistration account is required for all persons logging in to the system and for persons who will be listed as a primary contact or person responsible for the filing. At the present time, only public information can be submitted via the efiling system. However, all Order No. 890 OATT filings are considered public. The Commission prefers filings in text-searchable formats. 
                </P>
                <P>
                    The electronic filing guidelines attached to this notice will also be available on the Commission's Web site at 
                    <E T="03">http://www.ferc.gov/help/how-to.asp</E>
                     and updated when necessary. 
                </P>
                <SIG>
                    <NAME>Philis J. Posey, </NAME>
                    <TITLE>Acting Secretary. </TITLE>
                </SIG>
                <HD SOURCE="HD1">Filing Guidelines for Open Access Transmission Tariffs and Related Filings Pursuant to Commission Order No. 890 and 18 CFR Part 35 and 37 </HD>
                <P>
                    On February 16, 2007, the Federal Energy Regulatory Commission issued Order No. 890,
                    <SU>2</SU>
                    <FTREF/>
                     which amends the regulations and the 
                    <E T="03">pro forma</E>
                     open access transmission tariff (OATT) adopted in Order Nos. 888 
                    <SU>3</SU>
                    <FTREF/>
                     and 889 
                    <SU>4</SU>
                    <FTREF/>
                     to ensure that transmission services are provided on a basis that is just, reasonable and not unduly discriminatory or preferential. 
                </P>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         
                        <E T="03">Preventing Undue Discrimination and Preference in Transmission Service,</E>
                         Order No. 890, 72 FR 12266 (March 15, 2007), FERC Stats. &amp; Regs. ¶ 31,241 (2007), 
                        <E T="03">reh'g pending.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         
                        <E T="03">Promoting Wholesale Competition Through Open Access Non-discriminatory Transmission Services by Public Utilities; Recovery of Stranded Costs by Public Utilities and Transmitting Utilities,</E>
                         Order No. 888, 61 FR 21540 (May 10, 1996), FERC Stats. &amp; Regs. ¶ 31,036 (1996), 
                        <E T="03">order on reh'g,</E>
                         Order No. 888-A, 62 FR 12274 (Mar. 14, 1997), FERC Stats. &amp; Regs. ¶ 31,048 (1997), 
                        <E T="03">order on reh'g,</E>
                         Order No. 888-B, 81 FERC ¶ 61,248 (1997), 
                        <E T="03">order on reh'g,</E>
                         Order No. 888-C, 82 FERC ¶ 61,046 (1998), 
                        <E T="03">aff'd in relevant part sub nom. Transmission Access Policy Study Group v. FERC,</E>
                         225 F.3d 667 (D.C. Cir. 2000) (
                        <E T="03">TAPS</E>
                         v. 
                        <E T="03">FERC</E>
                        ), 
                        <E T="03">aff'd sub nom. New York</E>
                         v. 
                        <E T="03">FERC,</E>
                         535 U.S. 1 (2002).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         
                        <E T="03">Open Access Same-Time Information System (Formerly Real-Time Information Networks) and Standards of Conduct,</E>
                         Order No. 889, 61 FR 21737 (May 10, 1996), FERC Stats. &amp; Regs. ¶ 31,035 (1996), 
                        <E T="03">order on reh'g,</E>
                         Order No. 889-A, FERC Stats. &amp; Regs. ¶ 31,049 (1997), 
                        <E T="03">order on reh'g</E>
                        , Order No. 889-B, 81 FERC ¶ 61,253 (1997).
                    </P>
                </FTNT>
                <P>This document contains guidelines for the electronic submission of OATT tariffs and other information required by Order No. 890. The attached table includes specific filing guidelines and references to the pertinent paragraph(s) in Order No. 890 for each type of submission. </P>
                <P>
                    The Commission's electronic filing system can be accessed on its web site at: 
                    <E T="03">http://www.ferc.gov/docs-filing/docs-filing.asp.</E>
                     An eRegistration account is required for all persons logging in to the system and for persons who will be listed as a primary contact or person responsible for the filing. At the present time, only public information can be submitted via the efiling system. However, all Order No. 890 OATT filings are considered public. 
                </P>
                <P>The Commission prefers filings in text-searchable formats. Our standard word processing application is MS Word, but the efiling system can also accept documents in WordPerfect and PDF formats. The Commission will add notice of these filings to its Combined Notice of Filing Report, so it is not necessary to include a “Form of Notice” file as part of an Order No. 890 OATT compliance submission. </P>
                <P>The general eFiling procedure for Order No. 890 compliance OATT efilings is: </P>
                <P>1. For Order No. 890 OATT compliance related submissions, the header of the document should contain OA07__000 (or OA08 after September 30, 2007) unless you are filing a correction or supplement to a previously assigned OA docket. NERC/NAESB submissions should refer to RM05-17 and RM05-25. </P>
                <P>2. Select the filing type “Order No. 890 OATT”. For NERC/NAESB status reports only, select “Production of Document”. </P>
                <P>3. On the Select Docket screen, enter OA07-1 in the docket number search block and select OA7-1-000 from the search results. A new OA Docket will be assigned to your submission. For NERC/NAESB status reports only, query and select dockets RM05-17 and RM05-25. </P>
                <P>4. Before you browse, select, and attach the file(s) make sure that the file name is less than 25 characters and contains no spaces or special characters. There is a maximum number of 10 files per session and no file should be larger than 10 Mb. </P>
                <P>5. On the Submission Description Screen, modify the default description: </P>
                <P>(1) For OATT submissions, replace “Order No. 890 OATT” with the description information in the table for the appropriate filing type, or a comparable description, to describe your submission. </P>
                <P>(2) For NERC/NAESB status reports only, replace “Production of Document” with the description information in the table for the appropriate filing type or a comparable description. </P>
                <P>(3) For any amendment or correction to a prior submission, select the OA Docket assigned to the prior filing and add “Correction to”, “Supplement to”, or other appropriate indicator to the edited description of the filing. </P>
                <P>6. Upon receipt, the eFiling system will send a Confirmation of Receipt e-mail to the e-mail address for the log in account. </P>
                <P>
                    Order No. 890 OATT submissions will be stored in eLibrary in the “Electric” library with Class = 
                    <PRTPAGE P="18571"/>
                    Application/Petition/Request, Type = Tariff Filing, and the OA docket number assigned to the submission. 
                </P>
                <P>NERC/NAESB status reports will be stored in the “Electric” library with Class = Status Report, Type = Status Report, and docket numbers RM05-17 and RM05-25. </P>
                <P>
                    Please be advised that all voluntary section 205 OATT related filings proposing variations from the non-rate terms and conditions contained in the pro forma OATT adopted in Order No. 890 will continue to be assigned ER Docket Numbers and will not be assigned OA Docket Numbers associated with the implementation of the Order No. 890 compliance filings.
                    <SU>5</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         With the exception of the optional section 205 implementation filing described in Order No. 890 at P 138-139.
                    </P>
                </FTNT>
                <GPOTABLE COLS="3" OPTS="L2,tp0,i1" CDEF="s35,r200,12">
                    <TTITLE>  </TTITLE>
                    <BOXHD>
                        <CHED H="1">
                            Deadline: Days from Mar. 15, 2007 
                            <LI>(FR publication) </LI>
                        </CHED>
                        <CHED H="1">Compliance action </CHED>
                        <CHED H="1">Final rule paragraph No. </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">30 Days, or April 16, 2007 </ENT>
                        <ENT>
                            Optional Implementation FPA section 205 filings allowing transmission providers to propose previously approved variations from the 
                            <E T="03">pro forma</E>
                             OATT that have been affected by 
                            <E T="03">pro forma</E>
                             OATT Final Rule reforms to remain in effect subject to a demonstration that such variations continue to be consistent with or superior to the revised Final Rule 
                            <E T="03">pro forma</E>
                             OATT (non RTO/ISO transmission providers). Such optional filings must request a 90 day effective date to facilitate Commission review under section 205 
                        </ENT>
                        <ENT>¶ 139 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT O="xl">Filing Type: Order No. 890 OATT. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT O="xl">File Under Docket OA07-1; new OA Docket will be assigned. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT O="xl">Description: Implementation FPA section 205 filing. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">60 days, or May 14, 2007 </ENT>
                        <ENT>
                            Non-ISO/RTO transmission providers submit FPA section 206 filings that contain the non-rate terms and conditions set forth in Final Rule. These filings need only contain the revised provisions adopted in the Final Rule. Transmission providers utilizing the optional Implementation FPA section 205 filing described above, need only submit tariff sheets necessary to implement the remaining modifications required under the Final Rule, 
                            <E T="03">i.e.</E>
                            , modifications related to tariff provisions that did not implicate previously-approved variations 
                        </ENT>
                        <ENT>¶ 135 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT O="xl">Filing Type: Order No. 890 OATT. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT O="xl">File Under Docket OA07-1; new OA Docket will be assigned. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT O="xl">Description: FPA section 206 filing with non-rate terms and conditions. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">75 days, or May 29, 2007 </ENT>
                        <ENT>Transmission Providers must post a “strawman” proposal for compliance with each of the nine planning principles adopted in the Final Rule. This may be posted on the Transmission Providers Web site or its OASIS site </ENT>
                        <ENT>¶ 443 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT O="xl">No Filing Requirement with FERC. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">90 days, or June 13, 2007 </ENT>
                        <ENT>NERC/NAESB status report and work plan for completion of ATC related business practices and standards.</ENT>
                        <ENT>¶ 223 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT O="xl">Filing Type: Production of Document. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT O="xl">File Under Docket RM05-17 and RM05-25. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT O="xl">Description: NERC/NAESB status report and work plan for completion of ATC related business practices and standard. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">90 days, or June 13, 2007 </ENT>
                        <ENT>NAESB status report and work plan for completion of OASIS functionality or uniform business practices (other than those related to ATC) </ENT>
                        <ENT>¶ 141 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT O="xl">Filing Type: Production of Document. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT O="xl">File Under Docket RM05-17 and RM05-25. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT O="xl">Description: NAESB status report and work plan for completion of OASIS functionality or uniform business practices. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">120 days, or July 13, 2007 </ENT>
                        <ENT>Transmission Providers must submit redesigned transmission charges that reflect the Capacity Benefit Margin set-aside through a limited issue section 205 rate filing as part of their initial ATC related compliance filings </ENT>
                        <ENT>¶ 263 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT O="xl">Filing Type: Order No. 890 OATT. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT O="xl">File Under Docket OA07-1; new OA Docket will be assigned. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT O="xl">Description: Redesigned Transmission Charges. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">180 days, or Sept.11, 2007 </ENT>
                        <ENT>
                            Submit compliance filings with Attachment C (ATC) of the 
                            <E T="03">pro forma</E>
                             OATT 
                        </ENT>
                        <ENT>¶ 140 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT O="xl">Filing Type: Order No. 890 OATT. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT O="xl">File Under Docket OA07-1; new OA Docket will be assigned. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT O="xl">Description: Attachment C Compliance Filing. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">210 days, or Oct. 11, 2007 </ENT>
                        <ENT>
                            ISOs and RTOs, and transmission providers located within an ISO/RTO footprint, submit FPA section 206 filings that contain the non-rate terms and conditions set forth in the Final Rule. These filings need only contain the revised provisions adopted in the Final Rule or a demonstration that previously approved variations continue to be consistent with or superior to the revised 
                            <E T="03">pro forma</E>
                             OATT 
                        </ENT>
                        <ENT>¶ 157, ¶ 161 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT O="xl">Filing Type: Order No. 890 OATT. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT O="xl">File Under Docket OA07-1; new OA Docket will be assigned. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT O="xl">Description: FPA Section 206 Filing With Non-Rate Terms and Conditions. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">210 days, or Oct. 11, 2007 </ENT>
                        <ENT>
                            Submit compliance filings with Attachment K (Planning) of the 
                            <E T="03">pro forma</E>
                             OATT or RTOs and ISOs file a demonstration that their planning processes are consistent with or superior to the planning principles in the Final Rule 
                        </ENT>
                        <ENT>¶ 140, ¶ 442 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT O="xl">Filing Type: Order No. 890 OATT. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT O="xl">File Under Docket OA07-1; new OA Docket will be assigned. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT O="xl">Description: Attachment K Compliance Filing. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">N/A </ENT>
                        <ENT>Transmission Providers must file a revised Attachment C to incorporate any changes to NERC's and NAESB's reliability and business practice standards to achieve consistency in ATC within 60 days of completion of the NERC and NAESB processes </ENT>
                        <ENT>¶ 325 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT O="xl">Filing Type: Order No. 890 OATT. </ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="18572"/>
                        <ENT I="22"> </ENT>
                        <ENT O="xl">File Under Docket OA07-1; new OA Docket will be assigned. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT O="xl">Description: Revised Attachment C Filing. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">N/A </ENT>
                        <ENT>
                            After the submission of FPA section 206 compliance filings, transmission providers may submit FPA section 205 filings proposing rates for the services provided for in the tariff, as well as non-rate terms and conditions that differ from those set forth in the Final Rule if those provisions are “consistent with or superior to” the 
                            <E T="03">pro forma</E>
                             OATT 
                        </ENT>
                        <ENT>¶ 135 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT O="xl">Do not eFile. File according to procedures current at the time of submission for FPA section 205 filings. </ENT>
                    </ROW>
                </GPOTABLE>
                <P>If you are unable to file electronically, you must submit original and 5 paper copies of the filing to: Kimberly D. Bose, Secretary, Federal Energy Regulatory Commission, 888 First Street, NE., Washington, DC 20426.</P>
            </SUPLINF>
            <FRDOC>[FR Doc. E7-7000 Filed 4-12-07; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 6717-01-P </BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF ENERGY </AGENCY>
                <SUBAGY>Federal Energy Regulatory Commission </SUBAGY>
                <CFR>18 CFR Part 388 </CFR>
                <DEPDOC>[Docket No. RM06-24-001; Order No. 683-A] </DEPDOC>
                <SUBJECT>Critical Energy Infrastructure Information </SUBJECT>
                <DATE>Issued April 9, 2007. </DATE>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Energy Regulatory Commission, Department of Energy. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final Rule, order on rehearing. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>On September 21, 2006, the Commission issued a final rule that clarified the definition of Critical Energy Infrastructure Information (CEII), required requesters of CEII to submit executed non-disclosure agreements with their requests, and provided that the notice and opportunity to comment on a CEII request would be combined with the notice of release of information. The Commission is denying the petition for rehearing filed by Edison Electric Institute. </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES: </HD>
                    <P>
                        <E T="03">Effective Date:</E>
                         This order denying rehearing of the final rule will become effective May 14, 2007. 
                    </P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Teresina A. Stasko, Office of the General Counsel, Federal Energy Regulatory Commission, 888 First Street, NE., Washington, DC 20426, Phone (202) 502-8317. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <EXTRACT>
                    <P>Before Commissioners: Joseph T. Kelliher, Chairman; Suedeen G. Kelly, Marc Spitzer, Philip D. Moeller, and Jon Wellinghoff.</P>
                </EXTRACT>
                <HD SOURCE="HD1">Order on Rehearing </HD>
                <HD SOURCE="HD3">(Issued April 9, 2007) </HD>
                <P>
                    1. This order addresses the request for rehearing filed by Edison Electric Institute (EEI) of the Commission's September 21, 2006 Order in this proceeding (September 21 Order), a final rule that clarified the definition of Critical Energy Infrastructure Information (CEII), required requesters of CEII to submit executed non-disclosure agreements (NDA) with their requests, and provided that the notice and opportunity to comment on a CEII request would be combined with the notice of release of information. 
                    <E T="03">Critical Energy Infrastructure Information</E>
                    , Order No. 683.
                    <SU>1</SU>
                    <FTREF/>
                     This order denies EEI's request for rehearing for the reasons explained below.
                    <SU>2</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         71 FR 58,273 (October 3, 2006), FERC Stats. &amp; Regs. ¶ 31,228 (2006). 
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         The California Coastal Commission, California Energy Commission, California Electricity Oversight Board, and California State Lands Commission (collectively the California State Agencies) filed a request for reconsideration. Although labeled as a “Request for Reconsideration,” the request is actually an untimely request for rehearing. As explained below, the Commission has long held that it lacks authority to consider requests for rehearing filed more than 30 days after issuance of a Commission order. 
                    </P>
                </FTNT>
                <HD SOURCE="HD2">Background </HD>
                <P>
                    2. The Commission began its efforts with respect to CEII shortly after the attacks of September 11, 2001. 
                    <E T="03">See Statement of Policy on Treatment of Previously Public Documents.</E>
                    <SU>3</SU>
                    <FTREF/>
                     The Commission issued a final rule on CEII on February 21, 2003, defining CEII to include information about proposed facilities, as well as facilities already licensed or certificated by the Commission, and to exclude information that simply identified the location of the infrastructure. 
                    <E T="03">See</E>
                     Order No. 630.
                    <SU>4</SU>
                    <FTREF/>
                     The final rule also established the position of CEII Coordinator. The Commission issued Order No. 630-A on July 23, 2003,
                    <SU>5</SU>
                    <FTREF/>
                     which made several minor procedural changes and clarifications, added a reference in the regulation regarding the filing of Non-Internet Public (NIP) information, a term first described in Order No. 630,
                    <SU>6</SU>
                    <FTREF/>
                     and added a commitment to review the effectiveness of the new process after six months.
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         66 FR 52917 (Oct. 18, 2001), 97 FERC ¶ 61,130 (2001). 
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         68 FR 9857, FERC Stats. &amp; Regs. ¶ 31,140 (Mar. 3, 2003). 
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         68 FR 46456, FERC Stats. &amp; Regs. ¶ 31,147 (Aug. 6, 2003) 
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         NIP information includes location maps and diagrams that do not rise to the level of CEII. Order No. 630 provided the following examples of NIP: “(1) USGS 7.5 minute topographic maps showing the location of pipelines, dams, or other aboveground facilities, (2) alignment sheets showing the location of pipeline and aboveground facilities, right of way dimensions, and extra work areas; (3) drawings showing site or project boundaries, footprints, building locations and reservoir extent; and (4) general location maps.” 68 FR 9857, FERC Stats. &amp; Regs. ¶ 31,140. 
                    </P>
                </FTNT>
                <P>
                    3. Simultaneous with the issuance of the September 21 Order, the Commission issued a notice of proposed rulemaking (NOPR) in Docket No. RM06-23-000.
                    <SU>7</SU>
                    <FTREF/>
                     In the September 21 NOPR, the Commission sought comments on the revisions to its regulations to: (1) Allow an annual certification for repeat requesters; (2) allow an authorized representative of an organization to execute an NDA on behalf of the organization's employees; (3) include a fee provision; (4) respond to CEII requests by letters from the CEII Coordinator rather than by Commission orders with rights to rehearing; and (5) allow landowners access to alignment sheets for the routes across or in the vicinity of their properties. The September 21 NOPR also proposed to narrow the scope of information on Commission forms that are defined as containing CEII and proposed to abolish the NIP designation. 
                </P>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         71 FR 58,325 (October 3, 2006), FERC Stats. &amp; Regs. ¶ 32,607 (2006) (September 21 NOPR). 
                    </P>
                </FTNT>
                <HD SOURCE="HD2">Requests for Rehearing </HD>
                <P>
                    4. On October 23, 2006, EEI filed a timely request for rehearing of the September 21 Order, and requested that the Commission revoke its September 21 Order and reissue it as a new notice of proposed rulemaking to be considered with the September 21 NOPR. EEI alleged that the Commission did not provide the due process protections of the Administrative 
                    <PRTPAGE P="18573"/>
                    Procedure Act (APA), 5 U.S.C. 553, because the September 21 Order: (1) Modified the definition of CEII without proper notice and comment; (2) combined the notice and opportunity to comment with the notice of release; and (3) permitted the CEII Coordinator to enforce the CEII regulations by rejecting applications if information is mislabeled or legal justifications for CEII are not provided. 
                </P>
                <P>5. On November 2, 2006, the California State Agencies filed an untimely request for reconsideration. The California State Agencies requested that the CEII Coordinator allow flexibility to allow state agencies to execute non-disclosure agreements which depart from the standard state agency NDA found on the Commission's Web site. The California State Agencies further requested that the Commission amend its CEII regulations to exclude state agencies from the requirement of showing a need for access in their CEII requests, and to require the CEII Coordinator to grant state agencies access to CEII upon receiving a completed CEII request, including an executed NDA in a format acceptable to the Commission. </P>
                <HD SOURCE="HD2">Discussion </HD>
                <HD SOURCE="HD3">Procedural Issues </HD>
                <P>
                    6. The California State Agencies' request for reconsideration is equivalent to an untimely request for rehearing.
                    <SU>8</SU>
                    <FTREF/>
                     Rule 713 of the Commission's Rules of Practice and Procedure requires that requests for rehearing be made within thirty days of the date of the order.
                    <SU>9</SU>
                    <FTREF/>
                     Rule 713(a)(1) provides that the rule is applicable “to any request for rehearing of a final Commission decision or other final order.”
                    <SU>10</SU>
                    <FTREF/>
                     The final date for filing a request for rehearing of the September 21 Order was October 23, 2006,
                    <SU>11</SU>
                    <FTREF/>
                     a deadline not met by the California State Agencies. However, the California State Agencies also filed their “Comments and Request for Reconsideration” in response to the September 21 NOPR. Their comments address issues raised in the September 21 NOPR and will be considered in that proceeding. 
                </P>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         We decline to treat the request for rehearing as a request for reconsideration. Granting such a request would in effect treat the rehearing request as if it had been timely filed. 
                        <E T="03">See Midwest Independent Transmission System Operator, Inc.,</E>
                         112 FERC ¶ 61,211 at P 10 (2005); 
                        <E T="03">Golden Valley Power Company,</E>
                         114 FERC ¶ 61,212 at P 6 (2006). 
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         18 CFR 385.713 (2006). 
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         18 CFR 385.713(a)(1) (2006). 
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         The expiration of the thirty-day period, October 21, 2006, fell on a Saturday; therefore, the filing deadline for requests for rehearing was October 23, 2006, the next business day. 
                    </P>
                </FTNT>
                <HD SOURCE="HD2">EEI's Request for Rehearing </HD>
                <HD SOURCE="HD3">Clarification of the Definition of CEII </HD>
                <P>
                    7. EEI's contention that any modification to the definition of CEII is substantive is without merit. The APA provides exemptions to its notice and comment rulemaking requirements. 
                    <E T="03">See</E>
                     5 U.S.C. 553(b)(A). Specifically, interpretative rules, general statements of policy, or rules of agency organization, procedure, or practice are exempt. 
                    <E T="03">Id.</E>
                     As the Commission's September 21 Order interprets its definition of CEII, it is not a substantive change requiring notice and comment. The Commission may interpret and clarify its regulations without making a substantive change. Courts have found that agency rules explaining terms in statutes and regulations are interpretive.
                    <SU>12</SU>
                    <FTREF/>
                     Courts have also held that rules that merely restate existing duties, rather than creating new duties, are interpretive.
                    <SU>13</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         
                        <E T="03">See, e.g., American Postal Workers Union</E>
                         v. 
                        <E T="03">United States Postal Service</E>
                        , 707 F.2d 548, 559-60 (D.C. Cir. 1983) (finding that the postal service's new method of calculating retirement benefits was interpretive because adoption of the method turned on the agency's understanding of the statutory term “average pay”), 
                        <E T="03">cert. denied</E>
                        , 465 U.S. 1100 (1984). 
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         
                        <E T="03">See, e.g., General Motors Corp.</E>
                         v. 
                        <E T="03">Ruckelshaus</E>
                        , 742 F.2d 1561, 1565 (D.C. Cir. 1984) (finding interpretive a rule that restated consistent agency practice based on the Environmental Protection Agency's understanding of the recall provision of the Clean Air Act), 
                        <E T="03">cert. denied</E>
                        , 471 U.S. 1074 (1985).
                    </P>
                </FTNT>
                <P>
                    8. A clarification “does not * * *  become an amendment merely because it supplies crisper and more detailed lines than the authority being interpreted.”
                    <SU>14</SU>
                    <FTREF/>
                     Previously, the regulation stated that “Critical energy infrastructure information means information about proposed or existing critical infrastructure that: (i) Relates to the production, generation, transportation, transmission, or distribution of energy; (ii) Could be useful to a person in planning an attack on critical infrastructure; (iii) Is exempt from mandatory disclosure under the Freedom of Information Act, 5 U.S.C. 552; and (iv) Does not simply give the location of the critical infrastructure.” 18 CFR 388.113(c)(1). The September 21 Order explained that “information about proposed or existing critical infrastructure” means “specific engineering, vulnerability, or detailed design information about proposed or existing critical infrastructure.”
                    <SU>15</SU>
                    <FTREF/>
                     The clarification explained the existing term “information.” The clarification serves to advise the public of the Commission's construction of the term information as defined in Order No. 630. The September 21 Order also clarified the meaning of “relates to the production, generation, transportation, transmission, or distribution of energy.” The September 21 Order advised the public that it is the “details about the production, generation, transportation, transmission, or distribution of energy” that the Commission deems CEII.
                    <SU>16</SU>
                    <FTREF/>
                     These explanations and clarifications are merely interpretations and notice and comment are unnecessary. 
                </P>
                <FTNT>
                    <P>
                        <SU>14</SU>
                         
                        <E T="03">American Mining Congress</E>
                         v. 
                        <E T="03">Mine Safety &amp; Health Admin.</E>
                        , 995 F.2d 1106, 1112 (D.C. Cir. 1993).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>15</SU>
                         September 21 Order at P 6.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>16</SU>
                         
                        <E T="03">Id</E>
                        .
                    </P>
                </FTNT>
                <HD SOURCE="HD2">Combination of the Notice and Opportunity to Comment With the Notice of Release </HD>
                <P>9. EEI is mistaken that the combination of the notice and opportunity to comment with the notice of release eliminates due process rights of CEII submitters or reduces the notice from ten days to five days. Pursuant to 18 CFR 388.112, any person submitting documents to the Commission may request special treatment of some or all of the information found in the documents. Paragraph (d) of this section provides the standards for notifying the submitter of a request for the information, and states:</P>
                <EXTRACT>
                    <P>When a FOIA or CEII requester seeks a document for which privilege or CEII status has been claimed, or when the Commission itself is considering release of such information, the Commission official who will decide whether to release the information will notify the person who submitted the document and give the person an opportunity (at least five calendar days) in which to comment in writing on the request. A copy of this notice will be sent to the requester.</P>
                </EXTRACT>
                <P>Paragraph (e) of this section provides the standards for notification prior to release of documents for which privileged treatment was requested, and states:</P>
                <EXTRACT>
                    <P>Notice of a decision by the Director, Office of External Affairs, the Chairman of the Commission, the General Counsel or General Counsel's designee, a presiding officer in a proceeding under part 385 of this chapter, or any other appropriate official to deny a claim of privilege in whole or in part, or to make a limited release of CEII, will be given to any person claiming that information is privileged or CEII no less than five days before public disclosure. The notice will briefly explain why the person's objections to disclosure are not sustained by the Commission. A copy of this notice will be sent to the FOIA or CEII requester.</P>
                </EXTRACT>
                <P>
                    Thus, when the submitter of information requests confidential or CEII treatment of that information and opposes its release, the Commission 
                    <PRTPAGE P="18574"/>
                    will, by regulation, notify the submitter at least five days prior to disclosure. This allows the submitter an opportunity to respond, as well as to pursue an injunction against release in district court. 
                </P>
                <P>
                    10. The Commission's regulations do not require separation of the opportunity to comment and notice of release. However, it was the Commission's practice in processing CEII requests to issue these notifications separately. As the Commission explained in its September 21 Order, combining the two will increase the efficiency of processing CEII requests. 
                    <E T="03">See</E>
                     September 21 Order at P 9-10. But those opposing release will continue to have ten days of notice before the information is released. 
                </P>
                <P>
                    11. Contrary to EEI's assertion, there is no inconsistency in the application of the rules to CEII and FOIA requests. The combined notice that the Commission sends pursuant to the September 21 Order explains that a submitter has an opportunity (5-day minimum) to submit timely comments opposing release. 
                    <E T="03">See</E>
                     18 CFR 388.112(d). It further explains that if the submitter provides timely comments, he or she will be notified in advance of the release of any information in accordance with 18 CFR 388.112(e) (another 5-day minimum). In other words, if the submitter provides comments, a second notice of release follows the first (a total of 10-day minimum). In the event timely comments opposing release are not received, the combined notice constitutes notice of release of the specified document in accordance with 18 CFR 388.112(e), subject to an appropriate non-disclosure agreement. The combined opportunity to comment and notice of release does not reduce the submitter's opportunity to respond or to pursue judicial relief. 
                </P>
                <HD SOURCE="HD2">Requirements To Comply With Procedural Requirements </HD>
                <P>
                    12. The September 21 Order states that an application will be rejected in its entirety if information is mislabeled as CEII or a legal justification for CEII is not provided. The purpose of that rule is to dissuade applicants from carelessly using the CEII designation because such misuse prevents interested parties and other deserving members of the public from accessing needed information in the timeliest manner. As the Commission said in the September 21 NOPR, the “Commission retains its concern for CEII filing abuses and will take action against applicants or parties who knowingly misfile information as CEII.” 
                    <SU>17</SU>
                    <FTREF/>
                     The Commission disagrees with EEI's assertion that rejection is unacceptably harsh. Applications are frequently rejected for failure to comply with procedural requirements. 
                    <E T="03">See</E>
                    , 
                    <E T="03">e.g.</E>
                    , 
                    <E T="03">ANR Pipeline Co.</E>
                    , 103 FERC ¶ 61,261 at P 8 (2003) (rejecting filing without prejudice to filing a fully supported application in accordance with the Commission's regulations). In instances in which documents are rejected for filing, the rejection is usually without prejudice and no substantive rights are lost. 
                    <E T="03">Id.</E>
                     The application must merely be refiled in accordance with the procedural requirements. That is not harsh, but rather promotes the proper use of the CEII designation. 
                </P>
                <FTNT>
                    <P>
                        <SU>17</SU>
                         September 21 NOPR at P 17. 
                    </P>
                </FTNT>
                <P>
                    <E T="03">The Commission orders:</E>
                </P>
                <P>EEI's request for rehearing is denied as described above. The California State Agencies' request for reconsideration is rejected in this docket as untimely filed. </P>
                <SIG>
                    <P>By the Commission. </P>
                    <NAME> Philis J. Posey, </NAME>
                    <TITLE>Acting Secretary.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC> [FR Doc. E7-7005 Filed 4-12-07; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 6717-01-P </BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF HOMELAND SECURITY </AGENCY>
                <SUBAGY>Bureau of Customs and Border Protection </SUBAGY>
                <CFR>19 CFR Part 123 </CFR>
                <SUBJECT>Advance Electronic Presentation of Cargo Information for Truck Carriers Required To Be Transmitted Through ACE Truck Manifest at Ports in the States of Vermont, North Dakota and New Hampshire </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Customs and Border Protection, Department of Homeland Security. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>Pursuant to section 343(a) of the Trade Act of 2002 and implementing regulations, truck carriers and other eligible parties are required to transmit advance electronic truck cargo information to the Bureau of Customs and Border Protection (CBP) through a CBP-approved electronic data interchange. In a previous document, CBP designated the Automated Commercial Environment (ACE) Truck Manifest System as the approved interchange and announced that the requirement that advance electronic cargo information be transmitted through ACE would be phased in by groups of ports of entry. This document announces that at all land border ports in Vermont and New Hampshire and at the land border ports in North Dakota in which ACE has not yet been required, truck carriers will be required to file electronic manifests through the ACE Truck Manifest System. </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Trucks entering the United States through land border ports of entry in the states of Vermont and New Hampshire and at the ports of St. John, Fortuna, Ambrose, Carbury, Noonan, Dunseith, Sherwood, Antler, Northgate, Westhope, and Portal in the state of North Dakota, will be required to transmit the advance information through the ACE Truck Manifest system effective July 12, 2007. </P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Mr. James Swanson, via e-mail at 
                        <E T="03">james.d.swanson@dhs.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Background </HD>
                <P>Section 343(a) of the Trade Act of 2002, as amended (the Act; 19 U.S.C. 2071 note), required that CBP promulgate regulations providing for the mandatory transmission of electronic cargo information by way of a CBP-approved electronic data interchange (EDI) system before the cargo is brought into or departs 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. </P>
                <P>
                    On December 5, 2003, CBP published in the 
                    <E T="04">Federal Register</E>
                     (68 FR 68140) a final rule to effectuate the provisions of the Act. In particular, a new section 123.92 (19 CFR 123.92) was added to the regulations to implement the inbound truck cargo provisions. Section 123.92 describes the general requirement that, in the case of any inbound truck required to report its arrival under section 123.1(b), if the truck will have commercial cargo aboard, CBP must electronically receive certain information regarding that cargo through a CBP-approved EDI system no later than 1 hour prior to the carrier's reaching the first port of arrival in the United States. For truck carriers arriving with shipments qualified for clearance under the FAST (Free and Secure Trade) program, section 123.92 provides that CBP must electronically receive such cargo information through the CBP-approved EDI system no later than 30 minutes prior to the carrier's reaching the first port of arrival in the United States. 
                    <PRTPAGE P="18575"/>
                </P>
                <HD SOURCE="HD1">ACE Truck Manifest Test </HD>
                <P>
                    On September 13, 2004, CBP published a notice in the 
                    <E T="04">Federal Register</E>
                     (69 FR 55167) announcing a test allowing participating Truck Carrier Accounts to transmit electronic manifest data for inbound cargo through ACE, with any such transmissions automatically complying with advance cargo information requirements as provided in section 343(a) of the Trade Act of 2002. Truck Carrier Accounts participating in the test were given the ability to electronically transmit the truck manifest data and obtain release of their cargo, crew, conveyances, and equipment via the ACE Portal or electronic data interchange messaging. 
                </P>
                <P>
                    A series of notices announced additional deployments of the test, with deployment sites being phased in as clusters. Clusters were announced in the following notices published in the 
                    <E T="04">Federal Register</E>
                    : 70 FR 30964 (May 31, 2005); 70 FR 43892 (July 29, 2005); 70 FR 60096 (October 14, 2005); 71 FR 3875 (January 24, 2006); 71 FR 23941 (April 25, 2006); 71 FR 42103 (July 25, 2006), 71 FR 77404 (December 26, 2006) and 72 FR 7058 (February 14, 2007). 
                </P>
                <P>
                    CBP continues to test ACE at various ports. CBP will continue, as necessary, to announce in subsequent notices in the 
                    <E T="04">Federal Register</E>
                     the deployment of the ACE truck manifest system test at additional ports. 
                </P>
                <HD SOURCE="HD1">Designation of ACE Truck Manifest System as the Approved Data Interchange System </HD>
                <P>In a notice published October 27, 2006 (71 FR 62922), CBP designated the Automated Commercial Environment (ACE) Truck Manifest System as the approved EDI for the transmission of required data and announced that the requirement that advance electronic cargo information be transmitted through ACE would be phased in by groups of ports of entry. </P>
                <P>ACE will be phased in as the required transmission system at some ports even while it is still being tested at other ports. However, the use of ACE to transmit advance electronic truck cargo information will not be required in any port in which CBP has not first conducted the test. </P>
                <P>The October 27, 2006, document identified all land border ports in the states of Washington and Arizona and the ports of Pembina, Neche, Walhalla, Maida, Hannah, Sarles, and Hansboro in North Dakota as the first group of ports where use of the ACE Truck Manifest System is mandated. Subsequently, CBP announced on January 19, 2007 (72 FR 2435) that, after 90 days notice, the use of the ACE Truck Manifest System will be mandatory at all land border ports in the states of California, Texas and New Mexico. On February 23, 2007 (72 FR 8109), CBP announced that, again after 90 days notice, the ACE Truck Manifest System will be mandatory at all land border ports in Michigan and New York, as well. </P>
                <HD SOURCE="HD1">ACE Mandated at Land Border Ports of Entry in Vermont and New Hampshire and Identified Ports in North Dakota </HD>
                <P>
                    Applicable regulations (19 CFR 123.92(e)) require CBP, 90 days prior to mandating advance electronic information at a port of entry, to publish notice in the 
                    <E T="04">Federal Register</E>
                     informing affected carriers that the EDI system is in place and fully operational. Accordingly, CBP is announcing in this document that, effective 90 days from the date of publication of this notice, truck carriers entering the United States through land border ports of entry in the states of Vermont and New Hampshire and through the ports of St. John, Fortuna, Ambrose, Carbury, Noonan, Dunseith, Sherwood, Antler, Northgate, Westhope, and Portal, in the state of North Dakota, will be required to present advance electronic cargo information regarding truck cargo through the ACE Truck Manifest System. Together with the ports announced in 71 FR 62922, use of the ACE Truck Manifest System will, 90 days from the date of publication of this notice, be mandatory in all land border ports in the state of North Dakota, as well as the land border ports in the states of Vermont and New Hampshire. 
                </P>
                <P>Although other systems that have been deemed acceptable by CBP for transmitting advance truck manifest data will continue to operate and may still be used in the normal course of business for purposes other than transmitting advance truck manifest data, use of systems other than ACE will no longer satisfy advance electronic cargo information requirements at the ports of entry announced in this document as of July 12, 2007. </P>
                <HD SOURCE="HD1">Compliance Sequence </HD>
                <P>
                    CBP will be publishing subsequent notices in the 
                    <E T="04">Federal Register</E>
                     as it phases in the requirement that truck carriers utilize the ACE system to present advance electronic truck cargo information at other ports. ACE will be phased in as the mandatory EDI system at the ports identified below in the sequential order in which they are listed. The sequential order provided below is somewhat different than that announced in the October 27, 2006, notice. Although further changes to this order are not currently anticipated, CBP will state in future notices if changes do occur. In any event, as mandatory ACE is phased in at these remaining ports, CBP will always provide 90 days' notice through publication in the 
                    <E T="04">Federal Register</E>
                     prior to requiring the use of ACE for the transmission of advance electronic truck cargo information at a particular group of ports. 
                </P>
                <P>The remaining ports at which the mandatory use of ACE will be phased in, listed in sequential order, are as follows: </P>
                <P>1. All land border ports in the states of Idaho and Montana. </P>
                <P>2. All land border ports in the state of Maine. </P>
                <P>3. All land border ports in the states of Alaska and Minnesota. </P>
                <SIG>
                    <DATED>Dated: April 6, 2007. </DATED>
                    <NAME>Deborah J. Spero, </NAME>
                    <TITLE>Acting Commissioner,  Customs and Border Protection.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC> [FR Doc. E7-6908 Filed 4-12-07; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 9111-14-P </BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF THE TREASURY </AGENCY>
                <SUBAGY>Internal Revenue Service </SUBAGY>
                <CFR>26 CFR Part 1 </CFR>
                <DEPDOC>[TD 9313] </DEPDOC>
                <RIN>RIN 1545-BG29 </RIN>
                <SUBJECT>Corporate Reorganizations; Additional Guidance on Distributions Under Sections 368(a)(1)(D) and 354(b)(1)(B); Correction </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Internal Revenue Service (IRS), Treasury. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Correcting amendment. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        This document contains a correction to temporary regulations (TD 9313) that were published in the 
                        <E T="04">Federal Register</E>
                         on Thursday, March 1, 2007 (72 FR 9262) providing guidance regarding the qualification of certain transactions as reorganizations described in section 368(a)(1)(D) where no stock and/or securities of the acquiring corporation are issued and distributed in the transaction. 
                    </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>This correcting amendment is effective April 13, 2007. </P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Bruce A. Decker at (202) 622-7550  (not a toll-free number). </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Background </HD>
                <P>
                    The temporary regulations that are the subject of this correction are under section 368 of the Internal Revenue Code. 
                    <PRTPAGE P="18576"/>
                </P>
                <HD SOURCE="HD1">Need for Correction </HD>
                <P>As published, temporary regulations (TD 9313) contain an error that may prove to be misleading and is in need of clarification. </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 26 CFR Part 1 </HD>
                    <P>Income taxes, Reporting and recordkeeping requirements.</P>
                </LSTSUB>
                <REGTEXT TITLE="26" PART="1">
                    <HD SOURCE="HD1">Correction of Publication </HD>
                    <AMDPAR>Accordingly, 26 CFR part 1 is corrected by making the following amendment: </AMDPAR>
                    <PART>
                        <HD SOURCE="HED">PART 1—INCOME TAXES </HD>
                    </PART>
                    <AMDPAR>
                        <E T="04">Paragraph 1.</E>
                         The authority citation for part 1 continues to read, in part, as follows: 
                    </AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>26 U.S.C. 7805 * * * </P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="26" PART="1">
                    <AMDPAR>
                        <E T="04">Par. 2.</E>
                         Section 1.368-2T is amended by revising paragraph (l)(2)(iv) to read as follows: 
                    </AMDPAR>
                    <SECTION>
                        <SECTNO>§ 1.368-2T </SECTNO>
                        <SUBJECT>Definition of terms (temporary). </SUBJECT>
                        <STARS/>
                        <P>(l) * * *</P>
                        <P>(2) * * *</P>
                        <P>
                            (iv) 
                            <E T="03">Exception.</E>
                             This paragraph (l)(2) does not apply to a transaction otherwise described in section 1.358-6(b)(2) or section 368(a)(1)(G) by reason of section 368(a)(2)(D). 
                        </P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <SIG>
                    <NAME>LaNita Van Dyke, </NAME>
                    <TITLE>Chief, Publications and Regulations Branch Legal Processing Division, Associate Chief Counsel (Procedure and Administration).</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. E7-6979 Filed 4-12-07; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4830-01-P </BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">PENSION BENEFIT GUARANTY CORPORATION </AGENCY>
                <CFR>29 CFR Parts 4022 and 4044 </CFR>
                <SUBJECT>Benefits Payable in Terminated Single-Employer Plans; Allocation of Assets in Single-Employer Plans; Interest Assumptions for Valuing and Paying Benefits </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Pension Benefit Guaranty Corporation. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The Pension Benefit Guaranty Corporation's regulations on Benefits Payable in Terminated Single-Employer Plans and Allocation of Assets in Single-Employer Plans prescribe interest assumptions for valuing and paying benefits under terminating single-employer plans. This final rule amends the regulations to adopt interest assumptions for plans with valuation dates in May 2007. Interest assumptions are also published on the PBGC's Web site (
                        <E T="03">http://www.pbgc.gov</E>
                        ). 
                    </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Effective May 1, 2007. </P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Catherine B. Klion, Manager, Regulatory and Policy Division, Legislative and Regulatory Department, Pension Benefit Guaranty Corporation, 1200 K Street, NW., Washington, DC 20005, 202-326-4024. (TTY/TDD users may call the Federal relay service toll-free at 1-800-877-8339 and ask to be connected to 202-326-4024.) </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The PBGC's regulations prescribe actuarial assumptions—including interest assumptions—for valuing and paying plan benefits of terminating single-employer plans covered by title IV of the Employee Retirement Income Security Act of 1974. The interest assumptions are intended to reflect current conditions in the financial and annuity markets. </P>
                <P>Three sets of interest assumptions are prescribed: (1) A set for the valuation of benefits for allocation purposes under section 4044 (found in Appendix B to Part 4044), (2) a set for the PBGC to use to determine whether a benefit is payable as a lump sum and to determine lump-sum amounts to be paid by the PBGC (found in Appendix B to Part 4022), and (3) a set for private-sector pension practitioners to refer to if they wish to use lump-sum interest rates determined using the PBGC's historical methodology (found in Appendix C to Part 4022). </P>
                <P>This amendment (1) adds to Appendix B to Part 4044 the interest assumptions for valuing benefits for allocation purposes in plans with valuation dates during May 2007, (2) adds to Appendix B to Part 4022 the interest assumptions for the PBGC to use for its own lump-sum payments in plans with valuation dates during May 2007, and (3) adds to Appendix C to Part 4022 the interest assumptions for private-sector pension practitioners to refer to if they wish to use lump-sum interest rates determined using the PBGC's historical methodology for valuation dates during May 2007. </P>
                <P>For valuation of benefits for allocation purposes, the interest assumptions that the PBGC will use (set forth in Appendix B to part 4044) will be 5.20 percent for the first 20 years following the valuation date and 4.87 percent thereafter. These interest assumptions represent an increase (from those in effect for April 2007) of 0.21 percent for the first 20 years following the valuation date and 0.21 percent for all years thereafter. </P>
                <P>The interest assumptions that the PBGC will use for its own lump-sum payments (set forth in Appendix B to part 4022) will be 3.00 percent for the period during which a benefit is in pay status and 4.00 percent during any years preceding the benefit's placement in pay status. These interest assumptions represent an increase (from those in effect for April 2007) of 0.25 percent in the immediate annuity rate and are otherwise unchanged. For private-sector payments, the interest assumptions (set forth in Appendix C to part 4022) will be the same as those used by the PBGC for determining and paying lump sums (set forth in Appendix B to part 4022). </P>
                <P>The PBGC has determined that notice and public comment on this amendment are impracticable and contrary to the public interest. This finding is based on the need to determine and issue new interest assumptions promptly so that the assumptions can reflect current market conditions as accurately as possible. </P>
                <P>Because of the need to provide immediate guidance for the valuation and payment of benefits in plans with valuation dates during May 2007, the PBGC finds that good cause exists for making the assumptions set forth in this amendment effective less than 30 days after publication. </P>
                <P>The PBGC has determined that this action is not a “significant regulatory action” under the criteria set forth in Executive Order 12866. </P>
                <P>Because no general notice of proposed rulemaking is required for this amendment, the Regulatory Flexibility Act of 1980 does not apply. See 5 U.S.C. 601(2). </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects </HD>
                    <CFR>29 CFR Part 4022 </CFR>
                    <P>Employee benefit plans, Pension insurance, Pensions, Reporting and recordkeeping requirements. </P>
                    <CFR>29 CFR Part 4044 </CFR>
                    <P>Employee benefit plans, Pension insurance, Pensions.</P>
                </LSTSUB>
                <REGTEXT TITLE="29" PART="4022">
                    <AMDPAR>In consideration of the foregoing, 29 CFR parts 4022 and 4044 are amended as follows: </AMDPAR>
                    <PART>
                        <HD SOURCE="HED">PART 4022—BENEFITS PAYABLE IN TERMINATED SINGLE-EMPLOYER PLANS </HD>
                    </PART>
                    <AMDPAR>1. The authority citation for part 4022 continues to read as follows: </AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>29 U.S.C. 1302, 1322, 1322b, 1341(c)(3)(D), and 1344. </P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="29" PART="4022">
                    <AMDPAR>
                        2. In appendix B to part 4022, Rate Set 163, as set forth below, is added to the table. 
                        <PRTPAGE P="18577"/>
                    </AMDPAR>
                    <HD SOURCE="HD1">Appendix B to Part 4022—Lump Sum Interest Rates for PBGC Payments </HD>
                    <STARS/>
                    <GPOTABLE COLS="9" OPTS="L1,tp0,i1" CDEF="10C,10C,10C,10C,10C,10C,10C,10C,10C">
                        <TTITLE> </TTITLE>
                        <BOXHD>
                            <CHED H="1">Rate set</CHED>
                            <CHED H="1">For plans with a valuation date</CHED>
                            <CHED H="2">On or after</CHED>
                            <CHED H="2">Before</CHED>
                            <CHED H="1">
                                Immediate 
                                <LI>annuity rate </LI>
                                <LI>(percent)</LI>
                            </CHED>
                            <CHED H="1">
                                Deferred annuities
                                <LI>(percent)</LI>
                            </CHED>
                            <CHED H="2">
                                <E T="03">i</E>
                                <E T="52">1</E>
                            </CHED>
                            <CHED H="2">
                                <E T="03">i</E>
                                <E T="52">2</E>
                            </CHED>
                            <CHED H="2">
                                <E T="03">i</E>
                                <E T="52">3</E>
                            </CHED>
                            <CHED H="2">
                                <E T="03">n</E>
                                <E T="52">1</E>
                            </CHED>
                            <CHED H="2">
                                <E T="03">n</E>
                                <E T="52">2</E>
                            </CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="22"> </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="28">*         *         *         *         *         *         *</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">163</ENT>
                            <ENT>5-1-07</ENT>
                            <ENT>6-1-07</ENT>
                            <ENT>3.00</ENT>
                            <ENT>4.00</ENT>
                            <ENT>4.00</ENT>
                            <ENT>4.00</ENT>
                            <ENT>7</ENT>
                            <ENT>8</ENT>
                        </ROW>
                    </GPOTABLE>
                </REGTEXT>
                <REGTEXT TITLE="29" PART="4022">
                    <AMDPAR>3. In appendix C to part 4022, Rate Set 163, as set forth below, is added to the table. </AMDPAR>
                    <HD SOURCE="HD1">Appendix C to Part 4022—Lump Sum Interest Rates for Private-Sector Payments </HD>
                    <STARS/>
                    <GPOTABLE COLS="9" OPTS="L1,tp0,i1" CDEF="10C,10C,10C,10C,10C,10C,10C,10C,10C">
                        <TTITLE> </TTITLE>
                        <BOXHD>
                            <CHED H="1">Rate set</CHED>
                            <CHED H="1">For plans with a valuation date</CHED>
                            <CHED H="2">On or after</CHED>
                            <CHED H="2">Before</CHED>
                            <CHED H="1">
                                Immediate 
                                <LI>annuity rate </LI>
                                <LI>(percent)</LI>
                            </CHED>
                            <CHED H="1">
                                Deferred annuities
                                <LI>(percent)</LI>
                            </CHED>
                            <CHED H="2">
                                <E T="03">i</E>
                                <E T="52">1</E>
                            </CHED>
                            <CHED H="2">
                                <E T="03">i</E>
                                <E T="52">2</E>
                            </CHED>
                            <CHED H="2">
                                <E T="03">i</E>
                                <E T="52">3</E>
                            </CHED>
                            <CHED H="2">
                                <E T="03">n</E>
                                <E T="52">1</E>
                            </CHED>
                            <CHED H="2">
                                <E T="03">n</E>
                                <E T="52">2</E>
                            </CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="22"> </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="28">*         *         *         *         *         *         *</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">163</ENT>
                            <ENT>5-1-07</ENT>
                            <ENT>6-1-07</ENT>
                            <ENT>3.00</ENT>
                            <ENT>4.00</ENT>
                            <ENT>4.00</ENT>
                            <ENT>4.00</ENT>
                            <ENT>7</ENT>
                            <ENT>8</ENT>
                        </ROW>
                    </GPOTABLE>
                </REGTEXT>
                <REGTEXT TITLE="29" PART="4044">
                    <PART>
                        <HD SOURCE="HED">PART 4044—ALLOCATION OF ASSETS IN SINGLE-EMPLOYER PLANS </HD>
                    </PART>
                    <AMDPAR>4. The authority citation for part 4044 continues to read as follows: </AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>29 U.S.C. 1301(a), 1302(b)(3), 1341, 1344, 1362. </P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="29" PART="4044">
                    <AMDPAR>5. In appendix B to part 4044, a new entry for May 2007, as set forth below, is added to the table. </AMDPAR>
                    <HD SOURCE="HD1">Appendix B to Part 4044—Interest Rates Used to Value Benefits </HD>
                    <STARS/>
                    <GPOTABLE COLS="07" OPTS="L1,tp0,i1" CDEF="s25,10,10,10,10,10,10">
                        <TTITLE> </TTITLE>
                        <BOXHD>
                            <CHED H="1">For valuation dates occurring in the month—</CHED>
                            <CHED H="1">
                                The values of 
                                <E T="03">i</E>
                                <E T="52">t</E>
                                 are:
                            </CHED>
                            <CHED H="2">
                                <E T="03">i</E>
                                <E T="52">t</E>
                            </CHED>
                            <CHED H="2">
                                for 
                                <E T="03">t</E>
                                 =
                            </CHED>
                            <CHED H="2">
                                <E T="03">i</E>
                                <E T="52">t</E>
                            </CHED>
                            <CHED H="2">
                                for 
                                <E T="03">t</E>
                                 =
                            </CHED>
                            <CHED H="2">
                                <E T="03">i</E>
                                <E T="52">t</E>
                            </CHED>
                            <CHED H="2">
                                for 
                                <E T="03">t</E>
                                 =
                            </CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="22"> </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="28">*         *         *         *         *         *         *</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">May 2007</ENT>
                            <ENT>.0520</ENT>
                            <ENT>1-20</ENT>
                            <ENT>.0487</ENT>
                            <ENT>&gt;20</ENT>
                            <ENT>N/A</ENT>
                            <ENT>N/A</ENT>
                        </ROW>
                    </GPOTABLE>
                </REGTEXT>
                <SIG>
                    <DATED/>
                    <P>Issued in Washington, DC, on this 10th day of April 2007. </P>
                    <NAME>Vincent K. Snowbarger, </NAME>
                    <TITLE>Interim Director, Pension Benefit Guaranty Corporation. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC> [FR Doc. E7-7071 Filed 4-12-07; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 7709-01-P </BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF THE INTERIOR </AGENCY>
                <SUBAGY>Minerals Management Service </SUBAGY>
                <CFR>30 CFR Part 250 </CFR>
                <RIN>RIN 1010-AD10 </RIN>
                <SUBJECT>Oil, Gas, and Sulphur Operations in the Outer Continental Shelf (OCS)—Plans and Information—Protection of Marine Mammals and Threatened and Endangered Species </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Minerals Management Service (MMS), Interior. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This final rule requires lessees of Federal oil and gas leases in the OCS to provide information on how they will conduct their proposed activities in a manner consistent with provisions of the Endangered Species Act (ESA) and the Marine Mammal Protection Act (MMPA). It identifies environmental, monitoring, and mitigation information that lessees must submit with plans for exploration and development and production. This final rulemaking specifies what information the MMS needs to ensure compliance with the OCSLA, the ESA, and the MMPA. The final rule will help assure that lessees conduct their activities in a manner consistent with the provisions of the ESA and the MMPA. </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        <E T="03">Effective Date:</E>
                         This regulation is effective as of May 14, 2007. 
                    </P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Judy Wilson, Chief, Environmental Compliance Unit, Environmental Division, (703) 787-1075. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    The OCS Lands Act (OCSLA) at 43 U.S.C. 1333, mandates “The Constitution and laws and civil and political jurisdiction of the United States (U.S.) are extended to the subsoil and seabed of the OCS and to all artificial islands, and all installations and other devices permanently or temporarily attached to the seabed which may be erected thereon for the purpose of exploring for, developing, or producing resources therefrom, or any such installation or other device (other than a ship or vessel) for the purpose of transporting such resources * * *” Those laws include the ESA and the MMPA. Every lease the MMS issues contains a requirement that the lessee must comply with applicable laws. The OCSLA at 43 U.S.C. 1332, requires “* * * expeditious and orderly development, subject to environmental safeguards * * *” 
                    <PRTPAGE P="18578"/>
                </P>
                <P>The MMS, as a Federal agency, has a duty to carry out agency actions and authorizations in a manner that is not likely to jeopardize species listed under the ESA or result in the destruction or adverse modification of designated critical habitat, or have more than a negligible impact on marine mammals or the availability of marine mammals for subsistence use under the MMPA. </P>
                <P>Section 7(a)(1) of the ESA, 16 U.S.C. 1536(a)(1), mandates that the “Secretary shall review other programs administered by him and utilize such programs in furtherance of the purposes of this Act. All other Federal agencies shall, in consultation with and with the assistance of the Secretary, utilize their authorities in furtherance of the purposes of this Act by carrying out programs for the conservation of endangered species and threatened species listed pursuant to section 4 of this Act.” Therefore, based on all of the above, it is the responsibility of the MMS to require that lessees and operators conduct their activities in a manner that is consistent with the provisions of the ESA and the MMPA. </P>
                <P>For these reasons, the MMS is amending 30 CFR part 250, subpart B—Plans and Information, to specify that lessees must provide specific environmental information concerning threatened or endangered species listed under the ESA and marine mammals protected under the MMPA. Information in the form of impact-monitoring data will be required when submitting plans for approval, and also while operating on the OCS. The MMS must often require mitigation measures and monitoring by lessees operating on the OCS. Mitigation and monitoring must be non-discretionary if the operations we permit may result in an incidental take. If incidental take were to occur, the Services would not consider incidental take prohibited under the ESA providing the take is in compliance with the terms and conditions of the incidental take statement. The ESA defines the term “take” as “to harass, harm, pursue, hunt, shoot, wound, kill, trap, capture, or collect, or to attempt to engage in any such conduct.” </P>
                <P>In order to monitor the incidental take of listed species, the ESA section 7 regulations require reporting. Monitoring programs resulting from the ESA section 7 (interagency) consultations are designed to: </P>
                <P>(a) Detect adverse effects resulting from a proposed action; </P>
                <P>(b) Assess the actual level of incidental take in comparison with the level of anticipated incidental take documented in the biological opinion; </P>
                <P>(c) Detect when the level of anticipated incidental take is exceeded; and </P>
                <P>(d) Determine the effectiveness of reasonable and prudent measures and their implementing terms and conditions.</P>
                <P>In addition, there can be no relief from the ESA section 9 prohibitions regarding listed marine mammals until take of marine mammals has been authorized under the MMPA and its 1994 amendments. The MMPA defines take as “to harass (injure or disturb), hunt, capture, kill, or attempt to harass, hunt, capture or kill any marine mammal.” The MMPA has mitigation, monitoring and reporting requirements similar to the ESA. </P>
                <P>The MMS has been required by the National Oceanic and Atmospheric Administration (NOAA) through several ESA section 7 consultations to adopt mitigation, monitoring, and reporting requirements. These non-discretionary requirements are related to mitigating the effects of noise, vessel traffic, and marine trash and debris (specific measures have been included in Alaska OCS Region project specific permits or Gulf of Mexico OCS Region lease stipulations and Notices to Lessees (NTLs), such as: Vessel Strike Avoidance and Injured/Dead Protected Species, Marine Trash and Debris Awareness and Elimination, Structure Removal Operations, and Implementation of Seismic Survey Mitigation). The ESA implementing regulations at 50 CFR 402.14(i)(3) state that, “In order to monitor the impacts of incidental take, the Federal agency or any applicant must report the progress of the action and its impact on the species to the Service as specified in the incidental take statement.” The MMS must have the Office of Management and Budget (OMB) Information Collection (IC) approval before collecting and using the information required by the ESA section 7 consultations. The MMS has received the OMB IC approval for the non-discretionary requirements identified above (see the Paperwork Reduction Act (PRA) discussion under Procedural Matters). </P>
                <P>These regulatory changes to subpart B will incorporate the general ESA information requirements. The revisions to subpart B require industry to comply with specific environmental laws in a general way. The final rule will assure that lessees mitigate for potential takes of protected species and monitor for potential takes of protected species to aid in assessing the actual level of take and the effectiveness of the mitigation. </P>
                <P>The information requirement under this final rule will not substitute for a Letter of Authorization or Incidental Harassment Authorization. The MMS does not have authority through the reporting requirements to authorize the taking of any marine mammal under the MMPA. This final rule does not enable the MMS to make determinations under the ESA or the MMPA on the level or significance of takings that could occur or otherwise substitute the MMS judgment for the Fish and Wildlife Service (FWS) or the National Marine Fisheries Service (NMFS) of the NOAA. The purpose of this final rule is to require that lessees describe how they will mitigate the potential for takes to occur, monitor for potential takes, and report any takes, should they occur. </P>
                <HD SOURCE="HD1">Changes to Subpart B Regulations </HD>
                <P>The requirements concerning the contents of the Exploration Plans (EP) are amended in the following sections: </P>
                <P>• § 250.216(a)—biological environmental reports must address federally listed species and designated critical habitat as well as marine mammals; </P>
                <P>• § 250.221(b)—monitoring systems must address federally listed species and marine mammals if there is reason to believe the exploration activities may result in an incidental take; </P>
                <P>• § 250.223—mitigation measures must address federally listed species and marine mammals if there is reason to believe the exploration activities may result in an incidental take; and </P>
                <P>• § 250.227—environmental impact analysis information must be as detailed as necessary to support the MMS's effort to comply with the ESA and the MMPA by analyzing the potential direct and indirect impacts of exploration activities on federally listed species and marine mammals. </P>
                <P>The requirements concerning the contents of the Development and Production Plans (DPP) and the Development Operations Coordination Documents (DOCD) are amended in the following sections: </P>
                <P>• § 250.247(a)—biological environmental reports must address federally listed species and designated critical habitat as well as marine mammals; </P>
                <P>• § 250.252(b)—monitoring systems must address federally listed species and marine mammals if there is reason to believe the development and production activities may result in an incidental take; </P>
                <P>
                    • § 250.254—mitigation measures must address federally listed species and marine mammals if there is reason to believe the development and 
                    <PRTPAGE P="18579"/>
                    production activities may result in an incidental take; 
                </P>
                <P>• § 250.261—environmental impact analysis information must be as detailed as necessary to support our effort to comply with the ESA and the MMPA by analyzing the potential direct and indirect impacts of development and production activities on federally listed species and marine mammals; </P>
                <P>• § 250.270—correcting the citation at § 250.270(a)(1)(i) that currently reads “267(a)(1),” to “250.267(a)(1),”; and </P>
                <P>• § 250.282—the post-approval requirements for the EP, the DPP, and the DOCD are amended to require that post-approval monitoring programs must include monitoring in accordance with the ESA and the MMPA requirements. </P>
                <HD SOURCE="HD1">Discussion and Analysis of Comments to the Proposed Rule </HD>
                <P>The MMS published a proposed rule on September 6, 2005 (70 FR 52953). The public comment period ended November 7, 2005. On October 25, 2005, we published notice of a 60-day extension to the comment period (January 6, 2006) because of the damage and subsequent flooding in the Gulf of Mexico (GOM) area caused by Hurricanes Katrina and Rita (70 FR 61589). The extension provided additional time to the oil and gas industry for reviewing and preparing comments to the rule. Comments on the proposed rule came from the FWS, the Humane Society of the United States, the Alaska Eskimo Whaling Commission, the Center for Regulatory Effectiveness, ConocoPhillips Alaska Inc., and ExxonMobil. All comments were posted on the MMS Internet Web site. A summary of the comments received on the proposed rule and our responses to the comments follow: </P>
                <P>
                    <E T="03">Comment:</E>
                     The FWS supports the proposed amendments as they will benefit the MMS and lessees by expediting the ESA section 7 consultation process and assist lessees in complying with the ESA and the MMPA. 
                </P>
                <P>
                    <E T="03">Response:</E>
                     The regulatory changes will lead to a common understanding of how MMS is implementing, and will implement in the future, the terms and conditions of incidental take statements under the ESA and the MMPA. 
                </P>
                <P>
                    <E T="03">Comment:</E>
                     The FWS recommended expanding the proposed amendments to include information for proposed species and proposed critical habitat to expedite formal consultation following an eventual listing or designation of critical habitat. In such circumstances, the FWS could prepare a conference opinion that can be quickly converted to a biological opinion, thereby preventing or reducing disruption to a lessee's ongoing operations. 
                </P>
                <P>
                    <E T="03">Response:</E>
                     The MMS agrees that having information on proposed species and proposed critical habitat would expedite the FWS and the NMFS preparing a biological opinion when a species is listed or critical habitat designated. However, we will not require operators and lessees to include monitoring or mitigation information for proposed or candidate listings or candidate designations in their plans. An ESA conference is required only when a proposed action is likely to jeopardize the continued existence of a proposed species or destroy or adversely modify proposed critical habitat. 
                </P>
                <P>When a new species is listed or critical habitat designated, and it is necessary to reinitiate a formal consultation, the existing opinion remains valid until revised or reissued. Therefore, while including a candidate species (petitioned species that are actively being considered for listing as threatened or endangered under the ESA) in a formal consultation is not required by law, we believe the existing ESA consultation process is flexible and can respond to proposed species listings or proposed critical habitat designations. We also believe the administrative process associated with listing species or designating critical habitat would allow sufficient time for the MMS, the FWS, and the NMFS to address the information available. </P>
                <P>
                    <E T="03">Comment:</E>
                     The FWS recommended including critical habitat in the monitoring and reporting requirements, if applicable, to assist the MMS in knowing whether it was necessary to reinitiate an ESA section 7 consultation (50 CFR 402.16(b)). 
                </P>
                <P>
                    <E T="03">Response:</E>
                     If a formal consultation results in specific reasonable and prudent alternatives to avoid adverse modification of a designated critical habitat, then the Regional Supervisor has discretion under § 250.282 to direct the lessee/operator to conduct post-approval monitoring programs in accordance with the ESA. All data from the monitoring programs must be made available to the MMS upon request. No change to the rule is necessary. 
                </P>
                <P>
                    <E T="03">Comment:</E>
                     The FWS recommended extending the requirement for mitigating measures to include critical habitat, where applicable, since it is possible that future designations and biological opinions could include conservation measures to ensure critical habitat is not adversely modified or destroyed. 
                </P>
                <P>
                    <E T="03">Response:</E>
                     Regulations at 30 CFR 250.227(b)(4) and 250.261 require lessees to provide impact analysis information on “Threatened or endangered species and their critical habitat” and at 30 CFR 250.227(c)(4) to “Describe potential measures to minimize or mitigate these potential impacts.” In addition, should measures to prevent habitat degradation be included in lease stipulations, 30 CFR 250.222 and 250.253 require lessees to provide “A description of the measures you took, or will take, to satisfy the conditions of lease stipulations.” No change to the rule is necessary. 
                </P>
                <P>
                    <E T="03">Comment:</E>
                     The FWS recommended an editorial correction in 
                    <E T="02">SUPPLEMENTARY INFORMATION</E>
                     to change “reasonable and prudent alternatives” to “reasonable and prudent measures,” which have implementing terms and conditions. 
                </P>
                <P>
                    <E T="03">Response:</E>
                     The 
                    <E T="02">SUPPLEMENTARY INFORMATION</E>
                     has been changed accordingly. 
                </P>
                <P>
                    <E T="03">Comment:</E>
                     The Humane Society supports the MMS acknowledging the importance of complete information regarding potential impacts of leasing activities on protected species and post-activity monitoring. 
                </P>
                <P>
                    <E T="03">Response:</E>
                     No change required. 
                </P>
                <P>
                    <E T="03">Comment:</E>
                     The Humane Society expressed concern that there is no requirement in the proposed rule for applicants to provide information on baseline conditions or to conduct baseline monitoring. The Humane Society further commented that the lack of baseline information makes impossible reasonable statements about the consequences of activities, thus negating the utility of post-activity monitoring. 
                </P>
                <P>
                    <E T="03">Response:</E>
                     The MMS believes the existing requirements in § 250.227(b)(3) and (4) (What environmental impact analysis (EIA) information must accompany the EP and § 250.261(b)(3) and (4) (What environmental impact analysis (EIA) information must accompany the DPP or DOCD) address this concern. The information in the EIA, which must accompany plans, requires the lessee to describe those resources (identified as marine mammals and threatened and endangered species and their critical habitat) and conditions that could be affected by proposed exploration, or development and production activities. No change to the rule is necessary. 
                </P>
                <P>
                    <E T="03">Comment:</E>
                     The Humane Society expressed concern that the requirement for lessees to submit plans for mitigation measures would allow lessees to suggest measures ad hoc and rely on previous assertions of the effectiveness of mitigation measures without fully considering evidence that questions efficacy. This limits the MMS's ability to assess the potential cumulative 
                    <PRTPAGE P="18580"/>
                    impacts from a number of projects taking place along the range of marine mammal species, and identify the most meaningful mitigation measures for similar activities. 
                </P>
                <P>
                    <E T="03">Response:</E>
                     The MMS's ability to assess potential cumulative impacts is not limited to the OCSLA and subpart B regulations. We assess activities, mitigation measures, and cumulative impacts through the CZMA, the NEPA, and the ESA. The MMS believes §§ 250.231 through 235 and §§ 250.266 through 273 address this concern. We must review all plans and determine if the information is sufficient and accurate. After review, we may request the lessee to revise or modify a plan as necessary. Plans must also be submitted to the States for consistency review and determination under the Coastal Zone Management Act (CZMA). We also evaluate the environmental impact of exploration, development, and production activities, including mitigation measures, and prepare environmental documentation under the National Environmental Policy Act (NEPA) (42 U.S.C. 4321 
                    <E T="03">et seq.</E>
                    ) and the implementing regulations (40 CFR parts 1500 through 1508). In addition, the ESA consultation process also allows for a meaningful analysis of mitigation for threatened and endangered species. The results of consultation are included in the biological opinion and associated incidental take statements. No changes to the final rule are necessary. 
                </P>
                <P>
                    <E T="03">Comment:</E>
                     The Center for Regulatory Effectiveness commented that the MMS should comply with the PRA before proceeding further with the rulemaking. They asserted that the proposed rule contains new IC requirements that were not reviewed and approved by OMB under 1010-0151.
                </P>
                <P>
                    <E T="03">Response:</E>
                     The MMS disagrees that the proposed rule does not comply with the PRA. This proposed rule clarifies information requirements for plans and accompanying information in subpart B already approved under the OMB Control Number 1010-0151. Section 250.202 in subpart B clearly states, “Your EP, DPP, or DOCD must demonstrate that you have planned and are prepared to conduct the proposed activities in a manner that: (a) Conforms to the OCSLA as amended, applicable implementing regulations, lease provisions and stipulations, and other Federal laws * * *” We also have the OMB approval for all the requirements associated with trash and debris, vessel collisions, and seismic survey mitigation and monitoring activities (NTLs) required through the ESA section 7 consultation with the NMFS (OMB Control Number 1010-0154, 22,305 burden hours). When this rule becomes effective, we will consolidate the requirements and burdens from 1010-0154 into the primary collection for 30 CFR part 250 subpart B, 1010-0151. 
                </P>
                <P>
                    <E T="03">Comment:</E>
                     ConocoPhillips Alaska Inc., recommended the MMS withdraw the rule as unnecessary or revise and reissue the rule to clarify: how lessees should develop monitoring, mitigation, and reporting programs for listed species prior to completion of the ESA section 7 consultation; and the manner in which lessees should determine if take under the ESA or the MMPA is reasonably certain to occur. 
                </P>
                <P>
                    <E T="03">Response:</E>
                     In general, the agency will not require lessees to develop additional monitoring, mitigation, or reporting plans for listed species prior to completion of ESA Section 7 consultations. We intend that lessees rely on the conditions provided in the completed relevant Section 7 consultations to determine the appropriate mitigation, monitoring, and reporting requirements that should be part of Exploration Plans. The MMS consults under the ESA with the FWS and the NMFS on every lease sale and all activities associated with exploration, development, production, and decommissioning before a lease sale occurs. Therefore, activities associated with a lease already require a determination as to whether the activities are likely to jeopardize the continued existence of listed species or destroy or adversely modify designated critical habitat. That determination is the subject of the biological opinion. If take of a listed species is anticipated, an associated incidental take statement describes the reasonable and prudent measures and implementing terms and conditions. Should we reinitiate a consultation and the reasonable and prudent measures and implementing terms and conditions change, we would notify lessees and operators. The FWS or the NMFS clarify in the biological opinion and incidental take statements the manner and extent of anticipated take, as well as any mitigation, monitoring, and reporting requirements associated with minimizing such take. 
                </P>
                <P>Section 7(a)(2) of ESA requires each Federal Agency to consult with the Secretary to insure that any action they authorize, fund, or carry out is not likely to jeopardize the continued existence of a listed species or result in the destruction or adverse modification of designated critical habitat. In fulfilling these requirements, each agency is to use the best scientific and commercial data available. The ESA section 7 consultation process is a cooperative process. The Services do not have all the answers and actively seek the views of the action agency and its designated representatives in preparing the biological opinion, developing reasonable and prudent alternatives, reasonable and prudent measures, terms and conditions to minimize the impacts of incidental take, and conservation recommendations. Whenever incidental take of a marine mammal is anticipated, the Services may not issue an incidental take statement under the ESA for the marine mammal until such take is authorized under section 101(a)(5) of the MMPA. Following the MMPA authorization, the Service may amend the biological opinion to include the incidental take statement for marine mammals, as appropriate. </P>
                <P>
                    The MMPA implementing regulations specify that incidental take authorizations will set forth permissible methods of taking, and requirements or conditions pertaining to monitoring and reporting after citizens engaged in the specific activity provide a detailed description of the activity, the manner and extent of incidental take and the means of effecting the least practicable impact upon the marine mammal. In such cases when incidental take of listed marine mammal requires MMPA authorization, the Secretary will set forth the terms and conditions (including, but not limited to, reporting requirements) that must be complied with by the Federal agency or applicant (if any), or both, to implement the measures specified in the incidental take statement. Lessees and operators must decide whether a take is reasonably likely to occur in deciding whether to file a petition with the FWS or the NMFS for incidental take under the MMPA. By statute and regulation, notice of petitions and authorizations for incidental take must be published in the 
                    <E T="04">Federal Register</E>
                    . Specific examples would include petitions involving activities such as pile driving, seismic surveys, and structure removals using explosives. In addition, under the MMPA implementing regulations (50 CFR 216.104), in order for the NMFS to consider authorizing take by U.S. citizens, or to make a finding that an incidental take is unlikely to occur, a written request must be submitted to the Assistant Administrator. The information required in the request is specified in the same section. No changes to the rule are necessary. 
                </P>
                <P>
                    <E T="03">Comment:</E>
                     ConocoPhillips Alaska Inc., disagrees with the position reflected in the proposed rule that the ESA or the MMPA expand the MMS's existing statutory authority. The MMS may not impose the ESA- or the MMPA-
                    <PRTPAGE P="18581"/>
                    related requirements upon lessees or operators unless such requirements are necessary and authorized under the MMS's enabling legislation. 
                </P>
                <P>
                    <E T="03">Response:</E>
                     This final rule is consistent with our mandate under the OCSLA. Under §§ 1333 and 1334 of the OCSLA, the MMS must ensure that the proposed activities will comply with other applicable Federal laws and regulations, which may include the Clean Air Act (CAA), the ESA, the MMPA, the National Historic Preservation Act, the CZMA, and the Clean Water Act. Section 25(c) of the OCSLA (43 U.S.C. 1351(c)) mandates the scope and content of oil and gas development and production plans include “environmental safeguards to be implemented.” In addition, section 11 of the OCSLA (43 U.S.C. 1340) states that any permits for geological explorations shall be issued only if the Secretary determines “such exploration will not be unduly harmful to aquatic life in the area, result in pollution, create hazardous or unsafe conditions, unreasonably interfere with other uses of the area, or disturb any site, structure, or object of historical or archaeological significance.” The regulations at 30 CFR part 250 subpart B are intended to enable the MMS to carry out these responsibilities under the OCSLA. No changes to the rule are necessary. 
                </P>
                <P>
                    <E T="03">Comment:</E>
                     ConocoPhillips Alaska Inc., disagrees that the MMS, and by extension, lessees or operators are somehow obligated to monitor and report take under the ESA in the absence of an affirmative finding that a proposed action is either likely to adversely affect a listed species, or adversely modify designated critical habitat. 
                </P>
                <P>
                    <E T="03">Response:</E>
                     This rule intends to apply to lessees' activities that have been the subject of ESA Section 7 consultations where the consultations resulted in specific terms and conditions requiring mitigation, monitoring, and reporting. The MMS consults under section 7 of the ESA with the FWS or the NMFS on every lease sale and all activities associated with exploration, development, production, and decommissioning. Section 7 consultation is required for any proposed action that “may affect” listed species or designated critical habitat. No formal consultation is required if a proposed action “may affect, but is not likely to adversely affect” listed species or critical habitat. Therefore, every activity associated with a lease already requires a determination as to whether an activity is likely to adversely affect listed species or designated critical habitat. If adverse effects are likely, MMS will enter into a formal consultation during which a biological opinion on whether listed species would likely be jeopardized or critical habitat destroyed or adversely modified would be prepared. There are documents prepared by Federal agencies or those responsible for conducting activities during such consultations that describe adverse effects to listed species and critical habitat. In those cases where the Services provide a statement of incidental take with a biological opinion, the ESA specifies the Secretary must set forth the terms and conditions (including, but not limited to, reporting requirements) that must be complied with by the Federal agency or applicant (if any), or both, to implement the measures specified in the incidental take statement. No changes to the rule are appropriate. 
                </P>
                <P>
                    <E T="03">Comment:</E>
                     ConocoPhillips Alaska Inc., expressed concern that the proposed rule does not address the potential impact of proposed Threatened and Endangered Species Recovery Act (TESRA) legislation (H.R. 3824), and therefore, should be delayed until Congress takes action on H.R. 3824. 
                </P>
                <P>
                    <E T="03">Response:</E>
                     The MMS disagrees that we should wait for Congress to act on the TESRA, H.R. 3824. It cannot be known when and in what form such legislation may be passed. The MMS has reviewed the H.R. 3824. None of the proposed amendments to the ESA would change the information requirements for plans submitted by lessees to the MMS. The MMS still has a responsibility under the OCSLA to review and approve plans before activities may be conducted and to ensure that activities will comply with other applicable Federal laws and regulations currently in effect. 
                </P>
                <P>
                    <E T="03">Comment:</E>
                     ConocoPhillips Alaska Inc., expressed concern that the proposed rule uses “take” interchangeably under the ESA and the MMPA and does not explain the statutory differences between take under the ESA and the MMPA. 
                </P>
                <P>
                    <E T="03">Response:</E>
                     “Take” has been defined by statute and implementing regulations for both the ESA and the MMPA. The MMS need not repeat those definitions in our regulations. Every person has a responsibility to comply with those laws and understand their meaning. The term “take” is defined by the ESA to mean “to harass, harm, pursue, hunt, shoot, wound, kill, trap, capture, or collect, or attempt to engage in any such conduct.” Harass has further been defined by FWS regulations to mean “an intentional or negligent act or omission which creates the likelihood of injury to wildlife by annoying it to such an extent as to significantly disrupt normal behavior patterns which include, but are not limited to breeding, feeding, or sheltering.” Harm means “an act which actually kills or injures wildlife.” 
                </P>
                <P>The MMPA defines take to mean “to harass, hunt, capture, collect, kill, or attempt to harass, hunt, capture, collect, or kill any marine mammal.” The Act further defines Level A and Level B harassment as “any act of pursuit, torment or annoyance which has the potential to injure a marine mammal or marine mammal stock in the wild” or any act of pursuit, torment, or annoyance which has the potential to disturb a marine mammal or marine mammal stock in the wild * * *” </P>
                <P>
                    <E T="03">Comment:</E>
                     ConocoPhillips Alaska Inc., disagrees that the proposed rule will result in “no additional costs” because it merely clarifies requirements that already exist. 
                </P>
                <P>
                    <E T="03">Response:</E>
                     The MMS disagrees that this rule results in additional costs. Whether we list the specific ESA or MMPA provisions in the regulations or not, current subpart B still requires lessees to provide the appropriate biological information with their plans. The amendments to subpart B do not add any additional information requirements, nor do the amendments require any additional information beyond what is already required under the ESA or the MMPA. Putting these specific provisions in the 250 regulations specifies what information is needed to ensure compliance with subpart B, the ESA, and the MMPA. 
                </P>
                <P>
                    <E T="03">Comment:</E>
                     The Alaska Eskimo Whaling Commission commented that the proposed rule does not state the MMPA standard that incidental take of marine mammals “will not have an unmitigable adverse impact on the availability [of marine mammals] for taking for subsistence uses.” The final rule should reflect this standard. 
                </P>
                <P>
                    <E T="03">Response:</E>
                     Stating the MMPA standards is beyond the scope of this rule. The scope of this rule is limited to existing regulatory information requirements for plans submitted by lessees/operators. Our Alaska Region offers to meet with the Alaska Eskimo Whaling Commission and the NMFS to further discuss this standard and other MMPA-related issues. Such discussions have begun informally at the open water meeting forum and MMS hopes to expand those discussions as they begin the Multisale process for 2007-2012 lease sales. 
                </P>
                <P>
                    <E T="03">Comment:</E>
                     The Alaska Eskimo Whaling Commission commented that the proposed rule gives the MMS the opportunity to issue clear guidance to 
                    <PRTPAGE P="18582"/>
                    applicants proposing activities in the Alaskan OCS. Specifically, applicants must demonstrate their ability to meet the MMPA's “no unmitigable adverse impact” standard; and the MMS should use §§ 250.220 and 250.251 to inform its Alaskan OCS applicants of the information requirements relevant to the protection of subsistence species. They suggested specific wording for programs currently in operation, such as conflict avoidance agreements and good neighbor agreements. 
                </P>
                <P>
                    <E T="03">Response:</E>
                     As offered in the previous response, the proposals are beyond the scope of this rulemaking. The MMS Alaska Region offers to meet with the Alaska Eskimo Whaling Commission to further discuss the suggestion. 
                </P>
                <P>
                    <E T="03">Comment:</E>
                     The Alaska Eskimo Whaling Commission commented that the MMS should clarify its requirements for information from applicants in the sections on Environmental Impact Analysis. The MMS should clarify that it will independently verify and evaluate all analyses submitted by applicants. The MMS should also avoid requiring analyses or assessments in favor of requiring applicants to “identify” or “describe” potential impacts that will assist the MMS in its environmental reviews under the NEPA, the ESA, and the MMPA. Finally, we should adopt the NEPA definition of “cumulative impacts” to encourage applicants to provide the most comprehensive information to the MMS. 
                </P>
                <P>
                    <E T="03">Response:</E>
                     Sections 250.227 and 250.261 are specific in stating that the information must be as detailed as necessary to assist us in complying with the NEPA and other Federal laws. Further, under 40 CFR 1506.5, the MMS must independently evaluate the information submitted and be responsible for its accuracy. Cumulative impacts are defined under the ESA (50 CFR 402.02) and the NEPA (40 CFR 1508.7). It is not necessary to repeat those requirements or definitions in our regulations. 
                </P>
                <P>
                    <E T="03">Comment:</E>
                     ExxonMobil expressed concern that the proposed rule assumes that offshore oil and gas activities will result in “takes” of marine mammals and endangered species rather than basing the rule on a sound scientific assessment of risk. Further, it places a burden on industry to define what a “take” is for the purposes of the ESA and the MMPA. 
                </P>
                <P>
                    <E T="03">Response:</E>
                     The rule does not assume offshore oil and gas activities will result in “takes.” Through Agency to Agency consultations, the FWS or the NMFS clarifies in the biological opinion and incidental take statements the manner and extent of anticipated take. The rule clearly specifies information regarding monitoring and mitigation measures would only be necessary in those cases where there is “reason to believe that protected species may be incidentally taken.” “Reason to believe” is an objective standard whereby a reasonable person is looking at all the available facts and factors, it does not pre-determine take. This is also why §§ 250.221, 250.223, 250.252, and 250.254 each contain wording indicating that the required action in the case of marine mammals applies only “as appropriate” and “as may be necessary.” The language of the final rule does not pre-determine any activity will result in an incidental take. Take under the ESA and the MMPA is defined by statute and regulation. 
                </P>
                <P>Under the ESA, Federal action agencies must determine if a proposed action “may affect” listed species or designated critical habitat, using the best scientific and commercial data available. The biological assessment is a tool used to identify impacts to listed species or designated critical habitat so that a decision can be made as to whether a proposed action is likely to adversely affect listed species or designated critical habitat. </P>
                <P>The MMPA places responsibilities on the entity conducting a specific activity (and who wishes an incidental take of a marine mammal to be allowed and not prohibited) to take the initiative in identifying actions that could result in a taking in order to avoid sanctions should a take occur. Under the implementing regulations (50 CFR 216.104), in order for the NMFS to consider authorizing take by U.S. citizens, or to make a finding that an incidental take is unlikely to occur, a written request must be submitted to the Assistant Administrator by the requester providing, “A detailed description of the specific activity or class of activities that can be expected to result in incidental taking of marine mammals,” “the types of incidental take authorization that is being requested,” and “by age, sex, and reproductive condition (if possible), the number of marine mammals (by species) that may be taken by each type of taking identified * * * and the number of times such takings by each type of taking are likely to occur.” No changes to the rule are necessary. </P>
                <P>
                    <E T="03">Comment:</E>
                     ExxonMobil suggested that rather than requiring lessees and operators to implement monitoring and mitigation measures “as appropriate,” the MMS and industry should work together to obtain the promulgation of the incidental take regulations and then determine what further actions, if any, need to be taken with respect to the MMS regulatory program in connection with the MMPA and the ESA. 
                </P>
                <P>
                    <E T="03">Response:</E>
                     The MMS petitioned for regulations under the MMPA for both seismic survey activities conducted in the GOM and for decommissioning offshore structures in the GOM. Both the MMS and industry will have an opportunity to comment on both sets of the proposed MMPA regulations and the Environmental Impact Statement (EIS) the NMFS intends to prepare to support their rulemaking process for seismic survey activities. In the meantime, while the NMFS continues its regulatory process for those two specific activities in the GOM, the MMS still has a responsibility under the OCSLA to review and approve plans before activities may be conducted to ensure the proposed activities are environmentally sound and will be conducted in a manner consistent with applicable Federal laws and regulations. We also require this information in plans to assist the Regional Supervisor in complying with the NEPA, the ESA, and the MMPA as stated in §§ 250.227 and 250.261. No changes to the rule will be made. 
                </P>
                <P>
                    <E T="03">Comment:</E>
                     ExxonMobil pointed out that the rule would require the lessees and operators to describe how mitigation would reduce the potential for takes under the ESA and the MMPA. This in turn would affect how the MMS and industry interact with other agencies because the lessee or operator will not know how to comply with the proposed rule without interacting with the ESA/MMPA regulatory agencies. 
                </P>
                <P>
                    <E T="03">Response:</E>
                     With respect to the ESA, when the Services believe the Agency or the applicant may take actions to avoid incidental take of a listed species the opinion will contain a thorough explanation of how reasonable and prudent alternatives will minimize or avoid incidental takes. MMS has always communicated directly with the lessee/operators through various means regarding non-discretionary mitigation measures specified in an incidental take statement. We would continue this communication. In addition, industry may take the role of an applicant under the ESA and participate in the consultation process as they have done in the past. The MMS and other MMPA/ESA regulatory agencies have provided those opportunities in the past and would continue this process. 
                </P>
                <P>
                    With respect to the MMPA, the implementing regulations are very clear. If an operator or lessee has reason to believe their activities may result in incidental take of marine mammals and they wish the Secretary to allow the 
                    <PRTPAGE P="18583"/>
                    incidental take, then the operator or lessee must request the authorization. The MMPA implementing regulations spell out the process necessary to receive an incidental take authorization. Nothing in the final rule changes that process or how industry would interact with other agencies. No changes to the final rule are necessary. 
                </P>
                <P>
                    <E T="03">Comment:</E>
                     ExxonMobil commented that the proposed rule does not address the time required for interaction with other regulatory agencies. Additionally, if the proposed rule results in additional workload on another agency, it could delay industry exploring for and developing oil and natural gas supplies in waters of the U.S. while interaction occurs. 
                </P>
                <P>
                    <E T="03">Response:</E>
                     The final rule does nothing to change the statutory and regulatory timeframes associated with the ESA and the MMPA processes for allowing or authorizing incidental take of protected species, which otherwise would be prohibited by the Acts. This final rule does not change the level of interaction with or workload for the FWS or the NMFS. The level of interaction and workload issues are defined by the quality of the interaction, the responsiveness to regulatory requirements of the ESA and the MMPA, and the potential for activities to adversely affect or to take protected species as defined by the ESA and the MMPA. This final rule is designed to facilitate environmentally sound operations on the OCS as mandated under the OCSLA. No changes to the final rule are necessary. 
                </P>
                <P>
                    <E T="03">Comment:</E>
                     ExxonMobil suggested that the NTLs MMS has issued are a proper response to the MMPA and the ESA requirements pending NOAA's promulgation of incidental take regulations and that the MMS, along with industry, should focus its efforts on the development of incidental take regulations requested from the NOAA and clarifying the respective roles of the NOAA and the MMS with respect to offshore activities. 
                </P>
                <P>
                    <E T="03">Response:</E>
                     MMS has decided to utilize regulations rather than NTLs to impose general requirements like these, in contrast to the NTLs previously issued that addressed a particular biological opinion. This rule addresses any activity that may incidentally take a protected species in any planning area of the OCS. Under the OCSLA, we must ensure that the proposed activities will comply with other applicable Federal laws and regulations as referenced above. Both the MMS and industry will have an opportunity to comment on the proposed MMPA regulations and the EIS that the NMFS intends to prepare to support their regulations for seismic survey activities in the GOM. Promulgating regulations defining the role of the NOAA under the MMPA is not within the authority of the Department of the Interior (DOI). No changes to the final rule are necessary. 
                </P>
                <HD SOURCE="HD1">Procedural Matters </HD>
                <HD SOURCE="HD2">Regulatory Planning and Review (Executive Order (E.O.) 12866) </HD>
                <P>The Office of Management and Budget (OMB) has determined that this is a significant rule for OMB review under Executive Order 12866. </P>
                <P>(1) This final rule will not have an effect of $100 million or more on the economy. It will not adversely affect in a material way the economy, productivity, competition, jobs, the environment, public health or safety, or State, local, or tribal governments or communities. The final rule is necessary for us to implement nondiscretionary terms and conditions to be exempt from prohibition at section 9 of the ESA, of the taking of listed species. There are no new costs associated with this rulemaking and it will not cause an annual effect on the economy of $100 million or more. </P>
                <P>(2) This final rule will not create a serious inconsistency or otherwise interfere with an action taken or planned by another agency. The MMS consulted with the FWS and the NOAA. These agencies agree that the final rule is consistent with their authorities and implementing regulations. The final rule does not affect how lessees or operators interact with other agencies. Nor does the final rule affect how the MMS will interact with other agencies. </P>
                <P>(3) This final rule does not alter the budgetary effects or entitlements, grants, user fees, or loan programs or the rights or obligations of their recipients. </P>
                <P>(4) The OMB has determined that this rule raises novel legal or policy issues. The rule specifies that lessees must provide information to MMS on how they will conduct their proposed activities in a manner consistent with provisions of ESA and MMPA to ensure compliance with the OCSLA. </P>
                <HD SOURCE="HD2">Regulatory Flexibility Act (RFA) </HD>
                <P>
                    The DOI certifies that this final rule does not have a significant economic effect on a substantial number of small entities as defined under the RFA (5 U.S.C. 601 
                    <E T="03">et seq.</E>
                    ). No additional costs are associated with this final rule because it clarifies requirements that already exist. This final rule reduces the ambiguity in our regulations. Accordingly, a Small Entity Compliance Guide is not required. 
                </P>
                <P>Your comments are important. The Small Business and Agriculture Regulatory Enforcement Ombudsman and 10 Regional Fairness Boards were established to receive comments from small businesses about Federal agency enforcement actions. The Ombudsman will annually evaluate the enforcement activities and rate each agency's responsiveness to small business. If you wish to comment on the actions of the MMS, call 1-888-734-3247. You may comment to the Small Business Administration without fear of retaliation. Disciplinary action for retaliation by an MMS employee may include suspension or termination from employment with the DOI. </P>
                <HD SOURCE="HD2">Small Business Regulatory Enforcement Fairness Act (SBREFA) </HD>
                <P>This final rule is not a major rule under the SBREFA, (5 U.S.C. 804(2)). This final rule: </P>
                <P>a. Will not have an annual effect on the economy of $100 million or more. </P>
                <P>b. Will not cause a major increase in costs or prices for consumers, individual industries, Federal, State, or local government agencies, or geographic regions because the final rule incorporates monitoring, mitigation and reporting requirements specified in current NTLs and lease stipulations. </P>
                <P>c. Will not have significant adverse effects on competition, employment, investment, productivity, innovation, or ability of U.S.-based enterprises to compete with foreign-based enterprises. All lessees and operators, regardless of nationality, must comply with the requirements of this final rule. The final rule will not affect competition, employment, investment, productivity, innovation, or the ability of U.S.-based enterprises to compete with foreign-based enterprises. </P>
                <HD SOURCE="HD2">Unfunded Mandates Reform Act (UMRA) </HD>
                <P>
                    This final rule will not impose an unfunded mandate on State, local, or tribal governments or the private sector of more than $100 million per year. The final rule does not have a significant or unique effect on State, local, or tribal governments or the private sector. A statement containing the information required by the UMRA (2 U.S.C. 1531 
                    <E T="03">et seq.</E>
                    ) is not required. There are no mandates for State, local, or tribal governments. 
                </P>
                <HD SOURCE="HD2">Takings Implication Assessment (Executive Order 12630) </HD>
                <P>
                    The final rule is not a governmental action capable of interference with constitutionally protected property rights. Thus, MMS did not need to 
                    <PRTPAGE P="18584"/>
                    prepare a Takings Implication Assessment according to E.O. 12630, Governmental Actions and Interference with Constitutionally Protected Property Rights. 
                </P>
                <HD SOURCE="HD2">Federalism (Executive Order 13132) </HD>
                <P>With respect to E.O. 13132, this final rule would not have federalism implications. This final rule would not substantially and directly affect the relationship between the Federal and State governments. To the extent that State and local governments have a role in OCS activities, this proposed rule would not affect that role. </P>
                <HD SOURCE="HD2">Civil Justice Reform (Executive Order 12988) </HD>
                <P>With respect to E.O. 12988 the Office of the Solicitor has determined that this final rule does not unduly burden the judicial system and does meet the requirements of sections 3(a) and 3(b)(2) of the Order. </P>
                <HD SOURCE="HD2">Paperwork Reduction Act (PRA) </HD>
                <P>The revisions to 30 CFR part 250, subpart B, refer to, but do not change the IC requirements in current regulations. The final rule contains no new reporting or recordkeeping requirements, and therefore, an IC request has not been submitted to the OMB under the PRA. The MMS received two comments that related to the PRA. One was a comment from the Center for Regulatory Effectiveness that felt the MMS was not complying with the PRA. They asserted that this rule contained new IC requirements that were not reviewed and approved by OMB under 1010-0151. There are no new IC requirements in this rule. All requirements are covered under OMB Control Numbers 1010-0151 (exp. 7/31/08, 320,815 hours) and 1010-0154 (exp. 12/31/06, 22,305 hours). The second comment was from ConocoPhillips Alaska Inc., and they disagreed that the rule would result in “no additional costs.” The MMS disagrees that this rule results in additional costs. The rule contains new language but does not contain new requirements or new costs. Current subpart B requires lessees to provide the appropriate biological information with their plans. The rulemaking adds no new IC beyond what is already required under the ESA or the MMPA. By putting these provisions in 30 CFR 250 regulations, it clarifies what information is needed to ensure compliance with subpart B, the ESA, and the MMPA. The PRA provides that an agency may not conduct or sponsor a collection of information unless it displays a currently valid OMB control number. Until OMB approves a collection of information and assigns a control number, you are not required to respond. The OMB approved the referenced IC requirements under the OMB control number 1010-0151, expiration 7/31/08. </P>
                <HD SOURCE="HD2">National Environmental Policy Act (NEPA) of 1969 </HD>
                <P>The MMS has determined that this final rule qualifies for a categorical exclusion under 516 Department Manual (DM) Chapter 2, Appendix 1.10. The rule is procedural in nature, it clarifies existing requirements concerning the contents of Exploration Plans, Development and Production Plans, and Development Operation Coordination Documents. Therefore, it is categorically excluded from environmental review under section 102(2)(C) of the NEPA, pursuant to 516 DM, Chapter 2, Appendix 1. In addition, the final rule does not involve any of the 10 extraordinary circumstances listed in 516 DM, Chapter 2, Appendix 2. Pursuant to Council on Environmental Quality regulations (40 CFR 1508.4) and the environmental policies and procedures of the DOI, the term “categorical exclusions” means a category of actions which do not individually or cumulatively have a significant effect on the human environment and that have been found to have no such effect in procedures adopted by a Federal agency and for which neither an environmental assessment nor an environmental impact statement is required. </P>
                <HD SOURCE="HD2">Energy Supply, Distribution, or Use (Executive Order 13211) </HD>
                <P>Executive Order 13211 requires the agency to prepare a Statement of Energy Effects when it takes a regulatory action that is identified as a significant energy action. This final rule is not a significant energy action, and therefore would not require a Statement of Energy Effects because it: </P>
                <P>a. Is not a significant regulatory action under E.O. 12866, </P>
                <P>b. Is not likely to have a significant adverse effect on the supply, distribution, or use of energy, and </P>
                <P>c. Has not been designated by the Administrator of the Office of Information and Regulatory Affairs, OMB, as a significant energy action. </P>
                <HD SOURCE="HD2">Consultation with Indian Tribes (Executive Order 13175) </HD>
                <P>Under the criteria in E.O. 13175, we have evaluated this final rule and determined that it has no potential effects on federally recognized Indian tribes. There are no Indian or tribal lands on the OCS. </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 30 CFR Part 250 </HD>
                    <P>Administrative practice and procedure, Continental shelf, Environmental impact statements, Environmental protection, Government contracts, Investigations, Oil and gas exploration, Penalties, Pipelines, Public lands—mineral resources, Public lands—rights-of-way, Reporting and recordkeeping requirements, Sulphur.</P>
                </LSTSUB>
                <SIG>
                    <DATED>Dated: December 8, 2006. </DATED>
                    <NAME>C. Stephen Allred, </NAME>
                    <TITLE>Assistant Secretary—Land and Minerals Management. </TITLE>
                </SIG>
                <EDNOTE>
                    <HD SOURCE="HED"/>
                    <P>
                        This document was received at the Office of the 
                        <E T="04">Federal Register</E>
                         on April 10, 2007.
                    </P>
                </EDNOTE>
                <REGTEXT TITLE="30" PART="250">
                    <AMDPAR>For the reasons stated in the preamble, the Minerals Management Service amends 30 CFR part 250 as follows: </AMDPAR>
                    <PART>
                        <HD SOURCE="HED">PART 250—OIL AND GAS AND SULPHUR OPERATIONS IN THE OUTER CONTINENTAL SHELF </HD>
                    </PART>
                    <AMDPAR>1. The authority citation for part 250 continues to read as follows: </AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>
                            43 U.S.C. 1331 
                            <E T="03">et seq.</E>
                            ; 31 U.S.C. 9701.
                        </P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="30" PART="250">
                    <AMDPAR>2. Revise § 250.216 paragraph (a) to read as follows: </AMDPAR>
                    <SECTION>
                        <SECTNO>§ 250.216 </SECTNO>
                        <SUBJECT>What biological, physical, and socioeconomic information must accompany the EP? </SUBJECT>
                        <STARS/>
                        <P>
                            (a) 
                            <E T="03">Biological environment reports</E>
                            . Site-specific information on chemosynthetic communities, federally listed threatened or endangered species, marine mammals protected under the Marine Mammal Protection Act (MMPA), sensitive underwater features, marine sanctuaries, critical habitat designated under the Endangered Species Act (ESA), or other areas of biological concern. 
                        </P>
                        <STARS/>
                          
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="30" PART="250">
                    <AMDPAR>3. In § 250.221, redesignate paragraph (b) as paragraph (c) and add paragraph (b) to read as follows: </AMDPAR>
                    <SECTION>
                        <SECTNO>§ 250.221 </SECTNO>
                        <SUBJECT>What environmental monitoring information must accompany the EP? </SUBJECT>
                        <STARS/>
                        <P>
                            (b) 
                            <E T="03">Incidental takes</E>
                            . If there is reason to believe that protected species may be incidentally taken by planned exploration activities, you must describe how you will monitor for incidental take of: 
                        </P>
                        <P>(1) Threatened and endangered species listed under the ESA and </P>
                        <P>(2) Marine mammals, as appropriate, if you have not already received authorization for incidental take as may be necessary under the MMPA. </P>
                        <STARS/>
                          
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="30" PART="250">
                    <PRTPAGE P="18585"/>
                    <AMDPAR>4. Revise § 250.223 to read as follows: </AMDPAR>
                    <SECTION>
                        <SECTNO>§ 250.223 </SECTNO>
                        <SUBJECT>What mitigation measures information must accompany the EP? </SUBJECT>
                        <P>(a) If you propose to use any measures beyond those required by the regulations in this part to minimize or mitigate environmental impacts from your proposed exploration activities, a description of the measures you will use must accompany your EP. </P>
                        <P>(b) If there is reason to believe that protected species may be incidentally taken by planned exploration activities, you must include mitigation measures designed to avoid or minimize the incidental take of: </P>
                        <P>(1) Threatened and endangered species listed under the ESA and </P>
                        <P>(2) Marine mammals, as appropriate, if you have not already received authorization for incidental take as may be necessary under the MMPA. </P>
                    </SECTION>
                    <AMDPAR>5. Revise paragraphs (a)(3) and (c)(1) in § 250.227 to read as follows: </AMDPAR>
                </REGTEXT>
                <REGTEXT TITLE="30" PART="250">
                    <SECTION>
                        <SECTNO>§ 250.227 </SECTNO>
                        <SUBJECT>What environmental impact analysis (EIA) information must accompany the EP? </SUBJECT>
                        <STARS/>
                        <P>(a) * * * </P>
                        <P>
                            (3) Be as detailed as necessary to assist the Regional Supervisor in complying with the National Environmental Policy Act (NEPA) of 1969 (42 U.S.C. 4321 
                            <E T="03">et seq.</E>
                            ) and other relevant Federal laws such as the ESA and the MMPA. 
                        </P>
                        <STARS/>
                        <P>(c) * * * </P>
                        <P>(1) Analyze the potential direct and indirect impacts (including those from accidents, cooling water intake structures, and those identified in relevant ESA biological opinions such as, but not limited to, those from noise, vessel collisions, and marine trash and debris) that your proposed exploration activities will have on the identified resources, conditions, and activities; </P>
                        <STARS/>
                          
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="30" PART="250">
                    <AMDPAR>6. Revise § 250.247 (a) to read as follows: </AMDPAR>
                    <SECTION>
                        <SECTNO>§ 250.247 </SECTNO>
                        <SUBJECT>What biological, physical, and socioeconomic information must accompany the DPP or DOCD? </SUBJECT>
                        <STARS/>
                        <P>
                            (a) 
                            <E T="03">Biological environment reports</E>
                            . Site-specific information on chemosynthetic communities, federally listed threatened or endangered species, marine mammals protected under the MMPA, sensitive underwater features, marine sanctuaries, critical habitat designated under the ESA, or other areas of biological concern. 
                        </P>
                        <STARS/>
                          
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="30" PART="250">
                    <AMDPAR>7. In § 250.252, redesignate paragraph (b) as paragraph (c) and add paragraph (b) to read as follows: </AMDPAR>
                    <SECTION>
                        <SECTNO>§ 250.252 </SECTNO>
                        <SUBJECT>What environmental monitoring information must accompany the DPP or DOCD? </SUBJECT>
                        <STARS/>
                        <P>
                            (b) 
                            <E T="03">Incidental takes</E>
                            . If there is reason to believe that protected species may be incidentally taken by planned development and production activities, you must describe how you will monitor for incidental take of: 
                        </P>
                        <P>(1) Threatened and endangered species listed under the ESA and </P>
                        <P>(2) Marine mammals, as appropriate, if you have not already received authorization for incidental take of marine mammals as may be necessary under the MMPA. </P>
                        <STARS/>
                          
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="30" PART="250">
                    <AMDPAR>8. Revise § 250.254 to read as follows: </AMDPAR>
                    <SECTION>
                        <SECTNO>§ 250.254 </SECTNO>
                        <SUBJECT>What mitigation measures information must accompany the DPP or DOCD? </SUBJECT>
                        <P>(a) If you propose to use any measures beyond those required by the regulations in this part to minimize or mitigate environmental impacts from your proposed development and production activities, a description of the measures you will use must accompany your DPP or DOCD. </P>
                        <P>(b) If there is reason to believe that protected species may be incidentally taken by planned development and production activities, you must include mitigation measures designed to avoid or minimize that incidental take of: </P>
                        <P>(1) Threatened and endangered species listed under the ESA and </P>
                        <P>(2) Marine mammals, as appropriate, if you have not already received authorization for incidental take as may be necessary under the MMPA. </P>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="30" PART="250">
                    <AMDPAR>9. Revise paragraphs (a)(3) and (c)(1) in § 250.261 to read as follows: </AMDPAR>
                    <SECTION>
                        <SECTNO>§ 250.261 </SECTNO>
                        <SUBJECT>What environmental impact analysis (EIA) information must accompany the DPP or DOCD? </SUBJECT>
                        <STARS/>
                        <P>(a) * * * </P>
                        <P>
                            (3) Be as detailed as necessary to assist the Regional Supervisor in complying with the NEPA of 1969 (42 U.S.C. 4321 
                            <E T="03">et seq.</E>
                            ) and other relevant Federal laws such as the ESA and the MMPA. 
                        </P>
                        <STARS/>
                        <P>(c) * * * </P>
                        <P>(1) Analyze the potential direct and indirect impacts (including those from accidents, cooling water intake structures, and those identified in relevant ESA biological opinions such as, but not limited to, those from noise, vessel collisions, and marine trash and debris) that your proposed development and production activities will have on the identified resources, conditions, and activities; </P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="30" PART="250">
                    <AMDPAR>10. Revise paragraph (a)(1)(i) of § 250.270 to read as follows: </AMDPAR>
                    <SECTION>
                        <SECTNO>§ 250.270 </SECTNO>
                        <SUBJECT>What decisions will MMS make on the DPP or DOCD and within what timeframe? </SUBJECT>
                        <P>
                            (a) 
                            <E T="03">Timeframe.</E>
                             * * * 
                        </P>
                        <P>(1) * * * </P>
                        <P>(i) The comment period provided in § 250.267(a)(1), (a)(2), and (b) closes; </P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="30" PART="250">
                    <AMDPAR>11. Revise the introductory paragraph in § 250.282 to read as follows: </AMDPAR>
                    <SECTION>
                        <SECTNO>§ 250.282 </SECTNO>
                        <SUBJECT>Do I have to conduct post-approval monitoring? </SUBJECT>
                        <P>After approving your EP, DPP, or DOCD, the Regional Supervisor may direct you to conduct monitoring programs, including monitoring in accordance with the ESA and the MMPA. You must retain copies of all monitoring data obtained or derived from your monitoring programs and make them available to the MMS upon request. The Regional Supervisor may require you to: </P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
            </SUPLINF>
            <FRDOC>[FR Doc. E7-7028 Filed 4-12-07; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4310-MR-P </BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF HOMELAND SECURITY </AGENCY>
                <SUBAGY>Coast Guard </SUBAGY>
                <CFR>33 CFR Part 165 </CFR>
                <DEPDOC>[COTP Sector St. Petersburg 07-048] </DEPDOC>
                <RIN>RIN 1625-AA00 </RIN>
                <SUBJECT>Safety Zone; Intracoastal Waterway, Treasure Island, 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>The Coast Guard is establishing a temporary safety zone on the waters of the Intracoastal Waterway at Treasure Island, Florida, in the vicinity of the Treasure Island Causeway Bascule Bridge, while the bridge leaf sections are installed. This rule is necessary to ensure the safety of the workers and mariners on the navigable waters of the United States. </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>This rule is effective from 8 a.m. on March 21 through 6 p.m. on April 18, 2007. </P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Documents indicated in this preamble as being available in the 
                        <PRTPAGE P="18586"/>
                        docket are part of docket [COTP 07-048] and are available for inspection or copying at Coast Guard Sector St. Petersburg, Prevention Department, 155 Columbia Drive, Tampa, Florida 33606-3598 between 7:30 a.m. and 3:30 p.m., Monday through Friday, except Federal holidays. 
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>BM1 Charles Voss at Coast Guard Sector St. Petersburg (813) 228-2191 Ext 8307. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <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. The information for the installation was not given with sufficient time to publish an NPRM. Publishing an NPRM and delaying its effective date would be contrary to the public interest since immediate action is needed to minimize potential danger to the workers and mariners transiting the area. The Coast Guard will issue a broadcast notice to mariners to advise mariners of the restriction. </P>
                <P>
                    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 Coast Guard will issue a broadcast notice to mariners and will place Coast Guard or local law enforcement vessels in the vicinity of this zone to advise mariners of the restriction. 
                </P>
                <HD SOURCE="HD1">Background and Purpose </HD>
                <P>Johnson Brothers will be installing the tip sections of the east and west leafs on the Treasure Island Causeway Bridge. In order to install the tip sections, a crane barge will need to be placed in the center of the channel to hoist the tip sections and hold them in place while they are fasted to the bridge leafs. The nature of the installation and environment surrounding the Treasure Island Causeway Bridge presents a danger to the workers and mariners transiting the area. The installation will be conducted between 8 a.m. and 6 p.m. on March 21 and April 18, 2007. </P>
                <HD SOURCE="HD1">Discussion of Rule </HD>
                <P>The safety zone encompasses the following waters of the Intracoastal Waterway, Florida: all waters from surface to bottom, within a 200 foot radius of the following coordinates: 27°46′15″ N, 82°45′12″ W. Vessels are prohibited from anchoring, mooring, or transiting within this zone, unless authorized by the Captain of the Port Sector St. Petersburg or his designated representative. The zone will be enforced from 8 a.m. until 6 p.m. on March 21, and April 18, 2007. </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>We expect the economic impact of this rule to be so minimal that a full Regulatory Evaluation under the regulatory policies and procedures of DHS is unnecessary. The rule will only be enforced for a limited time in a location where marine traffic is minimal. Moreover, vessels may still enter the safety zone with the express permission of the Captain of the Port Sector St. Petersburg or his designated representative. </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 within a 200 foot radius from the Treasure Island Causeway Bascule Bridge on March 21 and April 18, 2007. This safety zone will not have a significant economic impact on a substantial number of small entities for the following reasons. This rule will only be enforced for a limited time in a location where marine traffic is minimal. Additionally, traffic will be allowed to enter the zone with the permission of the Captain of the Port Sector St. Petersburg or his designated representative. </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. Small entities may contact the person listed under 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                     for assistance in understanding and participating in this rulemaking. We also have a point of contact for commenting on actions by employees of the Coast Guard. 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 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 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. 
                    <PRTPAGE P="18587"/>
                </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 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">Technical Standards </HD>
                <P>The National Technology Transfer and Advancement Act (NTTAA) (15 U.S.C. 272 note) directs agencies to use voluntary consensus standards in their regulatory activities unless the agency provides Congress, through the Office of Management and Budget, with an explanation of why using these standards would be inconsistent with applicable law or otherwise impractical. Voluntary consensus standards are technical standards (e.g., specifications of materials, performance, design, or operation; test methods; sampling procedures; and related management systems practices) that are developed or adopted by voluntary consensus standards bodies. </P>
                <P>This rule does not use technical standards. Therefore, we did not consider the use of voluntary consensus standards. </P>
                <HD SOURCE="HD1">Environment </HD>
                <P>
                    We have analyzed this rule under Commandant Instruction M16475.lD and Department of Homeland Security Management Directive 5100.1, which guide 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. A final “Environmental Analysis Check List” and a final “Categorical Exclusion Determination” are 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; 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 temporary § 165.T07-048 to read as follows: </AMDPAR>
                    <SECTION>
                        <SECTNO>§ 165.T07-048 </SECTNO>
                        <SUBJECT>Safety Zone; Intracoastal Waterway, Treasure Island, Florida. </SUBJECT>
                        <P>
                            (a) 
                            <E T="03">Regulated Area.</E>
                             The Coast Guard is establishing a safety zone on the waters of the Intracoastal Waterway in the vicinity of the Treasure Island Causeway Bascule Bridge. The safety zone encompasses all waters within a 200 foot radius of the Treasure Island Bascule bridge located at 27°46′15″ N, 82°45′12″ W. 
                        </P>
                        <P>
                            (b) 
                            <E T="03">Definitions.</E>
                             As used in this section 
                            <E T="03">Designated representative</E>
                             means a Coast Guard Patrol Commander, including Coast Guard coxswains, petty officers and other officers operating Coast Guard vessels, and Federal, State, and local officers designated by or assisting the Captain of the Port of Miami in restricting vessels and persons from entering the temporary safety zone. 
                        </P>
                        <P>
                            (c) 
                            <E T="03">Regulations.</E>
                             In accordance with the general regulations in § 165.23 of this part, entry into this Regulated Area is prohibited to all vessels and persons without the prior permission of the Coast Guard Captain of the Port Sector St. Petersburg or his designated representative. 
                        </P>
                        <P>
                            (d) 
                            <E T="03">Enforcement Period.</E>
                             The regulated area will only be enforced from 8 a.m. until 6 p.m. on March 21 and April 18, 2007. 
                        </P>
                        <P>
                            (e) 
                            <E T="03">Effective Dates.</E>
                             This regulation is effective from 8 a.m. on March 21 through 6 p.m. on April 18, 2007.
                        </P>
                    </SECTION>
                </REGTEXT>
                <SIG>
                    <DATED>Dated: March 20, 2007. </DATED>
                    <NAME>J.A. Servidio, </NAME>
                    <TITLE>Captain, U.S. Coast Guard, Captain of the Port Sector St. Petersburg, Florida.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. E7-7073 Filed 4-12-07; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4910-15-P </BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF HOMELAND SECURITY </AGENCY>
                <SUBAGY>Federal Emergency Management Agency </SUBAGY>
                <CFR>44 CFR Part 65 </CFR>
                <SUBJECT>Changes in Flood Elevation Determinations </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Emergency Management Agency, DHS. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>Modified Base (1% annual-chance) Flood Elevations (BFEs) are finalized for the communities listed below. These modified BFEs will be used to calculate flood insurance premium rates for new buildings and their contents. </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The effective dates for these modified BFEs are indicated on the following table and revise the Flood Insurance Rate Maps (FIRMs) in effect for the listed communities prior to this date. </P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>The modified BFEs for each community are available for inspection at the office of the Chief Executive Officer of each community. The respective addresses are listed in the table below. </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>William R. Blanton, Jr., Engineering Management Section, Mitigation Division, Federal Emergency Management Agency, 500 C Street, SW., Washington, DC 20472, (202) 646-3151. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    The Federal Emergency Management Agency (FEMA) makes the final determinations listed below of the modified BFEs for each community listed. These modified 
                    <PRTPAGE P="18588"/>
                    BFEs have been published in newspapers of local circulation and ninety (90) days have elapsed since that publication. The Mitigation Division Director of FEMA resolved any appeals resulting from this notification. 
                </P>
                <P>The modified BFEs are not listed for each community in this notice. However, this final rule includes the address of the Chief Executive Officer of the community where the modified BFEs determinations are available for inspection. </P>
                <P>
                    The modified BFEs are made pursuant to section 206 of the Flood Disaster Protection Act of 1973, 42 U.S.C. 4105, and are in accordance with the National Flood Insurance Act of 1968, 42 U.S.C. 4001 
                    <E T="03">et seq.</E>
                    , and with 44 CFR part 65. 
                </P>
                <P>For rating purposes, the currently effective community number is shown and must be used for all new policies and renewals. </P>
                <P>The modified BFEs are the basis for the floodplain management measures that the community is required to either adopt or to show evidence of being already in effect in order to qualify or to remain qualified for participation in the National Flood Insurance Program (NFIP). </P>
                <P>These modified BFEs, together with the floodplain management criteria required by 44 CFR 60.3, are the minimum that are required. They should not be construed to mean that the community must change any existing ordinances that are more stringent in their floodplain management requirements. The community may at any time enact stricter requirements of its own, or pursuant to policies established by other Federal, State, or regional entities. </P>
                <P>These modified BFEs are used to meet the floodplain management requirements of the NFIP and are also used to calculate the appropriate flood insurance premium rates for new buildings built after these elevations are made final, and for the contents in these buildings. The changes in BFEs are in accordance with 44 CFR 65.4. </P>
                <P>
                    <E T="03">National Environmental Policy Act.</E>
                     This final rule is categorically excluded from the requirements of 44 CFR part 10, Environmental Consideration. An environmental impact assessment has not been prepared. 
                </P>
                <P>
                    <E T="03">Regulatory Flexibility Act.</E>
                     As flood elevation determinations are not within the scope of the Regulatory Flexibility Act, 5 U.S.C. 601-612, a regulatory flexibility analysis is not required. 
                </P>
                <P>
                    <E T="03">Regulatory Classification.</E>
                     This final rule is not a significant regulatory action under the criteria of section 3(f) of Executive Order 12866 of September 30, 1993, Regulatory Planning and Review, 58 FR 51735. 
                </P>
                <P>
                    <E T="03">Executive Order 13132, Federalism.</E>
                     This final rule involves no policies that have federalism implications under Executive Order 13132, Federalism. 
                </P>
                <P>
                    <E T="03">Executive Order 12988, Civil Justice Reform.</E>
                     This final rule meets the applicable standards of Executive Order 12988. 
                </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 44 CFR Part 65 </HD>
                    <P>Flood insurance, Floodplains, Reporting and recordkeeping requirements.</P>
                </LSTSUB>
                <REGTEXT TITLE="44" PART="65">
                    <AMDPAR>Accordingly, 44 CFR part 65 is amended to read as follows: </AMDPAR>
                    <PART>
                        <HD SOURCE="HED">PART 65—[AMENDED] </HD>
                    </PART>
                    <AMDPAR>1. The authority citation for part 65 continues to read as follows: </AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>
                            42 U.S.C. 4001 
                            <E T="03">et seq.</E>
                            ; Reorganization Plan No. 3 of 1978, 3 CFR, 1978 Comp., p. 329; E.O. 12127, 44 FR 19367, 3 CFR, 1979 Comp., p. 376. 
                        </P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="44" PART="65">
                    <SECTION>
                        <SECTNO>§ 65.4 </SECTNO>
                        <SUBJECT>[Amended] </SUBJECT>
                    </SECTION>
                    <AMDPAR>2. The tables published under the authority of § 65.4 are amended as follows: </AMDPAR>
                    <GPOTABLE COLS="6" OPTS="L2,tp0,p7,7/8,i1" CDEF="s50,r50,r75,r100,xs80,10">
                        <TTITLE>  </TTITLE>
                        <BOXHD>
                            <CHED H="1">State and county </CHED>
                            <CHED H="1">Location and case No. </CHED>
                            <CHED H="1">Date and name of newspaper where notice was published </CHED>
                            <CHED H="1">Chief executive officer of community </CHED>
                            <CHED H="1">
                                Effective date of 
                                <LI>modification </LI>
                            </CHED>
                            <CHED H="1">Community No. </CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="22">Arkansas: </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Crawford, (FEMA Docket No.: B-7467)</ENT>
                            <ENT>City of Van Buren (05-06-A486P)</ENT>
                            <ENT>
                                May 17, 2006; May 24, 2006; 
                                <E T="03">Press Argus-Courier</E>
                            </ENT>
                            <ENT>The Honorable John Riggs, Mayor, City of Van Buren, 1003 Broadway, Van Buren, Arkansas 72956</ENT>
                            <ENT>April 27, 2006</ENT>
                            <ENT>050053 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Pulaski, (FEMA Docket No.: B-7467)</ENT>
                            <ENT>City of Jacksonville (05-06-1464P)</ENT>
                            <ENT>
                                December 21, 2005; December 28, 2005; 
                                <E T="03">Jacksonville Patriot</E>
                            </ENT>
                            <ENT>The Honorable Tommy Swaim, Mayor, City of Jacksonville, One Municipal Drive, Jacksonville, Arkansas 72076</ENT>
                            <ENT>March 29, 2006</ENT>
                            <ENT>050180 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Pulaski, (FEMA Docket No.: B-7467)</ENT>
                            <ENT>City of North Little Rock (05-06-1777P)</ENT>
                            <ENT>
                                April 13, 2006; April 20, 2006; 
                                <E T="03">North Little Rock Times</E>
                            </ENT>
                            <ENT>The Honorable Patrick H. Hays, Mayor, City of North Little Rock, 300 Main Street, North Little Rock, Arkansas 72114</ENT>
                            <ENT>July 20, 2006</ENT>
                            <ENT>050182 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Pulaski, (FEMA Docket No.: B-7467)</ENT>
                            <ENT>Unincorporated Areas of Pulaski County (05-06-1777P)</ENT>
                            <ENT>
                                April 13, 2006; April 20, 2006; 
                                <E T="03">North Little Rock Times</E>
                            </ENT>
                            <ENT>The Honorable Floyd G. Villines, Pulaski County Judge, Pulaski County Courthouse, 201 South Broadway, Little Rock, Arkansas 72201</ENT>
                            <ENT>July 20, 2006</ENT>
                            <ENT>050179 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">Arizona: </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Maricopa, (FEMA Docket No.: B-7467)</ENT>
                            <ENT>City of Glendale (06-09-B380P)</ENT>
                            <ENT>
                                July 20, 2006; July 27, 2006; 
                                <E T="03">Arizona Business Gazette</E>
                            </ENT>
                            <ENT>The Honorable Elaine Scrugss, Mayor, City of Glendale, 5850 West Glendale Avenue, Glendale, Arizona 85301</ENT>
                            <ENT>October 26, 2006</ENT>
                            <ENT>040045 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Maricopa, (FEMA Docket No.: B-7467)</ENT>
                            <ENT>City of Goodyear (05-09-0791P)</ENT>
                            <ENT>
                                June 15, 2006; June 22, 2006; 
                                <E T="03">Arizona Business Gazette</E>
                            </ENT>
                            <ENT>The Honorable Jim Cavanaugh, Mayor, City of Goodyear, 190 North Litchfield Road, Goodyear, Arizona 85338</ENT>
                            <ENT>June 30, 2006</ENT>
                            <ENT>040046 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Maricopa, (FEMA Docket No.: B-7467)</ENT>
                            <ENT>City of Litchfield Park (05-09-0791P)</ENT>
                            <ENT>
                                June 15, 2006; June 22, 2006; 
                                <E T="03">Arizona Business Gazette</E>
                            </ENT>
                            <ENT>The Honorable J. Woodfin Thomas, Mayor, City of Litchfield Park, 214 West Wigman Boulevard, Litchfield Park, Arizona 85340</ENT>
                            <ENT>June 30, 2006</ENT>
                            <ENT>040128 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Maricopa, (FEMA Docket No.: B-7467)</ENT>
                            <ENT>City of Peoria (06-09-B380P)</ENT>
                            <ENT>
                                July 20, 2006; July 27, 2006; 
                                <E T="03">Arizona Business Gazette</E>
                            </ENT>
                            <ENT>The Honorable John Keegan, Mayor, City of Peoria, 8410 West Monroe Street, Peoria, Arizona 85345</ENT>
                            <ENT>October 26, 2006</ENT>
                            <ENT>040050 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">Connecticut: </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Fairfield, (FEMA Docket No.: B-7467)</ENT>
                            <ENT>Town of Greenwich (05-01-0751P)</ENT>
                            <ENT>
                                February 16, 2006; February 23, 2006; 
                                <E T="03">The Greenwich Time</E>
                            </ENT>
                            <ENT>Mr. Jim Lash, First Selectman, Town of Greenwich, Town Hall, First Floor, 101 Field Point Road, Greenwich, Connecticut 06830</ENT>
                            <ENT>May 25, 2006</ENT>
                            <ENT>090008 </ENT>
                        </ROW>
                        <ROW>
                            <PRTPAGE P="18589"/>
                            <ENT I="03">New Haven, (FEMA Docket No.: B-7467)</ENT>
                            <ENT>Town of Madison (05-01-0798P)</ENT>
                            <ENT>
                                August 24, 2006; August 31, 2006; 
                                <E T="03">New Haven Register</E>
                            </ENT>
                            <ENT>The Honorable Thomas S. Scarpati, Selectman, Town of Madison, Town Hall, 8 Campus Drive, Madison, Connecticut 06443</ENT>
                            <ENT>June 30, 2006</ENT>
                            <ENT>090079 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">Delaware: </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">New Castle, (FEMA Docket No.: B-7467)</ENT>
                            <ENT>Unincorporated Areas of New Castle County (05-03-0432P)</ENT>
                            <ENT>
                                July 27, 2006; August 3, 2006; 
                                <E T="03">The News Journal</E>
                            </ENT>
                            <ENT>The Honorable Christopher A. Coons, New Castle County Executive, New Castle County Government Center, 87 Reads Way, New Castle, Delaware 19720</ENT>
                            <ENT>November 2, 2006</ENT>
                            <ENT>105085 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">New Castle, (FEMA Docket No.: B-7467)</ENT>
                            <ENT>Unincorporated Areas of New Castle County (05-03-0872P)</ENT>
                            <ENT>
                                August 24, 2006; August 31, 2006; 
                                <E T="03">The News Journal</E>
                            </ENT>
                            <ENT>The Honorable Christopher A. Coons, New Castle County Executive, New Castle County Government Center, 87 Reads Way, New Castle, Delaware 19720</ENT>
                            <ENT>November 30, 2006</ENT>
                            <ENT>105085 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">New Castle, (FEMA Docket No.: B-7467)</ENT>
                            <ENT>Unincorporated Areas of New Castle County (05-03-0955P)</ENT>
                            <ENT>
                                June 22, 2006; June 29, 2006; 
                                <E T="03">The News Journal</E>
                            </ENT>
                            <ENT>The Honorable Christopher A. Coons, New Castle County Executive, New Castle County Government Center, 87 Reads Way, New Castle, Delaware 19720</ENT>
                            <ENT>September 28, 2006</ENT>
                            <ENT>105085 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">New Castle, (FEMA Docket No.: B-7467)</ENT>
                            <ENT>Unincorporated Areas of New Castle County (05-03-1010P)</ENT>
                            <ENT>
                                April 14, 2006; April 21, 2006; 
                                <E T="03">Newark Post</E>
                            </ENT>
                            <ENT>The Honorable Christopher A. Coons, New Castle County Executive, New Castle County Gov't Center, 87 Reads Way, New Castle, Delaware 19720</ENT>
                            <ENT>March 28, 2006</ENT>
                            <ENT>105085 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Sussex, (FEMA Docket No.: B-7467)</ENT>
                            <ENT>Town of Dagsboro (05-03-0353P)</ENT>
                            <ENT>
                                December 28, 2005; January 4, 2006; 
                                <E T="03">Delaware Wave</E>
                            </ENT>
                            <ENT>The Honorable Brad Conner, Mayor, Town of Dagsboro, P.O. Box 420, Dagsboro, Delaware 19939</ENT>
                            <ENT>April 5, 2006</ENT>
                            <ENT>100033 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Sussex, (FEMA Docket No.: B-7467)</ENT>
                            <ENT>Unincorporated Areas of Sussex County (05-03-0353P)</ENT>
                            <ENT>
                                December 28, 2005; January 4, 2006; 
                                <E T="03">Delaware Wave</E>
                            </ENT>
                            <ENT>Mr. Robert L. Stickels, County Administrator, Sussex County, P.O. Box 589, Georgetown, Delaware 19947</ENT>
                            <ENT>April 5, 2006</ENT>
                            <ENT>100029 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">Florida: </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Duvall, (FEMA Docket No.: B-7703)</ENT>
                            <ENT>City of Jacksonville (06-04-BL18P)</ENT>
                            <ENT>
                                November 20, 2006; November 27, 2006; 
                                <E T="03">Jacksonville Daily Record</E>
                            </ENT>
                            <ENT>The Honorable John Peyton, Mayor, City of Jacksonville, 117 West Duval Street, Jacksonville, Florida 32202</ENT>
                            <ENT>October 31, 2006</ENT>
                            <ENT>120077 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Duvall, (FEMA Docket No.: B-7703)</ENT>
                            <ENT>City of Jacksonville (06-04-BL19P)</ENT>
                            <ENT>
                                November 27, 2006; December 4, 2006; 
                                <E T="03">Jacksonville Daily Record</E>
                            </ENT>
                            <ENT>The Honorable John Peyton, Mayor, City of Jacksonville, City Hall at St. James, Fourth Floor, 117 West Duval Street, Jacksonville, Florida 32202</ENT>
                            <ENT>December 1, 2006</ENT>
                            <ENT>120077 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">Idaho: </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Canyon, (FEMA Docket No.: B-7467)</ENT>
                            <ENT>Unincorporated Areas of Canyon County (05-10-0594P)</ENT>
                            <ENT>
                                April 20, 2006; April 27, 2006; 
                                <E T="03">Idaho Press-Tribune</E>
                            </ENT>
                            <ENT>The Honorable Matt Beebe, Chairman, Canyon County, Board of Commissioners, 1115 Albany Street, Caldwell, Idaho 83605</ENT>
                            <ENT>July 27, 2006</ENT>
                            <ENT>160208 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Caribou, (FEMA Docket No.: B-7467)</ENT>
                            <ENT>City of Bancroft (06-10-B109P)</ENT>
                            <ENT>
                                June 22, 2006; June 29, 2006; 
                                <E T="03">Caribou County Sun</E>
                            </ENT>
                            <ENT>The Honorable William Lester, Mayor, City of Bancroft, P.O. Box 549, Bancroft, Idaho 83217</ENT>
                            <ENT>May 31, 2006</ENT>
                            <ENT>160040 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">Louisiana: </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">St. Tammany Parish, (FEMA Docket No.: B-7467)</ENT>
                            <ENT>St. Tammany Parish (06-06-BA65P)</ENT>
                            <ENT>
                                August 2, 2006; August 9, 2006; 
                                <E T="03">St. Tammany News</E>
                            </ENT>
                            <ENT>The Honorable Kevin Davis, Parish President, St. Tammany Parish, P.O. Box 628, Covington, Louisiana 70434</ENT>
                            <ENT>November 8, 2006</ENT>
                            <ENT>225205 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">St. Tammany Parish, (FEMA Docket No.: B-7467)</ENT>
                            <ENT>St. Tammany Parish (06-06-BD86P)</ENT>
                            <ENT>
                                September 13, 2006; September 20, 2006; 
                                <E T="03">St. Tammany News</E>
                            </ENT>
                            <ENT>The Honorable Kevin Davis, Parish President, St. Tammany Parish, P.O. Box 628, Covington, Louisiana 70434</ENT>
                            <ENT>August 25, 2006</ENT>
                            <ENT>225205 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">Maine: </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Cumberland, (FEMA Docket No.: B-7467)</ENT>
                            <ENT>City of Falmouth (06-01-B534P)</ENT>
                            <ENT>
                                August 17, 2006; August 24, 2006; 
                                <E T="03">Falmouth Community Leader</E>
                            </ENT>
                            <ENT>Mr. John D. Harris, Town Manager, Town of Falmouth, 271 Falmouth Road, Falmouth, Maine 04105</ENT>
                            <ENT>November 23, 2006</ENT>
                            <ENT>230045 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Cumberland, (FEMA Docket No.: B-7467)</ENT>
                            <ENT>Town of Harpswell (05-01-B113P)</ENT>
                            <ENT>
                                June 15, 2006; June 22, 2006; 
                                <E T="03">Portland Press Herald</E>
                            </ENT>
                            <ENT>The Honorable Gordon L. Weil, Chair, Board of Selectmen, Town of Harpswell, P.O. Box 39, Harpswell, Maine 04079</ENT>
                            <ENT>May 25, 2006</ENT>
                            <ENT>230169 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Cumberland, (FEMA Docket No.: B-7467)</ENT>
                            <ENT>Town of Standish (05-01-A566P)</ENT>
                            <ENT>
                                May 11, 2006; May 18, 2006; 
                                <E T="03">Portland Press Herald</E>
                            </ENT>
                            <ENT>Mr. Gordon F. Billington, Town Manager, Town of Standish, 175 Northeast Road, Standish, Maine 04084</ENT>
                            <ENT>August 17, 2006</ENT>
                            <ENT>230207 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Washington, (FEMA Docket No.: B-7467)</ENT>
                            <ENT>Town of Milbridge (05-01-0691P)</ENT>
                            <ENT>
                                May 11, 2006; May 18, 2006; 
                                <E T="03">Bangor Daily News</E>
                            </ENT>
                            <ENT>Mr. Fred Ventresco, Town Manager, Town of Milbridge, P.O. Box 66, Milbridge, Maine 04658, </ENT>
                            <ENT>April 24, 2006, </ENT>
                            <ENT>230142 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">York, (FEMA Docket No.: B-7467)</ENT>
                            <ENT>Town of Alfred (05-01-B101X)</ENT>
                            <ENT>
                                February 23, 2006; March 2, 2006; 
                                <E T="03">York County Coast Star</E>
                            </ENT>
                            <ENT>The Honorable John Sylvestor, Chair, Board of Selectman, Town of Alfred, P.O. Box 667, Alfred, Maine 04002</ENT>
                            <ENT>June 1, 2006</ENT>
                            <ENT>230191 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">York, (FEMA Docket No.: B-7467)</ENT>
                            <ENT>Town of Lyman (05-01-B101X)</ENT>
                            <ENT>
                                February 23, 2006; March 2, 2006; 
                                <E T="03">York County Coast Star</E>
                            </ENT>
                            <ENT>The Honorable Norman Hutchins, Chair, Board of Selectman, Town of Lyman, 11 South Waterboro Road, Lyman, Maine 04002</ENT>
                            <ENT>June 1, 2006</ENT>
                            <ENT>230195 </ENT>
                        </ROW>
                        <ROW>
                            <PRTPAGE P="18590"/>
                            <ENT I="22">Maryland: </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Carroll, (FEMA Docket No.: B-7467)</ENT>
                            <ENT>Unincorporated Areas of Carroll County (05-03-0321P)</ENT>
                            <ENT>
                                August 31, 2006; September 7, 2006; 
                                <E T="03">Carroll County Times</E>
                            </ENT>
                            <ENT>The Honorable Julia W. Gouge, President, Carroll County, Board of Commissioners, 225 North Center Street, Westminster, Maryland 21157</ENT>
                            <ENT>December 7, 2006</ENT>
                            <ENT>240015 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Frederick, (FEMA Docket No.: B-7467)</ENT>
                            <ENT>City of Frederick (05-03-0831P)</ENT>
                            <ENT>
                                June 14, 2006; June 21, 2006; 
                                <E T="03">The Frederick News Post</E>
                            </ENT>
                            <ENT>The Honorable William J. Holtzinger, Mayor, City of Frederick, City Hall, 101 North Court Street, Frederick, Maryland 21701-5415</ENT>
                            <ENT>September 21, 2006</ENT>
                            <ENT>240030 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Frederick, (FEMA Docket No.: B-7467)</ENT>
                            <ENT>Unincorporated Areas of Frederick County (05-03-0831P)</ENT>
                            <ENT>
                                June 14, 2006; June 21, 2006; 
                                <E T="03">The Frederick News Post</E>
                            </ENT>
                            <ENT>The Honorable John L. Thompson, President, Frederick County, Board of Commissioners, 12 East Church Street, Frederick, Maryland 21701</ENT>
                            <ENT>September 21, 2006</ENT>
                            <ENT>240027 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">Massachusetts: </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Barnstable, (FEMA Docket No.: B-7467)</ENT>
                            <ENT>Town of Barnstable (05-01-0764P)</ENT>
                            <ENT>
                                March 30, 2006; April 6, 2006; 
                                <E T="03">Cape Cod Times</E>
                            </ENT>
                            <ENT>Mr. John C. Klimm, Town Manager, Town of Barnstable, Barnstable Town Hall, 369 Main Street, Hyannis, Massachusetts 02601</ENT>
                            <ENT>March 14, 2006</ENT>
                            <ENT>250001 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Barnstable, (FEMA Docket No.: B-7467)</ENT>
                            <ENT>Town of Bourne (05-01-A062P)</ENT>
                            <ENT>
                                May 25, 2006; June 1, 2006; 
                                <E T="03">Cape Cod Times</E>
                            </ENT>
                            <ENT>Mr. Thomas Guerino, Town Administrator, Town of Bourne, Town Hall, 24 Perry Avenue, Bourne, Massachusetts 02532</ENT>
                            <ENT>August 31, 2006</ENT>
                            <ENT>255210 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Barnstable, (FEMA Docket No.: B-7467)</ENT>
                            <ENT>Town of Provincetown (05-01-0580P)</ENT>
                            <ENT>
                                May 11, 2006; May 18, 2006; 
                                <E T="03">Cape Cod Times</E>
                            </ENT>
                            <ENT>Mr. Keith A. Bergman, Town Manager, Town of Provincetown, Provincetown Town Hall, 260 Commercial Street, Provincetown, Massachusetts 02657</ENT>
                            <ENT>April 24, 2006</ENT>
                            <ENT>255218 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Plymouth, (FEMA Docket No.: B-7467)</ENT>
                            <ENT>Town of Duxbury (05-01-0410P)</ENT>
                            <ENT>
                                December 1, 2005; December 8, 2005; 
                                <E T="03">The Enterprise</E>
                            </ENT>
                            <ENT>The Honorable John J. Tuffy, Chairman, Board of Selectman, Town of Duxbury, Town Hall, 878 Tremont Street, Duxbury, Massachusetts 02332</ENT>
                            <ENT>November 7, 2005</ENT>
                            <ENT>250263 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Worcester, (FEMA Docket No.: B-7467)</ENT>
                            <ENT>Town of Milford (05-01-0129P)</ENT>
                            <ENT>
                                December 8, 2005; December 15, 2005; 
                                <E T="03">Milford Daily News</E>
                            </ENT>
                            <ENT>The Honorable Dino B. DeBartolomeis, Chairman, Board of Selectman, Town of Milford, 52 Main Street, Milford, Massachusetts 01757</ENT>
                            <ENT>December 21, 2005</ENT>
                            <ENT>250317 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">Mississippi: </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Rankin, (FEMA Docket No.: B-7467)</ENT>
                            <ENT>City of Brandon (06-04-B977P)</ENT>
                            <ENT>
                                August 16, 2006; August 23, 2006; 
                                <E T="03">Rankin County News</E>
                            </ENT>
                            <ENT>The Honorable Carlo Martella, Mayor, City of Brandon, P.O. Box 1539, Brandon, Mississippi 39043</ENT>
                            <ENT>November 22, 2006</ENT>
                            <ENT>280143 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Rankin, (FEMA Docket No.: B-7474)</ENT>
                            <ENT>City of Pearl (06-04-B935P)</ENT>
                            <ENT>
                                September 20, 2006; September 27, 2006; 
                                <E T="03">Rankin County News</E>
                            </ENT>
                            <ENT>The Honorable Jimmy Foster, Mayor, City of Pearl, 2420 Old Brandon Rd, Pearl, Mississippi 39208</ENT>
                            <ENT>December 27, 2006</ENT>
                            <ENT>280145 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">New Jersey: </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Middlesex, (FEMA Docket No.: B-7466)</ENT>
                            <ENT>City of South Amboy (05-02-0716P)</ENT>
                            <ENT>
                                April 12, 2006; April 19, 2006; 
                                <E T="03">Home News Tribune</E>
                            </ENT>
                            <ENT>The Honorable John T. O'Leary, Jr., Mayor, City of South Amboy, Municipal Building, 140 North Broadway, South Amboy, New Jersey 08879</ENT>
                            <ENT>March 29, 2006</ENT>
                            <ENT>340277 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Ocean, (FEMA Docket No.: B-7466)</ENT>
                            <ENT>Township of Jackson (04-02-A038P)</ENT>
                            <ENT>
                                August 24, 2006; August 31, 2006; 
                                <E T="03">Ocean County Observer</E>
                            </ENT>
                            <ENT>The Honorable Mark A. Seda Mayor, Township of Jackson 95 West Veterans Highway Jackson, New Jersey 08527</ENT>
                            <ENT>August 7, 2006</ENT>
                            <ENT>340375 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Union, (FEMA Docket No.: B-7466)</ENT>
                            <ENT>Borough of Roselle Park (05-02-0038P)</ENT>
                            <ENT>
                                January 26, 2006; February 2, 2006; 
                                <E T="03">Newark Star Ledger</E>
                            </ENT>
                            <ENT>The Honorable Joseph DeIorio, Mayor, Borough of Roselle Park, 110 East Westfield Avenue, Roselle, New Jersey 07204</ENT>
                            <ENT>January 11, 2006</ENT>
                            <ENT>340473 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">New Mexico: </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Bernalillo, (FEMA Docket No.: B-7466)</ENT>
                            <ENT>City of Albuquerque (06-06-BC48P)</ENT>
                            <ENT>
                                August 17, 2006; August 24, 2006; 
                                <E T="03">Albuquerque Journal</E>
                                  
                            </ENT>
                            <ENT>The Honorable Martin J Chavez, Mayor, City of Albuquerque, P.O. Box 1293, Albuquerque, New Mexico 87103</ENT>
                            <ENT>July 26, 2006</ENT>
                            <ENT>350002 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Chaves, (FEMA Docket No.: B-7466)</ENT>
                            <ENT>City of Roswell (06-06-B752P)</ENT>
                            <ENT>
                                June 22, 2006; June 29, 2006; 
                                <E T="03">Roswell Daily Record</E>
                            </ENT>
                            <ENT>The Honorable Sam D. LaGrone, Mayor, City of Roswell, P.O. Box 1838, Roswell, New Mexico 88202</ENT>
                            <ENT>May 30, 2006</ENT>
                            <ENT>350006 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Sandoval, (FEMA Docket No.: B-7466)</ENT>
                            <ENT>City of Rio Rancho (05-06-0661P)</ENT>
                            <ENT>
                                November 28, 2005; November 30, 2005; 
                                <E T="03">Santa Fe New Mexican</E>
                            </ENT>
                            <ENT>The Honorable Jim Owen, Mayor, City of Rio Rancho, 3900 Southern Boulevard, Rio Rancho, New Mexico 87124</ENT>
                            <ENT>November 14, 2005</ENT>
                            <ENT>350146 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">New York: </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Orange, (FEMA Docket No.: B-7466)</ENT>
                            <ENT>Town of Wallkill (06-02-B016P)</ENT>
                            <ENT>
                                July 27, 2006; August 3, 2006; 
                                <E T="03">Times Herald-Record</E>
                            </ENT>
                            <ENT>Mr. John Ward, Supervisor, Town of Wallkill, P.O. Box 398, Middletown, New York 10940</ENT>
                            <ENT>June 30, 2006</ENT>
                            <ENT>360634 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">Oklahoma: </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Oklahoma, (FEMA Docket No.: B-7466)</ENT>
                            <ENT>City of Edmond (05-06-1554P)</ENT>
                            <ENT>
                                April 12, 2006; April 19, 2006; 
                                <E T="03">The Edmond Sun</E>
                            </ENT>
                            <ENT>The Honorable Saundra Naifeh, Mayor, City of Edmond, P.O. Box 2970, Edmond, Oklahoma 73083</ENT>
                            <ENT>July 19, 2006</ENT>
                            <ENT>400252 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Oklahoma, (FEMA Docket No.: B-7466)</ENT>
                            <ENT>City of Midwest (05-06-0976P)</ENT>
                            <ENT>
                                August 23, 2006; August 30, 2006; 
                                <E T="03">The Sun</E>
                            </ENT>
                            <ENT>The Honorable Eddie Reed, Mayor, City of Midwest City, P.O. Box 10870, Midwest City, Oklahoma 73140</ENT>
                            <ENT>August 28, 2006</ENT>
                            <ENT>400405 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Pottawatomie, (FEMA Docket No.: B-7466)</ENT>
                            <ENT>City of Shawnee (06-06-B821P)</ENT>
                            <ENT>
                                August 17, 2006; August 24, 2006; 
                                <E T="03">The Shawnee News-Star</E>
                            </ENT>
                            <ENT>The Honorable Chuck Mills, Mayor, City of Shawnee, P.O. Box 1448, Shawnee, Oklahoma 74802-1448</ENT>
                            <ENT>July 31, 2006</ENT>
                            <ENT>400178 </ENT>
                        </ROW>
                        <ROW>
                            <PRTPAGE P="18591"/>
                            <ENT I="03">Tulsa, (FEMA Docket No.: B-7466)</ENT>
                            <ENT>City of Tulsa (05-06-A125P)</ENT>
                            <ENT>
                                August 10, 2006; August 17, 2006; 
                                <E T="03">Tulsa World</E>
                            </ENT>
                            <ENT>The Honorable Kathy Taylor, Mayor, City of Tulsa, 200 Civic Center, Tulsa, Oklahoma 74103</ENT>
                            <ENT>November 16, 2006</ENT>
                            <ENT>405381 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">Oregon: </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Marion, (FEMA Docket No.: B-7466)</ENT>
                            <ENT>City of Stayton (03-10-0442P)</ENT>
                            <ENT>
                                February 2, 2006; February 9, 2006; 
                                <E T="03">The Statesman Journal</E>
                            </ENT>
                            <ENT>The Honorable Gerry Aboud, Mayor, City of Stayton, 362 North Third Avenue, Stayton, Oregon 97383</ENT>
                            <ENT>May 11, 2006</ENT>
                            <ENT>410170 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Marion, (FEMA Docket No.: B-7466)</ENT>
                            <ENT>Unincorporated Areas of Marion County (03-10-0442P)</ENT>
                            <ENT>
                                February 2, 2006; February 9, 2006; 
                                <E T="03">The Statesman Journal</E>
                            </ENT>
                            <ENT>The Honorable Sam Brentano, Chairman, Marion County, Board of Commissioners, P.O. Box 14500, Salem, Oregon 97309</ENT>
                            <ENT>May 11, 2006</ENT>
                            <ENT>410154 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">Pennsylvania: </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Berks, (FEMA Docket No.: B-7466)</ENT>
                            <ENT>Township of Longswamp (05-03-0239P)</ENT>
                            <ENT>
                                March 2, 2006; March 9, 2006; 
                                <E T="03">Reading Eagle</E>
                            </ENT>
                            <ENT>The Honorable Donald C. Stegfried, Chairman, Longswamp Township, 1112 State Street, Mertztown, Pennsylvania 19539</ENT>
                            <ENT>June 8, 2006</ENT>
                            <ENT>421380 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Berks, (FEMA Docket No.: B-7466)</ENT>
                            <ENT>Township of Rockland (05-03-0239P)</ENT>
                            <ENT>
                                March 2, 2006; March 9, 2006; 
                                <E T="03">Reading Eagle</E>
                            </ENT>
                            <ENT>The Honorable Russell W. Coffin, Chairman, Rockland Township, Board of Supervisors, P.O. Box 149, Bowers, Pennsylvania 19511</ENT>
                            <ENT>June 8, 2006</ENT>
                            <ENT>421098 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Puerto Rico, (FEMA Docket No.: B-7466)</ENT>
                            <ENT>Commonwealth of Puerto Rico (05-02-0270P)</ENT>
                            <ENT>
                                August 17, 2006; August 24, 2006; 
                                <E T="03">The San Juan Star</E>
                            </ENT>
                            <ENT>The Honorable Anibal Acevedo-Vila, Governor of the Commonwealth of Puerto Rico, P.O. Box 82, La Fortaleza, San Juan, Puerto Rico 00901</ENT>
                            <ENT>November 23, 2006</ENT>
                            <ENT>720000 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Puerto Rico, (FEMA Docket No.: B-7466)</ENT>
                            <ENT>Commonwealth of Puerto Rico (05-02-0421P)</ENT>
                            <ENT>
                                June 29, 2006; July 6, 2006; 
                                <E T="03">The San Juan Star</E>
                            </ENT>
                            <ENT>The Honorable Anibal Acevedo-Vila, Governor of the Commonwealth of Puerto Rico, P.O. Box 82, La Fortaleza, San Juan, Puerto Rico 00901</ENT>
                            <ENT>October 5, 2006</ENT>
                            <ENT>720000 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">Rhode Island: </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Washington, (FEMA Docket No.: B-7466)</ENT>
                            <ENT>Town of Westerly (05-01-A502P)</ENT>
                            <ENT>
                                June 22, 2006; June 29, 2006; 
                                <E T="03">Westerly Sun</E>
                            </ENT>
                            <ENT>Mr. Joseph T. Turo, Esq., Town Manager, Town of Westerly, Town Hall, 45 Broad Street, Westerly, Rhode Island 02891</ENT>
                            <ENT>May 25, 2006</ENT>
                            <ENT>445410 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">Texas: </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Bexar, (FEMA Docket No.: B-7466)</ENT>
                            <ENT>City of San Antonio (05-06-0892P)</ENT>
                            <ENT>
                                December 8, 2005; December 15, 2005; 
                                <E T="03">Austin American-Statesman</E>
                            </ENT>
                            <ENT>The Honorable Phil Hardberger, Mayor, City of San Antonio, P.O. Box 839966, San Antonio, Texas 78283-3966</ENT>
                            <ENT>March 16, 2006</ENT>
                            <ENT>480045 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Bexar, (FEMA Docket No.: B-7466)</ENT>
                            <ENT>City of San Antonio (05-06-1714P)</ENT>
                            <ENT>
                                February 24, 2006; March 3, 2006; 
                                <E T="03">Daily Commercial Recorder</E>
                            </ENT>
                            <ENT>The Honorable Phil Hardberger, Mayor, City of San Antonio, P.O. Box 839966, San Antonio, Texas 78283</ENT>
                            <ENT>June 1, 2006</ENT>
                            <ENT>480045 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Bexar, (FEMA Docket No.: B-7466)</ENT>
                            <ENT>City of San Antonio (05-06-A206P)</ENT>
                            <ENT>
                                April 27, 2006; May 5, 2006; 
                                <E T="03">Daily Commercial Recorder</E>
                            </ENT>
                            <ENT>The Honorable Phil Hardberger, Mayor, City of San Antonio, P.O. Box 839966, San Antonio, Texas 78283</ENT>
                            <ENT>August 4, 2006</ENT>
                            <ENT>480045 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Bexar, (FEMA Docket No.: B-7466)</ENT>
                            <ENT>Unincorporated Areas of Bexar County (05-06-A206P)</ENT>
                            <ENT>
                                April 27, 2006; May 5, 2006; 
                                <E T="03">Daily Commercial Recorder</E>
                            </ENT>
                            <ENT>The Honorable Nelson W. Wolff, Bexar County Judge, Bexar County Courthouse, 230 North Pecos, Suite 420, San Antonio, Texas 78205</ENT>
                            <ENT>August 4, 2006</ENT>
                            <ENT>480035 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Bexar, (FEMA Docket No.: B-7466)</ENT>
                            <ENT>Unincorporated Areas of Bexar County (05-06-A521P)</ENT>
                            <ENT>
                                August 24, 2006; August 31, 2006; 
                                <E T="03">Daily Commercial Recorder</E>
                            </ENT>
                            <ENT>The Honorable Nelson W. Wolff, Bexar County Judge, Bexar County Courthouse, 230 North Pecos, Suite 420, San Antonio, Texas 78205</ENT>
                            <ENT>July 31, 2006</ENT>
                            <ENT>480035 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Bexar, (FEMA Docket No.: B-7466)</ENT>
                            <ENT>Unincorporated Areas of Bexar County (06-06-A673P)</ENT>
                            <ENT>
                                June 22, 2006; June 29, 2006; 
                                <E T="03">Daily Commercial Recorder</E>
                            </ENT>
                            <ENT>The Honorable Nelson W. Wolff, Bexar County Judge, Bexar County Courthouse, 230 North Pecos, Suite 420, San Antonio, Texas 78205</ENT>
                            <ENT>September 28, 2006</ENT>
                            <ENT>480035 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Collin, (FEMA Docket No.: B-7466)</ENT>
                            <ENT>City of Frisco (05-06-1675P)</ENT>
                            <ENT>
                                September 8, 2006; September 15, 2006; 
                                <E T="03">Frisco Enterprise</E>
                            </ENT>
                            <ENT>The Honorable Mike Simpson, Mayor, City of Frisco, 6891 Main Street, Frisco, Texas 75034</ENT>
                            <ENT>December 15, 2006</ENT>
                            <ENT>480134 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Collin, (FEMA Docket No.: B-7466)</ENT>
                            <ENT>City of McKinney (05-06-A318P)</ENT>
                            <ENT>
                                April 20, 2006; April 27, 2006; 
                                <E T="03">McKinney Courier-Gazette</E>
                            </ENT>
                            <ENT>The Honorable Bill Whitfield, Mayor, City of McKinney, 222 North Tennessee, McKinney, Texas 75069</ENT>
                            <ENT>July 27, 2006</ENT>
                            <ENT>480135 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Collin, (FEMA Docket No.: B-7466)</ENT>
                            <ENT>City of McKinney (06-06-B170P)</ENT>
                            <ENT>
                                August 24, 2006; August 31, 2006; 
                                <E T="03">McKinney Courier-Gazette</E>
                            </ENT>
                            <ENT>The Honorable Bill Whitfield, Mayor, City of McKinney, 222 North Tennessee, McKinney, Texas 75069</ENT>
                            <ENT>November 30, 2006</ENT>
                            <ENT>480135 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Collin, (FEMA Docket No.: B-7466)</ENT>
                            <ENT>City of Plano (06-06-B005P)</ENT>
                            <ENT>
                                March 16, 2006; March 23, 2006; 
                                <E T="03">Plano Star Courier</E>
                            </ENT>
                            <ENT>The Honorable Pat Evans, Mayor, City of Plano, P.O. Box 860358, Plano, Texas 75086-0358</ENT>
                            <ENT>February 24, 2006</ENT>
                            <ENT>480140 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Collin, (FEMA Docket No.: B-7466)</ENT>
                            <ENT>City of Plano (06-06-B026P)</ENT>
                            <ENT>
                                July 19, 2006; July 26, 2006; 
                                <E T="03">Plano Star Courier</E>
                            </ENT>
                            <ENT>The Honorable Pat Evans, Mayor, City of Plano, P.O. Box 860358, Plano, Texas 75074</ENT>
                            <ENT>October 25, 2006</ENT>
                            <ENT>480140 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Denton, (FEMA Docket No.: B-7466)</ENT>
                            <ENT>City of Corinth (05-06-1383P)</ENT>
                            <ENT>
                                March 9, 2006; March 16, 2006; 
                                <E T="03">Denton Record-Chronicle</E>
                            </ENT>
                            <ENT>The Honorable Vic Burgess, Mayor, Town of Corinth, 3300 Corinth Street, Corinth, Texas 76205</ENT>
                            <ENT>June 15, 2006</ENT>
                            <ENT>481143 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Denton, (FEMA Docket No.: B-7466)</ENT>
                            <ENT>City of Denton (05-06-1383P)</ENT>
                            <ENT>
                                March 9, 2006; March 16, 2006; 
                                <E T="03">Denton Record-Chronicle</E>
                            </ENT>
                            <ENT>The Honorable Euline Brock, Mayor, City of Denton, 215 East McKinney Street, Denton, Texas 76201</ENT>
                            <ENT>June 15, 2006</ENT>
                            <ENT>480194 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Denton, (FEMA Docket No.: B-7466)</ENT>
                            <ENT>City of Denton (05-06-A100P)</ENT>
                            <ENT>
                                August 10, 2006; August 17, 2006; 
                                <E T="03">Denton Record-Chronicle</E>
                            </ENT>
                            <ENT>The Honorable Michael Conduff, Mayor, City of Denton, 215 East McKinney, Denton, Texas 76201</ENT>
                            <ENT>November 16, 2006</ENT>
                            <ENT>480194 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Denton, (FEMA Docket No.: B-7466)</ENT>
                            <ENT>City of Lewisville (05-06-0170P)</ENT>
                            <ENT>
                                January 4, 2006; January 11, 2006; 
                                <E T="03">Lewisville Leader</E>
                            </ENT>
                            <ENT>The Honorable Gene Carey, Mayor, City of Lewisville, P.O. Box 299002, Lewisville, Texas 75029-9002</ENT>
                            <ENT>April 12, 2006</ENT>
                            <ENT>480195 </ENT>
                        </ROW>
                        <ROW>
                            <PRTPAGE P="18592"/>
                            <ENT I="03">Denton, (FEMA Docket No.: B-7466)</ENT>
                            <ENT>City of Ponder (06-06-B215P)</ENT>
                            <ENT>
                                July 13, 2006; July 20, 2006; 
                                <E T="03">Denton Record Chronicle</E>
                            </ENT>
                            <ENT>The Honorable Vivian Cockburn, Mayor, City of Ponder, P.O. Box 297, Ponder, Texas 76259</ENT>
                            <ENT>October 19, 2006</ENT>
                            <ENT>480784 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Denton, (FEMA Docket No.: B-7466)</ENT>
                            <ENT>Unincorporated Areas of Denton County (05-06-A100P)</ENT>
                            <ENT>
                                August 10, 2006; August 17, 2006; 
                                <E T="03">Denton Record-Chronicle</E>
                            </ENT>
                            <ENT>The Honorable Mary Horn, Denton County Judge, 110 West Hickory Street, Second Floor, Denton, Texas 76201</ENT>
                            <ENT>November 16, 2006</ENT>
                            <ENT>480774 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">El Paso, (FEMA Docket No.: B-7466)</ENT>
                            <ENT>Unincorporated Areas of El Paso County (06-06-B324P)</ENT>
                            <ENT>
                                May 11, 2006; May 18, 2006; 
                                <E T="03">El Paso Times</E>
                            </ENT>
                            <ENT>The Honorable John Cook, Mayor, City of El Paso, 2 Civic Center Plaza, 10th Floor, El Paso, Texas 79901</ENT>
                            <ENT>April 17, 2006</ENT>
                            <ENT>480214 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Fort Bend, (FEMA Docket No.: B-7466)</ENT>
                            <ENT>Fort Bend County M.U.D. No. 23 (06-06-B011P)</ENT>
                            <ENT>
                                May 18, 2006; May 25, 2006; 
                                <E T="03">Ford Bend Herald</E>
                            </ENT>
                            <ENT>Ms. Ellen Hughes, District President, Fort Bend County Municipal Utility, District No. 23, 1715 Misty Fawn Lane, Fresno, Texas 77545</ENT>
                            <ENT>August 24, 2006</ENT>
                            <ENT>481590 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Galveston, (FEMA Docket No.: B-7466)</ENT>
                            <ENT>City of League City (05-06-1666P)</ENT>
                            <ENT>
                                April 20, 2006; April 27, 2006; 
                                <E T="03">The Galveston County Daily News</E>
                            </ENT>
                            <ENT>The Honorable Jerry Shults, Mayor, City of League City, 300 West Walker Street, League City, Texas 77573</ENT>
                            <ENT>March 31, 2006</ENT>
                            <ENT>485488 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Gregg &amp; Rusk, (FEMA Docket No.: B-7466)</ENT>
                            <ENT>City of Kilgore (04-06-A011P)</ENT>
                            <ENT>
                                March 24, 2006; March 31, 2006; 
                                <E T="03">Kilgore News Herald</E>
                            </ENT>
                            <ENT>The Honorable Joe Parker, Mayor, City of Kilgore, P.O. Box 990, Kilgore, Texas 75663</ENT>
                            <ENT>June 30, 2006</ENT>
                            <ENT>480263 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Harris, (FEMA Docket No.: B-7466)</ENT>
                            <ENT>City of Houston (04-06-1460P)</ENT>
                            <ENT>
                                April 6, 2006; April 13, 2006; 
                                <E T="03">Houston Chronicle</E>
                            </ENT>
                            <ENT>The Honorable Bill White, Mayor, City of Houston, P.O. Box 1562, Houston, Texas 77251</ENT>
                            <ENT>July 6, 2006</ENT>
                            <ENT>480296 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Harris, (FEMA Docket No.: B-7466)</ENT>
                            <ENT>Unincorporated Areas of Harris County (04-06-1460P)</ENT>
                            <ENT>
                                April 6, 2006; April 13, 2006; 
                                <E T="03">Houston Chronicle</E>
                            </ENT>
                            <ENT>The Honorable Robert Eckels, Harris County Judge, 1001 Preston, Suite 911, Houston, Texas 77002</ENT>
                            <ENT>July 6, 2006</ENT>
                            <ENT>480287 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Lubbock, (FEMA Docket No.: B-7466)</ENT>
                            <ENT>City of Lubbock (05-06-1480P)</ENT>
                            <ENT>
                                March 30, 2006; April 6, 2006; 
                                <E T="03">Lubbock Avalanche-Journal</E>
                            </ENT>
                            <ENT>The Honorable Mark McDougal, Mayor, City of Lubbock, P.O. Box 2000, Lubbock, Texas 79457</ENT>
                            <ENT>March 1, 2006</ENT>
                            <ENT>480452 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Lubbock, (FEMA Docket No.: B-7466)</ENT>
                            <ENT>City of Lubbock (05-06-1579P)</ENT>
                            <ENT>
                                January 12, 2006; January 19, 2006; 
                                <E T="03">Lubbock Avalanche-Journal</E>
                            </ENT>
                            <ENT>The Honorable Mark McDougal, Mayor, City of Lubbock, P.O. Box 2000, Lubbock, Texas 79457</ENT>
                            <ENT>December 28, 2005</ENT>
                            <ENT>480452 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Tarrant, (FEMA Docket No.: B-7466)</ENT>
                            <ENT>City of Fort Worth (05-06-0796P)</ENT>
                            <ENT>
                                December 22, 2005; December 29, 2005; 
                                <E T="03">Fort Worth Star-Telegram</E>
                            </ENT>
                            <ENT>The Honorable Michael J. Moncrief, Mayor, City of Fort Worth, 10000 Throckmorton Street, Fort Worth, Texas 76102</ENT>
                            <ENT>December 13, 2005</ENT>
                            <ENT>480596 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Tarrant, (FEMA Docket No.: B-7466)</ENT>
                            <ENT>City of Fort Worth (05-06-1757P)</ENT>
                            <ENT>
                                January 12, 2006; January 19, 2006; 
                                <E T="03">Fort Worth Star-Telegram</E>
                            </ENT>
                            <ENT>The Honorable Michael J. Moncrief, Mayor, City of Fort Worth, 10000 Throckmorton Street, Fort Worth, Texas 76102</ENT>
                            <ENT>December 28, 2005</ENT>
                            <ENT>480596 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Tarrant, (FEMA Docket No.: B-7466)</ENT>
                            <ENT>City of Fort Worth (05-06-A171P)</ENT>
                            <ENT>
                                March 16, 2006; March 23, 2006; 
                                <E T="03">Fort Worth Star-Telegram</E>
                            </ENT>
                            <ENT>The Honorable Michael J. Moncrief, Mayor, City of Fort Worth, 10000 Throckmorton Street, Fort Worth, Texas 76102</ENT>
                            <ENT>February 28, 2006</ENT>
                            <ENT>480596 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Travis, (FEMA Docket No.: B-7466)</ENT>
                            <ENT>City of Austin (05-06-0770P)</ENT>
                            <ENT>
                                April 27, 2006; May 4, 2006; 
                                <E T="03">Austin American-Statesman</E>
                            </ENT>
                            <ENT>The Honorable Will Wynn, Mayor, City of Austin, P.O. Box 1088, Austin, Texas 78767</ENT>
                            <ENT>August 3, 2006</ENT>
                            <ENT>480624 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Travis, (FEMA Docket No.: B-7466)</ENT>
                            <ENT>City of Austin (04-06-1466P)</ENT>
                            <ENT>
                                July 13, 2006; July 20, 2006; 
                                <E T="03">Austin American-Statesman</E>
                            </ENT>
                            <ENT>The Honorable Will Wynn, Mayor, City of Austin, P.O. Box 1088, Austin, Texas 78767</ENT>
                            <ENT>October 19, 2006</ENT>
                            <ENT>480624 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Travis, (FEMA Docket No.: B-7466)</ENT>
                            <ENT>City of Austin (05-06-A445P)</ENT>
                            <ENT>
                                June 15, 2006; June 22, 2006; 
                                <E T="03">Austin American-Statesman</E>
                            </ENT>
                            <ENT>The Honorable Will Wynn, Mayor, City of Austin, City Hall, 301 West Second Street, Second Floor, Austin, Texas 78767</ENT>
                            <ENT>September 21, 2006</ENT>
                            <ENT>480624 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Travis, (FEMA Docket No.: B-7466)</ENT>
                            <ENT>City of Pflugerville (05-06-0397P)</ENT>
                            <ENT>
                                March 30, 2006; April 6, 2006; 
                                <E T="03">Austin American-Statesman</E>
                            </ENT>
                            <ENT>The Honorable Catherine T. Callen, Mayor, City of Pflugerville, P.O. Box 589, Pflugerville, Texas 78691</ENT>
                            <ENT>March 15, 2006</ENT>
                            <ENT>481028 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Travis, (FEMA Docket No.: B-7466)</ENT>
                            <ENT>Unincorporated Areas of Travis County (05-06-0770P)</ENT>
                            <ENT>
                                April 27, 2006; May 4, 2006; 
                                <E T="03">Austin American-Statesman</E>
                            </ENT>
                            <ENT>The Honorable Samuel T. Biscoe, Travis County Judge, 314 West 11th Street, #520, Austin, Texas 78701</ENT>
                            <ENT>August 3, 2006</ENT>
                            <ENT>481026 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">Vermont: </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Windsor, (FEMA Docket No.: B-7466)</ENT>
                            <ENT>Town of Woodstock (05-01-0727P)</ENT>
                            <ENT>
                                June 22, 2006; June 29, 2006; 
                                <E T="03">Valley News</E>
                            </ENT>
                            <ENT>The Honorable Philip Swanson, Mayor, Town of Woodstock, Woodstock Town Hall, 29 The Green, Woodstock, Vermont 05091</ENT>
                            <ENT>September 28, 2006</ENT>
                            <ENT>500160 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">Virginia: </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Fauquier, (FEMA Docket No.: B-7466)</ENT>
                            <ENT>Town of Warrenton (05-03-A447P)</ENT>
                            <ENT>
                                August 23, 2006; August 30, 2006; 
                                <E T="03">Fauquier Times</E>
                            </ENT>
                            <ENT>The Honorable George B. Fitch, Mayor, Town of Warrenton, 18 Court Street, Warrenton, Virginia 20186</ENT>
                            <ENT>November 30, 2006</ENT>
                            <ENT>510057 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Fauquier, (FEMA Docket No.: B-7466)</ENT>
                            <ENT>Unincorporated Areas of Fauquier County (04-03-A019P)</ENT>
                            <ENT>
                                December 29, 2005; January 5, 2006; 
                                <E T="03">The Fauquier Citizen</E>
                            </ENT>
                            <ENT>The Honorable Raymond E. Graham, Chairman, Fauquier County, Board of Supervisors, 10 Hotel Street, Suite 208, Warrenton, Virginia 20186</ENT>
                            <ENT>April 6, 2006</ENT>
                            <ENT>510055 </ENT>
                        </ROW>
                        <ROW>
                            <PRTPAGE P="18593"/>
                            <ENT I="03">Henry, (FEMA Docket No.: B-7474)</ENT>
                            <ENT>Unincorporated areas of Henry County (07-03-0087X)</ENT>
                            <ENT>
                                October 27, 2006; November 3, 2006; 
                                <E T="03">Martinsville Bulletin</E>
                            </ENT>
                            <ENT>Mr. Benny Summerlin, County Administrator, Henry County, P.O. Box 7, Collinsville, VA 24078</ENT>
                            <ENT>November 22, 2006</ENT>
                            <ENT>510078 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Independent City, (FEMA Docket No.: B-7466)</ENT>
                            <ENT>City of Fairfax (04-03-A027P)</ENT>
                            <ENT>
                                April 13, 2006; April 20, 2006; 
                                <E T="03">Fairfax Connection Newspapers</E>
                            </ENT>
                            <ENT>The Honorable Robert F. Lederer, Mayor, City of Fairfax, City Hall, 10455 Armstrong Street, Fairfax, Virginia 22030-3630</ENT>
                            <ENT>July 20, 2006</ENT>
                            <ENT>515524 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Loudoun, (FEMA Docket No.: B-7466)</ENT>
                            <ENT>Unincorporated Areas of Loudoun County (05-03-0412P)</ENT>
                            <ENT>
                                August 16, 2006; August 23, 2006; 
                                <E T="03">Loudoun Times Mirror</E>
                            </ENT>
                            <ENT>The Honorable Scott K. York, Chairman, Loudoun County, Board of Supervisors, One Harrison Street Southeast, Leesburg, Virginia 20177-7000</ENT>
                            <ENT>July 25, 2006</ENT>
                            <ENT>510090 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Loudoun, (FEMA Docket No.: B-7466)</ENT>
                            <ENT>Unincorporated Areas of Loudoun County (05-03-A388P)</ENT>
                            <ENT>
                                May 3, 2006; May 10, 2006; 
                                <E T="03">Loudoun Times</E>
                            </ENT>
                            <ENT>The Honorable Scott K. York, Chairman, Loudoun County, Board of Supervisors, P.O. Box 7000, Leesburg, Virginia 20177-7000</ENT>
                            <ENT>August 9, 2006</ENT>
                            <ENT>510090 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Rockbridge, (FEMA Docket No.: B-7466)</ENT>
                            <ENT>City of Lexington (05-03-0901P)</ENT>
                            <ENT>
                                August 23, 2006; August 30, 2006; 
                                <E T="03">Rockbridge Weekly</E>
                            </ENT>
                            <ENT>The Honorable John Knapp, Mayor, City of Lexington, 300 East Washington Street, Lexington, Virginia 24450</ENT>
                            <ENT>August 7, 2006</ENT>
                            <ENT>510089 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Stafford, (FEMA Docket No.: B-7466)</ENT>
                            <ENT>Unincorporated Areas of Stafford County (05-03-0456P)</ENT>
                            <ENT>
                                June 16, 2006; June 23, 2006; 
                                <E T="03">Stafford County Sun</E>
                            </ENT>
                            <ENT>Mr. R. Steve Crosby, County Administrator, Stafford County, P.O. Box 339, Stafford, Virginia 22555-0339</ENT>
                            <ENT>May 10, 2006</ENT>
                            <ENT>510154 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">Washington: </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">King, (FEMA Docket No.: B-7466)</ENT>
                            <ENT>City of Issaquah (06-10-B008P)</ENT>
                            <ENT>
                                February 22, 2006; March 1, 2006; 
                                <E T="03">Issaquah Press</E>
                            </ENT>
                            <ENT>The Honorable Ava Frisinger, Mayor, City of Issaquah, P.O. Box 1307, Issaquah, Washington 98027</ENT>
                            <ENT>May 31, 2006</ENT>
                            <ENT>530079 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Walla Walla, (FEMA Docket No.: B-7466)</ENT>
                            <ENT>Unincorporated Areas of Walla Walla County (05-10-0491P)</ENT>
                            <ENT>
                                August 17, 2006; August 24, 2006; 
                                <E T="03">The Times</E>
                            </ENT>
                            <ENT>The Honorable David G. Carey, Chairman, Walla Walla County, Board of Commissioners, P.O. Box 1506, Walla Walla, Washington 99362</ENT>
                            <ENT>November 23, 2006</ENT>
                            <ENT>530194 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Whatcom, (FEMA Docket No.: B-7466)</ENT>
                            <ENT>City of Bellingham (05-10-0554P)</ENT>
                            <ENT>
                                April 20, 2006; April 27, 2006; 
                                <E T="03">The Bellingham Herald</E>
                            </ENT>
                            <ENT>The Honorable Mark Asmundson, Mayor, City of Bellingham, Bellingham City Hall, Second Floor, 210 Lottie Street, Bellingham, Washington 98225</ENT>
                            <ENT>July 13, 2006</ENT>
                            <ENT>530199 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Yakima, (FEMA Docket No.: B-7466)</ENT>
                            <ENT>City of Toppenish (06-10-B462P)</ENT>
                            <ENT>
                                November 2, 2006; November 9, 2006; 
                                <E T="03">Yakima Herald-Republic</E>
                            </ENT>
                            <ENT>The Honorable Bill Rogers, Mayor, City of Toppenish, Toppenish City Hall, 21 West First Avenue, Toppenish, Washington 98948</ENT>
                            <ENT>December 14, 2006</ENT>
                            <ENT>530228 </ENT>
                        </ROW>
                    </GPOTABLE>
                </REGTEXT>
                <EXTRACT>
                    <FP>(Catalog of Federal Domestic Assistance No. 83.100, “Flood Insurance.”)</FP>
                </EXTRACT>
                <SIG>
                    <DATED>Dated:  March 26, 2007.</DATED>
                    <NAME>David I. Maurstad,</NAME>
                    <TITLE>Director, Mitigation Division, Federal Emergency Management Agency, Department of Homeland Security.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. E7-7009 Filed 4-12-07; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 9110-12-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>National Oceanic and Atmospheric Administration</SUBAGY>
                <CFR>50 CFR Part 622</CFR>
                <DEPDOC>[Docket No. 040205043-4043-01; I.D. 040607F]</DEPDOC>
                <SUBJECT>Fisheries of the Caribbean, Gulf of Mexico, and South Atlantic; Reef Fish Fishery of the Gulf of Mexico; Closure of the 2007 Gulf of Mexico Commercial Fishery for Tilefishes</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>Temporary rule; closure.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>NMFS closes the commercial fishery for tilefishes in the exclusive economic zone (EEZ) of the Gulf of Mexico. NMFS has determined that the quota for tilefishes for the commercial fishery will have been reached by April 18, 2007. This closure is necessary to protect tilefishes.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The closure is effective 12:01 a.m., local time, April 18, 2007, until 12:01 a.m., local time, January 1, 2008.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Jason Rueter, telephone 727-824-5350, fax 727-824-5308, e-mail 
                        <E T="03">Jason.Rueter@noaa.gov</E>
                        .
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The reef fish fishery of the Gulf of Mexico is managed under the Fishery Management Plan for the Reef Fish Resources of the Gulf of Mexico (FMP). The FMP was prepared by the Gulf of Mexico Fishery Management Council and is implemented under the authority of the Magnuson-Stevens Fishery Conservation and Management Act (Magnuson-Stevens Act) by regulations at 50 CFR part 622. Pursuant to 50 CFR 622.42(a)(1)(iv), the commercial quota for tilefishes in the Gulf of Mexico is 440,000 lb (199,581 kg) for the current fishing year, January 1 through December 31, 2007.</P>
                <P>
                    Under 50 CFR 622.43(a), NMFS is required to close the commercial fishery for a species or species group when the quota for that species or species group is reached, or is projected to be reached, by filing a notification to that effect in the 
                    <E T="04">Federal Register</E>
                    . Based on current statistics, NMFS has determined that the available commercial quota of 440,000 lb (199,581 kg) for tilefishes will be reached on or before April 18, 2007. Accordingly, NMFS is closing the commercial fishery for tilefishes in the Gulf of Mexico EEZ from 12:01 a.m., local time, on April 18, 2007, until 12:01 a.m., local time, on January 1, 2008. The operator of a vessel with a valid commercial vessel permit for Gulf reef fish having tilefishes aboard must have landed and bartered, traded, or sold such tilefishes prior to 12:01 a.m., local time, April 18, 2007.
                </P>
                <P>
                    During the closure, the bag and possession limits specified in 50 CFR 622.39(b) apply to all harvest or possession of tilefishes in or from the Gulf of Mexico EEZ, and the sale or purchase of tilefishes taken from the EEZ is prohibited. The prohibition on 
                    <PRTPAGE P="18594"/>
                    sale or purchase does not apply to sale or purchase of tilefishes that were harvested, landed ashore, and sold prior to 12:01 a.m., local time, April 18, 2007, and were held in cold storage by a dealer or processor.
                </P>
                <HD SOURCE="HD1">Classification</HD>
                <P>This action responds to the best available information recently obtained from the fishery. The Assistant Administrator for Fisheries, NOAA, finds that the need to immediately implement this action to close the fishery constitutes good cause to waive the requirements to provide prior notice and opportunity for public comment pursuant to the authority set forth in 5 U.S.C. 553(b)(3)(B), as such procedures would be unnecessary and contrary to the public interest. Such procedures would be unnecessary because the rule implementing the quota already has been subject to notice and comment, and all that remains is to notify the public of the closure. Similarly, there is a need to implement these measures in a timely fashion to prevent an overrun of the commercial quota of Gulf of Mexico tilefishes, given the capacity of the fishing fleet to harvest the quota quickly. Any delay in implementing this action would be impractical and contrary to the Magnuson-Stevens Act, the FMP, and the public interest. For these same reasons, NMFS finds good cause that the implementation of this action cannot be delayed for 30 days. Accordingly, under 5 U.S.C. 553(d), a delay in the effective date is waived.</P>
                <P>This action is taken under 50 CFR 622.43(a) and is exempt from review under Executive Order 12866.</P>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P>
                        16 U.S.C. 1801 
                        <E T="03">et seq.</E>
                    </P>
                </AUTH>
                <SIG>
                    <DATED>Dated: April 9, 2007.</DATED>
                    <NAME>James P. Burgess</NAME>
                    <TITLE>Acting Director, Office of Sustainable Fisheries, National Marine Fisheries Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. E7-6965 Filed 4-12-07; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3510-22-S</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>National Oceanic and Atmospheric Administration</SUBAGY>
                <CFR>50 CFR Part 648</CFR>
                <DEPDOC>[Docket No. 061124307-7013-02;  I.D. 112106A]</DEPDOC>
                <SUBJECT>Fisheries of the Northeastern United States; Atlantic Mackerel, Squid, and Butterfish Fisheries; Closure of the Trimester I Fishery for Loligo Squid</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> Closure.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                         NMFS announces that the directed fishery for Loligo squid in the Exclusive Economic Zone (EEZ) will be closed effective 0001 hours, April 13, 2007.  Vessels issued a Federal permit to harvest 
                        <E T="03">Loligo</E>
                         squid may not retain or land more than 2,500 lb (1,134 kg) of 
                        <E T="03">Loligo</E>
                         squid per trip for the remainder of the trimester (through April 30, 2007).  This action is necessary to prevent the fishery from exceeding its Trimester I quota and to allow for effective management of this stock. 
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P> Effective 0001 hours, April 13, 2007, through 2400 hours, April 30, 2007.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P> Don Frei, Fishery Management Specialist, 978-281-9221, Fax 978-281-9135.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    Regulations governing the 
                    <E T="03">Loligo</E>
                     squid fishery are found at 50 CFR part 648.  The regulations require specifications for maximum sustainable yield, initial optimum yield, allowable biological catch, domestic annual harvest (DAH), domestic annual processing, joint venture processing, and total allowable levels of foreign fishing for the species managed under the Atlantic Mackerel, Squid, and Butterfish Fishery Management Plan.  The procedures for setting the annual initial specifications are described in § 648.21.
                </P>
                <P>
                    The 2007 specification of DAH for 
                    <E T="03">Loligo</E>
                     squid was set at 16,872.4 mt  (72 FR 4211, January 30, 2007).  This amount is allocated by trimester, as shown below.
                </P>
                <GPOTABLE COLS="4" OPTS="L2,i1" CDEF="s10,10C,14C,10C">
                    <TTITLE>
                        Table. 1 
                        <E T="03">Loligo</E>
                         Squid Trimester Allocations.
                    </TTITLE>
                    <BOXHD>
                        <CHED H="1">Quarter</CHED>
                        <CHED H="1">Percent</CHED>
                        <CHED H="1">
                            Metric Tons 
                            <SU>1</SU>
                        </CHED>
                        <CHED H="1">Research Set-aside (mt)</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="22">I (Jan-Apr)</ENT>
                        <ENT>43.00 </ENT>
                        <ENT>7,090.70</ENT>
                        <ENT>N/A</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">II (May-Aug)</ENT>
                        <ENT>17.00</ENT>
                        <ENT>2,803.30</ENT>
                        <ENT>N/A</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">III (Sep-Dec)</ENT>
                        <ENT>40.00</ENT>
                        <ENT>6,596.00</ENT>
                        <ENT>N/A</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">Total</ENT>
                        <ENT>100</ENT>
                        <ENT>16,490.00</ENT>
                        <ENT>510</ENT>
                    </ROW>
                    <TNOTE>
                        <SU>1</SU>
                        Trimester allocations after 510-mt research set-aside deduction.
                    </TNOTE>
                </GPOTABLE>
                <P>
                    Section 648.22 requires NMFS to close the directed 
                    <E T="03">Loligo</E>
                     squid fishery in the EEZ when 90 percent of the trimester allocation is harvested in Trimester I, II,  and when 95 percent of the total annual DAH has been harvested in Trimester III.  NMFS is further required to notify, in advance of the closure, the Executive Directors of the Mid-Atlantic, New England, and South Atlantic Fishery Management Councils; mail notification of the closure to all holders of 
                    <E T="03">Loligo</E>
                     squid permits at least 72 hr before the effective date of the closure; provide adequate notice of the closure to recreational participants in the fishery; and publish notification of the closure in the 
                    <E T="04">Federal Register</E>
                    .  The Administrator, Northeast Region, NMFS, based on dealer reports and other available information, has determined that 90 percent of the DAH for 
                    <E T="03">Loligo</E>
                     squid in Trimester I  will be harvested.  Therefore, effective 0001 hours, April 13, 2007, the directed fishery for 
                    <E T="03">Loligo</E>
                     squid is closed and vessels issued Federal permits for 
                    <E T="03">Loligo</E>
                     squid may not retain or land more than 2,500 lb (1,134 kg) of 
                    <E T="03">Loligo</E>
                     during a calendar day.  The directed fishery will reopen effective 0001 hours, May 1, 2007, when the Trimester II quota becomes available.
                </P>
                <HD SOURCE="HD1">Classification</HD>
                <P>This action is required by 50 CFR part 648 and is exempt from review under Executive Order 12866.</P>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P>
                        16 U.S.C. 1801 
                        <E T="03">et seq.</E>
                    </P>
                </AUTH>
                <SIG>
                    <DATED>Dated:  April 09, 2007.</DATED>
                    <NAME>James P. Burgess,</NAME>
                    <TITLE>Acting Director, Office Of Sustainable Fisheries, National Marine Fisheries Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 07-1824 Filed 4-9-07; 3:14 pm]</FRDOC>
            <BILCOD>BILLING CODE 3510-22-S</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <PRTPAGE P="18595"/>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>National Oceanic and Atmospheric Administration</SUBAGY>
                <CFR>50 CFR Part 679</CFR>
                <DEPDOC>[Docket No. 070213033-7033-01; I.D. 040607E]</DEPDOC>
                <SUBJECT>Fisheries of the Exclusive Economic Zone Off Alaska; Rock Sole, Flathead Sole, and “Other Flatfish” by Vessels Using Trawl Gear in Bering Sea and Aleutian Islands Management Area</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>Temporary rule; closure.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>NMFS is closing directed fishing for rock sole, flathead sole, and “other flatfish” by vessels using trawl gear in the Bering Sea and Aleutian Islands management area (BSAI). This action is necessary to prevent exceeding the second seasonal allowance of the 2007 halibut bycatch allowance specified for the trawl rock sole, flathead sole, and “other flatfish” fishery category in the BSAI.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Effective 1200 hrs, Alaska local time (A.l.t.), April 9, 2007, through 1200 hrs, A.l.t., July 1, 2007.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Jennifer Hogan, 907-586-7228.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>NMFS manages the groundfish fishery in the BSAI according to the Fishery Management Plan for Groundfish of the Bering Sea and Aleutian Islands Management Area (FMP) prepared by the North Pacific Fishery Management Council under authority of the Magnuson-Stevens Fishery Conservation and Management Act. Regulations governing fishing by U.S. vessels in accordance with the FMP appear at subpart H of 50 CFR part 600 and 50 CFR part 679.</P>
                <P>The second seasonal allowance of the 2007 halibut bycatch allowance specified for the trawl rock sole, flathead sole, and “other flatfish” fishery category in the BSAI is 164 metric tons as established by the 2007 and 2008 final harvest specifications for groundfish in the BSAI (72 FR 9451, March 2, 2007).</P>
                <P>In accordance with § 679.21(e)(7)(v), the Administrator, Alaska Region, NMFS, has determined that the second seasonal allowance of the 2007 halibut bycatch allowance specified for the trawl rock sole, flathead sole, and “other flatfish” fishery category in the BSAI has been reached. Consequently, NMFS is closing directed fishing for rock sole, flathead sole, and “other flatfish” by vessels using trawl gear in the BSAI.</P>
                <P>“Other flatfish” includes Alaska plaice, as well as all other flatfish species except for Pacific halibut (a prohibited species), Greenland turbot, rock sole, yellowfin sole, flathead sole, and arrowtooth flounder.</P>
                <P>After the effective date of this closure the maximum retainable amounts at § 679.20(e) and (f) apply at any time during a trip.</P>
                <HD SOURCE="HD1">Classification</HD>
                <P>This action responds to the best available information recently obtained from the fishery. The Assistant Administrator for Fisheries, NOAA (AA), finds good cause to waive the requirement to provide prior notice and opportunity for public comment pursuant to the authority set forth at 5 U.S.C. 553(b)(B) as such requirement is impracticable and contrary to the public interest. This requirement is impracticable and contrary to the public interest as it would prevent NMFS from responding to the most recent fisheries data in a timely fashion and would delay the closure of directed fishing for rock sole, flathead sole, and “other flatfish” by vessels using trawl gear in the BSAI. NMFS was unable to publish a notice providing time for public comment because the most recent, relevant data only became available as of April 6, 2007.</P>
                <P>The AA also finds good cause to waive the 30-day delay in the effective date of this action under 5 U.S.C. 553(d)(3). This finding is based upon the reasons provided above for waiver of prior notice and opportunity for public comment.</P>
                <P>This action is required by § 679.21 and is exempt from review under Executive Order 12866.</P>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P>
                        16 U.S.C. 1801 
                        <E T="03">et seq.</E>
                    </P>
                </AUTH>
                <SIG>
                    <DATED>Dated: April 6, 2007.</DATED>
                    <NAME>Alan D. Risenhoover</NAME>
                    <TITLE>Director, Office of Sustainable Fisheries, National Marine Fisheries Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 07-1823 Filed 4-9-07; 3:14 pm]</FRDOC>
            <BILCOD>BILLING CODE 3510-22-S</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>National Oceanic and Atmospheric Administration</SUBAGY>
                <CFR>50 CFR Part 679</CFR>
                <DEPDOC>[Docket No. 070213033-7033-01; I.D. 040607A]</DEPDOC>
                <SUBJECT>Fisheries of the Exclusive Economic Zone Off Alaska; Reallocation of Pacific Cod in the Bering Sea and Aleutian Islands Management Area</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>Temporary rule; reallocation.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>NMFS is reallocating the projected unused amount of Pacific cod from vessels using jig gear to catcher vessels less than 60 feet (18.3 meters (m)) length overall (LOA) using pot or hook-and-line gear in the Bering Sea and Aleutian Islands management area (BSAI). These actions are necessary to allow the 2007 B season total allowable catch (TAC) of Pacific cod to be harvested.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Effective April 30, 2007, 1200 hrs, Alaska local time (A.l.t.), through 2400 hrs, A.l.t., December 31, 2007.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Jennifer Hogan, 907-586-7228.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>NMFS manages the groundfish fishery in the BSAI according to the Fishery Management Plan for Groundfish of the Bering Sea and Aleutian Islands Management Area (FMP) prepared by the North Pacific Fishery Management Council under authority of the Magnuson-Stevens Fishery Conservation and Management Act. Regulations governing fishing by U.S. vessels in accordance with the FMP appear at subpart H of 50 CFR part 600 and 50 CFR part 679.</P>
                <P>The 2007 B season allowance of the Pacific cod TAC specified for vessels using jig gear in the BSAI is 632 metric tons (mt) as established by the 2007 and 2008 final harvest specifications for groundfish in the BSAI (72 FR 9451, March 2, 2007) and the adjustment of the Pacific cod TACs in the BSAI on March 5, 2007 (72 FR 10428, March 8, 2007), for the period 1200 hrs, A.l.t., April 30, 2007, through 1200 hrs, A.l.t., August 31, 2007. See § 679.20(c)(3)(iii), § 679.20(c)(5), and § 679.20(a)(7)(i)(A).</P>
                <P>
                    The Administrator, Alaska Region, NMFS, has determined that jig vessels will not be able to harvest 532 mt of the B season apportionment of Pacific cod allocated to those vessels under 
                    <PRTPAGE P="18596"/>
                    § 679.20(a)(7)(i)(A) and § 679.20(a)(7)(iii)(A)(
                    <E T="03">3</E>
                    ). Therefore, in accordance with § 679.20(a)(7)(ii)(C)(
                    <E T="03">1</E>
                    ), NMFS apportions 532 mt of Pacific cod from the B season jig gear apportionment to catcher vessels less than 60 feet (18.3 m) LOA using pot or hook-and-line gear.
                </P>
                <P>The harvest specifications for Pacific cod included in the harvest specifications for groundfish in the BSAI (72 FR 9451, March 2, 2007) are revised as follows: 100 mt to the B season apportionment for vessels using jig gear and 2,853 mt to catcher vessels less than 60 feet (18.3 m) LOA using pot or hook-and-line gear.</P>
                <HD SOURCE="HD1">Classification</HD>
                <P>This action responds to the best available information recently obtained from the fishery. The Assistant Administrator for Fisheries, NOAA (AA), finds good cause to waive the requirement to provide prior notice and opportunity for public comment pursuant to the authority set forth at 5 U.S.C. 553(b)(B) as such requirement is impracticable and contrary to the public interest. This requirement is impracticable and contrary to the public interest as it would prevent NMFS from responding to the most recent fisheries data in a timely fashion and would delay the reallocation of Pacific cod specified for jig vessels to catcher vessels less than 60 feet (18.3 m) LOA using pot or hook-and-line gear. Since the fishery is currently open, it is important to immediately inform the industry as to the revised allocations. Immediate notification is necessary to allow for the orderly conduct and efficient operation of this fishery, to allow the industry to plan for the fishing season, and to avoid potential disruption to the fishing fleet as well as processors. NMFS was unable to publish a notice providing time for public comment because the most recent, relevant data only became available as of April 5, 2007.</P>
                <P>The AA also finds good cause to waive the 30-day delay in the effective date of this action under 5 U.S.C. 553(d)(3). This finding is based upon the reasons provided above for waiver of prior notice and opportunity for public comment.</P>
                <P>This action is required by § 679.20 and is exempt from review under Executive Order 12866.</P>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P>
                        16 U.S.C. 1801 
                        <E T="03">et seq.</E>
                    </P>
                </AUTH>
                <SIG>
                    <DATED>Dated: April 6, 2007.</DATED>
                    <NAME>Alan D. Risenhoover</NAME>
                    <TITLE>Director, Office of Sustainable Fisheries, National Marine Fisheries Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. E7-7038 Filed 4-12-07; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3510-22-S</BILCOD>
        </RULE>
    </RULES>
    <VOL>72</VOL>
    <NO>71</NO>
    <DATE>Friday, April 13, 2007</DATE>
    <UNITNAME>Proposed Rules</UNITNAME>
    <PRORULES>
        <PRORULE>
            <PREAMB>
                <PRTPAGE P="18597"/>
                <AGENCY TYPE="F">DEPARTMENT OF TRANSPORTATION </AGENCY>
                <SUBAGY>Federal Aviation Administration </SUBAGY>
                <CFR>14 CFR Part 25 </CFR>
                <DEPDOC>[Docket No. NM364 Special Conditions No. 25-07-01-SC] </DEPDOC>
                <SUBJECT>Special Conditions: Boeing Model 787-8 Airplane; Systems and Data Networks Security—Isolation or Protection From Unauthorized Passenger Domain Systems Access </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 special conditions. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This notice proposes special conditions for the Boeing Model 787-8 airplane. This airplane will have novel or unusual design features when compared to the state of technology envisioned in the airworthiness standards for transport category airplanes. These novel or unusual design features are associated with connectivity of the passenger domain systems to the airplane critical systems and data networks. For these design features, the applicable airworthiness regulations do not contain adequate or appropriate safety standards for protection and security of airplane systems and data networks against unauthorized access. These proposed special conditions contain the additional safety standards that the Administrator considers necessary to establish a level of safety equivalent to that established by the existing airworthiness standards. Additional special conditions will be issued for other novel or unusual design features of the Boeing Model 787-8 airplanes. </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be received on or before May 29, 2007. </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Comments on this proposal may be mailed in duplicate to: Federal Aviation Administration, Transport Airplane Directorate, Attention: Rules Docket (ANM-113), Docket No. NM364, 1601 Lind Avenue, SW., Renton, Washington 98057-3356; or delivered in duplicate to the Transport Airplane Directorate at the above address. All comments must be marked Docket No. NM364. Comments may be inspected in the Rules Docket weekdays, except Federal holidays, between 7:30 a.m. and 4 p.m. </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Will Struck, FAA, Airplane and Flight Crew Interface, ANM-111, Transport Airplane Directorate, Aircraft Certification Service, 1601 Lind Avenue, SW., Renton, Washington 98057-3356; telephone (425) 227-2764; facsimile (425) 227-1149. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Comments Invited </HD>
                <P>The FAA invites interested persons to participate in this rulemaking by submitting written comments, data, or views. The most helpful comments reference a specific portion of the special conditions, explain the reason for any recommended change, and include supporting data. We ask that you send us two copies of written comments. </P>
                <P>
                    We will file in the docket all comments we receive as well as a report summarizing each substantive public contact with FAA personnel concerning these proposed special conditions. The docket is available for public inspection before and after the comment closing date. If you wish to review the docket in person, go to the address in the 
                    <E T="02">ADDRESSES</E>
                     section of this notice between 7:30 a.m. and 4 p.m., Monday through Friday, except Federal holidays. 
                </P>
                <P>We will consider all comments we receive on or before the closing date for comments. We will consider comments filed late if it is possible to do so without incurring expense or delay. We may change the proposed special conditions based on comments we receive. </P>
                <P>If you want the FAA to acknowledge receipt of your comments on this proposal, include with your comments a pre-addressed, stamped postcard on which the docket number appears. We will stamp the date on the postcard and mail it back to you. </P>
                <HD SOURCE="HD1">Background </HD>
                <P>On March 28, 2003, Boeing applied for an FAA type certificate for its new Boeing Model 787-8 passenger airplane. The Boeing Model 787-8 airplane will be an all-new, two-engine jet transport airplane with a two-aisle cabin. The maximum takeoff weight will be 476,000 pounds, with a maximum passenger count of 381 passengers. </P>
                <HD SOURCE="HD1">Type Certification Basis </HD>
                <P>Under provisions of 14 CFR 21.17, Boeing must show that Boeing Model 787-8 airplanes (hereafter referred to as “the 787”) meet the applicable provisions of 14 CFR part 25, as amended by Amendments 25-1 through 25-117, except §§ 25.809(a) and 25.812, which will remain at Amendment 25-115. If the Administrator finds that the applicable airworthiness regulations do not contain adequate or appropriate safety standards for the 787 because of a novel or unusual design feature, special conditions are prescribed under provisions of 14 CFR 21.16. </P>
                <P>In addition to the applicable airworthiness regulations and special conditions, the 787 must comply with the fuel vent and exhaust emission requirements of 14 CFR part 34 and the noise certification requirements of part 36. In addition, the FAA must issue a finding of regulatory adequacy pursuant to section 611 of Public Law 92-574, the “Noise Control Act of 1972.” </P>
                <P>Special conditions, as defined in § 11.19, are issued in accordance with § 11.38 and become part of the type certification basis in accordance with § 21.17(a)(2). </P>
                <P>Special conditions are initially applicable to the model for which they are issued. Should the type certificate for that model be amended later to include any other model that incorporates the same or similar novel or unusual design feature, the special conditions would also apply to the other model under the provisions of § 21.101. </P>
                <HD SOURCE="HD1">Novel or Unusual Design Features </HD>
                <P>The digital systems architecture for the 787 consists of several networks connected by electronics and embedded software. This proposed network architecture is used for a diverse set of functions, including the following.</P>
                <P>1. Flight-safety-related control and navigation and required systems (Aircraft Control Domain). </P>
                <P>2. Airline business and administrative support (Airline Information Services Domain). </P>
                <P>
                    3. Passenger entertainment, information, and Internet services 
                    <PRTPAGE P="18598"/>
                    (Passenger Information and Entertainment Services Domain). 
                </P>
                <P>The proposed architecture of the 787 is different from that of existing production (and retrofitted) airplanes. It allows new kinds of passenger connectivity to previously isolated data networks connected to systems that perform functions required for the safe operation of the airplane. Because of this new passenger connectivity, the proposed data network design and integration may result in security vulnerabilities from intentional or unintentional corruption of data and systems critical to the safety and maintenance of the airplane. The existing regulations and guidance material did not anticipate this type of system architecture or electronic access to aircraft systems that provide flight critical functions. Furthermore, 14 CFR regulations and current system safety assessment policy and techniques do not address potential security vulnerabilities that could be caused by unauthorized access to aircraft data buses and servers. Therefore, a special condition is proposed to ensure that security, integrity, and availability of the aircraft systems and data networks are not compromised by certain wired or wireless electronic connections between airplane data buses and networks. </P>
                <HD SOURCE="HD1">Applicability </HD>
                <P>As discussed above, these proposed special conditions are applicable to the 787. Should Boeing apply at a later date for a change to the type certificate to include another model incorporating the same novel or unusual design features, these proposed special conditions would apply to that model as well under the provisions of § 21.101. </P>
                <HD SOURCE="HD1">Conclusion </HD>
                <P>This action affects only certain novel or unusual design features of the 787. It is not a rule of general applicability, and it affects only the applicant that applied to the FAA for approval of these features on the airplane. </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 14 CFR Part 25 </HD>
                    <P>Aircraft, Aviation safety, Reporting and recordkeeping requirements. </P>
                </LSTSUB>
                <P>The authority citation for these Special Conditions is as follows: </P>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P>49 U.S.C. 106(g), 40113, 44701, 44702, 44704. </P>
                </AUTH>
                <HD SOURCE="HD1">The Proposed Special Conditions </HD>
                <P>Accordingly, the Administrator of the Federal Aviation Administration (FAA) proposes the following special conditions as part of the type certification basis for the Boeing Model 787-8 airplane. </P>
                <EXTRACT>
                    <P>The design shall prevent all inadvertent or malicious changes to, and all adverse impacts upon, all systems, networks, hardware, software, and data in the Aircraft Control Domain and in the Airline Information Domain from all points within the Passenger Information and Entertainment Domain. </P>
                </EXTRACT>
                <SIG>
                    <DATED>Issued in Renton, Washington, on April 5, 2007. </DATED>
                    <NAME>Stephen P. Boyd, </NAME>
                    <TITLE>Acting Manager, Transport Airplane Directorate, Aircraft Certification Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. E7-7065 Filed 4-12-07; 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. FAA-2007-27533; Directorate Identifier 2007-CE-022-AD] </DEPDOC>
                <RIN>RIN 2120-AA64 </RIN>
                <SUBJECT>Airworthiness Directives; Diamond Aircraft Industries GmbH Model DA 42 Airplanes </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration (FAA), Department of Transportation (DOT). </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of proposed rulemaking (NPRM). </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>We propose to adopt a new airworthiness directive (AD) for the products listed above. This proposed AD results from mandatory continuing airworthiness information (MCAI) originated by an aviation authority of another country to identify and correct an unsafe condition on an aviation product. The MCAI describes the unsafe condition as: </P>
                    <EXTRACT>
                        <P>Shortly after an engine change, the aluminium fitting attached to the engine gearbox holding lines and fittings of the propeller control system was found to be cracked. This led to a pressure loss in the propeller control system following a control system malfunction and led to an  in-flight engine shutdown. </P>
                        <P>The broken fitting is part of the engine installation and was initially a steel part. It was later modified by the engine manufacturer to an aluminium design. </P>
                        <P>Investigation determined that the area is critical for cracks due to combination of mass, material and installation torque values. </P>
                        <P>Diamond Aircraft Industries incorporated with Design Change MÄM 42-184 an additional bracket into production airplanes to improve the installations and prevent vibration cracks.</P>
                    </EXTRACT>
                    <P>The proposed AD would require actions that are intended to address the unsafe condition described in the MCAI. </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>We must receive comments on this proposed AD by May 14, 2007. </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may send comments by any of the following methods: </P>
                    <P>
                        • DOT Docket Web site: Go to 
                        <E T="03">http://dms.dot.gov</E>
                         and follow the instructions for sending your comments electronically. 
                    </P>
                    <P>• Fax: (202) 493-2251. </P>
                    <P>• Mail: Docket Management Facility, U.S. Department of Transportation, 400 Seventh Street, SW., Nassif Building, Room PL-401, Washington, DC 20590-0001. </P>
                    <P>• Hand Delivery: Room PL-401 on the plaza level of the Nassif Building, 400 Seventh Street, SW., Washington, DC, between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays. </P>
                    <P>
                        • Federal eRulemaking Portal: Go to 
                        <E T="03">http://www.regulations.gov</E>
                        . Follow the instructions for submitting comments. 
                    </P>
                </ADD>
                <HD SOURCE="HD1">Examining the AD Docket </HD>
                <P>
                    You may examine the AD docket on the Internet at 
                    <E T="03">http://dms.dot.gov</E>
                    ; or in person at the Docket Management Facility between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays. The AD docket contains this proposed AD, the regulatory evaluation, any comments received, and other information. The street address for the Docket Office (telephone (800) 647-5227) is in the 
                    <E T="02">ADDRESSES</E>
                     section. Comments will be available in the AD docket shortly after receipt. 
                </P>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Sarjapur Nagarajan, Aerospace Engineer, FAA, Small Airplane Directorate, 901 Locust, Room 301, Kansas City, Missouri 64106; telephone: (816) 329-4145; fax: (816) 329-4090.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Streamlined Issuance of AD </HD>
                <P>
                    The FAA is implementing a new process for streamlining the issuance of ADs related to MCAI. This streamlined process will allow us to adopt MCAI safety requirements in a more efficient manner and will reduce safety risks to the public. This process continues to follow all FAA AD issuance processes to meet legal, economic, Administrative Procedure Act, and 
                    <E T="04">Federal Register</E>
                     requirements. We also continue to meet our technical decision-making responsibilities to identify and correct unsafe conditions on U.S.-certificated products. 
                </P>
                <P>
                    This proposed AD references the MCAI and related service information that we considered in forming the engineering basis to correct the unsafe condition. The proposed AD contains text copied from the MCAI and for this reason might not follow our plain language principles. 
                    <PRTPAGE P="18599"/>
                </P>
                <HD SOURCE="HD1">Comments Invited </HD>
                <P>
                    We invite you to send any written relevant data, views, or arguments about this proposed AD. Send your comments to an address listed under the 
                    <E T="02">ADDRESSES</E>
                     section. Include “Docket No. FAA-2007-27533; Directorate Identifier 2007-CE-022-AD” at the beginning of your comments. We specifically invite comments on the overall regulatory, economic, environmental, and energy aspects of this proposed AD. We will consider all comments received by the closing date and may amend this proposed AD because of those comments. 
                </P>
                <P>
                    We will post all comments we receive, without change, to 
                    <E T="03">http://dms.dot.gov</E>
                    , including any personal information you provide. We will also post a report summarizing each substantive verbal contact we receive about this proposed AD. 
                </P>
                <HD SOURCE="HD1">Discussion </HD>
                <P>The European Aviation Safety Agency (EASA), which is the Technical Agent for the Member States of the European Community, has issued AD No: 2006-0277, dated September 06, 2006 (referred to after this as “the MCAI”), to correct an unsafe condition for the specified products. The MCAI states: </P>
                <EXTRACT>
                    <P>Shortly after an engine change, the aluminium fitting attached to the engine gearbox holding lines and fittings of the propeller control system was found to be cracked. This led to a pressure loss in the propeller control system following a control system malfunction and led to a in-flight engine shutdown. </P>
                    <P>The broken fitting is part of the engine installation and was initially a steel part. It was later modified by the engine manufacturer to an aluminium design. </P>
                    <P>Investigation determined that the area is critical for cracks due to combination of mass, material and installation torque values. </P>
                    <P>Diamond Aircraft Industries incorporated with Design Change MÄM 42-184 an additional bracket into production airplanes to improve the installations and prevent vibration cracks. </P>
                    <P>The MCAI requires: </P>
                    <P>This airworthiness directive requires the retroactive installation of this bracket for all airplanes, including the airplanes with steel fittings. </P>
                    <P>You may obtain further information by examining the MCAI in the AD docket.</P>
                </EXTRACT>
                <HD SOURCE="HD1">Relevant Service Information </HD>
                <P>Diamond Aircraft Industries GmbH has issued Mandatory Service Bulletin No. MSB-42-024/3, dated September 19, 2006. The actions described in this service information are intended to correct the unsafe condition identified in the MCAI. </P>
                <HD SOURCE="HD1">FAA's Determination and Requirements of the Proposed AD </HD>
                <P>This product has been approved by the aviation authority of another country, and is approved for operation in the United States. Pursuant to our bilateral agreement with this State of Design Authority, they have notified us of the unsafe condition described in the MCAI and service information referenced above. We are proposing this AD because we evaluated all information and determined the unsafe condition exists and is likely to exist or develop on other products of the same type design. </P>
                <HD SOURCE="HD1">Differences Between This Proposed AD and the MCAI or Service Information </HD>
                <P>We have reviewed the MCAI and related service information and, in general, agree with their substance. But we might have found it necessary to use different words from those in the MCAI to ensure the AD is clear for U.S. operators and is enforceable. In making these changes, we do not intend to differ substantively from the information provided in the MCAI and related service information. </P>
                <P>We might also have proposed different actions in this AD from those in the MCAI in order to follow FAA policies. Any such differences are highlighted in a NOTE within the proposed AD. </P>
                <HD SOURCE="HD1">Costs of Compliance </HD>
                <P>Based on the service information, we estimate that this proposed AD would affect about 70 products of U.S. registry. We also estimate that it would take about 1 work-hour per product to comply with the basic requirements of this proposed AD. The average labor rate is $80 per work-hour. Required parts would cost about $208 per product. Where the service information lists required parts costs that are covered under warranty, we have assumed that there will be no charge for these costs. As we do not control warranty coverage for affected parties, some parties may incur costs higher than estimated here. </P>
                <P>Based on these figures, we estimate the cost of the proposed AD on U.S. operators to be $20,160, or $288 per product. </P>
                <HD SOURCE="HD1">Authority for This Rulemaking </HD>
                <P>Title 49 of the United States Code specifies the FAA's authority to issue rules on aviation safety. Subtitle I, section 106, describes the authority of the FAA Administrator. “Subtitle VII: Aviation Programs,” describes in more detail the scope of the Agency's authority.</P>
                <P>We are issuing this rulemaking under the authority described in “Subtitle VII, Part A, Subpart III, Section 44701: General requirements.” Under that section, Congress charges the FAA with promoting safe flight of civil aircraft in air commerce by prescribing regulations for practices, methods, and procedures the Administrator finds necessary for safety in air commerce. This regulation is within the scope of that authority because it addresses an unsafe condition that is likely to exist or develop on products identified in this rulemaking action. </P>
                <HD SOURCE="HD1">Regulatory Findings </HD>
                <P>We 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>
                <P>For the reasons discussed above, I certify this proposed regulation:</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 regulatory evaluation of the estimated costs to comply with this proposed AD and placed it in the AD docket. </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 FAA 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 adding the following new AD:</P>
                        <EXTRACT>
                            <FP SOURCE="FP-2">
                                <E T="04">Diamond Aircraft Industries GmbH:</E>
                                 Docket No. FAA-2007-27533; Directorate Identifier 2007-CE-022-AD. 
                                <PRTPAGE P="18600"/>
                            </FP>
                            <HD SOURCE="HD1">Comments Due Date </HD>
                            <P>(a) We must receive comments by May 14, 2007. </P>
                            <HD SOURCE="HD1">Affected ADs </HD>
                            <P>(b) None. </P>
                            <HD SOURCE="HD1">Applicability </HD>
                            <P>(c) This AD applies to DA 42 airplanes, serial numbers 42.004 through 42.129, 42.177, and 42.AC001, certificated in any category. </P>
                            <HD SOURCE="HD1">Subject </HD>
                            <P>(d) Air Transport Association of America (ATA) Code 72: Engine. </P>
                            <HD SOURCE="HD1">Reason </HD>
                            <P>(e) The mandatory continuing airworthiness information (MCAI) states: </P>
                            <P>Shortly after an engine change, the aluminium fitting attached to the engine gearbox holding lines and fittings of the propeller control system was found to be cracked. This led to a pressure loss in the propeller control system following a control system malfunction and led to a in-flight engine shutdown. </P>
                            <P>The broken fitting is part of the engine installation and was initially a steel part. It was later modified by the engine manufacturer to an aluminium design. </P>
                            <P>Investigation determined that the area is critical for cracks due to combination of mass, material and installation torque values. </P>
                            <P>Diamond Aircraft Industries incorporated with Design Change MÄM 42-184 an additional bracket into production airplanes to improve the installations and prevent vibration cracks. </P>
                            <HD SOURCE="HD1">Actions and Compliance </HD>
                            <P>(f) Unless already done, within 50 hours time-in-service or 30 days after the effective date of this AD, whichever occurs first, install the additional steel bracket following Diamond Aircraft Industries GmbH Mandatory Service Bulletin NO. MSB-42-024/3, dated September 19, 2006. </P>
                            <NOTE>
                                <HD SOURCE="HED">Note 1:</HD>
                                <P>If the above action was accomplished following the procedures described in Diamond Aircraft Industries GmbH Mandatory Service Bulletin No. MSB-42-024/2, dated August 31, 2006, you may take “unless already done” credit, and no further action per this AD is necessary.</P>
                            </NOTE>
                            <HD SOURCE="HD1">FAA AD Differences </HD>
                            <NOTE>
                                <HD SOURCE="HED">Note 2:</HD>
                                <P>This AD differs from the MCAI and/or service information as follows: No differences.</P>
                            </NOTE>
                            <HD SOURCE="HD1">Other FAA AD Provisions </HD>
                            <P>(g) The following provisions also apply to this AD: </P>
                            <P>(1) Alternative Methods of Compliance (AMOCs): The Manager, Standards Staff, FAA, ATTN: Sarjapur Nagarajan, Aerospace Engineer, FAA, Small Airplane Directorate, 901 Locust, Room 301, Kansas City, Missouri 64106; telephone: (816) 329-4145; fax: (816) 329-4090, has the authority to approve AMOCs for this AD, if requested using the procedures found in 14 CFR 39.19. Before using any approved AMOC on any airplane to which the AMOC applies, notify your appropriate principal inspector (PI) in the FAA Flight Standards District Office (FSDO), or lacking a PI, your local FSDO. </P>
                            <P>(2) Airworthy Product: For any requirement in this AD to obtain corrective actions from a manufacturer or other source, use these actions if they are FAA-approved. Corrective actions are considered FAA-approved if they are approved by the State of Design Authority (or their delegated agent). You are required to assure the product is airworthy before it is returned to service. </P>
                            <P>(3) Reporting Requirements: For any reporting requirement in this AD, under the provisions of the Paperwork Reduction Act (44 U.S.C. 3501 et.seq.), the Office of Management and Budget (OMB) has approved the information collection requirements and has assigned OMB Control Number 2120-0056. </P>
                            <HD SOURCE="HD1">Related Information </HD>
                            <P>(h) Refer to MCAI European Aviation Safety Agency (EASA) AD No: 2006-0277, dated September 06, 2006; and Diamond Aircraft Industries GmbH, Mandatory Service Bulletin No. MSB-42-024/3, dated September 19, 2006, for related information.</P>
                        </EXTRACT>
                    </SECTION>
                    <SIG>
                        <DATED>Issued in Kansas City, Missouri, on April 6, 2007. </DATED>
                        <NAME>Kim Smith, </NAME>
                        <TITLE>Manager, Small Airplane Directorate, Aircraft Certification Service.</TITLE>
                    </SIG>
                </PART>
            </SUPLINF>
            <FRDOC>[FR Doc. E7-7050 Filed 4-12-07; 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. FAA-2007-27708; Directorate Identifier 2007-CE-027-AD] </DEPDOC>
                <RIN>RIN 2120-AA64 </RIN>
                <SUBJECT>Airworthiness Directives; Diamond Aircraft Industries GmbH Model DA 42 Airplanes </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration (FAA), Department of Transportation (DOT). </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of proposed rulemaking (NPRM). </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>We propose to adopt a new airworthiness directive (AD) for the products listed above. This proposed AD results from mandatory continuing airworthiness information (MCAI) originated by an aviation authority of another country to identify and correct an unsafe condition on an aviation product. The MCAI describes the unsafe condition as: </P>
                    <EXTRACT>
                        <P>From airplanes that have installed the Auxiliary Fuel Tank Optional Design Change (O-M) No. 42-056, three in-service failures of the auxiliary fuel tank venting system have been reported. These failures have led to the inability to supply the complete auxiliary fuel quantity to the main tanks and the collapse of the auxiliary tank. It is suspected that the vent lines were obstructed either by ice accretion under certain climatic conditions or by blockage of the vent valves because of fuel contaminants. </P>
                        <P>Undetected malfunctions of the venting system and damaged auxiliary fuel tanks may lead to a lower usable fuel quantity, subsequent fuel starvation and/or fuel spillage into the nacelle.</P>
                    </EXTRACT>
                    <P>The proposed AD would require actions that are intended to address the unsafe condition described in the MCAI. </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>We must receive comments on this proposed AD by May 14, 2007. </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may send comments by any of the following methods: </P>
                    <P>
                        • 
                        <E T="03">DOT Docket Web site:</E>
                         Go to 
                        <E T="03">http://dms.dot.gov</E>
                         and follow the instructions for sending your comments electronically. 
                    </P>
                    <P>
                        • 
                        <E T="03">Fax:</E>
                         (202) 493-2251. 
                    </P>
                    <P>
                        • 
                        <E T="03">Mail:</E>
                         Docket Management Facility, U.S. Department of Transportation, 400 Seventh Street, SW., Nassif Building, Room PL-401, Washington, DC 20590-0001. 
                    </P>
                    <P>
                        • 
                        <E T="03">Hand Delivery:</E>
                         Room PL-401 on the plaza level of the Nassif Building, 400 Seventh Street, SW., Washington, DC, between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays. 
                    </P>
                    <P>
                        • 
                        <E T="03">Federal eRulemaking Portal:</E>
                         Go to 
                        <E T="03">http://www.regulations.gov</E>
                        . Follow the instructions for submitting comments. 
                    </P>
                </ADD>
                <HD SOURCE="HD1">Examining the AD Docket </HD>
                <P>
                    You may examine the AD docket on the Internet at 
                    <E T="03">http://dms.dot.gov</E>
                    ; or in person at the Docket Management Facility between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays. The AD docket contains this proposed AD, the regulatory evaluation, any comments received, and other information. The street address for the Docket Office (telephone (800) 647-5227) is in the 
                    <E T="02">ADDRESSES</E>
                     section. Comments will be available in the AD docket shortly after receipt. 
                </P>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Sarjapur Nagarajan, Aerospace Engineer, FAA, Small Airplane Directorate, 901 Locust, Room 301, Kansas City, Missouri 64106; telephone: (816) 329-4145; fax: (816) 329-4090. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Streamlined Issuance of AD </HD>
                <P>
                    The FAA is implementing a new process for streamlining the issuance of ADs related to MCAI. This streamlined process will allow us to adopt MCAI safety requirements in a more efficient manner and will reduce safety risks to the public. This process continues to follow all FAA AD issuance processes to 
                    <PRTPAGE P="18601"/>
                    meet legal, economic, Administrative Procedure Act, and 
                    <E T="04">Federal Register</E>
                     requirements. We also continue to meet our technical decision-making responsibilities to identify and correct unsafe conditions on U.S.-certificated products. 
                </P>
                <P>This proposed AD references the MCAI and related service information that we considered in forming the engineering basis to correct the unsafe condition. The proposed AD contains text copied from the MCAI and for this reason might not follow our plain language principles. </P>
                <HD SOURCE="HD1">Comments Invited </HD>
                <P>
                    We invite you to send any written relevant data, views, or arguments about this proposed AD. Send your comments to an address listed under the 
                    <E T="02">ADDRESSES</E>
                     section. Include “Docket No. FAA-2007-27708; Directorate Identifier 2007-CE-027-AD” at the beginning of your comments. We specifically invite comments on the overall regulatory, economic, environmental, and energy aspects of this proposed AD. We will consider all comments received by the closing date and may amend this proposed AD because of those comments. 
                </P>
                <P>
                    We will post all comments we receive, without change, to 
                    <E T="03">http://dms.dot.gov</E>
                    , including any personal information you provide. We will also post a report summarizing each substantive verbal contact we receive about this proposed AD. 
                </P>
                <HD SOURCE="HD1">Discussion </HD>
                <P>The European Aviation Safety Agency (EASA), which is the Technical Agent for the Member States of the European Community, has issued AD No: 2007-0047 (referred to after this as “the MCAI”), to correct an unsafe condition for the specified products. The MCAI states: </P>
                <EXTRACT>
                    <P>From airplanes that have installed the Auxiliary Fuel Tank Optional Design Change (O-M) No. 42-056, three in-service failures of the auxiliary fuel tank venting system have been reported. These failures have led to the inability to supply the complete auxiliary fuel quantity to the main tanks and the collapse of the auxiliary tank. It is suspected that the vent lines were obstructed either by ice accretion under certain climatic conditions or by blockage of the vent valves because of fuel contaminants.</P>
                    <P>Undetected malfunctions of the venting system and damaged auxiliary fuel tanks may lead to a lower usable fuel quantity, subsequent fuel starvation and/or fuel spillage into the nacelle. </P>
                    <P>The MCAI requires: </P>
                    <P>* * * to check for proper operation the auxiliary fuel tank venting system, and check for damage the fuel tanks' structure. </P>
                    <P>* * * also requires installation of ventilation holes in the filler caps' fitting and introduction of a temporary revision into the Aircraft Maintenance Manual (AMM). </P>
                </EXTRACT>
                <P>You may obtain further information by examining the MCAI in the AD docket. </P>
                <HD SOURCE="HD1">Relevant Service Information </HD>
                <P>Diamond Aircraft Industries GmbH has issued Mandatory Service Bulletin No. MSB-42-032/1, dated January 24, 2007. The actions described in this service information are intended to correct the unsafe condition identified in the MCAI. </P>
                <HD SOURCE="HD1">FAA's Determination and Requirements of the Proposed AD </HD>
                <P>This product has been approved by the aviation authority of another country, and is approved for operation in the United States. Pursuant to our bilateral agreement with this State of Design Authority, they have notified us of the unsafe condition described in the MCAI and service information referenced above. We are proposing this AD because we evaluated all information and determined the unsafe condition exists and is likely to exist or develop on other products of the same type design. </P>
                <HD SOURCE="HD1">Differences Between This Proposed AD and the MCAI or Service Information </HD>
                <P>We have reviewed the MCAI and related service information and, in general, agree with their substance. But we might have found it necessary to use different words from those in the MCAI to ensure the AD is clear for U.S. operators and is enforceable. In making these changes, we do not intend to differ substantively from the information provided in the MCAI and related service information. </P>
                <P>We might also have proposed different actions in this AD from those in the MCAI in order to follow FAA policies. Any such differences are highlighted in a NOTE within the proposed AD. </P>
                <HD SOURCE="HD1">Costs of Compliance </HD>
                <P>Based on the service information, we estimate that this proposed AD would affect about 47 products of U.S. registry. We also estimate that it would take about 2 work-hours per product to comply with the basic requirements of this proposed AD. The average labor rate is $80 per work-hour. </P>
                <P>Based on these figures, we estimate the cost of the proposed AD on U.S. operators to be $7,520, or $160 per product. </P>
                <HD SOURCE="HD1">Authority for This Rulemaking </HD>
                <P>Title 49 of the United States Code specifies the FAA's authority to issue rules on aviation safety. Subtitle I, section 106, describes the authority of the FAA Administrator. “Subtitle VII: Aviation Programs,” describes in more detail the scope of the Agency's authority. </P>
                <P>We are issuing this rulemaking under the authority described in “Subtitle VII, Part A, Subpart III, Section 44701: General requirements.” Under that section, Congress charges the FAA with promoting safe flight of civil aircraft in air commerce by prescribing regulations for practices, methods, and procedures the Administrator finds necessary for safety in air commerce. This regulation is within the scope of that authority because it addresses an unsafe condition that is likely to exist or develop on products identified in this rulemaking action. </P>
                <HD SOURCE="HD1">Regulatory Findings </HD>
                <P>We 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>
                <P>For the reasons discussed above, I certify this proposed regulation: </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 regulatory evaluation of the estimated costs to comply with this proposed AD and placed it in the AD docket. </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 FAA 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>
                        <PRTPAGE P="18602"/>
                        <SECTNO>§ 39.13 </SECTNO>
                        <SUBJECT>[Amended] </SUBJECT>
                        <P>2. The FAA amends § 39.13 by adding the following new AD: </P>
                        <EXTRACT>
                            <FP SOURCE="FP-2">
                                <E T="04">Diamond Aircraft Industries GmbH:</E>
                                 Docket No. FAA-2007-27708; Directorate Identifier 2007-CE-027-AD. 
                            </FP>
                            <HD SOURCE="HD1">Comments Due Date </HD>
                            <P>(a) We must receive comments by May 14, 2007. </P>
                            <HD SOURCE="HD1">Affected ADs </HD>
                            <P>(b) None.</P>
                            <HD SOURCE="HD1">Applicability </HD>
                            <P>(c) This AD applies to Model DA 42 airplanes; serial numbers 42.015, 42.028, 42.036, 42.044, 42.055, 42.059, 42.062, 42.067, 42.069, 42.075 through 42.100, 42.105, 42.106, 42.108, 42.114, 42.115, 42.117 through 42.122, and 42.124; certificated in any category. </P>
                            <HD SOURCE="HD1">Subject </HD>
                            <P>(d) Air Transport Association of America (ATA) Code 28: Fuel. </P>
                            <HD SOURCE="HD1">Reason </HD>
                            <P>(e) The mandatory continuing airworthiness information (MCAI) states: </P>
                            <P>From airplanes that have installed the Auxiliary Fuel Tank Optional Design Change (OÄM) No. 42-056, three in-service failures of the auxiliary fuel tank venting system have been reported. These failures have led to the inability to supply the complete auxiliary fuel quantity to the main tanks and the collapse of the auxiliary tank. It is suspected that the vent lines were obstructed either by ice accretion under certain climatic conditions or by blockage of the vent valves because of fuel contaminants. </P>
                            <P>Undetected malfunctions of the venting system and damaged auxiliary fuel tanks may lead to a lower usable fuel quantity, subsequent fuel starvation and/or fuel spillage into the nacelle. </P>
                            <HD SOURCE="HD1">Actions and Compliance </HD>
                            <P>(f) Unless already done, do the following actions within the next 30 days after the effective date of this AD: </P>
                            <P>(1) Inspect and modify the auxiliary fuel tank system following Diamond Aircraft Industries GmbH Mandatory Service Bulletin No. MSB-42-032/1, dated January 24, 2007. </P>
                            <P>
                                (2) Incorporate Doc. No. 7.02.01, Section 05-20-00, page 68a of Diamond Aircraft DA 42 AMM Temporary Revision AMM-TR-OÄM-42-056f, dated January 23, 2007, into the Airworthiness Limitations documents of the FAA-approved maintenance program (
                                <E T="03">e.g.,</E>
                                 maintenance manual). The owner/operator holding at least a private pilot certificate as authorized by section 43.7 of the Federal Aviation Regulations (14 CFR 43.7) may insert the information specified in paragraph (f)(2) of this AD into the maintenance program (e.g., maintenance manual). Make an entry into the aircraft records showing compliance with this portion of the AD in accordance with section 43.9 of the Federal Aviation Regulations (14 CFR 43.9). 
                            </P>
                            <NOTE>
                                <HD SOURCE="HED">Note 1:</HD>
                                <P>Doc. No. 7.02.01, Section 05-20-00, page 68a of Diamond Aircraft DA 42 AMM Temporary Revision AMM-TR-OÄM-42-056f, dated January 23, 2007, specifies additional repetitive inspections for the auxiliary tank vent system.</P>
                            </NOTE>
                            <HD SOURCE="HD1">FAA AD Differences </HD>
                            <NOTE>
                                <HD SOURCE="HED">Note 2:</HD>
                                <P>This AD differs from the MCAI and/or service information as follows: No differences.</P>
                            </NOTE>
                            <HD SOURCE="HD1">Other FAA AD Provisions </HD>
                            <P>(g) The following provisions also apply to this AD: </P>
                            <P>(1) Alternative Methods of Compliance (AMOCs): The Manager, Standards Staff, FAA, ATTN: Sarjapur Nagarajan, Aerospace Engineer, FAA, Small Airplane Directorate, 901 Locust, Room 301, Kansas City, Missouri 64106; telephone: (816) 329-4145; fax: (816) 329-4090, has the authority to approve AMOCs for this AD, if requested using the procedures found in 14 CFR 39.19. Before using any approved AMOC on any airplane to which the AMOC applies, notify your appropriate principal inspector (PI) in the FAA Flight Standards District Office (FSDO), or lacking a PI, your local FSDO. </P>
                            <P>(2) Airworthy Product: For any requirement in this AD to obtain corrective actions from a manufacturer or other source, use these actions if they are FAA-approved. Corrective actions are considered FAA-approved if they are approved by the State of Design Authority (or their delegated agent). You are required to assure the product is airworthy before it is returned to service. </P>
                            <P>(3) Reporting Requirements: For any reporting requirement in this AD, under the provisions of the Paperwork Reduction Act (44 U.S.C. 3501 et. seq.), the Office of Management and Budget (OMB) has approved the information collection requirements and has assigned OMB Control Number 2120-0056. </P>
                            <HD SOURCE="HD1">Related Information </HD>
                            <P>(h) Refer to MCAI European Aviation Safety Agency (EASA) AD No.: 2007-0047, dated February 23, 2007; Diamond Aircraft Industries GmbH Mandatory Service Bulletin No. MSB-42-032/1, dated January 24, 2007; and Diamond Aircraft DA 42 AMM Temporary Revision AMM-TR-OÄM-42-056f, dated January 23, 2007 for related information. </P>
                        </EXTRACT>
                    </SECTION>
                    <SIG>
                        <DATED>Issued in Kansas City, Missouri, on April 6, 2007. </DATED>
                        <NAME>Kim Smith, </NAME>
                        <TITLE>Manager, Small Airplane Directorate, Aircraft Certification Service.</TITLE>
                    </SIG>
                </PART>
            </SUPLINF>
            <FRDOC>[FR Doc. E7-7049 Filed 4-12-07; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4910-13-P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="N">ENVIRONMENTAL PROTECTION AGENCY </AGENCY>
                <CFR>40 CFR Parts 52 and 81 </CFR>
                <DEPDOC>[EPA-R03-OAR-2006-0919; FRL-8298-2] </DEPDOC>
                <SUBJECT>Approval and Promulgation of Air Quality Implementation Plans; Virginia; Redesignation of the Hampton Roads 8-Hour Ozone Nonattainment Area to Attainment and Approval of the Associated Maintenance Plan and 2002 Base-Year Inventory </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 is proposing to approve a redesignation request and State Implementation Plan (SIP) revisions submitted by the Commonwealth of Virginia. The Virginia Department of Environmental Quality (VADEQ) is requesting that the Hampton Roads ozone nonattainment area (“Hampton Roads Area” or “Area”) be redesignated as attainment for the 8-hour ozone national ambient air quality standard (NAAQS). The Area is comprised of the Cities of Chesapeake, Hampton, Newport News, Norfolk, Poquoson, Portsmouth, Suffolk, Virginia  Beach, and Williamsburg, and the Counties of Gloucester, Isle of Wight, James City, and York, Virginia. EPA is proposing to approve the ozone redesignation request for the Hampton Roads Area. In conjunction with its redesignation request, the Commonwealth submitted a SIP revision consisting of a maintenance plan for the Hampton Roads Area that provides for continued attainment of the 8-hour ozone NAAQS for at least 10 years after redesignation. EPA is proposing to make a determination that the Hampton Roads Area has attained the 8-hour ozone NAAQS, based upon three years of complete, quality-assured ambient air quality monitoring data for 2003-2005. EPA's proposed approval of the 8-hour ozone redesignation request is based on its determination that the Hampton Roads Area has met the criteria for redesignation to attainment specified in the Clean Air Act (CAA). In addition, the Commonwealth of Virginia has also submitted a 2002 base-year inventory for the Hampton Roads Area, and EPA is proposing to approve that inventory for the Hampton Roads Area as a SIP revision. EPA is also providing information on the status of its adequacy determination for the motor vehicle emission budgets (MVEBs) that are identified in the maintenance plan for the Hampton Roads Area for purposes of transportation conformity, and is also proposing to approve those 
                        <PRTPAGE P="18603"/>
                        MVEBs. EPA is proposing approval of the redesignation request and of the maintenance plan and 2002 base-year inventory SIP revisions in accordance with the requirements of the CAA. 
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Written comments must be received on or before May 14, 2007. </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Submit your comments, identified by Docket ID Number EPA-R03-OAR-2006-0919 by one of the following methods: </P>
                    <P>
                        A. 
                        <E T="03">www.regulations.gov</E>
                        . Follow the on-line instructions for submitting comments. 
                    </P>
                    <P>
                        B. E-mail: 
                        <E T="03">morris.makeba@epa.gov</E>
                    </P>
                    <P>C. Mail: EPA-R03-OAR-2006-0919, Makeba Morris, Chief, Air Quality Planning Branch, Mailcode 3AP21, U.S. Environmental Protection Agency, Region III, 1650 Arch Street, Philadelphia, Pennsylvania 19103. </P>
                    <P>D. Hand Delivery: At the previously-listed EPA Region III address. Such deliveries are only accepted during the Docket's normal hours of operation, and special arrangements should be made for deliveries of boxed information. </P>
                    <P>
                        <E T="03">Instructions:</E>
                         Direct your comments to Docket ID No. EPA-R03-OAR-2006-0919. EPA's policy is that all comments received will be included in the public docket without change, and may be made available online at 
                        <E T="03">www.regulations.gov</E>
                        , including any personal information provided, unless the comment includes information claimed to be Confidential Business Information (CBI) or other information whose disclosure is restricted by statute. Do not submit information that you consider to be CBI or otherwise protected through 
                        <E T="03">www.regulations.gov</E>
                         or e-mail. The 
                        <E T="03">www.regulations.gov</E>
                         Web site is an “anonymous access”  system, which means EPA will not know your identity or contact information unless you provide it in the body of your comment. If you send an e-mail comment directly to EPA without going through 
                        <E T="03">www.regulations.gov,</E>
                         your e-mail address will be automatically captured and included as part of the comment that is placed in the public docket and made available on the Internet. If you submit an electronic comment, EPA recommends that you include your name and other contact information in the body of your comment and with any disk or CD-ROM you submit. 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. Electronic files should avoid the use of special characters, any form of encryption, and be free of any defects or viruses. 
                    </P>
                    <P>
                        <E T="03">Docket:</E>
                         All documents in the electronic docket are listed in the 
                        <E T="03">www.regulations.gov</E>
                         index. Although listed in the index, some information is not publicly available, i.e., CBI or other information whose disclosure is restricted by statute. Certain other material, such as copyrighted material, is not placed on the Internet and will be publicly available only in hard copy form. Publicly available docket materials are available either electronically in 
                        <E T="03">www.regulations.gov</E>
                         or in hard copy during normal business hours at the Air Protection Division, U.S. Environmental Protection Agency, Region III, 1650 Arch Street, Philadelphia, Pennsylvania 19103. Copies of the State submittal are available at the Virginia Department of Environmental Quality, 629 East Main Street, Richmond, Virginia 23219. 
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Amy Caprio, (215) 814-2156, or by e-mail at 
                        <E T="03">caprio.amy@epa.gov</E>
                        . 
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>Throughout this document whenever “we,” “us,” or “our” is used, we mean EPA. </P>
                <EXTRACT>
                    <HD SOURCE="HD1">Table of Contents </HD>
                    <FP SOURCE="FP-2">I. What Are the Actions EPA Is Proposing to Take? </FP>
                    <FP SOURCE="FP-2">II. What Is the Background for These Proposed Actions? </FP>
                    <FP SOURCE="FP-2">III. What Are the Criteria for Redesignation to Attainment? </FP>
                    <FP SOURCE="FP-2">IV. Why Is EPA Taking These Actions? </FP>
                    <FP SOURCE="FP-2">V. What Would Be the Effect of These Actions? </FP>
                    <FP SOURCE="FP-2">VI. What Is EPA's Analysis of the Commonwealth's Request? </FP>
                    <FP SOURCE="FP-2">VII. Are the Motor Vehicle Emissions Budgets Established and Identified in the Maintenance Plan for the Hampton Roads Area Adequate and Approvable? </FP>
                    <FP SOURCE="FP-2">VIII. Proposed Actions </FP>
                    <FP SOURCE="FP-2">IX. Statutory and Executive Order Reviews</FP>
                </EXTRACT>
                <HD SOURCE="HD1">I. What Are the Actions EPA Is Proposing to Take? </HD>
                <P>
                    On October 16, 2006 the VADEQ formally submitted a request to redesignate the Hampton Roads Area from nonattainment to attainment of the 8-hour NAAQS for ozone. On October 18, 2006 Virginia submitted a maintenance plan for the Hampton Roads Area as a SIP revision to ensure continued attainment in the Area over the next 11 years. VADEQ also submitted a 2002 base-year inventory for the Hampton Roads Area as a SIP revision on October 12, 2006 and supplements to the base-year inventory were submitted on November 20, 2006 and February 13, 2007. The Hampton Roads Area is comprised of the Cities of Chesapeake, Hampton, Newport News, Norfolk, Poquoson, Portsmouth, Suffolk, Virginia Beach, and Williamsburg, and the Counties of Gloucester, Isle of Wight, James City, and York, Virginia. It is currently designated a marginal 8-hour ozone nonattainment area. EPA is proposing to determine that the Hampton Roads Area has attained the 8-hour ozone NAAQS and that it has met the requirements for redesignation pursuant to section 107(d)(3)(E) of the CAA. EPA is, therefore, proposing to approve the redesignation request to change the designation of the Hampton Roads Area from nonattainment to attainment for the 8-hour ozone NAAQS. EPA is also proposing to approve the Hampton Roads maintenance plan as a SIP revision for the Area (such approval being one of the CAA criteria for redesignation to attainment status). The maintenance plan is designed to ensure continued attainment in the Hampton Roads Area for the next 11 years. Concurrently, the Commonwealth is requesting that this 8-hour maintenance plan supersede the previous 1-hour maintenance plan. EPA is also proposing to approve the 2002 base-year inventory for the Hampton Roads Area as a SIP revision. Additionally, EPA is announcing its action on the adequacy process for the MVEBs identified in the Hampton Roads maintenance plan, and proposing to approve the MVEBs identified for volatile organic compounds (VOCs) and nitrogen oxides (NO
                    <E T="52">X</E>
                    ) for the Hampton Roads Area for transportation conformity purposes. 
                </P>
                <HD SOURCE="HD1">II. What Is the Background for These Proposed Actions? </HD>
                <HD SOURCE="HD2">A. General </HD>
                <P>
                    Ground-level ozone is not emitted directly by sources. Rather, emissions of NO
                    <E T="52">X</E>
                     and VOC react in the presence of sunlight to form ground-level ozone. The air pollutants NO
                    <E T="52">X</E>
                     and VOC are referred to as precursors of ozone. The CAA establishes a process for air quality management through the attainment and maintenance of the NAAQS. 
                </P>
                <P>
                    On July 18, 1997, EPA promulgated a revised 8-hour ozone standard of 0.08 parts per million (ppm). This new standard is more stringent than the previous 1-hour standard. EPA designated, as nonattainment, any area violating the 8-hour ozone NAAQS based on the air quality data for the three years of 2001-2003. These were the most recent three years of data at the time EPA designated 8-hour areas. The Hampton Roads Area was designated a marginal 8-hour ozone nonattainment area in a 
                    <E T="04">Federal Register</E>
                     notice signed on April 15, 2004 and published on April 30, 2004 (69 FR 23857), based on its exceedance of the 8-hour health-based standard for ozone during the 
                    <PRTPAGE P="18604"/>
                    years 2001-2003. On April 30, 2004, EPA issued a final rule (69 FR 23951, 23996) to revoke the 1-hour ozone NAAQS in the Hampton Roads Area (as well as most other areas of the country) effective June 15, 2005. See 40 CFR 50.9(b); 69 FR at 23996 (April 30, 2004); and see 70 FR 44470 (August 3, 2005). 
                </P>
                <P>
                    However, on December 22, 2006, the U.S. Court of Appeals for the District of Columbia Circuit vacated EPA's Phase 1 Implementation Rule for the 8-hour Ozone Standard. (69 FR 23951, April 30, 2004). 
                    <E T="03">South Coast Air Quality Management Dist.</E>
                     v. 
                    <E T="03">EPA</E>
                    , 472 F.3d 882 (D.C. Cir. 2006) (hereafter “South Coast.”). The Court held that certain provisions of EPA's Phase I Rule were inconsistent with the requirements of the Clean Air Act. The Court rejected EPA's reasons for implementing the 8-hour standard in nonattainment areas under Subpart 1 in lieu of subpart 2 of Title I, part D of the Act. The Court also held that EPA improperly failed to retain four measures required for 1-hour nonattainment areas under the anti-backsliding provisions of the regulations: (1) Nonattainment area New Source Review (NSR) requirements based on an area's 1-hour nonattainment classification; (2) Section 185 penalty fees for 1-hour severe or extreme nonattainment areas; (3) measures to be implemented pursuant to section 172(c)(9) or 182(c)(9) of the Act, on the contingency of an area not making reasonable further progress toward attainment of the 1-hour NAAQS, or for failure to attain that NAAQS; and (4) the certain conformity requirements for certain types of federal. The Court upheld EPA's authority to revoke the 1-hour standard provided there were adequate anti-backsliding provisions. Elsewhere in this document, mainly in section VI. B. “The Hampton Roads Area Has Met All Applicable Requirements under Section 110 and Part D of the CAA and Has a Fully Approved SIP Under Section 110(k) of the CAA,” EPA discusses its rationale why the decision in South Coast is not an impediment to redesignating the Hampton Roads Area to attainment of the 8-hour ozone NAAQS. 
                </P>
                <P>The CAA, title I, part D, contains two sets of provisions—subpart 1 and subpart 2—that address planning and control requirements for nonattainment areas. Subpart 1 (which EPA refers to as “basic” nonattainment) contains general, less prescriptive requirements for nonattainment areas for any pollutant—including ozone—governed by a NAAQS. Subpart 2 (which EPA refers to as “classified” nonattainment) provides more specific requirements for ozone nonattainment areas. In 2004, the Hampton Roads Area was classified a marginal 8-hour ozone nonattainment area based on air quality monitoring data from 2001-2003. Therefore, the Hampton Roads Area is subject to the requirements of subpart 2 of part D. </P>
                <P>Under 40 CFR part 50, the 8-hour ozone standard is attained when the 3-year average of the annual fourth-highest daily maximum 8-hour average ambient air quality ozone concentrations is less than or equal to 0.08 ppm (i.e., 0.084 ppm when rounding is considered). See 69 FR 23857 (April 30, 2004) for further information. Ambient air quality monitoring data for the 3-year period must meet data completeness requirements. The data completeness requirements are met when the average percent of days with valid ambient monitoring data is greater than 90 percent, and no single year has less than 75 percent data completeness as determined in Appendix I of 40 CFR part 50. The ozone monitoring data indicates that the Hampton Roads Area has a design value of 0.078 ppm for the 3-year period of 2003-2005, using complete, quality-assured data. Therefore, the ambient ozone data for the Hampton Roads Area indicates no violations of the 8-hour ozone standard. </P>
                <HD SOURCE="HD2">B. The Hampton Roads Area </HD>
                <P>
                    Under the 1-hour ozone NAAQS, the Hampton Roads Area consists of the Cities of Chesapeake, Hampton, Newport News, Norfolk, Poquoson, Portsmouth, Suffolk, Virginia Beach, and Williamsburg, and the Counties of James City, and York, Virginia. Under the 8-hour ozone NAAQS, the Hampton Roads Area was expanded to also include Gloucester County and Isle of Wight County. Prior to the Area's designation as an 8-hour ozone nonattainment area, the Hampton Roads Area was a maintenance area for the 1-hour ozone NAAQS.
                    <SU>1</SU>
                    <FTREF/>
                     See June 26, 1997 (62 FR 34408). 
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         Under the 1-hour ozone NAAQS the Hampton Roads Area consisted of the Cities of Chesapeake, Hampton, Newport News, Norfolk, Poquoson, Portsmouth, Suffolk, Virginia Beach, and Williamsburg, and the Counties of James City and York. See November 6, 1991 (58 FR 56694). 
                    </P>
                </FTNT>
                <P>On October 16, 2006 the VADEQ requested that the Hampton Roads Area be redesignated to attainment for the 8-hour ozone standard. The redesignation request included three years of complete, quality-assured data for the period of 2003-2005, indicating that the 8-hour NAAQS for ozone had been achieved in the Hampton Roads Area. The data satisfies the CAA requirements that the 3-year average of the annual fourth-highest daily maximum 8-hour average ozone concentration (commonly referred to as the area's design value), must be less than or equal to 0.08 ppm (i.e., 0.084 ppm when rounding is considered). Under the CAA, a nonattainment area may be redesignated if sufficient complete, quality-assured data is available to determine that the area has attained the standard and the area meets the other CAA redesignation requirements set forth in section 107(d)(3)(E). </P>
                <HD SOURCE="HD1">III. What Are the Criteria for Redesignation to Attainment? </HD>
                <P>The CAA provides the requirements for redesignating a nonattainment area to attainment. Specifically, section 107(d)(3)(E) of the CAA, allows for redesignation, providing that: </P>
                <P>(1) EPA determines that the area has attained the applicable NAAQS; </P>
                <P>(2) EPA has fully approved the applicable implementation plan for the area under section 110(k); </P>
                <P>(3) EPA determines that the improvement in air quality is due to permanent and enforceable reductions in emissions resulting from implementation of the applicable SIP and applicable Federal air pollutant control regulations and other permanent and enforceable reductions; </P>
                <P>(4) EPA has fully approved a maintenance plan for the area as meeting the requirements of section 175A; and </P>
                <P>(5) The State containing such area has met all requirements applicable to the area under section 110 and part D. </P>
                <P>EPA provided guidance on redesignations in the General Preamble for the Implementation of Title I of the CAA Amendments of 1990, on April 16, 1992 (57 FR 13498), and supplemented this guidance on April 28, 1992 (57 FR 18070). EPA has provided further guidance on processing redesignation requests in the following documents: </P>
                <P>• “Ozone and Carbon Monoxide Design Value Calculations,” Memorandum from Bill Laxton, June, 18, 1990; </P>
                <P>• “Maintenance Plans for Redesignation of Ozone and Carbon Monoxide Nonattainment Areas,” Memorandum from G.T. Helms, Chief, Ozone/Carbon Monoxide Programs Branch, April 30, 1992; </P>
                <P>• “Contingency Measures for Ozone and Carbon Monoxide (CO) Redesignations,” Memorandum from G.T. Helms, Chief, Ozone/Carbon Monoxide Programs Branch, June 1, 1992; </P>
                <P>
                    • “Procedures for Processing Requests to Redesignate Areas to Attainment,” Memorandum from John Calcagni, Director, Air Quality 
                    <PRTPAGE P="18605"/>
                    Management Division, September 4, 1992; 
                </P>
                <P>• “State Implementation Plan (SIP) Actions Submitted in Response to Clean Air Act (Act) Deadlines,” Memorandum from John Calcagni Director, Air Quality Management Division, October 28, 1992; </P>
                <P>• “Technical Support Documents (TSDs) for Redesignation Ozone and Carbon Monoxide (CO) Nonattainment Areas,” Memorandum from G.T. Helms, Chief, Ozone/Carbon Monoxide Programs Branch, August 17, 1993; </P>
                <P>• “State Implementation Plan (SIP) Requirements for Areas Submitting Requests for Redesignation to Attainment of the Ozone and Carbon Monoxide (CO) National Ambient Air Quality Standards (NAAQS) on or after November 15, 1992,” Memorandum from Michael H. Shapiro, Acting Assistant Administrator for Air and Radiation, September 17, 1993; </P>
                <P>• Memorandum from D. Kent Berry, Acting Director, Air Quality Management Division, to Air Division Directors, Regions 1-10, “Use of Actual Emissions in Maintenance Demonstrations for Ozone and CO Nonattainment Areas,” dated November 30, 1993; </P>
                <P>• “Part D New Source Review (part D NSR) Requirements for Areas Requesting Redesignation to Attainment,” Memorandum from Mary D. Nichols, Assistant Administrator for Air and Radiation, October 14, 1994; and </P>
                <P>• “Reasonable Further Progress, Attainment Demonstration, and Related Requirements for Ozone Nonattainment Areas Meeting the Ozone National Ambient Air Quality Standard,” Memorandum from John S. Seitz, Director, Office of Air Quality Planning and Standards, May 10, 1995. </P>
                <HD SOURCE="HD1">IV. Why Is EPA Taking These Actions? </HD>
                <P>On October 16, 2006, the VADEQ requested redesignation of the Hampton Roads Area to attainment for the 8-hour ozone standard. On October 18, 2006, VADEQ submitted a maintenance plan for the Hampton Roads Area as a SIP revision, to ensure continued attainment of the 8-hour ozone NAAQS over the next 11 years, until 2018. Concurrently, Virginia is requesting that 8-hour maintenance plan submittal supersede the 1-hour maintenance plan requirements already in place and that the 8-hour maintenance plan meet the requirement of CAA section 175A(b) with respect to the 1-hour ozone maintenance plan update. EPA is proposing to approve the maintenance plan to fulfill the requirement of section 175A(b) for submission of a maintenance plan update eight years after the area was redesignated to attainment of the 1-hour ozone NAAQS. EPA believes that such an update must ensure that the maintenance plan in the SIP provides maintenance of the NAAQS for a period of 20 years after the area is initially redesignated to attainment. EPA can propose approval because the maintenance plan, which demonstrates maintenance of the 8-hour ozone NAAQS through 2018, also demonstrates maintenance of the 1-hour ozone NAAQS through 2018. </P>
                <P>VADEQ also submitted a 2002 base-year inventory with its maintenance plan as a SIP revision on October 12, 2006 and supplemental to that submittal on November 20, 2006 and February 13, 2007, which is an applicable requirement for the Hampton Roads Area for purposes of redesignation. EPA has determined that the Hampton Roads Area has attained the 8-hour ozone standard and has met the requirements for redesignation set forth in section 107(d)(3)(E). </P>
                <HD SOURCE="HD1">V. What Would Be the Effect of These Actions? </HD>
                <P>
                    Approval of the redesignation request would change the official designation of the Hampton Roads Area from nonattainment to attainment for the 8-hour ozone NAAQS found at 40 CFR part 81. It would also incorporate into the Virginia SIP a 2002 base-year inventory and a maintenance plan ensuring continued attainment of the 8-hour ozone NAAQS in the Hampton Roads Area for the next 11 years, until 2018. The maintenance plan includes contingency measures to remedy any future violations of the 8-hour NAAQS (should they occur), and identifies the NO
                    <E T="52">X</E>
                     and VOC MVEBs for transportation conformity purposes for the years 2011 and 2018. These MVEBs are displayed in the following table: 
                </P>
                <GPOTABLE COLS="3" OPTS="L2,i1" CDEF="s25,10,10">
                    <TTITLE>Table 1.—Motor Vehicle Emissions Budgets in Tons per Day (tpd) </TTITLE>
                    <BOXHD>
                        <CHED H="1">Year </CHED>
                        <CHED H="1">VOC </CHED>
                        <CHED H="1">
                            NO
                            <E T="52">X</E>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">2011 </ENT>
                        <ENT>37.846 </ENT>
                        <ENT>50.387 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">2018 </ENT>
                        <ENT>27.574</ENT>
                        <ENT>31.890 </ENT>
                    </ROW>
                </GPOTABLE>
                <HD SOURCE="HD1">VI. What Is EPA's Analysis of the Commonwealth's Request? </HD>
                <P>EPA is proposing to determine that the Hampton Roads Area has attained the 8-hour ozone standard and that all other redesignation criteria have been met. The following is a description of how the VADEQ's October 16, 2006 (redesignation request), October 18, 2006 (maintenance plan and MVEBs), October 12, 2006 (base-year emissions inventory), November 20, 2006 (supplement to base-year inventory), and February 13, 2007 (second supplement to base-year inventory) submittals satisfy the requirements of section 107(d)(3)(E) of the CAA. </P>
                <HD SOURCE="HD2">A. The Hampton Roads Area Has Attained the 8-Hour Ozone NAAQS </HD>
                <P>EPA is proposing to determine that the Hampton Roads Area has attained the 8-hour ozone NAAQS. For ozone, an area may be considered to be attaining the 8-hour ozone NAAQS if there are no violations, as determined in accordance with 40 CFR 50.10 and Appendix I of Part 50, based on three complete, consecutive calendar years of quality-assured air quality monitoring data. To attain this standard, the 3-year average of the fourth-highest daily maximum 8-hour average ozone concentrations measured at each monitor, within the area, over each year must not exceed the ozone standard of 0.08 ppm. Based on the rounding convention described in 40 CFR part 50, Appendix I, the standard is attained if the design value is 0.084 ppm or below. The data must be collected and quality-assured in accordance with 40 CFR part 58, and recorded in the Air Quality System (AQS). The monitors generally should have remained at the same location for the duration of the monitoring period required for demonstrating attainment. </P>
                <P>
                    There are three ozone monitors in the Hampton Roads Area. As part of its redesignation request, Virginia referenced ozone monitoring data for the years 2003-2005 for the Hampton Roads Area. This data has been quality assured and is recorded in the AQS. The fourth-high 8-hour daily maximum concentrations, along with the three-year averages are summarized in Table 2. The Hampton and Suffolk—TCC monitoring sites had the highest 3-year average of the fourth highest daily maximum 8-hour average and are therefore used to make air quality determinations. 
                    <PRTPAGE P="18606"/>
                </P>
                <GPOTABLE COLS="6" OPTS="L2,i1" CDEF="s50,12,12,12,12,12">
                    <TTITLE>Table 2.—Hampton Roads Area Fourth Highest 8-Hour Average Values, Hampton Roads Monitors, Parts per Million (ppm) </TTITLE>
                    <BOXHD>
                        <CHED H="1">Monitor </CHED>
                        <CHED H="1">AQS ID No. </CHED>
                        <CHED H="1">2003 </CHED>
                        <CHED H="1">2004 </CHED>
                        <CHED H="1">2005 </CHED>
                        <CHED H="1">
                            3-year 
                            <LI>average </LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Hampton</ENT>
                        <ENT>516500004 </ENT>
                        <ENT>0.083</ENT>
                        <ENT>0.074</ENT>
                        <ENT>0.078</ENT>
                        <ENT>0.078 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Suffolk—TCC</ENT>
                        <ENT>518000004 </ENT>
                        <ENT>0.083</ENT>
                        <ENT>0.074</ENT>
                        <ENT>0.077</ENT>
                        <ENT>0.078 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Suffolk—Holland</ENT>
                        <ENT>518000005 </ENT>
                        <ENT>0.079</ENT>
                        <ENT>0.075</ENT>
                        <ENT>0.078</ENT>
                        <ENT>0.077 </ENT>
                    </ROW>
                    <TNOTE>The average for the 3-year period 2003-2005 is 0.078 ppm. </TNOTE>
                </GPOTABLE>
                <P>The air quality data for 2003-2005 show that the Hampton Roads Area has attained the standard with a design value of 0.078 ppm. The data collected at the Hampton Roads Area monitors satisfy the CAA requirement that the 3-year average of the annual fourth-highest daily maximum 8-hour average ozone concentration is less than or equal to 0.08 ppm. The VADEQ's request for redesignation for the Hampton Roads Area indicates that the data is complete and was quality assured in accordance with 40 CFR part 58. The VADEQ uses the AQS as the permanent database to maintain its data and quality assures the data transfers and content for accuracy. In addition, as discussed below with respect to the maintenance plan, VADEQ has committed to continue monitoring in accordance with 40 CFR part 58. In summary, EPA has determined that the data submitted by Virginia indicates that the Hampton Roads Area has attained the 8-hour ozone NAAQS. </P>
                <HD SOURCE="HD2">B. The Hampton Roads Area Has Met All Applicable Requirements Under Section 110 and Part D of the CAA and Has a Fully Approved SIP Under Section 110(k) of the CAA </HD>
                <P>
                    EPA has determined that the Hampton Roads Area has met all SIP requirements applicable for purposes of this redesignation under section 110 of the CAA (General SIP Requirements) and that it meets all applicable SIP requirements under part D of Title I of the CAA, in accordance with section 107(d)(3)(E)(v). In addition, EPA has determined that the SIP is fully approved with respect to all requirements applicable for purposes of redesignation in accordance with section 107(d)(3)(E)(ii). In making these proposed determinations, EPA ascertained which requirements are applicable to the Hampton Roads Area and determined that the applicable portions of the SIP meeting these requirements are fully approved under section 110(k) of the CAA. We note that SIPs must be fully approved only with respect to applicable requirements. The September 4, 1992 Calcagni memorandum (“Procedures for Processing Requests to Redesignate Areas to Attainment,” Memorandum from John Calcagni, Director, Air Quality Management Division, September 4, 1992) describes EPA's interpretation of section 107(d)(3)(E) with respect to the timing of applicable requirements. Under this interpretation, to qualify for redesignation, States requesting redesignation to attainment must meet only the relevant CAA requirements that came due prior to the submittal of a complete redesignation request. See also Michael Shapiro memorandum, September 17, 1993, and 60 FR 12459, 12465-66 (March 7, 1995) (redesignation of Detroit-Ann Arbor). Applicable requirements of the CAA that come due subsequent to the area's submittal of a complete redesignation request remain applicable until a redesignation is approved, but are not required as a prerequisite to redesignation. Section 175A(c) of the CAA. 
                    <E T="03">Sierra Club v. EPA</E>
                    , 375 F.3d 537 (7th Cir. 2004). See also 68 FR at 25424, 25427 (May 12, 2003) (redesignation of St. Louis). 
                </P>
                <P>
                    This section also sets forth EPA's views on the potential effect of the Court's ruling in 
                    <E T="03">South Coast</E>
                     on this redesignation action. For the reasons set forth below, EPA does not believe that the Court's ruling alters any requirements relevant to this redesignation action so as to preclude redesignation, and does not prevent EPA from finalizing this redesignation. EPA believes that the Court's decision, as it currently stands or as it may be modified based upon any petition for rehearing that has been filed, imposes no impediment to moving forward with redesignation of this area to attainment, because in either circumstance redesignation is appropriate under the relevant redesignation provisions of the Act and longstanding policies regarding redesignation requests. 
                </P>
                <HD SOURCE="HD3">1. Section 110 General SIP Requirements </HD>
                <P>Section 110(a)(2) of Title I of the CAA delineates the general requirements for a SIP, which include enforceable emissions limitations and other control measures, means, or techniques, provisions for the establishment and operation of appropriate devices necessary to collect data on ambient air quality, and programs to enforce the limitations. The general SIP elements and requirements set forth in section 110(a)(2) include, but are not limited to the following: </P>
                <P>• Submittal of a SIP that has been adopted by the State after reasonable public notice and hearing; </P>
                <P>• Provisions for establishment and operation of appropriate procedures needed to monitor ambient air quality; </P>
                <P>• Implementation of a source permit program; provisions for the implementation of part C requirements (Prevention of Significant Deterioration (PSD)); </P>
                <P>• Provisions for the implementation of part D requirements for New Source Review (NSR) permit programs; </P>
                <P>• Provisions for air pollution modeling; and </P>
                <P>• Provisions for public and local agency participation in planning and emission control rule development. </P>
                <P>
                    Section 110(a)(2)(D) requires that SIPs contain certain measures to prevent sources in a state from significantly contributing to air quality problems in another State. To implement this provision, EPA has required certain states to establish programs to address transport of air pollutants in accordance with the NO
                    <E T="52">X</E>
                     SIP Call, October 27, 1998 (63 FR 57356), amendments to the NO
                    <E T="52">X</E>
                     SIP Call, May 14, 1999 (64 FR 26298) and March 2, 2000 (65 FR 11222), and the Clean Air Interstate Rule (CAIR), May 12, 2005 (70 FR 25162). However, the section 110(a)(2)(D) requirements for a State are not linked with a particular nonattainment area's designation and classification in that State. EPA believes that the requirements linked with a particular nonattainment area's designation and classifications are the relevant measures to evaluate in reviewing a redesignation request. The transport SIP submittal requirements, where applicable, continue to apply to a state regardless of the designation of any one particular area in the State. 
                </P>
                <P>
                    Thus, we do not believe that these requirements are applicable requirements for purposes of 
                    <PRTPAGE P="18607"/>
                    redesignation. EPA believes that the other section 110 elements not connected with nonattainment plan submissions and not linked with an area's attainment status are not applicable requirements for purposes of redesignation. The Hampton Roads Area will still be subject to these requirements after it is redesignated. The section 110 and part D requirements, which are linked with a particular area's designation and classification, are the relevant measures to evaluate in reviewing a redesignation request. This policy is consistent with EPA's existing policy on applicability of conformity (
                    <E T="03">i.e.</E>
                    , for redesignations) and oxygenated fuels requirement. See Reading, Pennsylvania, proposed and final rulemakings (61 FR 53174, October 10, 1996), (62 FR 24826, May 7, 1997); Cleveland-Akron-Lorain, Ohio final rulemaking (61 FR 20458, May 7, 1996); and Tampa, Florida, final rulemaking (60 FR 62748, December 7, 1995). See also the discussion on this issue in the Cincinnati redesignation (65 FR at 37890, June 19, 2000), and in the Pittsburgh redesignation (66 FR at 53099, October 19, 2001). Similarly, with respect to the NO
                    <E T="52">X</E>
                     SIP Call rules, EPA noted in its Phase 1 Final Rule to Implement the 8-hour Ozone NAAQS, that the NO
                    <E T="52">X</E>
                     SIP Call rules are not “an” ‘applicable requirement' for purposes of section 110(1) because the NO
                    <E T="52">X</E>
                     rules apply regardless of an area's attainment or nonattainment status for the 8-hour (or the 1-hour) NAAQS.” 69 FR 23951, 23983 (April 30, 2004). 
                </P>
                <P>EPA believes that section 110 elements not linked to the Area's nonattainment status are not applicable for purposes of redesignation. As explained later in this notice, two part D requirements applicable for purposes of redesignation under the 8-hour standard became due prior to the submission of the redesignation request. </P>
                <P>Because the Virginia SIP satisfies all of the applicable general SIP elements and requirements set forth in section 110(a)(2), EPA concludes that Virginia has satisfied the criterion of section 107(d)(3)(E) regarding section 110 of the Act. </P>
                <HD SOURCE="HD3">2. Part D Nonattainment Requirements Under the 8-Hour Standard </HD>
                <P>The Hampton Roads Area was classified a Subpart 2, marginal nonattainment area for the 8-hour ozone standard. Sections 172-176 of the CAA, found in subpart 1 of part D, set forth the basic nonattainment requirements applicable to all nonattainment areas. Section 182 of the CAA, found in subpart 2 of part D, establishes additional specific requirements depending on the area's nonattainment classification. </P>
                <P>The Hampton Roads Area is classified as a Subpart 2, marginal nonattainment area. We do not believe that any part of the Court's opinion would require that this subpart 2 classification be changed upon remand to EPA. However, even assuming for present purposes that the Hampton Roads Area would become subject to a different classification under a classification scheme created in a future rule in response to the court's decision, that would not prevent EPA from finalizing a redesignation for this area. For the reasons set forth below, we believe that any additional requirements that might apply based on that different classification would not be applicable for purposes of evaluating the redesignation request. </P>
                <P>This belief is based upon (1) EPA's longstanding policy of evaluating redesignation requests in accordance with only the requirements due at the time the request was submitted; and (2) consideration of the inequity of applying retroactively any requirements that might be applied in the future. </P>
                <P>
                    First, at the time the redesignation request was submitted, the area was classified under Subpart 2 and was required to meet the Subpart 2 requirements. Under EPA's longstanding interpretation of section 107(d)(3)(E) of the Clean Air Act, to qualify for redesignation, states requesting redesignation to attainment must meet only the relevant SIP requirements that came due prior to the submittal of a complete redesignation request. September 4, 1992 Calcagni memorandum (“Procedures for Processing Requests to Redesignate Areas to Attainment”, Memorandum from John Calcagni, Director, Air Quality Management Division) See also Michael Shapiro Memorandum, September 17, 1993, and 60 FR 12459, 12465-66 (March 7, 1995) (redesignation of Detroit-Ann Arbor); 
                    <E T="03">Sierra Club</E>
                     v. 
                    <E T="03">EPA,</E>
                     375 F.3d 537 (7th Cir. 2004), which upheld this interpretation. See, 
                    <E T="03">e.g,</E>
                     also 68 FR 25418, 25424, 25427 (May 12, 2003) (redesignation of St. Louis). At the time the redesignation request was submitted, the Hampton Roads Area was classified as a marginal area under Subpart 2 and thus only Subpart 2 marginal area requirements are applicable for purposes of redesignation. 
                </P>
                <P>
                    Moreover, it would be inequitable to retroactively apply any new SIP requirements that were not applicable at the time the request was submitted, but which might later become applicable. The D.C. Circuit has recognized the inequity in such retroactive rulemaking. See 
                    <E T="03">Sierra Club</E>
                     v. 
                    <E T="03">Whitman,</E>
                     285 F.3d 63 (D.C. Cir. 2002), in which the D.C. Circuit upheld a District Court's ruling refusing to make retroactive an EPA determination of nonattainment that was past the statutory due date. Such a determination would have resulted in the imposition of additional requirements on the area. The Court stated: “Although EPA failed to make the nonattainment determination within the statutory time frame, Sierra Club's proposed solution only makes the situation worse. Retroactive relief would likely impose large costs on the States, which would face fines and suits for not implementing air pollution prevention plans in 1997, even though they were not on notice at the time.”
                    <E T="03"> Id.</E>
                     at 68. Similarly, here it would be unfair to penalize the area by applying to it for purposes of redesignation any additional requirements that were not in effect at the time it submitted its redesignation request, but that might apply in the future.
                </P>
                <P>
                    Two Subpart 2 requirements became due for the Hampton Roads Area under section 182(a) of the CAA prior to redesignation—a 2002 base-year inventory, and the emissions statement requirement pursuant to section 182(a)(3)(B). Virginia has in its approved SIP an approved emissions statement rule for the 1-hour standard covering those portions of the 8-hour nonattainment area that were part of the previous 1-hour attainment area, which satisfies the emissions statement requirement for the 8-hour standard. See 65 FR 21315 (April 21, 2000). Virginia recently submitted a rulemaking to expand the VOC and NO
                    <E T="52">X</E>
                     Hampton Roads Emissions Control Area to include Gloucester County and Isle of Wight County. EPA approved this rulemaking on March 2, 2007 (72 FR 9441) and will become effective on April 2, 2007. Today, EPA is proposing to approve the 2002 base-year inventory for the Hampton Roads Area, which was submitted on October 12, 2006, and supplemented on November 20, 2006 and February 13, 2007, concurrently with its maintenance plan, into the Virginia SIP. A detailed evaluation of Virginia's 2002 base-year inventory for the Hampton Roads Area can be found in a Technical Support Document (TSD) prepared by EPA for this rulemaking. EPA has determined that the emission inventory and emissions statement requirements for the Hampton Roads Area have been satisfied. 
                </P>
                <P>
                    EPA believes it is reasonable to interpret the general conformity and NSR requirements of part D as not requiring approval prior to 
                    <PRTPAGE P="18608"/>
                    redesignation. With respect to section 176, Conformity Requirements, section 176(c) of the CAA requires states to establish criteria and procedures to ensure that Federally-supported or funded projects conform to the air quality planning goals in the applicable SIP. The requirement to determine conformity applies to transportation plans, programs, and projects developed, funded or approved under Title 23 U.S.C. and the Federal Transit Act (“transportation conformity”) as well as to all other Federally supported or funded projects (“general conformity”). State conformity revisions must be consistent with Federal conformity regulations relating to consultation, enforcement and enforceability that the CAA required the EPA to promulgate. 
                </P>
                <P>
                    EPA believes it is reasonable to interpret the conformity SIP requirements as not applying for purposes of evaluating the redesignation request under section 107(d) since state conformity rules are still required after redesignation and federal conformity rules apply where state rules have not been approved. See 
                    <E T="03">Wall</E>
                     v. 
                    <E T="03">EPA,</E>
                     265 F. 3d 426, 438 (6th Cir. 2001), upholding this interpretation. See also 60 FR 62748 (December 7, 1995). 
                </P>
                <P>EPA has also determined that areas being redesignated need not comply with the requirement that a NSR program be approved prior to redesignation, provided that the area demonstrates maintenance of the standard without part D NSR in effect, because PSD requirements will apply after redesignation. The rationale for this position is described in a memorandum from Mary Nichols, Assistant Administrator for Air and Radiation, dated October 14, 1994, entitled, “Part D NSR Requirements or Areas Requesting Redesignation to Attainment.” Virginia has demonstrated that the Area will be able to maintain the standard without Part D NSR in effect in the Hampton Roads Area, and therefore, Virginia need not have a fully approved Part D NSR program prior to approval of the redesignation request. Virginia's SIP-approved PSD program will become effective in Hampton Roads upon redesignation to attainment. See rulemakings for Detroit, Michigan (60 FR at 12467-68); Cleveland-Akron-Lorrain, Ohio (61 FR at 20458, 20469-70); Louisville, Kentucky (66 FR 53665, 53669 October 23, 2001); Grand Rapids, Michigan (61 FR at 31831, 31834-37, June 21, 1996). </P>
                <HD SOURCE="HD3">3. Requirements Under the 1-Hour Standard </HD>
                <P>With respect to the 1-hour standard requirements, the Gloucester County and Isle of Wight County portions of the Hampton Roads Area were designated Unclassifiable/Attainment under the 1-hour standard and were never designated nonattainment for the 1-hour standard. Therefore, there are no outstanding 1-hour nonattainment area requirements these portions of the Hampton Roads Area would be required to meet. Thus, we find that the Court's ruling does not result in any additional 1-hour requirements for purposes of redesignation. </P>
                <P>The portion of the Hampton Roads Area consisting of the Cities of Chesapeake, Hampton, Newport News, Norfolk, Poquoson, Portsmouth, Suffolk, Virginia Beach, and Williamsburg, and the Counties of James City, and York, Virginia was an Attainment area subject to a Clean Air  Act section 175A maintenance plan under the 1-hour standard. The Court's ruling does not impact redesignation requests for these types of areas. </P>
                <P>
                    First, there are no conformity requirements that are relevant for redesignation requests for any standard, including the requirement to submit a transportation conformity SIP.
                    <SU>2</SU>
                    <FTREF/>
                     Under longstanding EPA policy, EPA believes that it is reasonable to interpret the conformity SIP requirement as not applying for purposes of evaluating a redesignation request under section 107(d) because state conformity rules are still required after redesignation and federal conformity rules apply where state rules have not been approved. 40 CFR 51.390. See 
                    <E T="03">Wall</E>
                     v. 
                    <E T="03">EPA,</E>
                     265 F.3d 426 (6th Cir. 2001), upholding this interpretation. See also 60 FR 62748 (Dec. 7, 1995) (Tampa, FL redesignation). 
                </P>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         Clean Air Act section 176(c)(4)(E) currently requires States to submit revisions to their SIPs to reflect certain federal criteria and procedures for determining transportation conformity. Transportation conformity SIPs are different from the motor vehicle emissions budgets that are established in control strategy SIPs and maintenance plans.
                    </P>
                </FTNT>
                <P>Second, with respect to the three other anti-backsliding provisions for the 1-hour standard that the Court found were not properly retained, this portion of the Hampton Roads Area is an attainment area subject to a maintenance plan for the 1-hour standard, and the NSR, contingency measure (pursuant to section 172(c)(9) or 182(c)(9)) and fee provision requirements no longer apply to an area that has been redesignated to attainment of the 1-hour standard. </P>
                <P>
                    Thus the decision in 
                    <E T="03">South Coast</E>
                     should not alter requirements that would preclude EPA from finalizing the redesignation of this area. 
                </P>
                <HD SOURCE="HD3">4. Hampton Roads Has a Fully Approved SIP for Purposes of Redesignation </HD>
                <P>
                    EPA has fully approved the Virginia SIP for the purposes of this redesignation. EPA may rely on prior SIP approvals in approving a redesignation request. Calcagni Memo, p. 3; 
                    <E T="03">Southwestern Pennsylvania Growth Alliance</E>
                     v. 
                    <E T="03">Browner,</E>
                     144 F. 3d 984, 989-90 (6th Cir. 1998), 
                    <E T="03">Wall</E>
                     v. 
                    <E T="03">EPA,</E>
                     265 F. 3d 426 (6th Cir. 2001), plus any additional measures it may approve in conjunction with a redesignation action. See 68 FR at 25425 (May 12, 2003) and citations therein. The Hampton Roads Area was a 1-hour ozone maintenance area at the time of its designation as a marginal 8-hour ozone nonattainment area on April 30, 2004. As stated previously, two subpart 2 part D requirements became due for the Hampton Roads Area prior to redesignation—a 2002 base-year inventory, and the emissions statement requirement. VADEQ has submitted concurrently with its maintenance plan, a 2002 base-year inventory as a SIP revision. In this action, EPA is proposing approval of this inventory. The emissions statement requirement for the entire Hampton Roads Area was recently fulfilled on March 2, 2007 (72 FR 9441). Because there are no outstanding SIP submission requirements applicable for the purposes of the redesignation of the Hampton Roads Area, the applicable implementation plan satisfies all pertinent SIP requirements. 
                </P>
                <HD SOURCE="HD2">C. The Air Quality Improvement in the Hampton Roads Area is Due to Permanent and Enforceable Reductions in Emissions Resulting From Implementation of the SIP and Applicable Federal Air Pollution Control Regulations and Other Permanent and Enforceable Reductions </HD>
                <P>
                    EPA believes that the Commonwealth has demonstrated that the observed air quality improvement in the Hampton Roads Area is due to permanent and enforceable reductions in emissions resulting from implementation of the SIP, Federal measures, and other State-adopted measures. Emissions reductions attributable to these rules are shown in Table 3. 
                    <PRTPAGE P="18609"/>
                </P>
                <GPOTABLE COLS="6" OPTS="L2,i1" CDEF="s25,12,12,12,12,12">
                    <TTITLE>
                        Table 3.—Total VOC and NO
                        <E T="52">X</E>
                         Emissions for 2002 and 2005 in Tons per Day (tpd) 
                    </TTITLE>
                    <BOXHD>
                        <CHED H="1">Year </CHED>
                        <CHED H="1">Point </CHED>
                        <CHED H="1">Area * </CHED>
                        <CHED H="1">Nonroad </CHED>
                        <CHED H="1">Mobile </CHED>
                        <CHED H="1">Total </CHED>
                    </BOXHD>
                    <ROW EXPSTB="05" RUL="s">
                        <ENT I="21">
                            <E T="02">Volatile Organic Compounds (VOC)</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="01">2002 </ENT>
                        <ENT>18.758 </ENT>
                        <ENT>87.402 </ENT>
                        <ENT>46.543 </ENT>
                        <ENT>67.293 </ENT>
                        <ENT>219.996 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">2005 </ENT>
                        <ENT>20.091 </ENT>
                        <ENT>91.980 </ENT>
                        <ENT>42.320 </ENT>
                        <ENT>50.591 </ENT>
                        <ENT>204.982 </ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01">Diff (02-05) </ENT>
                        <ENT>+1.333 </ENT>
                        <ENT>+4.578 </ENT>
                        <ENT>−4.223 </ENT>
                        <ENT>−16.702 </ENT>
                        <ENT>−15.014 </ENT>
                    </ROW>
                    <ROW EXPSTB="05" RUL="s">
                        <ENT I="21">
                            <E T="02">Nitrogen Oxides (NO</E>
                            <E T="52">X</E>
                            ) 
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="01">2002 </ENT>
                        <ENT>91.403 </ENT>
                        <ENT>57.961 </ENT>
                        <ENT>31.002 </ENT>
                        <ENT>93.844 </ENT>
                        <ENT>274.210 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">2005 </ENT>
                        <ENT>62.536 </ENT>
                        <ENT>55.207 </ENT>
                        <ENT>30.208 </ENT>
                        <ENT>78.169 </ENT>
                        <ENT>226.120 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Diff (02-05) </ENT>
                        <ENT>−28.867 </ENT>
                        <ENT>−2.754 </ENT>
                        <ENT>−0.794 </ENT>
                        <ENT>−15.675 </ENT>
                        <ENT>−48.090 </ENT>
                    </ROW>
                    <TNOTE>* Area source category includes emissions from motor vehicle refueling. </TNOTE>
                </GPOTABLE>
                <P>
                    Between 2002 and 2005, VOC emissions decreased by 15.014 tpd and NO
                    <E T="52">X</E>
                     emissions decreased by 48.090 tpd because of permanent and enforceable measures implemented by the Commonwealth and the federal government. These reductions, and anticipated future reductions, are due to the following permanent and enforceable measures. 
                </P>
                <HD SOURCE="HD3">Programs Currently in Effect </HD>
                <P>(a) Tier 1; </P>
                <P>(b) Tier 2; </P>
                <P>(c) National Low Emission Vehicle (NLEV) Program; and </P>
                <P>
                    (d) NO
                    <E T="52">X</E>
                     SIP Call. 
                </P>
                <P>EPA believes that permanent and enforceable emissions reductions are the cause of the long-term improvement in ozone levels and are the cause of the Area achieving attainment of the 8-hour ozone standard. </P>
                <HD SOURCE="HD2">D. The Hampton Roads Area Has a Fully Approvable Maintenance Plan Pursuant to Section 175A of the CAA </HD>
                <P>In conjunction with its request to redesignate the Hampton Roads Area to attainment status, Virginia submitted a SIP revision to provide for maintenance of the 8-hour ozone NAAQS in the Area for at least 11 years after redesignation. The Commonwealth is requesting that EPA approve this SIP revision as meeting the requirement of CAA 175A and 175A(b). Section 175A(a) was met with the October 18, 2006 submission of the maintenance plan, because it states that Hampton Roads will maintain the 8-hour ozone NAAQS for at least 10 years after redesignation. Section 175A(b) was met with the October 18, 2006 submission of the maintenance plan, because it will replace the 1-hour maintenance plan update requirement that was due 8 years after redesingation of Hampton Roads to attainment. Once approved, the maintenance plan for the 8-hour ozone NAAQS will ensure that the SIP for Hampton Roads meets the requirements of the CAA regarding maintenance of the applicable 8-hour ozone standard. </P>
                <HD SOURCE="HD3">What Is Required in a Maintenance Plan? </HD>
                <P>Section 175A of the CAA sets forth the elements of a maintenance plan for areas seeking redesignation from nonattainment to attainment. Under section 175A(a), the plan must demonstrate continued attainment of the applicable NAAQS for at least 10 years after approval of a redesignation of an area to attainment. Section 175A(b) states that eight years after redesignation from nonattainment to attainment, the State must submit a revised maintenance plan demonstrating that attainment will continue to be maintained for the next 10-year period following the initial 10-year period. To address the possibility of future NAAQS violations, the maintenance plan must contain such contingency measures, with a schedule for implementation, as EPA deems necessary to assure prompt correction of any future 8-hour ozone violations. Section 175A of the CAA sets forth the elements of a maintenance plan for areas seeking redesignation from nonattainment to attainment. The Calcagni memorandum dated September 4, 1992, provides additional guidance on the content of a maintenance plan. An ozone maintenance plan should address the following provisions: </P>
                <P>(a) An attainment emissions inventory; </P>
                <P>(b) A maintenance demonstration; </P>
                <P>(c) A monitoring network; </P>
                <P>(d) Verification of continued attainment; and </P>
                <P>(e) A contingency plan. </P>
                <HD SOURCE="HD3">Analysis of the Hampton Roads Area Maintenance Plan </HD>
                <P>
                    (a) Attainment inventory—An attainment inventory includes the emissions during the time period associated with the monitoring data showing attainment. VADEQ determined that the appropriate attainment inventory year is 2005. That year establishes a reasonable year within the three-year block of 2003-2005 as a baseline and accounts for reductions attributable to implementation of the CAA requirements to date. The 2005 inventory is consistent with EPA guidance and is based on actual “typical summer day” emissions of VOC and NO
                    <E T="52">X</E>
                     during 2005 and consists of a list of sources and their associated emissions. 
                </P>
                <P>
                    To develop the NO
                    <E T="52">X</E>
                     and VOC base year emissions inventories, VADEQ used the following approaches: 
                </P>
                <P>(i) Point source emissions were developed using the latest version of EPA's Economic Growth Analysis System (EGAS 5.0). </P>
                <P>(ii) Area source emissions were also developed using growth factors from EGAS 5.0 and then applied to the 2002 Area source inventory. </P>
                <P>(iii) Mobile nonroad emissions were developed using EPA's NONROAD 2005 model. The NONROAD 2005 model estimates fuel consumption and emissions of total hydrocarbons, carbon monoxide, nitrogen oxides, sulfur oxides, and particulate matter for all nonroad mobile source categories except for aircraft, locomotives, and commercial marine vessels (CMV).</P>
                <P>
                    (iv) Mobile on-road source emissions were calculated using EPA's MOBILE6.2 mobile source inventory model. The Virginia Department of Transportation (VDOT) provided daily vehicle miles traveled (DVMT), average speed data for each road type by jurisdiction, and annual growth rates that were used to forecast DVMT into the future. Also, the Virginia Department of Motor Vehicles provided registration data that was specific to each jurisdiction. Mobile source emission projections include the National Low Emission Vehicle Program (NLEV), the 2004 Tier 2 and Low Sulfur Gasoline Rule, the 2004 and 2007 Heavy-Duty Diesel Vehicle Rules, and the 2006 Low Sulfur Diesel Rule. In 
                    <PRTPAGE P="18610"/>
                    addition, James City, York, Chesapeake, Hampton, Newport News, Norfolk, Poquoson, Portsmouth, Suffolk, Virginia Beach, and Williamsburg were modeled with Phase II Reformulated Gasoline (RFG) while Gloucester and Isle of Wight were modeled with conventional gasoline fuel. 
                </P>
                <P>More detailed information on the compilation of the 2002, 2005, 2011, and 2018 inventories can found in the Technical Appendices, which are part of VADEQ's October 18, 2006 submittal. </P>
                <P>
                    (b) Maintenance Demonstration—On October 18, 2006, the VADEQ submitted a maintenance plan as required by section 175A of the CAA. The Hampton Roads maintenance plan shows maintenance of the 8-hour ozone NAAQS by demonstrating that future emissions of VOC and NO
                    <E T="52">X</E>
                     will not exceed the attainment year 2005 emissions levels throughout the Hampton Roads Area through the year 2018. A maintenance demonstration need not be based on modeling. See 
                    <E T="03">Wall</E>
                     v. 
                    <E T="03">EPA, supra; Sierra Club</E>
                     v. 
                    <E T="03">EPA, supra.</E>
                     See also 66 FR at 53099-53100; 68 FR at 25430-32. 
                </P>
                <P>
                    Tables 4 and 5 specify the VOC and NO
                    <E T="52">X</E>
                     emissions for the Hampton Roads Area for 2005, 2011, and 2018. The VADEQ chose 2011 as an interim year in the maintenance demonstration period to demonstrate that the VOC and NO
                    <E T="52">X</E>
                     emissions are not projected to increase above the 2005 attainment level during the time of the maintenance period. 
                </P>
                <GPOTABLE COLS="04" OPTS="L2,i1" CDEF="s50,12,12,12">
                    <TTITLE>Table 4.—Total VOC Emissions for 2005-2018 (tpd)</TTITLE>
                    <BOXHD>
                        <CHED H="1">Source category</CHED>
                        <CHED H="1">2005 VOC emissions</CHED>
                        <CHED H="1">2011 VOC emissions</CHED>
                        <CHED H="1">2018 VOC emissions</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Point</ENT>
                        <ENT>20.091</ENT>
                        <ENT>23.280</ENT>
                        <ENT>26.700</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            Area 
                            <SU>1</SU>
                        </ENT>
                        <ENT>91.980</ENT>
                        <ENT>100.960</ENT>
                        <ENT>112.790</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            Mobile 
                            <SU>2</SU>
                        </ENT>
                        <ENT>50.591</ENT>
                        <ENT>37.846</ENT>
                        <ENT>27.574</ENT>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="01">Nonroad</ENT>
                        <ENT>42.320</ENT>
                        <ENT>33.912</ENT>
                        <ENT>31.315</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Total</ENT>
                        <ENT>204.982</ENT>
                        <ENT>195.998</ENT>
                        <ENT>198.379</ENT>
                    </ROW>
                    <TNOTE>
                        <SU>1</SU>
                         Includes vehicle refueling emissions and the benefits of selected local controls (Stage I, CTG RACT, and open burning). Also includes site/project specific emissions estimates and projections.
                    </TNOTE>
                    <TNOTE>
                        <SU>2</SU>
                         Includes transportation provisions.
                    </TNOTE>
                </GPOTABLE>
                <GPOTABLE COLS="04" OPTS="L2,i1" CDEF="s50,12,12,12">
                    <TTITLE>
                        Table 5.—Total NO
                        <E T="52">X</E>
                         Emissions for 2005-2018 (tpd)
                    </TTITLE>
                    <BOXHD>
                        <CHED H="1">Source category</CHED>
                        <CHED H="1">
                            2005 NO
                            <E T="52">X</E>
                             emissions
                        </CHED>
                        <CHED H="1">
                            2011 NO
                            <E T="52">X</E>
                             emissions
                        </CHED>
                        <CHED H="1">
                            2018 NO
                            <E T="52">X</E>
                             emissions
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Point</ENT>
                        <ENT>62.536</ENT>
                        <ENT>69.333</ENT>
                        <ENT>75.241</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            Area 
                            <SU>1</SU>
                        </ENT>
                        <ENT>55.207</ENT>
                        <ENT>56.974</ENT>
                        <ENT>60.105</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            Mobile 
                            <SU>2</SU>
                        </ENT>
                        <ENT>78.169</ENT>
                        <ENT>50.387</ENT>
                        <ENT>31.890</ENT>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="01">Non-road</ENT>
                        <ENT>30.208</ENT>
                        <ENT>29.116</ENT>
                        <ENT>23.093</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Total</ENT>
                        <ENT>226.120</ENT>
                        <ENT>205.810</ENT>
                        <ENT>190.329</ENT>
                    </ROW>
                    <TNOTE>
                        <SU>1</SU>
                         Includes selected local controls (open burning). Also includes site/project specific emissions estimates and projections.
                    </TNOTE>
                    <TNOTE>
                        <SU>2</SU>
                         Includes transportation provisions.
                    </TNOTE>
                </GPOTABLE>
                <P>Additionally, the following programs are either effective or due to become effective and will further contribute to the maintenance demonstration of the 8-hour ozone NAAQS: </P>
                <P>Currently in Effect: </P>
                <P>• The National Low Emission Vehicle (NLEV) program; </P>
                <P>• Open burning restrictions for James City, York, Chesapeake, Hampton, Newport News, Norfolk, Poquoson, Portsmouth, Suffolk, Virginia Beach, and Williamsburg; </P>
                <P>• Control Technology Guideline (CTG) Reasonable Available Control Technology (RACT) requirements for James City, York, Chesapeake, Hampton, Newport News, Norfolk, Poquoson, Portsmouth, Suffolk, Virginia Beach, and Williamsburg; </P>
                <P>• Stage I gasoline vapor recovery requirements for James City, York, Chesapeake, Hampton, Newport News, Norfolk, Poquoson, Portsmouth, Suffolk, Virginia Beach, and Williamsburg; </P>
                <P>• Motor vehicle fleet turnover with new vehicles meeting the Tier 2 standards; and </P>
                <P>• Low sulfur gasoline. </P>
                <P>Additionally, the following programs are in place and either effective or are due to become effective: </P>
                <P>• Heavy duty diesel on-road (2004/2007) and low sulfur on-road (2006); 66 FR 5002, (January 18, 2001) </P>
                <P>• Non-road emission standards (2008) and off-road diesel fuel 2007/2010); 69 FR 38958 (June 29, 2004). </P>
                <P>Lastly, to further improve air quality and to provide room for industrial and population growth while maintaining emissions in the area to less than 2005 levels, the Commonwealth of Virginia has initiated rulemaking to implement the following programs: </P>
                <P>• Implement the Stage I requirements of 9 VAC 5 Chapter 40, Article 37 in Isle of Wight and Gloucester; </P>
                <P>• Implement open burning restriction requirements of 9 VAC 5 Chapter 40, Article 40 in Isle of Wight and Gloucester; and </P>
                <P>• Implement existing source CTG RACT requirements of 9 VAC 5 Chapter 40, Articles 5-6, 24-36, and 39 in Isle of Wight and Gloucester. </P>
                <P>Based on the comparison of the projected emissions and the attainment year emissions along with the additional measures, EPA concludes that VADEQ has successfully demonstrated that the 8-hour ozone standard should be maintained in the Hampton Roads Area. </P>
                <P>(c) Monitoring Network—There are three monitors measuring ozone in the Hampton Roads Area. VADEQ will continue to operate its current air quality monitors (located in the Hampton Roads Area), in accordance with 40 CFR part 58. </P>
                <P>
                    (d) Verification of Continued Attainment—In addition to maintaining the key elements of its regulatory program, the Commonwealth will acquire ambient and source emission data to track attainment and maintenance. The Commonwealth will track the progress of the maintenance demonstration by periodically updating 
                    <PRTPAGE P="18611"/>
                    the emissions inventory. This tracking will consist of annual and periodic evaluations. The annual evaluation will consist of checks on key emissions trend indicators as they actually emission update of stationary sources, the Highway Performance Monitoring System (HPMS) vehicle miles traveled data reported to the Federal Highway Administration, and other growth indicators. These indicators will be compared to the growth assumptions used in the plan to determine if the predicted versus the observed growth remains relatively constant. The Commonwealth will also develop and submit periodic (every three years) emission inventories prepared under EPA's Consolidated Emission Reporting Regulation (40 CFR 51, subpart A), beginning in 2005. 
                </P>
                <P>(e) The Maintenance Plan's Contingency Measures—The contingency plan provisions are designed to promptly correct a violation of the NAAQS that occurs after redesignation. Section 175A of the CAA requires that a maintenance plan include such contingency measures as EPA deems necessary to ensure that the Commonwealth will promptly correct a violation of the NAAQS that occurs after redesignation. The maintenance plan should identify the events that would “trigger” the adoption and implementation of a contingency measure(s), the contingency measure(s) that would be adopted and implemented, and the schedule indicating the time frame by which the state would adopt and implement the measure(s). </P>
                <P>
                    The ability of the Hampton Roads Area to stay in compliance with the 8-hour ozone standard after redesignation depends upon VOC and NO
                    <E T="52">X</E>
                     emissions in the Area remaining at or below 2005 levels. The Commonwealth's maintenance plan projects VOC and NO
                    <E T="52">X</E>
                     emissions to decrease and stay below 2005 levels through the year 2018. The Commonwealth's maintenance plan outlines the procedures for the adoption and implementation of contingency measures to further reduce emissions should a violation occur. 
                </P>
                <P>The Commonwealth's maintenance plan lays out situations where the need to adopt and implement a contingency measure to further reduce emissions would be triggered. Those situations are as follows:</P>
                <P>
                    (i) An actual increase of the VOC or NO
                    <E T="52">X</E>
                     emissions exceed the regional emissions budgets, which would be identified or predicted through the development of the comprehensive periodic tracking inventories—The maintenance plan states that the VADEQ will monitor the observed growth rates for VMT, population, and point source VOC and NO
                    <E T="52">X</E>
                     emissions on a yearly basis which will serve as an early warning indicator of the potential for a violation. The plan also states that comprehensive tracking inventories will also be developed every 3 years using current EPA-approved methods to estimate emissions, concentrating on areas identified in the less rigorous yearly evaluations as being potential problems. If the regional emissions budget for VOC or NO
                    <E T="52">X</E>
                     is exceeded, the following control strategies will be implemented as follows: 
                </P>
                <P>
                    • Preparation of a complete VOC and NO
                    <E T="52">X</E>
                     emission inventory; and 
                </P>
                <P>• The expanded implementation of one or more of the following control strategies, listed in Table 6, that are not currently in place in the Hampton Roads Area. </P>
                <GPOTABLE COLS="02" OPTS="L2,i1" CDEF="s100,r100">
                    <TTITLE>Table 6.—Maintenance Plan Contingency Measure Options</TTITLE>
                    <BOXHD>
                        <CHED H="1">Control strategy</CHED>
                        <CHED H="1">Description</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">9 VAC 5 Chapter 40, Article 42</ENT>
                        <ENT>Emission Standards for Portable Fuel Container Spillage.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">9 VAC 5 Chapter 40, Article 47</ENT>
                        <ENT>Emissions Standards for Solvent Metal Cleaning Operations.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">9 VAC 5 Chapter 40, Article 48</ENT>
                        <ENT>Emissions Standards for Mobile Equipment Repair and Refinishing Operations.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">9 VAC 5 Chapter 40, Article 49</ENT>
                        <ENT>Emissions Standards for Architectural and Industrial Maintenance Coatings.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">9 VAC 5 Chapter 40, Article 50</ENT>
                        <ENT>Emission Standards for Consumer Products.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">9 VAC 5-40-300 of 9 VAC 5 Chapter 40, Article 4</ENT>
                        <ENT>General Process Operations—Standard for Volatile Organic Compounds (non-CTG RACT for major sources).</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">9 VAC 5-40-310 of 9 VAC 5 Chapter 40, Article 4</ENT>
                        <ENT>General Process Operations—Standards for Nitrogen Oxides (non-CTG RACT for major sources).</ENT>
                    </ROW>
                </GPOTABLE>
                <P>(ii) A violation (any 3-year average of each annual fourth highest 8-hour average) of the 8-hour ozone NAAQS of 0.08 ppm occurs—The maintenance plan states that if a violation (any 3-year average of each annual fourth highest 8-hour average) of the 8-hour ozone NAAQS of 0.08 ppm occurs at a monitor located in the Hampton Roads monitoring network, the VADEQ will implement two of the following control strategies as follows: </P>
                <P>• The expanded implementation of one or more of the control strategies, listed in Table 6 that is not currently in place in the Hampton Roads Area. </P>
                <P>(iii) A violation (any 3-year average of each annual fourth highest 8-hour average) of the 8-hour ozone NAAQS of 0.08 ppm in any subsequent ozone season—The maintenance plan states that if a violation (any 3-year average of each annual fourth highest 8-hour average) of the 8-hour ozone NAAQS of 0.08 ppm occurs in the Hampton Roads monitoring network following the implementation of the requirements listed in the previous section (section e(ii)) and in any subsequent ozone season, two additional control strategies from Table 6 will be implemented. </P>
                <P>The following schedule for adoption, implementation and compliance applies to the contingency measures concerning non-CTG RACT requirements. It would also apply to the imposition of the area source VOC regulations if those regulations had not already been implemented due to other triggers or provisions of the maintenance plan. </P>
                <P>• Notification received from EPA that a contingency measure must be implemented, or three months after a recorded violation; </P>
                <P>• Applicable regulation to be adopted 6 months after this date; </P>
                <P>
                    • Applicable regulation to be implemented 6 months after adoption;
                    <SU>3</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         In the event of implementation of the RACT contingency measure, Virginia would amend its current RACT regulations to apply them to non-CTG sources in the Hampton Roads Area within 6 months after (a) notification received from EPA that the contingency measure must be implemented, or (b) three months after a recorded violation. The newly subject non-CTG RACT sources would need to develop source-specific RACT plans and comply with their plans no later than 12 months from the date of Virginia's adoption of the amended regulations.
                    </P>
                </FTNT>
                <PRTPAGE P="18612"/>
                <P>• Compliance with regulation to be achieved within 12 months of adoption. </P>
                <P>The maintenance plan adequately addresses the five basic components of a maintenance plan: Attainment inventory, maintenance demonstration, monitoring network, verification of continued attainment, and a contingency plan. EPA believes that the maintenance plan SIP revision submitted by Virginia for the Hampton Roads area meets the requirements of section 175A of the Act. </P>
                <HD SOURCE="HD1">VII. Are the Motor Vehicle Emissions Budgets Established and Identified in the Hampton Roads Maintenance Plan Adequate and Approvable? </HD>
                <HD SOURCE="HD2">A. What Are the Motor Vehicle Emissions Budgets?</HD>
                <P>Under the CAA, States are required to submit, at various times, control strategy SIPs and maintenance plans in ozone areas. These control strategy SIPs (i.e., RFP SIPs and attainment demonstration SIPs) and maintenance plans identify and establish MVEBs for certain criteria pollutants and/or their precursors to address pollution from on-road mobile sources. In the maintenance plan, the MVEBs are termed “on-road mobile source emission budgets.” Pursuant to 40 CFR part 93 and 51.112, MVEBs must be established in an ozone maintenance plan. An MVEB is the portion of the total allowable emissions that is allocated to highway and transit vehicle use and emissions. An MVEB serves as a ceiling on emissions from an area's planned transportation system. The MVEB concept is further explained in the preamble to the November 24, 1993, transportation conformity rule (58 FR 62188). The preamble also describes how to establish and revise the MVEBs in control strategy SIPs and maintenance plans. </P>
                <P>Under section 176(c) of the CAA, new transportation projects, such as the construction of new highways, must “conform” to (i.e., be consistent with) the part of the State's air quality plan that addresses pollution from cars and trucks. “Conformity” to the SIP means that transportation activities will not cause new air quality violations, worsen existing violations, or delay timely attainment of or reasonable progress towards the NAAQS. If a transportation plan does not “conform,” most new projects that would expand the capacity of roadways cannot go forward. Regulations at 40 CFR part 93 set forth EPA policy, criteria, and procedures for demonstrating and ensuring conformity of such transportation activities to a SIP. </P>
                <P>When reviewing submitted “control strategy” SIPs or maintenance plans containing MVEBs, EPA must affirmatively find the MVEB contained therein “adequate” for use in determining transportation conformity. After EPA affirmatively finds the submitted MVEB is adequate for transportation conformity purposes, that MVEB can be used by state and federal agencies in determining whether proposed transportation projects “conform” to the SIP as required by section 176(c) of the CAA. EPA's substantive criteria for determining “adequacy” of a MVEB are set out in 40 CFR 93.118(e)(4). </P>
                <P>
                    EPA's process for determining “adequacy” consists of three basic steps: Public notification of a SIP submission, a public comment period, and EPA's adequacy finding. This process for determining the adequacy of submitted SIP MVEBs was initially outlined in EPA's May 14, 1999 guidance, “Conformity Guidance on Implementation of March 2, 1999, Conformity Court Decision.” This guidance was finalized in the Transportation Conformity Rule Amendments for the “New 8-Hour Ozone and PM
                    <E T="52">2.5</E>
                     National Ambient Air Quality Standards and Miscellaneous Revisions for Existing Areas; Transportation Conformity Rule Amendments—Response to Court Decision and Additional Rule Change” on July 1, 2004 (69 FR 40004). EPA consults this guidance and follows this rulemaking in making its adequacy determinations. 
                </P>
                <P>The MVEBS for the Hampton Roads Area are listed in Table 1 of this document for 2011 and 2018, and are the projected emissions for the on-road mobile sources plus any portion of the safety margin allocated to the MVEBs (safety margin allocation for 2011 and 2018 only). These emission budgets, when approved by EPA, must be used for transportation conformity determinations. </P>
                <HD SOURCE="HD2">B. What Is a Safety Margin? </HD>
                <P>
                    A “safety margin” is the difference between the attainment level of emissions (from all sources) and the projected level of emissions (from all sources) in the maintenance plan. The attainment level of emissions is the level of emissions during one of the years in which the area met the NAAQS. The following example is for the 2018 safety margin: Hampton Roads first attained the 8-hour ozone NAAQS during the 2003 to 2005 time period. The Commonwealth used 2005 as the year to determine attainment levels of emissions for Hampton Roads. The total emissions from point, area, mobile on-road, and mobile non-road sources in 2005 equaled 204.982 tpd of VOC and 226.120 tpd of NO
                    <E T="52">X</E>
                    . The VADEQ projected emissions out to the year 2018 and projected a total of 198.379 tpd of VOC and 190.329 tpd of NO
                    <E T="52">X</E>
                     from all sources in Hampton Roads. The safety margin for 2018 would be the difference between these amounts, or 6.603 tpd of VOC and 35.791 tpd of NO
                    <E T="52">X</E>
                    . The emissions up to the level of the attainment year including the safety margins are projected to maintain the Area's air quality consistent with the 8-hour ozone NAAQS. The safety margin is the extra emissions reduction below the attainment levels that can be allocated for emissions by various sources as long as the total emission levels are maintained at or below the attainment levels. Table 7 shows the safety margins for the 2011 and 2018 years. 
                </P>
                <GPOTABLE COLS="3" OPTS="L2,i1" CDEF="s50,13,13">
                    <TTITLE>Table 7.—2011 and 2018 Safety Margins for Hampton Roads </TTITLE>
                    <BOXHD>
                        <CHED H="1">Inventory year </CHED>
                        <CHED H="1">
                            VOC emissions 
                            <LI>(tpd) </LI>
                        </CHED>
                        <CHED H="1">
                            NO
                            <E T="52">X</E>
                             emissions 
                            <LI>(tpd) </LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">2005 Attainment </ENT>
                        <ENT>204.982 </ENT>
                        <ENT>226.120 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">2011 Interim </ENT>
                        <ENT>195.998 </ENT>
                        <ENT>205.810 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">2011 Safety Margin </ENT>
                        <ENT>8.984 </ENT>
                        <ENT>20.310 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">2005 Attainment </ENT>
                        <ENT>204.982 </ENT>
                        <ENT>226.120 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">2018 Final </ENT>
                        <ENT>198.379 </ENT>
                        <ENT>190.329 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">2018 Safety Margin </ENT>
                        <ENT>6.603 </ENT>
                        <ENT>35.791 </ENT>
                    </ROW>
                </GPOTABLE>
                <PRTPAGE P="18613"/>
                <P>
                    The VADEQ allocated 1.000 tpd VOC and 3.000 tpd NO
                    <E T="52">X</E>
                     to the 2011 interim VOC projected on-road mobile source emissions projection and the 2011 interim NO
                    <E T="52">X</E>
                     projected on-road mobile source emissions projection to arrive at the 2011 MVEBs. For the 2018 MVEBs the VADEQ allocated 1.000 tpd VOC and 3.000 tpd NO
                    <E T="52">X</E>
                     from the 2018 safety margins to arrive at the 2018 MVEBs. Once allocated to the mobile source budgets these portions of the safety margins are no longer available, and may no longer be allocated to any other source category. Table 8 shows the final 2009 and 2018 MVEBS for the Hampton Roads Area. 
                </P>
                <GPOTABLE COLS="3" OPTS="L2,i1" CDEF="s50,13,13">
                    <TTITLE>Table 8.—2011 and 2018 Final MVEBs for Hampton Roads </TTITLE>
                    <BOXHD>
                        <CHED H="1">Inventory year </CHED>
                        <CHED H="1">
                            VOC emissions 
                            <LI>(tpd) </LI>
                        </CHED>
                        <CHED H="1">
                            NO
                            <E T="52">X</E>
                             emissions 
                            <LI>(tpd) </LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">2011 Projected on-road mobile source projected emissions </ENT>
                        <ENT>36.846 </ENT>
                        <ENT>47.387 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">2011 Safety Margin Allocated to MVEBs </ENT>
                        <ENT>1.000 </ENT>
                        <ENT>3.000 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">2011 MVEBs </ENT>
                        <ENT>37.846 </ENT>
                        <ENT>50.387 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">2018 Projected on-road mobile source projected emissions </ENT>
                        <ENT>26.574 </ENT>
                        <ENT>28.890 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">2018 Safety Margin Allocated to MVEBs </ENT>
                        <ENT>1.000 </ENT>
                        <ENT>3.000 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">2018 MVEBs </ENT>
                        <ENT>27.574 </ENT>
                        <ENT>31.890 </ENT>
                    </ROW>
                </GPOTABLE>
                <HD SOURCE="HD2">C. Why Are the MVEBs Approvable? </HD>
                <P>
                    The 2011 and 2018 MVEBs for the Hampton Roads Area are approvable because the MVEBs for NO
                    <E T="52">X</E>
                     and VOCs continue to maintain the total emissions at or below the attainment year inventory levels as required by the transportation conformity regulations. 
                </P>
                <HD SOURCE="HD2">D. What Is the Adequacy and Approval Process for the MVEBs in the Hampton Roads Maintenance Plan? </HD>
                <P>
                    The MVEBs for the Hampton Roads Area maintenance plan are being posted to EPA's conformity Web site concurrently with this proposal. The public comment period will end at the same time as the public comment period for this proposed rule. In this case, EPA is concurrently processing the action on the maintenance plan and the adequacy process for the MVEBs contained therein. In this proposed rule, EPA is proposing to find the MVEBs adequate and also proposing to approve the MVEBs as part of the maintenance plan. The MVEBs cannot be used for transportation conformity until the maintenance plan and associated MVEBs are approved in a final 
                    <E T="04">Federal Register</E>
                     notice, or EPA otherwise finds the budgets adequate in a separate action following the comment period. 
                </P>
                <P>
                    If EPA receives adverse written comments with respect to the proposed approval of the Hampton Roads MVEBs, or any other aspect of our proposed approval of this updated maintenance plan, we will respond to the comments on the MVEBs in our final action or proceed with the adequacy process as a separate action. Our action on the Hampton Roads Area MVEBs will also be announced on EPA's conformity Web site: 
                    <E T="03">http://www.epa.gov/otaq/stateresources/transconf/index.htm</E>
                    (once there, click on the “Conformity” button, then look for “Adequacy Review of SIP Submissions”). 
                </P>
                <HD SOURCE="HD1">VIII. Proposed Actions </HD>
                <P>EPA is proposing to determine that the Hampton Roads Area has attained the 8-hour ozone NAAQS. EPA is also proposing to approve the redesignation of the Hampton Roads Area from nonattainment to attainment for the 8-hour ozone NAAQS. EPA has evaluated Virginia's redesignation request and determined that it meets the redesignation criteria set forth in section 107(d)(3)(E) of the CAA. EPA believes that the redesignation request and monitoring data demonstrate that the Hampton Roads Area has attained the 8-hour ozone standard. The final approval of this redesignation request would change the designation of the Hampton Roads Area from nonattainment to attainment for the 8-hour ozone standard. EPA is also proposing to approve the associated maintenance plan for the Hampton Roads Area, submitted on October 18, 2006, as a revision to the Virginia SIP. EPA is proposing to approve the maintenance plan for the Hampton Roads Area because it meets the requirements of section 175A as described previously in this notice. EPA is also proposing to approve the 2002 base-year inventory for the Hampton Roads Area, and the MVEBs submitted by Virginia for the Hampton Roads Area in conjunction with its redesignation request. EPA is soliciting public comments on the issues discussed in this document. These comments will be considered before taking final action. </P>
                <HD SOURCE="HD1">IX. Statutory and Executive Order Reviews </HD>
                <P>
                    Under Executive Order 12866 (58 FR 51735, October 4, 1993), this proposed 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 proposes to approve state law as meeting Federal requirements and imposes no additional requirements beyond those imposed by state law. Accordingly, the Administrator certifies that this proposed 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 proposes to approve 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 (Public Law 104-4). This proposed rule also 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, as specified by Executive Order 13175 (65 FR 67249, November 9, 2000), nor will it 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), because it merely proposes to approve a state rule implementing a Federal requirement, and does not alter the relationship or the distribution of power and responsibilities established in the Clean Air Act. This proposed rule also is not subject to Executive Order 13045 (62 FR 19885, April 23, 1997), because it 
                    <PRTPAGE P="18614"/>
                    approves a state rule implementing a Federal standard. 
                </P>
                <P>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. Redesignation is an action that affects the status of a geographical area and does not impose any new requirements on sources. 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. As required by section 3 of Executive Order 12988 (61 FR 4729, February 7, 1996), in issuing this proposed rule, EPA has taken the necessary steps to eliminate drafting errors and ambiguity, minimize potential litigation, and provide a clear legal standard for affected conduct. EPA has complied with Executive Order 12630 (53 FR 8859, March 15, 1988) by examining the takings implications of the rule in accordance with the “Attorney General's Supplemental Guidelines for the Evaluation of Risk and Avoidance of Unanticipated Takings” issued under the executive order. </P>
                <P>
                    This rule, proposing to approve the redesignation of the Hampton Roads Area to attainment for the 8-hour ozone NAAQS, the associated maintenance plan, the 2002 base-year inventory, and the MVEBS identified in the maintenance plan, 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>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects </HD>
                    <CFR>40 CFR Part 52 </CFR>
                    <P>Environmental protection, Air pollution control, Nitrogen dioxide, Ozone, Reporting and recordkeeping requirements, Volatile organic compounds. </P>
                    <CFR>40 CFR Part 81 </CFR>
                    <P>Air pollution control, National parks, Wilderness areas.</P>
                </LSTSUB>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P>
                        42 U.S.C. 7401 
                        <E T="03">et seq.</E>
                    </P>
                </AUTH>
                <SIG>
                    <DATED>Dated: April 5, 2007. </DATED>
                    <NAME>Judith Katz, </NAME>
                    <TITLE>Acting Regional Administrator, Region III.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. E7-7017 Filed 4-12-07; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 6560-50-P </BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF TRANSPORTATION </AGENCY>
                <CFR>49 CFR Part 39 </CFR>
                <DEPDOC>[Docket OST 2007-26829] </DEPDOC>
                <RIN>RIN 2105-AB87 </RIN>
                <SUBJECT>Transportation for Individuals With Disabilities: Passenger Vessels </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Department of Transportation, Office of the Secretary. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Proposed rule; extension of comment period. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Department is extending through June 22, 2007, the period for interested persons to submit comments to its proposed rule to amend its Americans with Disabilities Act regulations concerning passenger vessels. </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">COMMENT CLOSING DATE:</HD>
                    <P>Comments should be submitted by June 22, 2007. Late-filed comments will be considered to the extent practicable. </P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may submit comments identified by the docket number OST 2007-26829 by any of the following methods: </P>
                    <P>
                        • 
                        <E T="03">Web site: http://dms.dot.gov</E>
                        . Follow the instructions for submitting comments on the DOT electronic docket site. 
                    </P>
                    <P>
                        • 
                        <E T="03">Federal e-Rulemaking Portal: http://www.regulations.gov</E>
                        . Follow the instructions for submitting comments. 
                    </P>
                    <P>
                        • 
                        <E T="03">Fax:</E>
                         (202) 493-2251. 
                    </P>
                    <P>
                        • 
                        <E T="03">Mail:</E>
                         Docket Management System; U.S. Department of Transportation, 400 Seventh Street, SW., Nassif Building, Room PL-401, Washington, DC 20590-0001. 
                    </P>
                    <P>
                        • 
                        <E T="03">Hand Delivery:</E>
                         To the Docket Management System; Room PL-401 on the plaza level of the Nassif Building, 400 Seventh Street, SW., Washington, DC, between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays. 
                    </P>
                    <P>
                        <E T="03">Instructions:</E>
                         You must include the agency name and docket number OST-2007-26829 or the Regulatory Identification Number (RIN) for this rulemaking at the beginning of your comment. Note that all comments received will be posted without change to 
                        <E T="03">http://dms.dot.gov</E>
                        , including any personal information provided. 
                    </P>
                    <P>
                        <E T="03">Docket:</E>
                         You may view the public docket through the Internet at 
                        <E T="03">http://dms.dot.gov</E>
                         or in person at the Docket Management System office at the above address. 
                    </P>
                    <P>
                        The Department of Transportation is in the process of moving to a new building. It is anticipated that the Docket Office will move to its new location before the end of the extended comment period. We do not yet have the complete address for the Docket Office in the Department's new building. The Department will publish a 
                        <E T="04">Federal Register</E>
                         notice when this information becomes available. The address change will not affect electronic submissions, and mail submissions will be forwarded to the new address. 
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Robert C. Ashby, Deputy Assistant General Counsel for Regulation and Enforcement, Department of Transportation, 400 7th Street, SW., Room 10424, Washington, DC 20590-0001. (202) 366-9306 (voice); (202) 755-7687 (TDD); bob.ashby@dot.gov (e-mail). </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>On January 23, 2007, the Department of Transportation issued a notice of proposed rulemaking (NPRM) (72 FR 2833) to amend its Americans with Disabilities Act (ADA) rules to add requirements concerning passenger vessels. The comment period for this NPRM was scheduled to end on April 23, 2007. A 90-day comment period is commonly provided for significant proposed rules. </P>
                <P>On January 31, 2007, the Cruise Lines International Association (CLIA) requested a 120-day extension of the comment period. CLIA cited as reasons for its request the need for potential commenters to consider the questions the Department asked in the preamble to the NPRM and the relationship between the NPRM and ongoing work of the Access Board concerning accessibility guidelines for passenger vessels. </P>
                <P>The Department believes that some extension of the comment period can be justified and that the Department can extend the comment period for a reasonable time without unduly delaying work toward a final rule. However, we do not believe that a 120-day extension, which would more the double the length of the original comment period, is necessary to allow interested persons to provide informed comments to the Department, and we are concerned that such a lengthy extension could create unnecessary delay. </P>
                <P>Consequently, the Department will extend the comment period for 60 days, through June 22, 2007. The Department does not anticipate the need for any further extensions. Given the additional time provided for comments, we urge interested persons to make every effort to provide detailed information concerning the issues they raise. </P>
                <SIG>
                    <PRTPAGE P="18615"/>
                    <DATED>Issued this 4th day of April, 2007, at Washington, DC. </DATED>
                    <NAME>Rosalind A. Knapp, </NAME>
                    <TITLE>Acting General Counsel.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. E7-6941 Filed 4-12-07; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4910-9X-P </BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION </AGENCY>
                <SUBAGY>Federal Motor Carrier Safety Administration </SUBAGY>
                <CFR>49 CFR Parts 385, 386, 390, 392, 393, 396, and Appendix G to Subchapter B of Chapter III </CFR>
                <DEPDOC>[Docket No. FMCSA-2005-23315] </DEPDOC>
                <RIN>RIN 2126-AA86 </RIN>
                <SUBJECT>Requirements for Intermodal Equipment Providers and Motor Carriers and Drivers Operating Intermodal Equipment; Reopening of Comment Period </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Motor Carrier Safety Administration (FMCSA), DOT. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of public listening sessions; reopening of comment period. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Federal Motor Carrier Safety Administration (FMCSA) is reopening until May 21, 2007, the comment period on its December 21, 2006 notice of proposed rulemaking (NPRM) concerning inspection, repair and maintenance responsibilities for intermodal equipment providers and motor carriers operating container chassis. The FMCSA is also announcing a series of public listening sessions to obtain additional feedback on the Agency's NPRM from motor carriers, representatives of the intermodal transportation industry, and interested parties. The listening sessions are intended to provide all interested parties an opportunity to respond to the issues associated with this rulemaking. All oral comments will be transcribed and placed in the public docket identified at the beginning of this notice. </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Your comments must be submitted to the docket on or before May 21, 2007. </P>
                    <P>
                        <E T="03">Dates for the public listening sessions:</E>
                         April 27, 2007, from 10 a.m. to 4:30 p.m., in Norfolk, VA; May 3, 2007, from 9:30 a,m. to 4:30 p.m., in Port Newark, NJ; and May 18, 2007, from 9:30 a.m. to 4:30 p.m., in Long Beach, CA. 
                    </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        The April 27, 2007 meeting will be held at the 
                        <E T="03">Kirn Memorial Library, 301 East City Hall Avenue, Norfolk, Virginia.</E>
                         The May 3, 2007 meeting will be held at 
                        <E T="03">The Seamen's Church Institute, SCI's Seafarers' Center, 118 Export Street, Port Newark, New Jersey</E>
                        . The May 18, 2007 meeting will be held at the 
                        <E T="03">Holiday Inn Long Beach Airport, 2640 Lakewood Boulevard, Long Beach, California</E>
                        . 
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Ms Deborah M. Freund, Senior Transportation Specialist, Vehicle and Roadside Operations Division, FMCSA, 400 Seventh Street, SW., Washington, DC 20590. Telephone (202) 366-4009 or e-mail 
                        <E T="03">deborah.freund@dot.gov</E>
                        . Office hours are from 8 a.m. to 4:30 p.m., e.t., Monday through Friday, except Federal holidays. 
                    </P>
                    <P>
                        If you wish to make a formal presentation, please contact Ms. Deborah Freund no later than 5 p.m., e.t., 2 business days before the date of the session you will attend. 
                        <E T="03">Information on Services for Individuals with Disabilities:</E>
                         For information on facilities or services for individuals with disabilities or to request special assistance at the meeting, please e-mail or telephone Deborah Freund. To request special assistance for one or more of the Listening Sessions, contact Ms. Freund no later than 5 business days before the date of the session. 
                    </P>
                    <P>You may also submit comments to the DOT Docket Management System (DMS), referencing Docket Number FMCSA-2005-23315, using any of the following methods: </P>
                    <P>
                        • 
                        <E T="03">Web Site: http://dms.dot.gov</E>
                        . Follow the instructions for submitting comments on the DOT electronic docket site. 
                    </P>
                    <P>
                        • 
                        <E T="03">Fax:</E>
                         1-202-493-2251. Mail: Docket Management Facility; U.S. Department of Transportation, 400 Seventh Street, SW., Nassif Building, Room PL-401, Washington, DC 20590-0001. 
                    </P>
                    <P>
                        • 
                        <E T="03">Hand Delivery:</E>
                         Room PL-401 on the plaza level of the Nassif Building, 400 Seventh Street, SW., Washington, DC, between 9 a.m. and 5 p.m., e.t., Monday through Friday, except Federal holidays. 
                    </P>
                    <P>
                        • 
                        <E T="03">Federal eRulemaking Portal:</E>
                         Go to 
                        <E T="03">http://www.regulations.gov.</E>
                         Follow the online instructions for submitting comments. 
                    </P>
                    <P>
                        <E T="03">Instructions:</E>
                         All submissions must include the Agency name and docket number or Regulatory Identification Number (RIN 2126-AA86) for this rulemaking. Note that all comments received will be posted without change to 
                        <E T="03">http://dms.dot.gov</E>
                         including any personal information provided. For additional information on submitting comments, see the Supplemental Information section of this document. 
                    </P>
                    <P>
                        <E T="03">Docket:</E>
                         For access to the docket to read background documents or comments received, go to 
                        <E T="03">http://dms.dot.gov</E>
                         at any time or to Room PL-401 on the plaza level of the Nassif Building, 400 Seventh Street, SW., Washington, DC, between 9 a.m. and 5 p.m., e.t., Monday through Friday, except Federal holidays. 
                    </P>
                    <P>
                        <E T="03">Privacy Act:</E>
                         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 comment (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-78) or you may visit 
                        <E T="03">http://dms.dot.gov</E>
                        .
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Background </HD>
                <P>On December 21, 2006 (71 FR 76796), FMCSA published an NPRM to amend the Federal Motor Carrier Safety Regulations (FMCSRs) to address the safety of intermodal equipment (IME) used by motor carriers for transportation of intermodal containers in interstate commerce. As mandated by section 4118 of the Safe, Accountable, Flexible, Efficient Transportation Equity Act: A Legacy for Users (SAFETEA-LU), this rulemaking would require intermodal equipment providers (IEPs) to register and file with FMCSA an Intermodal Equipment Provider Identification Report (Form MCS 150C); display the USDOT Number, or other unique identifier, on each intermodal container chassis offered for transportation in interstate commerce; establish a systematic inspection, repair, and maintenance program to ensure the safe operating condition of each intermodal container chassis; maintain documentation of the program; and provide a means to effectively respond to driver and motor carrier reports about intermodal container chassis mechanical defects and deficiencies. </P>
                <P>
                    The proposed regulations would for the first time make IEPs subject to the Federal Motor Carrier Safety Regulations (FMCSRs). The agency is also proposing additional inspection requirements for motor carriers and drivers operating intermodal equipment. The intent of this rulemaking is to ensure that intermodal equipment used to transport intermodal containers is safe and systematically maintained. Improved maintenance is expected to result in fewer out-of-service orders and highway breakdowns involving intermodal chassis and improved efficiency of the Nation's intermodal transportation system. To whatever extent inadequately maintained intermodal chassis are responsible for, 
                    <PRTPAGE P="18616"/>
                    or contribute to, crashes, this proposal would also help to ensure that commercial motor vehicle (CMV) operations are safer. 
                </P>
                <HD SOURCE="HD1">Purpose of the Listening Session </HD>
                <P>The FMCSA is committed to providing all interested parties an opportunity to discuss their perspectives on the pertinent issues that could affect any potential rulemaking changes. The Agency has received numerous comments in response to its NPRM but believes additional information could be obtained through these listening sessions. </P>
                <P>Participants at the listening sessions will be given the opportunity to submit questions that they would like to hear discussed by others in attendance. FMCSA encourages persons who have prepared statements to submit them to the public docket rather than use time at a listening session to read them aloud. Persons who wish to submit written comments or statements should submit the information to the public docket identified in this notice. Those who desire notification of receipt of their comments must include a self-addressed, stamped envelope or postcard. Comments made during the meeting will be transcribed to preserve an accurate record of the discussion. </P>
                <SIG>
                    <DATED>Issued on: April 10, 2007. </DATED>
                    <NAME>Larry W. Minor, </NAME>
                    <TITLE>Acting Associate Administrator, Policy and Program Development. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 07-1865 Filed 4-11-07; 12:48 pm] </FRDOC>
            <BILCOD>BILLING CODE 4910-EX-P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>National Oceanic and Atmospheric Administration</SUBAGY>
                <CFR>50 CFR Parts 223 and 224</CFR>
                <DEPDOC>[Docket No. 070402074-7074-01; I.D. No. 032207B]</DEPDOC>
                <SUBJECT>Endangered and Threatened Wildlife and Plants: 90-Day Finding for a Petition to List Black Abalone as Threatened or Endangered under the Endangered Species Act</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; petition finding; request for information.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        We, the NMFS, have received a petition to list the black abalone (
                        <E T="03">Haliotis cracherodii</E>
                        ) as a threatened or endangered species and to designate critical habitat under the Endangered Species Act (ESA). We find that the petition presents substantial scientific information indicating that the petitioned action may be warranted. This finding normally initiates a formal status review, but as described below in the Background section (see 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                        ), in this case, we had already initiated a formal status review on October 17, 2006. To ensure that the review is comprehensive, we are soliciting information pertaining to this species, any potential critical habitat, and recommendations of qualified individuals to peer review the agency's black abalone status review report.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Information and comments on this action must be received by June 12, 2007.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may submit information and/or comments by any of the following methods:</P>
                    <P>
                        • E-Mail: 
                        <E T="03">BlackAbalone.Comments@noaa.gov</E>
                    </P>
                    <P>• Mail: Submit written comments to Chief, Protected Resources Division, Southwest Region, National Marine Fisheries Service, 501 West Ocean Blvd., Suite 4200, Long Beach, CA, 90802-4213.</P>
                    <P>
                        • Federal eRulemaking Portal: 
                        <E T="03">http://www.regulations.gov</E>
                        . Follow the instructions for submitting comments.
                    </P>
                    <P>
                        An electronic version of the petition can be obtained via the Internet at: 
                        <E T="03">http://www.nmfs.noaa.gov</E>
                         or by submitting a request to the Assistant Regional Administrator, Protected Resources Division, Southwest Region, NMFS, 501 West Ocean Blvd., Suite 4200, Long Beach, CA 90802-4213.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Melissa Neuman, NMFS, Southwest Region (562) 980-4115 or Lisa Manning, NMFS, Office of Protected Resources (301) 713-1401.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Background</HD>
                <P>
                    Black abalone was added to NMFS' Candidate Species list on June 23, 1999 (64 FR 33466), transferred to NMFS' Species of Concern list on April 15, 2004 (69 FR 19975), and has since been considered for listing on the List of Endangered and Threatened Species under the ESA. The species is currently listed on the International Union for the Conservation of Nature and Natural Resources (IUCN) Red List of Threatened Species (Smith 
                    <E T="03">et al.</E>
                     2003). We initiated an informal ESA status review of black abalone on July 15, 2003, and conducted biological scoping workshops on January 29-30, 2004 and July 31-August 1, 2006. We formally announced initiation of a black abalone status review on October 17, 2006 (71 FR 61021), and at that time solicited information from the public on the following topics: (1) long-term trends in abundance throughout the species' range; (2) potential factors for the species' decline throughout its range (e.g., overharvesting, natural predation, disease, habitat loss etc.); (3) status of the black abalone fishery in Mexico; (4) implication of low population size for black abalone conservation; (5) factors important for black abalone management; (6) current estimate of population size and available habitat; (7) knowledge of various life history parameters (size/age at maturity, fecundity, length of larval stage, larval dispersal dynamics, etc.); and (8) projections on population growth or decline and risk of extinction. On December 27, 2006, we received a petition from the Center for Biological Diversity (CBD) requesting that we list black abalone as either an endangered or threatened species under the ESA and designate critical habitat for the species concurrently with any listing determination.
                </P>
                <P>
                    Section 4(b)(3)(A) of the ESA (16 U.S.C. 1531 
                    <E T="03">et seq.</E>
                    ) requires that we make a finding as to whether a petition to list, delist, or reclassify a species presents substantial scientific or commercial information to indicate that the petitioned action may be warranted. Our joint NMFS/U.S. Fish and Wildlife Service ESA implementing regulations (50 CFR 424.14) define “substantial information” as the amount of information that would lead a reasonable person to believe that the measure proposed in the petition may be warranted. In determining whether substantial information exists for a petition to list a species, we consider several factors, including information submitted with and referenced in the petition and all other information readily available in our files. To the maximum extent practicable, this finding is to be made within 90 days of the receipt of the petition, and the finding is to be published promptly in the 
                    <E T="04">Federal Register</E>
                    . If we find that a petition presents substantial information indicating that the requested action may be warranted, section 4(b)(3)(B) of the ESA requires the Secretary of Commerce (Secretary) to conduct a status review of the species and make a finding as to whether the petitioned action is warranted within 1 year of the receipt of the petition.
                    <PRTPAGE P="18617"/>
                </P>
                <HD SOURCE="HD1">Analysis of Petition</HD>
                <HD SOURCE="HD2">Natural History</HD>
                <P>
                    Black abalone is a marine mollusc and a member of the family 
                    <E T="03">Haliotidae</E>
                     and the genus 
                    <E T="03">Haliotis.</E>
                     There is some debate regarding the historic range of black abalone. Based on museum specimen records examined by Geiger (1999), black abalone ranged historically from Crescent City (Del Norte County, California) to Cabo San Lucas (Southern Baja California). Most experts agree that the current range of black abalone extends from Point Arena (Mendocino County, California) to Northern Baja California, but are rare north of San Francisco (Morris 
                    <E T="03">et al.</E>
                    , 1980) and south of Punta Eugenia (P. Raimondi, pers. comm.). Of the seven species of abalone found in California (Geiger, 1999), black abalone is a relatively shallow water species and is most abundant in rocky intertidal habitat (Morris 
                    <E T="03">et al.</E>
                    , 1980), although they do occur from the high intertidal zone to 6 m depth. Average black abalone shell length is approximately 115 mm (Ault, 1985), however, maximum shell length may exceed 200 mm (Morris 
                    <E T="03">et al.</E>
                    , 1980). The epipodium (the circular fringe of skin around the foot) and tentacles are black and the underside of the foot is pearly white. The outer surface of the shell is dark blue to black, smooth and has 5-9 open respiratory pores with edges that are flush with the shell surface (Haaker 
                    <E T="03">et al.</E>
                    , 1986).
                </P>
                <P>
                    The vacillatory nature of rocky intertidal habitat dictates that black abalone tolerate a wide range of environmental conditions (e.g. temperature, salinity, dessication, and wave action). For example, water temperatures may range between 7-24 °C (45-75 °F) (Howorth, 1978) in rocky intertidal areas throughout their range. In the absence of anthropogenic influences (e.g., harvest and spread of disease (Friedman and Finley, 2003)), a combination of black abalone life history, ecology, and behavior and these widely ranging environmental variables is what controls the species' spatial distribution. Black abalone are often found in a clumped distribution, with smaller abalone (&lt;90 mm) exhibiting cryptic behavior and tending to stay within the protective confines of crevices, under rocks, and in boulder fields (Blecha 
                    <E T="03">et al.</E>
                    , 1992; Tissot, 1995; Ault, 1985). Individuals larger than 90 mm often occupy more exposed rocks and surge channels in areas where sea otters are absent, but tend to reside in cracks and crevices in areas where sea otters are present (Morris 
                    <E T="03">et al.</E>
                    , 1980; Lowry and Pearse, 1973; Hines and Pearse, 1982; Blecha 
                    <E T="03">et al.</E>
                    , 1992).
                </P>
                <P>
                    Black abalone exhibit separate sexes and are thought to reach sexual maturity between 40-50 mm shell length in California. Sperm or eggs are broadcast into the water sometime between late spring and late summer (Webber and Giese, 1969; CDFG, 2005). This type of spawning strategy depends on densely aggregated adults to achieve the high gamete densities needed for successful fertilization (Davis, 1996). The free-swimming larval phase for this species may range from 5 to 14 days depending on water temperature (Ault, 1985). This relatively short dispersive phase combined with hydrodynamic conditions during the time of spawning may limit dispersal distances. Analysis of the genetic structure of black abalone populations on the central California coast indicates that these black abalone populations are composed predominantly of individuals that were spawned locally (Hamm and Burton, 2000). Patterns in recruitment of juveniles to central coastal populations provide additional evidence that black abalone larvae do not tend to travel very far along the coast and, therefore, populations are relatively closed (Raimondi 
                    <E T="03">et al.</E>
                    , 2002). In Southern California, results of a drift card study at San Nicolas Island suggest that black abalone larvae are locally retained with occasional migrants dispersing over long distances (&gt; 10 km; Chambers 
                    <E T="03">et al.</E>
                    , 2006).
                </P>
                <P>
                    Larval black abalone tend to settle into areas characterized by bare rock and coralline red algae (Douros, 1985; Miner 
                    <E T="03">et al.</E>
                    , 2006). Once settled onto rocky substrata, black abalone juveniles consume rock-encrusting coralline algae and diatom and bacterial films (Haaker 
                    <E T="03">et al.</E>
                    , 1986). Adult black abalone feed primarily on pieces of algae drifting with the surge or current, such as giant kelp, bull kelp, and feather boa kelp (Haaker 
                    <E T="03">et al.</E>
                    , 1986). Growth rates can vary depending on food availability, water temperature, and other environmental factors (CDFG, 2005). Abalone are long-lived (30+ years) and it takes approximately 20 years for black abalone to reach their maximum length (Blecha 
                    <E T="03">et al.</E>
                    , 1992). Black abalone are preyed upon by a wide variety of marine predators including sea stars, fishes, octopus, the southern sea otter, and striped shore crab.
                </P>
                <HD SOURCE="HD2">Abundance</HD>
                <P>
                    Historically, sea otter predation and hunting by Native Americans were two primary sources of mortality for large black abalone. The elimination or relocation of Native American coastal settlements during the 1700s and 1800s and sea otter (a primary predator on black abalone) hunting by Russian fur traders resulted in high densities (&lt; 40 individuals per m
                    <SU>2</SU>
                    ) of black abalone in many places throughout their range (Howorth, 1978; Douros, 1993; Richards and Davis, 1993). Chinese immigrants began harvesting abalone from dense intertidal beds in central and southern California and Baja California in the mid-1800s and annual harvest reached a peak of 1,814 metric tons (mt) in 1879 (Howorth, 1978; Rogers-Bennett 
                    <E T="03">et al.</E>
                    , 2002). Commercial harvest was banned in the early 1900s, during which time black abalone populations expanded slightly. However, in 1968 commercial harvest of black abalone resumed. The commercial harvest was greatest around the islands off southern California, particularly San Miguel, San Clemente and San Nicolas Islands (California Department of Fish and Game (CDFG), unpublished data). The average annual harvest declined from 290 mt in the 1970s, with a peak occurring in 1973 (868 mt; Rogers-Bennett 
                    <E T="03">et al.</E>
                    , 2002), to 175 mt in the 1980s, to 14 mt in the 1990s. By the mid-1980s overharvesting, as evidenced by declining trends in fishery-dependent data and eventual closure of the commercial fishery (B. Tissot, unpublished data), and possibly other factors such as pollution (Miller and Lawrenze-Miller, 1993), reduced southern California coastal populations of black abalone considerably. Remnant populations persisted primarily on offshore islands and inaccessible sections of the coast north of Santa Barbara. Commercial harvesting was prohibited again in 1993.
                </P>
                <P>
                    In the mid- and late-1980s, black abalone on the Channel Islands suffered massive local die-offs (generally &gt;90 percent losses) from a disease known as Withering Syndrome (WS) (Haaker 
                    <E T="03">et al.</E>
                    , 1992; Richards and Davis, 1993; Lafferty and Kuris, 1993). The cause of WS is unknown, but has been attributed to a Rickettsiales-like pathogen (Friedman 
                    <E T="03">et al.</E>
                    , 2000). The disease is manifested by severe weight loss, loss of appetite, followed by detachment from the substrate and eventual mortality (Tissot, 1991; Haaker 
                    <E T="03">et al.</E>
                    , 1992; Steinbeck 
                    <E T="03">et al.</E>
                    , 1992). There is also strong evidence that the intensity of mortality from this disease increases with increasing water temperature (Tissot, 1995; Steinbeck 
                    <E T="03">et al.</E>
                    , 1992; Alstatt 
                    <E T="03">et al.</E>
                    , 1996; Raimondi 
                    <E T="03">et al.</E>
                    , 2002). Prior to 1992, the only mainland site where a WS-related die-off had been observed was in Diablo Cove, the site of the discharge for the Diablo Canyon Power Plant (Steinbeck 
                    <E T="03">et al.</E>
                    , 1992). However, in 1992 a massive die-off 
                    <PRTPAGE P="18618"/>
                    began at a mainland site, Government Point, near Point Conception (Alstatt 
                    <E T="03">et al.</E>
                    , 1996). Subsequent monitoring of sites along the central California coast has detected a pattern of mortality suggesting that WS is progressing northward up the coast, but at a variable rate (Altstatt 
                    <E T="03">et al.</E>
                    , 1996; Raimondi 
                    <E T="03">et al.</E>
                    , 2002; Miner 
                    <E T="03">et al.</E>
                    , 2006).
                </P>
                <P>Fishery-independent data obtained from long-term monitoring studies (1975-present) were examined to detect trends in abundance from 32 sampling locations throughout California (B. Tissot, unpublished data). Percent changes in abundance were calculated by comparing mean densities prior to the onset of WS and after the onset of WS at each sampling location. Preliminary results suggest that black abalone have gone locally extinct or declined between 90-99 percent at 50 percent of the sampling locations and have declined between 80-89 percent at another 16 percent of the sampling locations. Thus, significant declines (&gt;80 percent) have occurred at over 50 percent of the locations sampled in California (Brian Tissot, unpublished data).</P>
                <P>Although abundance data for black abalone populations in Mexico are scant, existing fishery-dependent data suggest declines similar to those exhibited in California. Based on the data published in Hobday and Tegner (2000), the catch of black abalone declined from a high of 28 mt in 1990, to &lt;1 mt in 1998, an overall decline of &gt;95 percent.</P>
                <HD SOURCE="HD1">Summation</HD>
                <P>
                    The principal cause of black abalone population decline in southern and central California has been attributed to over-harvesting (Karpov 
                    <E T="03">et al.</E>
                    , 2000) and/or the onset of WS in southern California in the 1980s (Lafferty and Kuris, 1993) and the disease's northward progression. Black abalone populations have declined by over 99 percent (Brian Tissot, unpublished data) in southern California (except for San Nicolas and San Miguel Islands). In many locations recruitment rates are low, and in areas where remnant healthy populations are producing recruits, these recruits are retained locally and are not recolonizing historically populated areas only tens of kilometers away (Miller and Lawrenze-Miller, 1993; Raimondi 
                    <E T="03">et al.</E>
                    , 2002; Miner 
                    <E T="03">et al.</E>
                    , 2006). Miner 
                    <E T="03">et al.</E>
                     (2006) hypothesize that the causes of low (or no) recruitment at sites with low adult density include: (1) local adult densities too low for successful fertilization; (2) limited dispersal ability of larval abalone limiting the supply of larvae from healthy adjacent populations; (3) suitable larval settlement habitat overgrown in the absence of adult abalone; and (4) newly recruited juvenile abalone killed by WS before they can be observed and counted by researchers.
                </P>
                <HD SOURCE="HD1">Petition Finding</HD>
                <P>Given documented declines in abundance within the range of the species and the potential negative effects of ongoing and future threats posed primarily by the northward spread of WS, as described in the petition and in the information in our files, we have determined that the petition presents substantial information and that listing black abalone under the ESA may be warranted. We have supported efforts to learn more about the factors that have contributed to the decline of this species and encouraged Federal agencies and other appropriate parties to conserve and protect surviving black abalone throughout its range from Fort Bragg, California to southern Baja California. Despite these efforts, including closure of the fishery in southern California in 1993, the species continues to decline along the mainland coast of southern California and the northern Channel Islands. In compliance with section 4(b)(3)(B) of the ESA, the Secretary will make his determination whether the petitioned action is warranted within 12 months from the date the petition was received (December 27, 2006) following completion of an ESA status review.</P>
                <HD SOURCE="HD1">Listing Factors and Basis for Determination</HD>
                <P>Section 4(a)(1) of the ESA requires the Secretary to determine whether any species is a threatened or an endangered species because of any of the following factors: (1) The present or threatened destruction, modification, or curtailment of its habitat or range; (2) overutilization for commercial, recreational, scientific, or educational purposes; (3) disease or predation; (4) inadequacy of existing regulatory mechanisms; or (5) other natural or manmade factors affecting its continuing existence. Listing determinations are based solely on the best available scientific and commercial data after taking into account any efforts being made by any state or foreign nation to protect the species.</P>
                <HD SOURCE="HD1">Information Solicited</HD>
                <P>To ensure that the black abalone status review is complete and is based on the best available scientific and commercial data, we reiterate our previous solicitation for information on this species. We specifically request the following information: (1) long-term trends in abundance throughout the species' range; (2) potential factors for the species' decline throughout its range (e.g., overharvesting, natural predation, disease, habitat loss etc.); (3) historic and current range, distribution and habitat use of this species; (4) status of the black abalone populations in Baja California, Mexico; (5) historic and current estimates of population size and available habitat; (6) knowledge of various life history parameters (size/age at maturity, fecundity, length of larval stage, larval dispersal dynamics, etc.); (7) projections on population growth or decline and risk of extinction; and (8) efforts being made to protect black abalone throughout their range.</P>
                <HD SOURCE="HD1">Critical Habitat</HD>
                <P>We are also requesting information on areas that may qualify as critical habitat for black abalone, such as identification of areas that include the physical and biological features essential to the conservation of the species. Essential features include, but are not limited to: (1) space for individual and population growth and for normal behavior; (2) food, water, air, light, minerals, or other nutritional or physiological requirements; (3) cover or shelter; (4) sites for reproduction and development of offspring; and (5) habitats that are protected from disturbance or are representative of the historical, geographical and ecological distributions of the species (50 CFR 424.12). For areas potentially qualifying as critical habitat, we request information describing: (1) the activities that affect the areas or could be affected by the designation, and (2) the economic or other costs and benefits of additional management measures likely to result from a designation.</P>
                <HD SOURCE="HD1">Peer Review</HD>
                <P>
                    The joint NMFS/U.S. Fish and Wildlife Service peer review policy for review of scientific data was published on July 1, 1994 (59 FR 34270), and on January 14, 2005, the Office of Management and Budget (OMB) published its Final Information Quality Bulletin for Peer Review (70 FR 2664). The purpose of the peer review policy and the OMB Information Quality Bulletin is to ensure that listings are based on the best scientific and commercial data available. We are soliciting the names of recognized experts in the field that could take part in the peer review process for this status review. Independent peer reviewers will be selected from the academic and scientific community, Federal and state 
                    <PRTPAGE P="18619"/>
                    agencies, the private sector, and public interest groups.
                </P>
                <HD SOURCE="HD1">References</HD>
                <P>
                    A complete list of all references cited herein is available upon request (see 
                    <E T="02">ADDRESSES</E>
                     section).
                </P>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P>
                        16 U.S.C. 1531 
                        <E T="03">et seq.</E>
                    </P>
                </AUTH>
                <SIG>
                    <DATED>Dated: April 6, 2007.</DATED>
                    <NAME>William T. Hogarth,</NAME>
                    <TITLE>Assistant Administrator for Fisheries, National Marine Fisheries Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. E7-6966 Filed 4-12-07; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3510-22-S</BILCOD>
        </PRORULE>
    </PRORULES>
    <VOL>72</VOL>
    <NO>71</NO>
    <DATE>Friday, April 13, 2007</DATE>
    <UNITNAME>Notices</UNITNAME>
    <NOTICES>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="18620"/>
                <AGENCY TYPE="F">DEPARTMENT OF AGRICULTURE </AGENCY>
                <SUBAGY>Agricultural Marketing Service </SUBAGY>
                <DEPDOC>[Doc. No. TB-07-01] </DEPDOC>
                <SUBJECT>Request for an Extension of and Revision to a Currently Approved Information Collection </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Agricultural Marketing Service, USDA. </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 (44 U.S.C. Chapter 35), this notice announces the Agricultural Marketing Service's (AMS) intention to request approval from the Office of Management and Budget, for an extension of and revision to the currently approved information collection in support of the Fair and Equitable Tobacco Reform Act of 2004 (U.S.C. Chapter 518), the Rural Development, Food and Drug Administrative, and Related Agencies Appropriations Act for 2002 (Appropriations Act), and the Tobacco Inspection Act and Regulations Governing the Tobacco Standards. </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments received by June 12, 2007 will be considered. </P>
                    <P>
                        <E T="03">Additional Information Or Comments:</E>
                         Interested persons are invited to submit written comments concerning this proposal to Kenneth E. Wall, Chief, Standardization and Review Branch, Tobacco Programs, Agricultural Marketing Service, U.S. Department of Agriculture, 1306 Annapolis Drive, Raleigh, North Carolina 27608. Comments should be submitted in triplicate. Comments may also be submitted electronically through 
                        <E T="03">www.regulations.gov</E>
                        . All comments should reference the docket number and page number of this issue of the 
                        <E T="04">Federal Register</E>
                        . 
                    </P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Kenneth E. Wall, Chief, Standardization and Review Branch, Tobacco Programs, Agricultural Marketing Service, USDA, 1306 Annapolis Drive, Raleigh, North Carolina 27608, telephone (919) 856-4552 ext. 30 and facsimile (919) 856-4208, or e-mail at 
                        <E T="03">Kenneth.Wall@usda.gov</E>
                        . 
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P SOURCE="NPAR">
                    <E T="03">Title:</E>
                     Reporting and Recording Requirements for 7 CFR Part 29. 
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     0581-0056. 
                </P>
                <P>
                    <E T="03">Expiration Date of Approval:</E>
                     September 30, 2007. 
                </P>
                <P>
                    <E T="03">Type of Request:</E>
                     Extension and revision of a currently approved information collection. 
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     The Tobacco Inspection Act (7 U.S.C. 511 
                    <E T="03">et seq.</E>
                    ) requires that all tobacco sold at designated auction markets in the U.S. be inspected and graded. The Appropriations Act (7 U.S.C. 511s note) requires that all tobacco eligible for price support in the U.S. be inspected and graded. The Fair and Equitable Tobacco Reform Act of 2004 (7 U.S.C. 518) eliminated price supports and marketing quotas for all tobacco beginning with the 2005 crop year. Mandatory inspection and grading of domestic and imported tobacco was eliminated as well as the mandatory pesticide testing of imported tobacco and the tobacco market news program. The Tobacco Inspection Act also provides for interested parties to request inspection, pesticide testing and grading services on a permissive basis. 
                </P>
                <P>The information collection requirements authorized for the programs under the Tobacco Inspection Act and the Appropriations Act include: application for inspection of tobacco, application and other information used in the approval of new auction markets or the extension of services to designated tobacco markets, and the information required to be provided in connection with auction and non-auction sales. </P>
                <P>
                    <E T="03">Estimate of Burden:</E>
                     Public reporting burden for this collection of information is estimated to average 1.60 hours per response. 
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Primarily tobacco companies, tobacco manufacturers, import inspectors, and small businesses or organizations. 
                </P>
                <P>
                    <E T="03">Estimated Number of Respondents:</E>
                     50 
                </P>
                <P>
                    <E T="03">Estimated Number of Responses per Respondent:</E>
                     48 
                </P>
                <P>
                    <E T="03">Estimated Number of Responses:</E>
                     2415 
                </P>
                <P>
                    <E T="03">Estimated Total Annual Burden on Respondents:</E>
                     3851 
                </P>
                <P>
                    <E T="03">Comments are invited on:</E>
                     (1) 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; (2) 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; (3) ways to enhance the quality, utility, and clarity of the information to be collected; and (4) ways 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 technological collection techniques or other forms of information technology. Comments may be sent to Kenneth E. Wall, Chief, Standardization and Review Branch, Tobacco Programs, Agricultural Marketing Service, U.S. Department of Agriculture, 1306 Annapolis Drive, Raleigh, North Carolina 27608. All comments received will be available for public inspection during regular business hours at the same address. 
                </P>
                <P>All responses to this notice will be summarized and included in the request for OMB approval. All comments will become a matter of public record. </P>
                <SIG>
                    <DATED>Dated: April 9, 2007. </DATED>
                    <NAME>Lloyd C. Day, </NAME>
                    <TITLE>Administrator, Agricultural Marketing Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. E7-7039 Filed 4-12-07; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 3410-02-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF AGRICULTURE </AGENCY>
                <SUBAGY>Animal and Plant Health Inspection Service </SUBAGY>
                <DEPDOC>[Docket No. APHIS-2007-0036] </DEPDOC>
                <SUBJECT>Notice of Request for Extension of Approval of an Information Collection; Communicable Diseases in Horses </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 
                        <PRTPAGE P="18621"/>
                        information collection associated with regulations for the interstate movement of horses that have tested positive for equine infectious anemia. 
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>We will consider all comments that we receive on or before June 12, 2007. </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may submit comments by either of the following methods: </P>
                    <P>
                        • Federal eRulemaking Portal: Go to 
                        <E T="03">http://www.regulations.gov</E>
                        , select “Animal and Plant Health Inspection Service” from the agency drop-down menu, then click “Submit.” In the Docket ID column, select APHIS-2007-0036 to submit or view public comments and to view supporting and related materials available electronically. Information on using Regulations.gov, including instructions for accessing documents, submitting comments, and viewing the docket after the close of the comment period, is available through the site's “User Tips” link. 
                    </P>
                    <P>• Postal Mail/Commercial Delivery: Please send four copies of your comment (an original and three copies) to Docket No. APHIS-2007-0036, Regulatory Analysis and Development, PPD, APHIS, Station 3A-03.8, 4700 River Road Unit 118, Riverdale, MD 20737-1238. Please state that your comment refers to Docket No. APHIS-2007-0036. </P>
                    <P>
                        <E T="03">Reading Room:</E>
                         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>
                        <E T="03">Other Information:</E>
                         Additional information about APHIS and its programs is available on the Internet at 
                        <E T="03">http://www.aphis.usda.gov</E>
                        . 
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>For information on an information collection associated with regulations for the interstate movement of equine that have tested positive for equine infectious anemia, contact Dr. Tim Cordes, Senior Staff Veterinarian, Aquaculture, Swine, Equine, and Poultry Programs, NCAHP, VS, APHIS, 4700 River Road Unit 46, Riverdale, MD 20737; (301) 734-3279. 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>
                     Communicable Diseases in Horses. 
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     0579-0127. 
                </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 Animal Health Protection Act (7 U.S.C. 8301 
                    <E T="03">et seq.</E>
                    ), the Animal and Plant Health Inspection Service (APHIS) of the U.S. Department of Agriculture regulates the importation and interstate movement of animals and animal products, and conducts various other activities to protect the health of our Nation's livestock and poultry. 
                </P>
                <P>Equine infectious anemia (EIA) is an infectious and potentially fatal viral disease of equines. There is no vaccine or treatment for the disease. It is often difficult to differentiate from other fever-producing diseases, including anthrax, influenza, and equine encephalitis. </P>
                <P>The regulations in 9 CFR 75.4 govern the interstate movement of equines that have tested positive to an official test for EIA (EIA reactors) and provide for the approval of laboratories, diagnostic facilities, and research facilities. The regulations require the use of an official EIA test, a certificate for the interstate movement of an EIA reactor, and proper identification of the reactor, as well as recordkeeping by accredited and State veterinarians; laboratory, diagnostic, and research facility personnel; and stockyard personnel. </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 this information collection activity. These comments will help us: </P>
                <P>(1) Evaluate whether the information collection is necessary for the proper performance of our agency's functions, 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 collection of information 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.0882261 hours per response. 
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Accredited and State veterinarians; laboratory, diagnostic, and research facility personnel; stockyard personnel; and owners and shippers of horses. 
                </P>
                <P>
                    <E T="03">Estimated annual number of respondents:</E>
                     10,302. 
                </P>
                <P>
                    <E T="03">Estimated annual number of responses per respondent:</E>
                     191.8076. 
                </P>
                <P>
                    <E T="03">Estimated annual number of responses:</E>
                     1,976,002. 
                </P>
                <P>
                    <E T="03">Estimated total annual burden on respondents:</E>
                     174,335 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 9th day of April 2007. </DATED>
                    <NAME>Kevin Shea, </NAME>
                    <TITLE>Acting Administrator, Animal and Plant Health Inspection Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC> [FR Doc. E7-7042 Filed 4-12-07; 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. APHIS-2006-0181] </DEPDOC>
                <SUBJECT>Notice of Request for Extension of Approval of an Information Collection; Commercial Transportation of Equines for Slaughter </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 associated with regulations for the commercial transportation of equines to slaughtering facilities. </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>We will consider all comments that we receive on or before June 12, 2007. </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may submit comments by either of the following methods: </P>
                    <P>
                        • Federal eRulemaking Portal: Go to 
                        <E T="03">http://www.regulations.gov</E>
                        , select “Animal and Plant Health Inspection Service” from the agency drop-down menu, then click “Submit.” In the 
                        <PRTPAGE P="18622"/>
                        Docket ID column, select APHIS-2006-0181 to submit or view public comments and to view supporting and related materials available electronically. Information on using Regulations.gov, including instructions for accessing documents, submitting comments, and viewing the docket after the close of the comment period, is available through the site's “User Tips” link. 
                    </P>
                    <P>Postal Mail/Commercial Delivery: Please send four copies of your comment (an original and three copies) to Docket No. APHIS-2006-0181, Regulatory Analysis and Development, PPD, APHIS, Station 3A-03.8, 4700 River Road Unit 118, Riverdale, MD 20737-1238. Please state that your comment refers to Docket No. APHIS-2006-0181. </P>
                    <P>
                        <E T="03">Reading Room:</E>
                         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>
                        <E T="03">Other Information:</E>
                         Additional information about APHIS and its programs is available on the Internet at h
                        <E T="03">ttp://www.aphis.usda.gov</E>
                        . 
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>For information regarding an information collection associated with regulations for the commercial transportation of equines to slaughtering facilities, contact Dr. Tim Cordes, Senior Staff Veterinarian, Aquaculture, Swine, Equine, and Poultry Programs, NCAHP, VS, APHIS, 4700 River Road Unit 46, Riverdale, MD 20737; (301) 734-3279. 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>
                     Commercial Transportation of Equines for Slaughter. 
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     0579-0160. 
                </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 Federal Agriculture Improvement and Reform Act of 1996 (“the Farm Bill”), Congress gave responsibility to the Secretary of Agriculture to regulate the commercial transportation within the United States of equines for slaughter. Sections 901-905 of the Farm Bill (7 U.S.C. 1901 note) authorized the Secretary to issue guidelines for the regulation of commercial transportation of equines for slaughter by persons regularly engaged in that activity within the United States. As a result of that authority, the Animal and Plant Health Inspection Service, U.S. Department of Agriculture, established regulations in 9 CFR part 88, “Commercial Transportation of Equines for Slaughter.” 
                </P>
                <P>The minimum standards cover, among other things, the food, water, and rest provided to such equines. The regulations require the owner/shipper of the equines to take certain actions in loading and transporting the equines and to certify that the commercial transportation meets certain requirements. Our regulations prohibit the commercial transportation to slaughter facilities of equines considered to be unfit for travel, the use of electric prods on such animals in commercial transportation to slaughter, and the use of double-deck trailers for commercial transportation of equines to slaughtering facilities. </P>
                <P>These regulations require the use of two information collection activities: (1) The preparation of an owner-shipper certificate for each equine transported to slaughter and (2) the collection of business information from any individual or other entity found to be transporting horses to a slaughtering facility. </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.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.0523661 hours per response. 
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Owners and shippers of slaughter horses. 
                </P>
                <P>
                    <E T="03">Estimated annual number of respondents :</E>
                     200. 
                </P>
                <P>
                    <E T="03">Estimated annual number of responses per respondent:</E>
                     401.5. 
                </P>
                <P>
                    <E T="03">Estimated annual number of responses:</E>
                     80,300. 
                </P>
                <P>
                    <E T="03">Estimated total annual burden on respondents: 4,205 hours.</E>
                     (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 9th day of April 2007. </DATED>
                    <NAME>Kevin Shea, </NAME>
                    <TITLE>Acting Administrator, Animal and Plant Health Inspection Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. E7-7044 Filed 4-12-07; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 3410-34-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF AGRICULTURE </AGENCY>
                <SUBAGY>Farm Service Agency </SUBAGY>
                <SUBJECT>Notice of Availability of the Draft Programmatic Environmental Assessment for the 2005 Hurricane Tree Assistance Program </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Farm Service Agency, USDA. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This notice announces the availability of the Draft Programmatic Environmental Assessment (PEA) for the implementation of the 2005 Hurricane Tree Assistance Program (TAP), authorized by the Emergency Agricultural Disaster Assistance Act. The draft PEA assesses the potential environmental impacts of alternatives to be considered in the administration of this hurricane program. The draft PEA also provides a means for the public to voice any concerns they may have about the program, and any ideas for improving it. This Notice of Availability informs the public of the availability of the applicable draft PEA and solicits public comment. </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>FSA invites comments on the draft PEA. Comments should be submitted by close of business on April 30, 2007, to ensure consideration. Comments submitted after this date will be considered to the extent possible. </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Comments on and requests for copies of the draft PEA should be submitted to Matthew T. Ponish, National Environmental Compliance 
                        <PRTPAGE P="18623"/>
                        Manager, United States Department of Agriculture, Farm Service Agency, 1400 Independence Ave., SW., Mail Stop 0513, Washington DC 20250-0513, or by e-mail at 
                        <E T="03">Matthew.Ponish@wdc.usda.gov</E>
                        . The Draft PEA can be reviewed online at 
                        <E T="03">http://www.fsa.usda.gov/FSA/webapp?area=home&amp;subject=ecrc&amp;topic=nep-cd</E>
                        . 
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Matthew Ponish, USDA/FSA/CEPD/Stop 0513, 1400 Independence Ave., SW., Washington, DC 20250-0513, (202) 720-6853, or e-mail at: 
                        <E T="03">Matthew.Ponish@wdc.usda.gov</E>
                        . Persons with disabilities who require alternative means for communication (Braille, large print, audio tape, etc.) should contact the USDA Target Center at (202) 720-2600 (voice and TDD). 
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The Farm Service Agency announces the availability of the draft Programmatic Environmental Assessment (PEA) for the 2005 Hurricane TAP, authorized by the Emergency Agricultural Disaster Assistance Act (Pub. L. 109-234, section 3021), the goal of which is to reimburse eligible producers of eligible tree crops for certain costs associated with reestablishing crops lost because of the hurricanes of 2005. TAP will be implemented in counties declared disasters as a result of the 2005 hurricanes in the following states: Arkansas, Alabama, Florida, Louisiana, North Carolina, Mississippi, South Carolina, Tennessee, and Texas. In consideration of the analysis documented in the PEA, the program would not constitute a major State or Federal action that would significantly affect the human environment. Therefore, an Environmental Impact Statement will not be prepared. </P>
                <P>
                    The regulations promulgating the 2005 Hurricane TAP were published in the 
                    <E T="04">Federal Register</E>
                     on February 12, 2007 (72 FR 6435), along with the provision that no benefit shall be paid under the program until FSA has completed the PEA and issued a decision document. The draft PEA assesses the potential environmental impacts of alternatives to be considered in the administration of the 2005 TAP. The draft PEA also provides a means for the public to voice any concerns they may have about the program and any ideas for improving it. This Notice of Availability informs the public of the availability of the draft PEA and solicits public comment. 
                </P>
                <SIG>
                    <DATED>Signed in Washington DC on April 4, 2007.</DATED>
                    <NAME>Thomas B. Hofeller, </NAME>
                    <TITLE>Acting Administrator, Farm Service Agency.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. E7-6993 Filed 4-12-07; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 3410-05-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF AGRICULTURE</AGENCY>
                <SUBAGY>Forest Service</SUBAGY>
                <SUBJECT>Newspapers To Be Used for Publication of Legal Notice of Appealable Decisions and Publication of Notice of Proposed Actions for Southern Region; Alabama, Kentucky, Georgia, Tennessee, Florida, Louisiana, Mississippi, Virginia, West Virginia, Arkansas, Oklahoma, North Carolina, South Carolina, Texas, Puerto Rico</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Forest Service, USDA.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        Deciding Officers in the Southern Region will publish notice of decisions subject to administrative appeal under 36 CFR parts 215 and 217 in the legal notice section of the newspapers listed in the 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                         section of this notice. As provided in 36 CFR part 215.5 and 36 CFR part 217.5(d), the public shall be advised through 
                        <E T="04">Federal Register</E>
                         notice, of the newspaper of record to be utilized for publishing legal notice of decisions. Newspaper publication of notice of decisions is in addition to direct notice of decisions to those who have requested it and to those who have participated in project planning. Responsible Officials in the Southern Region will also publish notice of proposed actions under 36 CFR part 215 in the newspapers that are listed in the 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                         section of this notice. As provided in 36 CFR part 215.5, the public shall be advised, through 
                        <E T="04">Federal Register</E>
                         notice, of the newspaper of record to be utilized for publishing notices on proposed actions. Additionally, the Deciding Officers in the Southern Region will publish notice of the opportunity to object to a proposed authorized hazardous fuel reduction project under 36 CFR part 218.4 in the legal notice section of the newspapers listed in the 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                         section of this notice.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Use of these newspapers for purposes of publishing legal notice of decisions subject to appeal under 36 CFR parts 215 and 217, notices of proposed actions under 36 CFR part 215, and notices of the opportunity to object under 36 CFR  part 218 shall begin on or after the date of this publication.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>James W. Bennett, Regional Appeal Review Team Manager, Southern Region, Planning, 1720 Peachtree Road, NW., Atlanta, Georgia 30309, Phone: 404/347-2788.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>Deciding Officers in the Southern Region will give legal notice of decisions subject to appel under 36 CFR part 217, the Responsible Officials in the Southern Region will give notice of decisions subject to appeal under 36 CFR part 215 and opportunity to object to a proposed authorized hazardous fuel reduction project under 36 CFR part 218 in the following newspapers which are listed by Forest Service administrative unit. Responsible Officials in the Southern Region will also give notice of proposed actions under 36 CFR part 215 in the following newspapers of record which are listed by Forest Service administrative unit. The timeframe for comment on a proposed action shall be based on the date of publication of the notice of the proposed action in the newspaper of record. The timeframe for appeal shall be based on the date of publication of the legal notice of the decision in the newspaper of record for 36 CFR  parts 215 and 217. The timeframe for an objection shall be based on the date of publication of the legal notice of the opportunity to object for projects subject to 36 CFR part 218.</P>
                <P>Where more than one newspaper is listed for any unit, the first newspaper listed is the newspaper of record that will be utilized for publishing the legal notice of decisions and calculating timeframes. Secondary newspapers listed for a particular unit are those newspapers the Deciding Officer/Responsible Official expects to use for purposes of providing additional notice.</P>
                <P>The following newspapers will be used to provide notice.</P>
                <HD SOURCE="HD1">Southern Region</HD>
                <HD SOURCE="HD2">Regional Forester Decisions</HD>
                <P>
                    Affecting National Forest System lands in more than one Administrative unit of the 15 in the Southern Region, 
                    <E T="03">Atlanta Journal-Constitution</E>
                    , publishing daily in Atlanta, GA.
                </P>
                <P>Affecting National Forest System lands in only one Administrative unit or only one Ranger District will appear in the newspaper of record elected by the National Forest, National Grassland, National Recreation Area, or Ranger District as listed below.</P>
                <HD SOURCE="HD3">National Forests in Alabama</HD>
                <HD SOURCE="HD3">Forest Supervisor Decisions</HD>
                <P>
                    Affecting National Forest System lands in more than one Ranger District 
                    <PRTPAGE P="18624"/>
                    of the 6 in the National Forests in Alabama, 
                    <E T="03">Montgomery Advertiser</E>
                    , published daily in Montgomery, AL. Affecting National Forest System lands in only one Ranger District will appear in the newspaper of record elected by the Ranger District as listed below.
                </P>
                <HD SOURCE="HD3">District Ranger Decisions</HD>
                <FP SOURCE="FP-1">
                    Bankhead Ranger District: 
                    <E T="03">Northwest Alabamian</E>
                    , published bi-weekly (Wednesday &amp; Saturday) in Haleyville, AL.
                </FP>
                <FP SOURCE="FP-1">
                    Conecuh Ranger District: 
                    <E T="03">The Andalusia Star News</E>
                    , published daily (Tuesday through Saturday) in Andalusia, AL.
                </FP>
                <FP SOURCE="FP-1">
                    Oakmulgee Ranger District, 
                    <E T="03">The Tuscaloosa News</E>
                    , published daily in Tuscaloosa, AL.
                </FP>
                <FP SOURCE="FP-1">
                    Shoal Creek Ranger District: 
                    <E T="03">The Anniston Star</E>
                    , published daily in Anniston, AL.
                </FP>
                <FP SOURCE="FP-1">
                    Talladega Ranger District: 
                    <E T="03">The Daily Home</E>
                    , published daily in Talladega, AL.
                </FP>
                <FP SOURCE="FP-1">
                    Tuskegee Ranger District: 
                    <E T="03">Tuskegee News</E>
                    , published weekly (Thursday) in Tuskegee, AL.
                </FP>
                <HD SOURCE="HD3">Carribean National Forest, Puerto Rico</HD>
                <HD SOURCE="HD3">Forest Supervisor Decisions</HD>
                <FP SOURCE="FP-1">
                    <E T="03">El Nuevo Dia</E>
                    , published daily in Spanish in San Juan, PR.
                </FP>
                <FP SOURCE="FP-1">
                    <E T="03">San Juan Star</E>
                    , published daily in English in San Juan, PR.
                </FP>
                <HD SOURCE="HD2">Chattahoochee-Oconee National Forest, Georgia</HD>
                <HD SOURCE="HD3">Forest Supervisor Decisions</HD>
                <FP SOURCE="FP-1">
                    <E T="03">The Times</E>
                    , published daily in Gainesville, GA.
                </FP>
                <HD SOURCE="HD3">District Ranger Decisions</HD>
                <FP SOURCE="FP-1">
                    Armuchee-Cohutta Ranger District: 
                    <E T="03">Daily Citizen</E>
                    , published daily in Dalton, GA.
                </FP>
                <FP SOURCE="FP-1">
                    Brasstown Ranger District: 
                    <E T="03">North Georgia News,</E>
                     (newspaper of record) published weekly (Wednesday) in Blairsville, GA.
                </FP>
                <FP SOURCE="FP-1">
                    <E T="03">Towns County Herald,</E>
                     (secondary) published weekly (Thursday) in Hiawassee, GA.
                </FP>
                <FP SOURCE="FP-1">
                    <E T="03">The Dahlonega Nuggett,</E>
                     (secondary) published weekly (Wednesday) in Dahlonega, GA.
                </FP>
                <FP SOURCE="FP-1">
                    Chattooga Ranger District: 
                    <E T="03">Northeast Georgian,</E>
                     (newspaper of record) published bi-weekly (Tuesday &amp; Friday) in Cornelia, GA.
                </FP>
                <FP SOURCE="FP-1">
                    <E T="03">Chieftain &amp; Toccoa Record,</E>
                     (secondary) published bi-weekly (Tuesday &amp; Friday) in Toccoa, GA.
                </FP>
                <FP SOURCE="FP-1">
                    <E T="03">White County News Telegraph,</E>
                     (secondary) published weekly (Thursday) in Cleveland, GA.
                </FP>
                <FP SOURCE="FP-1">
                    <E T="03">The Dahlonega Nuggett,</E>
                     (secondary) published weekly (Thursday) in Dahlonega, GA.
                </FP>
                <FP SOURCE="FP-1">
                    Oconee Ranger District: 
                    <E T="03">Eatonton Messenger,</E>
                     published weekly (Thursday) in Eatonton, GA.
                </FP>
                <FP SOURCE="FP-1">
                    Tallulah Ranger District: 
                    <E T="03">Clayton Tribune,</E>
                     published weekly (Thursday) in Clayton, GA.
                </FP>
                <FP SOURCE="FP-1">
                    Toccoa Ranger District: 
                    <E T="03">The News Observer</E>
                     (newspaper of record) published bi-weekly (Tuesday &amp; Friday) in Blue Ridge, GA.
                </FP>
                <FP SOURCE="FP-1">
                    <E T="03">The Dahlonega Nuggett,</E>
                     (secondary) published weekly (Wednesday) in Dahlonega, GA.
                </FP>
                <HD SOURCE="HD3">Cherokee National Forest, Tennessee</HD>
                <HD SOURCE="HD3">Forest Supervisor Decisions</HD>
                <FP SOURCE="FP-1">
                    <E T="03">Knoxville News Sentinel,</E>
                     published daily in Knoxville, TN.
                </FP>
                <HD SOURCE="HD3">District Ranger Decisions</HD>
                <FP SOURCE="FP-1">
                    Nolichuchy-Unaka Ranger District: 
                    <E T="03">Greeneville Sun,</E>
                     published daily (except Sunday) in Greeneville, TN.
                </FP>
                <FP SOURCE="FP-1">
                    Ocoee-Hiwassee Ranger District: 
                    <E T="03">Polk County News,</E>
                     published weekly (Wednesday) in Benton, TN.
                </FP>
                <FP SOURCE="FP-1">
                    Tellico Ranger District: 
                    <E T="03">Monroe County Advocate &amp; Democrat,</E>
                     published tri-weekly (Wednesday, Friday, and Sunday) in Sweetwater, TN.
                </FP>
                <FP SOURCE="FP-1">
                    Watauga Ranger District: 
                    <E T="03">Johnson City Press,</E>
                     published daily in Johnson City, TN.
                </FP>
                <HD SOURCE="HD3">Daniel Boone National Forest, Kentucky</HD>
                <HD SOURCE="HD3">Forest Supervisor Decisions</HD>
                <FP SOURCE="FP-1">
                    <E T="03">Lexington Herald-Leader,</E>
                     published daily in Lexington, KY.
                </FP>
                <HD SOURCE="HD3">District Ranger Decisions</HD>
                <FP SOURCE="FP-1">
                    Cumberland Ranger District: 
                    <E T="03">Lexington Herald-Leader,</E>
                     published daily in Lexington, KY.
                </FP>
                <FP SOURCE="FP-1">
                    London Ranger District: 
                    <E T="03">The Sentinel-Echo,</E>
                     published tri-weekly (Monday, Wednesday, and Friday) in London, KY.
                </FP>
                <FP SOURCE="FP-1">
                    Redbird Ranger District: 
                    <E T="03">Manchester Enterprise,</E>
                     published weekly (Thursday) in Manchester, KY.
                </FP>
                <FP SOURCE="FP-1">
                    Stearns Ranger District: 
                    <E T="03">McCreary County Record,</E>
                     published weekly (Tuesday) in Whitley City, KY.
                </FP>
                <HD SOURCE="HD3">National Forests in Florida, Florida</HD>
                <HD SOURCE="HD3">Forest Supervisor Decisions</HD>
                <FP SOURCE="FP-1">
                    <E T="03">The Tallahassee Democrat,</E>
                     published daily in Tallahassee, FL.
                </FP>
                <HD SOURCE="HD3">District Ranger Decisions</HD>
                <FP SOURCE="FP-1">
                    Apalachicola Ranger District: 
                    <E T="03">Calhoun-Liberty Journal,</E>
                     published weekly (Wednesday) in Bristol, FL.
                </FP>
                <FP SOURCE="FP-1">
                    Lake George Ranger District: 
                    <E T="03">The Ocala Star Banner,</E>
                     published daily in Ocala, FL.
                </FP>
                <FP SOURCE="FP-1">
                    Osceola Ranger District: 
                    <E T="03">The Lake City Reporter</E>
                    , published daily (Monday-Saturday) in Lake City, FL.
                </FP>
                <FP SOURCE="FP-1">
                    Seminole Ranger District: 
                    <E T="03">The Daily Commercial,</E>
                     published in Leesburg, FL.
                </FP>
                <FP SOURCE="FP-1">
                    Wakulla Ranger District: 
                    <E T="03">The Tallahassee Democrat,</E>
                     published daily in Tallahassee, FL.
                </FP>
                <HD SOURCE="HD3">Francis Marion &amp; Sumter National Forests, South Carolina</HD>
                <HD SOURCE="HD3">Forest Supervisor Decisions</HD>
                <FP SOURCE="FP-1">
                    <E T="03">The State,</E>
                     published daily in Columbia, SC.
                </FP>
                <HD SOURCE="HD3">District Ranger Decisions</HD>
                <FP SOURCE="FP-1">
                    Andrew Pickens Ranger District: 
                    <E T="03">The Daily Journal,</E>
                     published daily (Tuesday through Saturday) in Seneca, SC.
                </FP>
                <FP SOURCE="FP-1">
                    Enoree Ranger District: 
                    <E T="03">Newberry Observer,</E>
                     published tri-weekly (Monday, Wednesday, and Friday) in Newberry, SC.
                </FP>
                <FP SOURCE="FP-1">
                    Long Cane Ranger District: 
                    <E T="03">The State</E>
                    , published daily in Columbia, SC.
                </FP>
                <FP SOURCE="FP-1">
                    Wambaw Ranger District: 
                    <E T="03">Post and Courier,</E>
                     published daily in Charleston, SC.
                </FP>
                <FP SOURCE="FP-1">
                    Witherbee Ranger District: 
                    <E T="03">Post and Courier,</E>
                     published daily in Charleston, SC.
                </FP>
                <HD SOURCE="HD3">George Washington and Jefferson National Forests, Virginia and West Virginia</HD>
                <HD SOURCE="HD3">Forest Supervisor Decisions</HD>
                <FP SOURCE="FP-1">
                    <E T="03">Roanoke Times,</E>
                     published daily in Roanoke, VA.
                </FP>
                <HD SOURCE="HD3">District Ranger Decisions</HD>
                <FP SOURCE="FP-1">
                    Clinch Ranger District: 
                    <E T="03">Coalfield Progress,</E>
                     published bi-weekly (Tuesday and Thursday) in Norton, VA.
                </FP>
                <FP SOURCE="FP-1">
                    North River Ranger District: 
                    <E T="03">Daily News Record,</E>
                     published daily (except Sunday) in Harrisonburg, VA.
                </FP>
                <FP SOURCE="FP-1">
                    Glenwood-Pedlar Ranger District: 
                    <E T="03">Roanoke Times,</E>
                     published daily in Roanoke, VA.
                </FP>
                <FP SOURCE="FP-1">
                    James River Ranger District: 
                    <E T="03">Virginian Review,</E>
                     published daily (except Sunday) in Covington, VA.
                </FP>
                <FP SOURCE="FP-1">
                    Lee Ranger District: 
                    <E T="03">Shenandoah Valley Herald,</E>
                     published weekly (Wednesday) in Woodstock, VA.
                </FP>
                <FP SOURCE="FP-1">
                    Mount Rogers National Recreation Area: 
                    <E T="03">Bristol Herald Courier,</E>
                     published daily in Bristol, VA.
                </FP>
                <FP SOURCE="FP-1">
                    Eastern Divide Ranger District: 
                    <E T="03">Roanoke Times,</E>
                     published daily in Roanoke, VA.
                </FP>
                <FP SOURCE="FP-1">
                    Warm Springs Ranger District: 
                    <E T="03">The Recorder,</E>
                     published weekly (Thursday) in Monterey, VA.
                </FP>
                <HD SOURCE="HD3">Kisatchie National Forest, Louisiana</HD>
                <HD SOURCE="HD3">Forest Supervisor Decisions</HD>
                <FP SOURCE="FP-1">
                    <E T="03">The Town Talk,</E>
                     published daily in Alexandria, LA.
                    <PRTPAGE P="18625"/>
                </FP>
                <HD SOURCE="HD3">District Ranger Decisions</HD>
                <FP SOURCE="FP-1">
                    Calcasieu Ranger District: 
                    <E T="03">The Town Talk,</E>
                     (newspaper of record) published daily in Alexandria, LA.
                </FP>
                <FP SOURCE="FP-1">
                    <E T="03">The Leesville Ledger,</E>
                     (secondary) published tri-weekly (Tuesday, Friday, and Sunday) in Leesville, LA.
                </FP>
                <FP SOURCE="FP-1">
                    Caney Ranger District: 
                    <E T="03">Minden Press Hearld,</E>
                     (newspaper of record) published daily in Minden, LA.
                </FP>
                <FP SOURCE="FP-1">
                    <E T="03">Homer Guardian Journal,</E>
                     (secondary) published weekly (Wednesday) in Homer, LA.
                </FP>
                <FP SOURCE="FP-1">
                    Catahoula Ranger District: 
                    <E T="03">The Town Talk,</E>
                     published daily in Alexandria, LA.
                </FP>
                <FP SOURCE="FP-1">
                    Kisatchie Ranger District; 
                    <E T="03">Natchitoches Times,</E>
                     published daily (Tuesday thru Friday and on Sunday) in Natchitoches, LA.
                </FP>
                <FP SOURCE="FP-1">
                    Winn Ranger District: 
                    <E T="03">Winn Parish Enterprise,</E>
                     published weekly (Wednesday) in Winnfield, LA.
                </FP>
                <HD SOURCE="HD3">Land Between the Lakes National Recreation Area, Kentucky and Tennessee</HD>
                <HD SOURCE="HD3">Area Supervisor Decisions</HD>
                <FP SOURCE="FP-1">
                    <E T="03">The Paducah Sun,</E>
                     published daily in Paducah, KY.
                </FP>
                <HD SOURCE="HD3">National Forests in Mississippi, Mississippi</HD>
                <HD SOURCE="HD3">Forest Supervisor Decisions</HD>
                <FP SOURCE="FP-1">
                    <E T="03">Clarion-Ledger,</E>
                     published daily in Jackson, MS.
                </FP>
                <HD SOURCE="HD3">District Ranger Decisions</HD>
                <FP SOURCE="FP-1">
                    Bienville Ranger District: 
                    <E T="03">Clarion-Ledger,</E>
                     published daily in Jackson, MS.
                </FP>
                <FP SOURCE="FP-1">
                    Chickasawhay Ranger District: 
                    <E T="03">Clarion-Ledger</E>
                    , published daily in Jackson, MS.
                </FP>
                <FP SOURCE="FP-1">
                    Delta Ranger District: 
                    <E T="03">Clarion-Ledger</E>
                    , published daily in Jackson, MS.
                </FP>
                <FP SOURCE="FP-1">
                    De Sota Ranger District: 
                    <E T="03">Clarion-Ledger</E>
                    , published daily in Jackson, MS.
                </FP>
                <FP SOURCE="FP-1">
                    Holly Springs Ranger District: 
                    <E T="03">Clarion-Ledger</E>
                    , published daily in Jackson, MS.
                </FP>
                <FP SOURCE="FP-1">
                    Homochitto Ranger District: 
                    <E T="03">Clarion-Ledger</E>
                    , published daily in Jackson, MS.
                </FP>
                <FP SOURCE="FP-1">
                    Tombigbee Ranger District: 
                    <E T="03">Clarion-Ledger</E>
                    , published daily in Jackson, MS.
                </FP>
                <HD SOURCE="HD3">National Forests in North Carolina, North Carolina</HD>
                <HD SOURCE="HD3">Forest Supervisor Decisions</HD>
                <FP SOURCE="FP-1">
                    <E T="03">The Asheville Citizen-Times</E>
                    , published daily in Asheville, NC.
                </FP>
                <HD SOURCE="HD3">District Ranger Decisions</HD>
                <FP SOURCE="FP-1">
                    Appalachian Ranger District: 
                    <E T="03">The Asheville Citizen-Times</E>
                    , published daily in Asheville, NC.
                </FP>
                <FP SOURCE="FP-1">
                    Cheoah Ranger District: 
                    <E T="03">Graham Star</E>
                    , published weekly (Thursday) in Robbinsville, NC.
                </FP>
                <FP SOURCE="FP-1">
                    Croatan Ranger District: 
                    <E T="03">The Sun Journal</E>
                    , published daily in New Bern, NC.
                </FP>
                <FP SOURCE="FP-1">
                    Grandfather Ranger District: 
                    <E T="03">McDowell News</E>
                    , published daily in Marion, NC.
                </FP>
                <FP SOURCE="FP-1">
                    Highlands Ranger District: 
                    <E T="03">The Highlander</E>
                    , published weekly (mid May-mid Nov. Tues. &amp; Fri.; mid Nov.-mid May Tues. only) in Highlands, NC.
                </FP>
                <FP SOURCE="FP-1">
                    PisgahRanger District: 
                    <E T="03">The Asheville Citizen-Times</E>
                    , published daily in Asheville, NC.
                </FP>
                <FP SOURCE="FP-1">
                    Tusquitee Ranger District: 
                    <E T="03">Cherokee Scout</E>
                    , published weekly (Wednesday) in Murphy, NC.
                </FP>
                <FP SOURCE="FP-1">
                    Uwharrie Ranger District: 
                    <E T="03">Montgomery Herald</E>
                    , published weekly (Wednesday) in Troy, NC.
                </FP>
                <FP SOURCE="FP-1">
                    Wayah Ranger District: 
                    <E T="03">The Franklin Press</E>
                    , published bi-weekly (Tuesday and Friday) in Franklin, NC.
                </FP>
                <HD SOURCE="HD3">Ouachita National Forest, Arkansas and Oklahoma</HD>
                <HD SOURCE="HD3">Forest Supervisor Decisions</HD>
                <FP SOURCE="FP-1">
                    <E T="03">Arkansas Democrat-Gazette</E>
                    , published in Little Rock, AR.
                </FP>
                <HD SOURCE="HD3">District Ranger Decisions</HD>
                <FP SOURCE="FP-1">
                    Caddo-Womble Ranger District: 
                    <E T="03">Arkansas Democrat-Gazette</E>
                    , published daily in Little Rock, AR.
                </FP>
                <FP SOURCE="FP-1">
                    Jessieville-Winona-Fourche Ranger District: 
                    <E T="03">Arkansas Democrat-Gazette</E>
                    , published daily in Little Rock, AR.
                </FP>
                <FP SOURCE="FP-1">
                    Mena-Oden Ranger District: 
                    <E T="03">Arkansas Democrat-Gazette</E>
                    , published daily in Little Rock, AR.
                </FP>
                <FP SOURCE="FP-1">
                    Oklahoma Ranger District (Choctaw; Kiamichi; and Tiak) 
                    <E T="03">Tulsa World</E>
                    , published in daily in Tulsa, OK.
                </FP>
                <FP SOURCE="FP-1">
                    Poteau-Cold Springs Ranger District: 
                    <E T="03">Arkansas Democrat-Gazette</E>
                    , published daily in Little Rock, AR.
                </FP>
                <HD SOURCE="HD3">Ozark-St. Francis National Forests, Arkansas</HD>
                <HD SOURCE="HD3">Forest Supervisor Decisions</HD>
                <FP SOURCE="FP-1">
                    <E T="03">The Courier</E>
                    , published daily (Tuesday through Sunday) in Russellville, AR.
                </FP>
                <HD SOURCE="HD3">District Ranger Decisions</HD>
                <FP SOURCE="FP-1">
                    Bayou Ranger District: 
                    <E T="03">The Courier</E>
                    , published daily (Tuesday through Sunday) in Russellville, AR.
                </FP>
                <FP SOURCE="FP-1">
                    Boston Mountain Ranger District: 
                    <E T="03">Southwest Times Record</E>
                    , published daily in Fort Smith, AR.
                </FP>
                <FP SOURCE="FP-1">
                    Buffalo Ranger District: 
                    <E T="03">Newton County Times</E>
                    , published weekly in Jasper, AR.
                </FP>
                <FP SOURCE="FP-1">
                    Magazine Ranger District: 
                    <E T="03">Southwest Times Record,</E>
                    , published daily in Fort Smith, AR.
                </FP>
                <FP SOURCE="FP-1">
                    Pleasant Hill Ranger District: 
                    <E T="03">Johnson County Graphic</E>
                    , published weekly (Wednesday) in Clarksville, AR.
                </FP>
                <FP SOURCE="FP-1">
                    St. Francis National Forest: 
                    <E T="03">The Daily World</E>
                    , published daily (Sunday through Friday) in Helena, AR.
                </FP>
                <FP SOURCE="FP-1">
                    Sylamore Ranger District: 
                    <E T="03">Stone County Leader</E>
                    , published weekly (Wednesday) in Mountain View, AR.
                </FP>
                <HD SOURCE="HD3">National Forests and Grasslands in Texas, Texas</HD>
                <HD SOURCE="HD3"> Forest Supervisor Decisions</HD>
                <FP SOURCE="FP-1">
                    <E T="03">The Lufkin Daily News</E>
                    , published daily in Lufkin, TX.
                </FP>
                <HD SOURCE="HD3">District Ranger Decisions</HD>
                <FP SOURCE="FP-1">
                    Angelina National Forest: 
                    <E T="03">The Lufkin Daily News</E>
                    , published daily in Lufkin, TX.
                </FP>
                <FP SOURCE="FP-1">
                    Caddo &amp; LBJ National Grasslands: 
                    <E T="03">Denton Record-Chronicle</E>
                    , published daily in Denton, TX.
                </FP>
                <FP SOURCE="FP-1">
                    Davy Crockett National Forest: 
                    <E T="03">The Lufkin Daily News</E>
                    , published daily in Lufkin, TX.
                </FP>
                <FP SOURCE="FP-1">
                    Sabine National Forest: 
                    <E T="03">The Lufkin Daily News</E>
                    , published daily in Lufkin, TX.
                </FP>
                <FP SOURCE="FP-1">
                    Sam Houston, National Forest: 
                    <E T="03">The Courier</E>
                    , published daily in Conroe, TX.
                </FP>
                <SIG>
                    <DATED>Dated: April 6, 2007.</DATED>
                    <NAME>Thomas A. Peterson,</NAME>
                    <TITLE>Deputy Regional Forester.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 07-1834  Filed 4-12-07; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3410-11-M</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF AGRICULTURE </AGENCY>
                <SUBAGY>Rural Housing Service </SUBAGY>
                <SUBJECT>Notice of Request for Extension of a Currently Approved Information Collection </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Rural Housing Service (RHS), USDA. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Proposed collection; Comments requested. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>In accordance with the Paperwork Reduction Act of 1995, this notice announces the intention of the above-named Agency to request an extension for a currently approved information collection in support of the Community Facilities Grant Program. </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments on this notice must be received by June 12, 2007 to be assured of consideration. </P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Derek L. Jones, Loan Specialist, Community Programs, RHS, USDA, 1400 Independence Ave. SW., Mail Stop 0787, Washington, DC 20250-0787. Telephone: (202) 720-1504. E-mail: 
                        <E T="03">derek.jones@wdc.usda.gov.</E>
                        <PRTPAGE P="18626"/>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P> </P>
                <P>
                    <E T="03">Title:</E>
                     Community Facilities Grant Program. 
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     0575-0173. 
                </P>
                <P>
                    <E T="03">Expiration Date of Approval:</E>
                </P>
                <P>
                    <E T="03">Type of Request:</E>
                     Extension of a currently approved information collection. 
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     Community Programs, a division of the Rural Housing Service (RHS), is part of the United States Department of Agriculture's Rural Development mission area. The Agency is authorized by Section 306(a) of the Consolidated Farm and Rural Development Act (7 U.S.C. 1926), as amended, to make grants to public agencies, nonprofit corporations, and Indian tribes to develop essential community facilities and services for public use in rural areas. These facilities include schools, libraries, child care, hospitals, clinics, assisted-living facilities, fire and rescue stations, police stations, community centers, public buildings, and transportation. Through its Community Programs, the Department of Agriculture is striving to ensure that such facilities are readily available to all rural communities. 
                </P>
                <P>Information will be collected by the field offices from applicants, consultants, lenders, and public entities. The collection of information is considered the minimum necessary to effectively evaluate the overall scope of the project. </P>
                <P>Failure to collect information could have an adverse impact on effectively carrying out the mission, administration, processing, and program requirements. </P>
                <P>
                    <E T="03">Estimate of Burden:</E>
                     Public reporting burden for this collection of information is estimated to average 2.02 hours per response. 
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Public bodies, nonprofit corporations and associations, and federally recognized Indian tribes. 
                </P>
                <P>
                    <E T="03">Estimated Number of Respondents:</E>
                     895. 
                </P>
                <P>
                    <E T="03">Estimated Number of Responses per Respondent:</E>
                     3.17. 
                </P>
                <P>
                    <E T="03">Estimated Number of Responses:</E>
                     2,844. 
                </P>
                <P>
                    <E T="03">Estimated Total Annual Burden on Respondents:</E>
                     5,759 hours. 
                </P>
                <P>Copies of this information collection can be obtained from Renita Bolden, Regulations and Paperwork Management Branch, at (202) 692-0035. 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 will have practical utility; (b) 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; (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 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. Comments may be sent to Renita Bolden, Regulations and Paperwork Management Branch, U.S. Department of Agriculture, Rural Development, STOP 0742, 1400 Independence Ave., SW., Washington, DC 20250-0742. 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>Dated: April 4, 2007. </DATED>
                    <NAME>Russell T. Davis, </NAME>
                    <TITLE>Administrator, Rural Housing Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. E7-7062 Filed 4-12-07; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 3410-XV-P</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 Deletion </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 deletion 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 a product previously furnished by such agencies. </P>
                    <P>
                        <E T="03">Comments Must be Received on or Before:</E>
                         May 13, 2007. 
                    </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, VA 22202-3259. </P>
                    <P>
                        <E T="03">For Further Information or to Submit Comments Contact:</E>
                         Kimberly M. Zeich, Telephone: (703) 603-7740, Fax: (703) 603-0655, or e-mail 
                        <E T="03">CMTEFedReg@jwod.gov.</E>
                    </P>
                </ADD>
            </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 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 products and services to the Government. </P>
                <P>2. If approved, 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>
                <FP>Comments on this certification are invited. Commenters should identify the statement(s) underlying the certification on which they are providing additional information. </FP>
                <HD SOURCE="HD2">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="HD1">Services </HD>
                    <P>
                        <E T="03">Service Type/Location:</E>
                         Catering Service, Seattle Military Entrance Processing Station (MEPS),  4735 E. Marginal Way South,  Seattle, WA. 
                    </P>
                    <P>
                        <E T="03">NPA:</E>
                         Northwest Center, Seattle, WA. 
                    </P>
                    <P>
                        <E T="03">Contracting Activity:</E>
                         ARMY-KNOX, U.S. Army Armor Center and Ft. Knox, Fort Knox, KY. 
                    </P>
                    <P>
                        <E T="03">Service Type/Location:</E>
                         Custodial Services, Juneau SSC, 9341 Glacier Highway, Juneau, AK. 
                    </P>
                    <P>
                        <E T="03">NPA:</E>
                         REACH, Inc., Juneau, AK. 
                    </P>
                    <P>
                        <E T="03">Contracting Activity:</E>
                         Department of Transportation, Federal Aviation Administration-ALASKA, Anchorage, AK. 
                    </P>
                    <P>
                        <E T="03">Service Type/Location:</E>
                         Custodial Services, USDA, Farm Service Agency (Delaware County Office), 557 Sunbury Road, Suite C, Delaware, OH. 
                    </P>
                    <P>
                        <E T="03">NPA:</E>
                         Alpha Group of Delaware, Inc., Delaware, OH. 
                    </P>
                    <P>
                        <E T="03">Contracting Activity:</E>
                         USDA Farm Service Agency Acquisition Management Division, Kansas City, MO. 
                    </P>
                </EXTRACT>
                <PRTPAGE P="18627"/>
                <HD SOURCE="HD1">Deletion </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 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 product is proposed for deletion from the Procurement List: </P>
                <EXTRACT>
                    <HD SOURCE="HD1">Product </HD>
                    <HD SOURCE="HD1">Inkjet Cartridge </HD>
                    <P>
                        <E T="03">NSN:</E>
                         7510-01-544-0834—Use in Canon printers BJC-30/50/55/70/80/85/85W. 
                    </P>
                    <P>
                        <E T="03">NPA:</E>
                         Alabama Industries for the Blind, Talladega, AL. 
                    </P>
                    <P>
                        <E T="03">Contracting Activity:</E>
                         Office Supplies &amp; Paper Products Acquisition Ctr, New York, NY. 
                    </P>
                </EXTRACT>
                <SIG>
                    <NAME>Kimberly M. Zeich, </NAME>
                    <TITLE>Director, Program Operations. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC> [FR Doc. E7-7057 Filed 4-12-07; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 6353-01-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>Economics and Statistics Administration</SUBAGY>
                <SUBJECT>Innovation Measurement</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Economics and Statistics Administration, Department of Commerce.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice and request for comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Department of Commerce is seeking public comment on issues related to the measurement of innovation. This request supports efforts of the Measuring Innovation in the 21st Century Economy Advisory Committee to collect seek advice from the public as it prepares recommendations for the Secretary of Commerce on new or improved measures of business innovation.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        Written comments on this notice must be submitted on or before May 11, 2007. Please note that all comments will be made public and published on the Committee's Web site at: 
                        <E T="03">www.innovationmetrics.gov</E>
                        .
                    </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may submit comments by any of the following methods:</P>
                    <P>
                        E-mail: 
                        <E T="03">innovationmetrics@doc.gov</E>
                        .
                    </P>
                    <P>Fax: (202) 482-2889 (Attn.: Elizabeth “E.R.” Anderson).</P>
                    <P>Mail or Hand Delivery/Courier: Elizabeth “E.R.” Anderson, Room 4836 U.S. Department of Commerce, Economics and Statistics Administration, 14th Street &amp; Pennsylvania Avenue, NW., Washington, DC 20230. Because we continue to experience delays in receiving mail, respondents are encouraged to submit comments by mail early, or to transmit them electronically.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>For questions on the submission of comments, contact Elizabeth “E.R.” Anderson.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The charter establishing the Measuring Innovation in the 21st Century Advisory Committee (the Committee) calls for the Committee to make recommendations to the Secretary of Commerce on ways that will permit better measurement of innovation and its impact on the U.S. economy.</P>
                <P>The Committee is charged with developing innovation metrics that inform policy decisions and enable policymakers and the business community to better monitor innovation. Among other things, the Committee's work should build on the way firms assess the effectiveness of their own innovative activities. The recommendations should not only focus on measuring innovation activities and inputs, but should also focus on the results and output of innovation. Furthermore, the recommendations should allow for analysis at industry, sector, national, and international levels.</P>
                <P>The type of innovation for which measurement improvement is sought is defined as:</P>
                <EXTRACT>
                    <P>The design, invention, development and/or implementation of new or altered products, services, processes, systems, organizational structures, or business models for the purpose of creating new value for customers and financial returns for the firm.”</P>
                </EXTRACT>
                <P>The recommendations will cover the following four major categories identified by the participants during the initial meeting of the Advisory Committee:</P>
                <P>1. Improvement of the underlying architecture of the U.S. System of National Accounts to facilitate development of improved and more granular measures of innovation and productivity;</P>
                <P>2. Identification of appropriate economy-wide and sector-specific statistical series or other indicators that could be used to quantify innovation and/or its impacts;</P>
                <P>3. Identification of firm-specific data items that could enable comparisons and aggregation; and</P>
                <P>4. Identification of specific “holes” in the current data collection system that limit our ability to measure innovation.</P>
                <P>Comments are solicited to address new and/or improved innovation measures in each of the above categories. Following are some specific issues and suggestions raised by Advisory Committee members, grouped according to the measurement categories listed above, on which the Committee specifically invites comment. Comments need not be limited to these issues and suggestions, but should address the specific data categories.</P>
                <P>
                    1. 
                    <E T="03">Improvement of the underlying architecture of the U.S. System of National Accounts to facilitate development of improved and more granular measures of innovation and productivity.</E>
                     Our national accounts are the main source of information about the growth of our national output, usually measured by the gross domestic product or GDP. Total Factor Productivity (TFP) which measures growth of output per unit of input for the economy as a whole and for individual industries is not included in the national accounts. Is the concept of TFP sufficiently related to innovation to warrant the inclusion of economy-wide and industry level TFP in the system of national accounts? If so, what is the most effective way to incorporate the concept into the national accounts? Are there ways to disaggregate the innovation component of TFP to differentiate innovation from other productivity drivers?
                </P>
                <P>
                    2. 
                    <E T="03">Identification of appropriate economy-wide and sector-specific indicators that could be used to quantify innovation and/or its impacts.</E>
                     Are there measures that accommodate economy-wide (or macro-economic) and sector-specific notions of innovation? What elements of innovation could serve as a foundation for statistical series? To what extent would the collection of better data on service sector outputs and services inputs used by all firms improve innovation measurement? Is market share growth a good indicator of innovation? If so, would estimates in the change in U.S. firms' shares of regional, national, and global markets be useful innovation measures? Could/should collaborative connections between entities be captured? Since a characteristic of markets is that the 
                    <PRTPAGE P="18628"/>
                    benefits of innovations flow, at least in part, to buyers, are there ways to identify the flow of innovations across firms and sectors?
                </P>
                <P>
                    3. 
                    <E T="03">Identification of firm-specific data items that could enable comparisons and aggregation.</E>
                     Current corporate innovation measurement appears to be done primarily on either a project or a portfolio basis. Are these measurement practices sufficiently widespread and uniform to make data collection on either of these bases practical? Is it possible or necessary to collect information on company culture, incentive structures, and organizational change? If customer satisfaction is an important measure of an innovative firm, how can that be captured? How important is it to distinguish between types of innovation (
                    <E T="03">i.e.</E>
                     radical versus incremental)?
                </P>
                <P>What data would be needed to differentiate the characteristics of innovative firms within industry sectors from non-innovative firms? What are the most important measures of the underlying process of how innovation and productivity advances are initiated or stimulated? Could/should an understanding of innovation from the consumer perspective be developed?</P>
                <P>Could data items from SEC filings be used to enhance understanding of innovation in public companies? Are there proxies for relative innovative success (e.g. percent of total revenue attributable to new—or significantly improved to the point where they could be considered new—products, services, or processes introduced within the last two years into markets where a firm has a growing market share) that would provide insight into relative innovative strength? Is two years long enough?</P>
                <P>
                    4. 
                    <E T="03">Identification of specific “holes” in the current data collection system that limit our ability to measure innovation.</E>
                     Some specific types of data holes were identified during the meeting, including lack of data on firm formation, intellectual property licensing costs as a type of purchased input, and insufficient product detail. What should be the prioritized list of specific data items needed to fill the holes?
                </P>
                <P>Limitations on our ability to link and coordinate across various data sets were also mentioned as a hole or deficiency of our current data collection system. Are there cost-effective ways of building on existing data sets to develop more information on innovation drivers and their link to success? How could data sharing and cooperation among federal agencies be improved insofar as such agencies maintain data series related to the measurement of innovation? Could existing private and/or foreign data be combined with existing official statistical series in order to better measure innovation? Are there changes that could be made to make such combinations possible or easier?</P>
                <P>To assist the Advisory Committee in evaluating and comparing specific ideas for new or improved innovation measurement, comments on proposals for new or improved innovation measurement should provide the following information:</P>
                <P>1. Description of proposal. Proposals for new or improved innovation measurement should include the following:</P>
                <P>• Specific description of the proposed change.</P>
                <P>• Identification of the specific Committee category to which the proposal applies.</P>
                <P>• Rationale for the proposed change.</P>
                <P>• Data description, sources and method of collection.</P>
                <P>• Approximate cost and burden estimate.</P>
                <P>2. Impact of proposal on innovation measurement. Proposals should include:</P>
                <P>• Description of how proposal improves measurement of innovation as defined by the Advisory Committee.</P>
                <P>• Description of the particular elements of innovation measurement that are improved by the proposal.</P>
                <P>• Description of how the proposal addresses the issues and questions raised by the Committee.</P>
                <P>• Description of how the new or improved measure would provide appropriate signals of changes in business behavior for the purpose of informing policy debates.</P>
                <P>Page Limit—Submissions should be limited to a maximum length of 10 pages. Identification and Cover Sheet—Each page of the submission should be clearly marked with the submitter's name (and organization, if applicable), date of submission, and contact information (if the submitter chooses to provide it). Each submission should be clearly marked as originating from one of the following categories of submitters: Individuals, Businesses, Government, Academia, or Organizations and Associations.</P>
                <P>All comments must be submitted to the address indicated in this notice. The Department requires that all comments be submitted in written form.</P>
                <P>
                    The Department encourages interested persons who wish to comment to do so at the earliest possible time. The period for submission of comments will close on May 11, 2007. The Department will consider all comments received before the close of the comment period. Comments received after the end of the comment period will be considered if possible, but their consideration cannot be assured. The Department will not accept comments accompanied by a request that part or all of the material be treated confidentially because of its business proprietary nature or for any other reason. All comments submitted in response to this notice will be a matter of public record. They will be available for public inspection and copying and posted on the Advisory Committee's Web site at 
                    <E T="03">http://www.innovationmetrics.gov</E>
                    .
                </P>
                <SIG>
                    <DATED>Dated: April 9, 2007.</DATED>
                    <NAME>Elizabeth (E.R.) Anderson,</NAME>
                    <TITLE>Deputy Under Secretary for Economic Affairs.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 07-1827 Filed 4-12-07; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3510-06-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>International Trade Administration</SUBAGY>
                <DEPDOC>(A-533-809)</DEPDOC>
                <SUBJECT>Certain Forged Stainless Steel Flanges from India: Notice of Final Results of New Shipper Review</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Import Administration, International Trade Administration, Department of Commerce.</P>
                </AGY>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        On January 31, 2007, the Department of Commerce (the Department) published the preliminary results of new shipper review of the antidumping duty order on certain forged stainless steel flanges from India. See 
                        <E T="03">Certain Forged Stainless Steel Flanges From India; Preliminary Results of New Shipper Review</E>
                        , 72 FR 4483 (January 31, 2007) (
                        <E T="03">Preliminary Results</E>
                        ). This new shipper review covers Kunj Forgings, Pvt., Ltd. (Kunj), a manufacturer and exporter of the subject merchandise. The period of review is February 1, 2005, through January 31, 2006.
                    </P>
                    <P>We did not receive any comments from parties, and we have not made any changes to our analysis. The final weighted-average dumping margin for Kunj is thus unchanged from our preliminary results of review, and is shown in the section entitled “Final Results of Review.”</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">EFFECTIVE DATE:</HD>
                    <P>April 13, 2007.</P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Fred Baker or Robert James, AD/CVD Operations, Office 7, Import Administration, International Trade Administration, U.S. Department of Commerce, 14th Street &amp; Constitution Avenue, NW., Washington, DC 20230; telephone: (202) 482-2924 or (202) 482-0649, respectively.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <PRTPAGE P="18629"/>
                <HD SOURCE="HD1">Background</HD>
                <P>
                    On January 31, 2007, the Department published in the 
                    <E T="04">Federal Register</E>
                     its preliminary results of new shipper review of forged stainless steel flanges from India for the period February 1, 2005, through January 31, 2006. See 
                    <E T="03">Preliminary Results</E>
                    . No party commented on the preliminary results.
                </P>
                <HD SOURCE="HD1">Scope of the Antidumping Duty Order</HD>
                <P>The products covered by this order are certain forged stainless steel flanges, both finished and not finished, generally manufactured to specification ASTM A-182, and made in alloys such as 304, 304L, 316, and 316L. The scope includes five general types of flanges. They are weld-neck, used for butt-weld line connection; threaded, used for threaded line connections; slip-on and lap joint, used with stub-ends/butt-weld line connections; socket weld, used to fit pipe into a machined recession; and blind, used to seal off a line. The sizes of the flanges within the scope range generally from one to six inches; however, all sizes of the above-described merchandise are included in the scope. Specifically excluded from the scope of this order are cast stainless steel flanges. Cast stainless steel flanges generally are manufactured to specification ASTM A-351. The flanges subject to this order are currently classifiable under subheadings 7307.21.1000 and 7307.21.5000 of the Harmonized Tariff Schedule of the United States (HTSUS). Although the HTSUS subheading is provided for convenience and customs purposes, the written description of the merchandise under review is dispositive of whether or not the merchandise is covered by the scope of the order.</P>
                <HD SOURCE="HD1">Changes Since the Preliminary Results</HD>
                <P>As noted above, no parties commented on the preliminary results. The Department is making no changes to its preliminary analysis.</P>
                <HD SOURCE="HD1">Final Results of Review</HD>
                <P>As a result of our review, we determine that a weighted-average dumping margin of 1.52 percent exists for Kunj for the period February 1, 2005, through January 31, 2006.</P>
                <HD SOURCE="HD1">Assessment Rates</HD>
                <P>The Department will determine, and U.S. Customs and Border Protection (CBP) shall assess, antidumping duties on all appropriate entries, pursuant to section 751(a)(1)(B) of the Tariff Act of 1930 (the Act), and 19 CFR 351.212(b). The Department calculated importer-specific duty assessment rates (or, when the importer was unknown by the respondent, customer-specific duty assessment rates) on the basis of the ratio of the total amount of antidumping duties calculated for the examined sales observations involving each importer (or customer, when appropriate) to the total entered value of the examined sales observations for that importer (or customer, when appropriate). We intend to issue assessment instructions to CBP 15 days after the date of publication of these final results of review.</P>
                <P>
                    The Department clarified its “automatic assessment” regulation on May 6, 2003. This clarification will apply to entries of subject merchandise during the POR produced by companies included in these final results of review for which the reviewed companies did not know the merchandise was destined for the United States. In such instances, we will instruct CBP to liquidate unreviewed entries at the all-others rate if there is no rate for an intermediate company(ies) involved in the transaction. For a discussion of this clarification, see 
                    <E T="03">Notice of Policy Concerning Assessment of Antidumping Duties</E>
                    , 68 FR 23954 (May 6, 2003).
                </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 new shipper review for all shipments of subject merchandise entered, or withdrawn from warehouse, for consumption on or after the publication, as provided by section 751(a)(1) of the Tariff Act: (1) the cash deposit rates for Kunj (
                    <E T="03">i.e.</E>
                    , the subject merchandise both manufactured and exported by Kunj) will be 1.52 percent; (2) the cash deposit rate for exporters who received a rate in a prior segment of the proceeding will continue to be the rate assigned in that segment of the proceeding; (3) the cash deposit rate for entries of subject merchandise exported by Kunj but not manufactured by Kunj will continue to be the “All Others” rate (
                    <E T="03">i.e.</E>
                    , 162.14 percent) or the rate applicable to the manufacturer, if so established; and (4) if neither the exporter nor the manufacturer is a firm covered in this review, or a prior segment of the proceeding, the cash deposit rate will be 162.14 percent, the “all others” rate established in the less-than-fair-value investigation. 
                    <E T="03">See Amended Final Determination and Antidumping Duty Order; Certain Forged Stainless Steel Flanges from India</E>
                    ; 59 FR 5994 (February 9, 1994). These cash deposit requirements shall remain in effect until publication of the final results of the next administrative review. There are no changes to the rates applicable to any other companies under this antidumping duty order.
                </P>
                <HD SOURCE="HD1">Notification of Interested Parties</HD>
                <P>This notice also serves as a final reminder to importers of their responsibility under 19 CFR 351.402(f)(2) 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 in the subsequent assessment of double antidumping duties.</P>
                <P>This notice also is the only reminder to parties subject to administrative protective order (APO) of their responsibility concerning the return or destruction of proprietary information disclosed under APO in accordance with 19 CFR 351.305. Timely written notification of the 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 these results and notice in accordance with sections 751(a)(1) and 777(i) of the Act.</P>
                <SIG>
                    <DATED>Dated: April 9, 2007.</DATED>
                    <NAME>David M. Spooner,</NAME>
                    <TITLE>Assistant Secretary for Import Administration.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. E7-7082 Filed 4-12-07; 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-504</DEPDOC>
                <SUBJECT>Petroleum Wax Candles from the People's Republic of China: Notice of Rescission of Antidumping Duty New Shipper Review</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Import Administration, International Trade Administration, Department of Commerce.</P>
                </AGY>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        On March 28, 2007, the Department of Commerce (“the Department”) published in the 
                        <E T="04">Federal Register</E>
                         a notice announcing the initiation of a new shipper review of the antidumping duty order on petroleum wax candles from the People's Republic of China (“PRC”) for Hangzhou Fashion Living Co., Ltd (“Fashion Living”). 
                        <E T="03">See Petroleum Wax Candles from the People's Republic of China: Initiation of New Shipper Review</E>
                        , 72 FR 14,521 (March 28, 2007) (“
                        <E T="03">Fashion Living Initiation</E>
                        ”). The period of review 
                        <PRTPAGE P="18630"/>
                        (“POR”) is August 1, 2006, to January 31, 2007. This review is now being rescinded because Fashion Living withdrew its request in a timely manner.
                    </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">EFFECTIVE DATE:</HD>
                    <P>April 13, 2007.</P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Nicole Bankhead, AD/CVD Operations, Office 9, Import Administration, U.S. Department of Commerce, 14
                        <SU>th</SU>
                         Street and Constitution Avenue, N.W., Room 4003, Washington, D.C. 20230; telephone: (202) 482-9068.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Background</HD>
                <P>
                    On August 28, 1986, the Department published in the 
                    <E T="04">Federal Register</E>
                     an antidumping duty order covering petroleum wax candles from the PRC. 
                    <E T="03">See Antidumping Duty Order: Petroleum Wax Candles From the People's Republic of China</E>
                    , 51 FR 30686 (August 28, 1986). On February 16, 2007, Fashion Living, requested, in accordance with section 751(a)(2)(B) of the Tariff Act of 1930, as amended (“the Act”), and 19 CFR 351.214(b), that the Department conduct a new shipper review of this antidumping duty order covering the period August 1, 2006, through January 31, 2007.
                </P>
                <P>
                    On March 19, 2007, the Department initiated a new shipper review of Fashion Living. 
                    <E T="03">See Fashion Living Initiation</E>
                    . On March 20, 2007, Fashion Living filed a letter withdrawing its request for a new shipper review.
                </P>
                <HD SOURCE="HD1">Rescission of Review</HD>
                <P>
                    The Department's regulations state that if a party that requested a new shipper review withdraws the request within 60 days of the publication of the notice of initiation of the requested review, the Secretary will rescind the review. 
                    <E T="03">See</E>
                     19 CFR 351.214(f)(1). Fashion Living withdrew its new shipper review request within the 60-day deadline. Accordingly, we are rescinding this new shipper review of the antidumping duty order on petroleum wax candles from the PRC for Fashion Living covering the period August 1, 2006, through January 31, 2007.
                </P>
                <HD SOURCE="HD1">Notification of Interested Parties</HD>
                <P>This notice serves as a final reminder to importers of their responsibility under 19 CFR 351.402(f)(2) 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 the antidumping duties occurred and the subsequent assessment of double antidumping duties.</P>
                <P>This notice also serves as a reminder to parties subject to administrative protective orders (“APOs”) of their responsibility concerning the return or destruction of proprietary information disclosed under APO in accordance with 19 CFR 351.305, which continues to govern business proprietary information in this segment of the proceeding. Timely written notification of the return/destruction of APO materials or conversion to judicial protective order is hereby requested. Failure to comply with the regulations and terms of an APO is a violation that is subject to sanction.</P>
                <P>This notice is issued and published in accordance with sections 751(a)(2)(B) and 777(i) of the Act and 19 CFR 351.214(f)(3).</P>
                <SIG>
                    <DATED>Dated: April 6, 2007.</DATED>
                    <NAME>Stephen J. Claeys,</NAME>
                    <TITLE>Deputy Assistant Secretary for Import Administration.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. E7-7051 Filed 4-12-07; 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-580-844</DEPDOC>
                <SUBJECT>Steel Concrete Reinforcing Bar from The Republic of Korea: Notice of Final Results and Final Partial Rescission of Antidumping Duty Administrative Review</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Import Administration, International Trade Administration, Department of Commerce.</P>
                </AGY>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>On October 10, 2006, the Department of Commerce published the preliminary results of the 2004 - 2005 administrative review of the antidumping duty order on steel concrete reinforcing bars from the Republic of Korea. The period of review (POR) is September 1, 2004, through August 31, 2005.</P>
                    <P>Based on our analysis of the comments received, we have not made changes in the margin calculations for the companies covered by this review. Therefore, the final results do not differ from the preliminary results. The final weighted-average dumping margins for the reviewed firms are listed below in the section entitled “Final Results of Review.”</P>
                    <P>Furthermore, we are rescinding this review with respect to Hanbo Iron &amp; Steel Co., Ltd. (Hanbo), INI Steel (INI) and Kosteel Co., Ltd. (Kosteel), as discussed below in the section entitled “Partial Rescission of Review.”</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">EFFECTIVE DATE:</HD>
                    <P>April 13, 2007.</P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Terre Keaton Stefanova or Katherine Johnson, AD/CVD Operations, Office 2, Import Administration, International Trade Administration, U.S. Department of Commerce, 14th Street and Constitution Avenue, NW, Washington, DC 20230; telephone: (202) 482- 1280 or (202) 482-4929, respectively.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Background</HD>
                <P>
                    The review covers the following producers/exporters of the subject merchandise: Dongkuk Steel Mill Co., Korea Iron and Steel Co., Hwanyoung Steel Industries Co., Ltd. (collectively DSM/KISCO/HSI or “the respondent”),
                    <FTREF/>
                    <SU>1</SU>
                     and Dongil Industries Co., Ltd (Dongil). The period of review is September 1, 2004, through August 31, 2005.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         In the preliminarily results, we determined that DSM, KISCO and HSI were affiliated and collapsed them into a single entity for margin calculation purposes because they met the regulatory criteria for collapsing affiliated producers/exporters. No interested party objected to our preliminary determination to collapse these companies. Therefore, for the final results margin calculation, we have continued to treat these companies as a single entity.
                    </P>
                </FTNT>
                <P>
                    October 10, 2006, the Department of Commerce (the Department) published the preliminary results of the administrative review of the antidumping duty order on steel concrete reinforcing bars from the Republic of Korea. 
                    <E T="03">See Steel Concrete Reinforcing Bar From The Republic of Korea: Notice of Preliminary Results and Preliminary Rescission, in Part, of Antidumping Duty Administrative Review</E>
                    , 71 FR 59440 (October 10, 2006) (Preliminary Results). We invited interested parties to comment on the Preliminary Results.
                </P>
                <P>
                    The petitioners filed a case brief on December 12, 2006.
                    <FTREF/>
                    <SU>2</SU>
                     The respondent filed a rebuttal brief on December 18, 2006. The respondent requested a hearing but subsequently withdrew its request. In lieu of a hearing, the petitioners and respondent requested separate 
                    <E T="03">ex parte</E>
                     meetings to discuss the yield strength model-matching criterion issue raised in their briefs. These 
                    <E T="03">ex parte</E>
                     meetings were held in January and February 2007 (
                    <E T="03">see</E>
                     January 29, 2007, and February 5, 2007, memoranda to the file). We have conducted this administrative review in 
                    <PRTPAGE P="18631"/>
                    accordance with section 751(a) of the Tariff Act of 1930, as amended (the Act).
                </P>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         The petitioners are Nucor Corporation, Commercial Metals Company, and Gerdau Ameristeel Inc., collectively, Rebar Trade Action Coalition.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Scope of the Order</HD>
                <P>
                    The product covered by this order is all rebar sold in straight lengths, currently classifiable in the Harmonized Tariff Schedule of the United States (HTSUS) under item number 7214.20.00 or any other tariff item number. Specifically excluded are plain rounds (
                    <E T="03">i.e.</E>
                    , non-deformed or smooth bars) and rebar that has been further processed through bending or coating. The HTSUS subheading is provided for convenience and customs purposes. The written description of the scope of this order is dispositive.
                </P>
                <HD SOURCE="HD1">Partial Rescission of Review</HD>
                <P>
                    In the Preliminary Results, the Department preliminarily rescinded the review with respect to Hanbo, INI and Kosteel because these companies notified the Department that they had no shipments of subject merchandise during the POR. We confirmed these claims with U.S. Customs and Border Protection (CBP). Pursuant to 19 CFR 351.213(d)(3), the Department may rescind an administrative review, in whole or with respect to a particular exporter or producer, if the Department concludes that, during the period covered by the review, there were no entries, exports, or sales of the subject merchandise. Because we found no evidence of POR entries of subject merchandise from these companies based on our review of entry data from CBP and we did not receive any comments from interested parties on our preliminary rescission decision, we are rescinding this review with respect to these companies. 
                    <E T="03">See</E>
                    , 
                    <E T="03">e.g.</E>
                    , 
                    <E T="03">Steel Concrete Reinforcing Bars From Turkey; Final Results, Rescission of Antidumping Duty Administrative Review in Part, and Determination not to Revoke in Part</E>
                    , 68 FR 53127 (September 9, 2003) (after finding no evidence of entries of subject merchandise from two companies that made “no-shipments” claims, the Department stated that “consistent with our practice, we are rescinding our review for Diler and Ekinciler”).
                </P>
                <HD SOURCE="HD1">Analysis of Comments Received</HD>
                <P>
                    The sole issue raised in the case and rebuttal briefs by parties to this antidumping duty administrative review is addressed in the “Issues and Decision Memorandum” (Decision Memo) from Stephen J. Claeys, Deputy Assistant Secretary for Import Administration, to David M. Spooner, Assistant Secretary for Import Administration, dated April 9, 2007, which is hereby adopted by this notice. The issue which parties have raised and to which we have responded in the Decision Memo pertains to model-matching criteria. Parties can find a complete discussion of the issue 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 Department building. 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/frn</E>
                    . The paper copy and electronic version of the Decision Memo are identical in content.
                </P>
                <HD SOURCE="HD1">Facts Available</HD>
                <P>In the Preliminary Results, pursuant to sections 776(a)(2)(A) and 776(b) of the Act, we based the dumping margin for Dongil on total adverse facts available (AFA) because Dongil failed to respond to the Department's antidumping questionnaire. A complete explanation of the application of AFA and the corroboration of the selected AFA rate can be found in the Preliminary Results, 71 FR at 59441-59443. The Department has neither received any comments from interested parties with regard to its preliminary decision to apply AFA to Dongil, nor obtained any additional information which would lead us to change that decision. Accordingly, for the final results, we continue to apply an AFA rate of 102.28 percent to Dongil.</P>
                <HD SOURCE="HD1">Final Results of Review</HD>
                <P>We determine that the following weighted-average margin percentages exist:</P>
                <GPOTABLE COLS="2" OPTS="L2,i1" CDEF="s50,9">
                    <BOXHD>
                        <CHED H="1">Manufacturer/exporter</CHED>
                        <CHED H="1">Margin (percent)</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Dongkuk Steel Mill Co., Ltd./Korea Iron and Steel Co., Ltd./Hwanyoung Steel Industries Co., Ltd.</ENT>
                        <ENT>0.00</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Dongil Industries Co., Ltd.</ENT>
                        <ENT>102.28</ENT>
                    </ROW>
                </GPOTABLE>
                <HD SOURCE="HD1">Assessment</HD>
                <P>
                    The Department shall determine, and CBP shall assess, antidumping duties on all appropriate entries, in accordance with 19 CFR 351.212(b). The Department will issue assessment instructions directly to CBP 15 days after the date of publication of these final results of review. Pursuant to 19 CFR 351.106(c)(2), we will instruct CBP to assess antidumping duties on all appropriate entries covered by this review if any importer-specific assessment rate calculated in the final results of this review is above 
                    <E T="03">de minimis</E>
                     (
                    <E T="03">i.e.</E>
                    , is not less than 0.50 percent). With respect to DSM/KISCO/HSI, we calculated an importer-specific assessment rate for the subject merchandise by aggregating the dumping margins calculated for all the U.S. sales examined and dividing this amount by the total entered value of the sales examined.
                </P>
                <P>
                    The Department clarified its “automatic assessment” regulation on May 6, 2003. 
                    <E T="03">See Antidumping and Countervailing Duty Proceedings: Assessment of Antidumping Duties</E>
                    , 68 FR 23954 (May 6, 2003). This clarification will apply to entries of subject merchandise during the POR produced by DSM/KISCO/HSI included in these final results of review for which DSM/KISCO/HSI did not know its merchandise was destined for the United States. In such instances, we will instruct CBP to liquidate unreviewed entries at the “All Others” rate if there is no rate for the intermediate company(ies) involved in the transaction.
                </P>
                <P>
                    With respect to the companies for which this review was rescinded, although they did not have any sales or exports of subject merchandise to the United States during the POR, their subject merchandise may have entered the United States during the POR under their CBP antidumping case number by way of intermediaries (without their knowledge). Fifteen days after publication of this notice, the Department will instruct CBP to liquidate such entries at the “All Others” rate in effect on the date of the entry. 
                    <E T="03">See Antidumping and Countervailing Duty Proceedings: Assessment of Antidumping Duties</E>
                    , 68 FR 23954 (May 6, 2003).
                </P>
                <HD SOURCE="HD1">Cash Deposit Requirements</HD>
                <P>
                    The following cash deposit requirements will be effective for all shipments of the subject merchandise entered, or withdrawn from warehouse, for consumption on or after the publication date of the final results of this administrative review, as provided by section 751(a)(1) of the Act: (1) no cash deposit will be required for DSM/KISCO/HSI and the cash deposit rate for Dongil will be 102.28 percent; (2) for previously reviewed or investigated companies not listed above, the cash deposit rate will continue to be the company-specific rate published for the most recent period; (3) if the exporter is not a firm covered in this review, a prior review, or the original less-than-fair-value (LTFV) investigation, but the manufacturer is, the cash deposit rate will be the rate established for the most recent period for the manufacturer of the merchandise; and (4) the cash 
                    <PRTPAGE P="18632"/>
                    deposit rate for all other manufacturers or exporters will continue to be 22.89 percent. This rate is the “All Others” rate from the LTFV investigation. These deposit requirements shall remain in effect until further notice.
                </P>
                <P>This notice also serves as a final reminder to importers of their responsibility under 19 CFR 351.402(f)(2) 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 751(a)(1) and 777(i) of the Act and 19 CFR 351.221.</P>
                <SIG>
                    <DATED>Dated: April 9, 2007.</DATED>
                    <NAME>David M. Spooner,</NAME>
                    <TITLE>Assistant Secretary for Import Administration.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. E7-7084 Filed 4-12-07; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3510-DS-S</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE </AGENCY>
                <SUBAGY>National Institute of Standards and Technology </SUBAGY>
                <SUBJECT>Advanced Technology Program Advisory Committee </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Institute of Standards and Technology; Department of Commerce. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of partially closed meeting. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>Pursuant to the Federal Advisory Committee Act, 5 U.S.C. app. 2, notice is hereby given that the Advanced Technology Program Advisory Committee, National Institute of Standards and Technology (NIST) will meet Tuesday, May 15, 2007 from 8:30 a.m. to 3 p.m. The Advanced Technology Program Advisory Committee is composed of ten members appointed by the Director of NIST who are eminent in such fields as business, research, new product development, engineering, education, and management consulting. The purpose of this meeting is to review and make recommendations regarding general policy for the Advanced Technology Program (ATP), its organization, its budget, and its programs within the framework of applicable national policies as set forth by the President and the Congress. The agenda will include an ATP Update and a presentation on “The Data Enclave.” A discussion scheduled to begin at 11 a.m. and to end at 3 p.m. on May 15, 2007, on ATP budget issues will be closed. Agenda may change to accommodate Committee business. </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The meeting will convene Tuesday, May 15, at 8:30 a.m. and will adjourn at 3 p.m. on Tuesday, May 15, 2007. </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        The meeting will be held at the National Institute of Standards and Technology, Administration Building, Employees' Lounge, Gaithersburg, Maryland 20899. All visitors to the National Institute of Standards and Technology site will have to pre-register to be admitted. Please submit your name, time of arrival, e-mail address and phone number to Donna Paul no later than Friday, May 11, and she will provide you with instructions for admittance. Ms. Paul's e-mail address is 
                        <E T="03">donna.paul@nist.gov</E>
                         and her phone number is 301/975-2162. 
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Donna Paul, National Institute of Standards and Technology, Gaithersburg, Maryland 20899-4700, telephone number (301) 975-2162. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The agenda will include an ATP Update and a presentation on The Data Enclave. A discussion scheduled to begin at 11 a.m. and to end at 3 p.m. on May 15, 2007, on ATP budget issues will be closed. Agenda may change to accommodate Committee business. The Assistant Secretary for Administration, with the concurrence of the General Counsel, formally determined on January 9, 2007, that portions of the meeting of the Advanced Technology Program Advisory Committee which involve discussion of proposed funding of the Advanced Technology Program may be closed in accordance with 5 U.S.C. 552b(c)(9)(B), because that portion will divulge matters the premature disclosure of which would be likely to significantly frustrate implementation of proposed agency actions. </P>
                <SIG>
                    <DATED>Dated: April 5, 2007. </DATED>
                    <NAME>William Jeffrey, </NAME>
                    <TITLE>Director.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. E7-7075 Filed 4-12-07; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 3510-13-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE </AGENCY>
                <SUBAGY>National Institute of Standards and Technology </SUBAGY>
                <SUBJECT>National Fire Codes: Request for Proposals for Revision of Codes and Standards </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Institute of Standards and Technology, Commerce. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The National Fire Protection Association (NFPA) proposes to revise some of its fire safety codes and standards and requests proposals from the public to amend existing or begin the process of developing new NFPA fire safety codes and standards. The purpose of this request is to increase public participation in the system used by NFPA to develop its codes and standards. The publication of this notice of request for proposals by the National Institute of Standards and Technology (NIST) on behalf of NFPA is being undertaken as a public service; NIST does not necessarily endorse, approve, or recommend any of the standards referenced in the notice. </P>
                    <P>The NFPA process provides ample opportunity for public participation in the development of its codes and standards. All NFPA codes and standards are revised and updated every three to five years in Revision Cycles that begin twice each year and that takes approximately two years to complete. Each Revision Cycle proceeds according to a published schedule that includes final dates for all major events in the process. The process contains five basic steps that are followed both for developing new documents as well as revising existing documents. These steps are: Calling for Proposals; Publishing the Proposals in the Report on Proposals (ROP); Calling for Comments on the Committee's disposition of the proposals and these Comments are published in the Report on Comments (ROC); having a Technical Report Session at the NFPA Annual Meeting; and finally, the Standards Council Consideration and Issuance of documents. </P>
                </SUM>
                <NOTE>
                    <HD SOURCE="HED">Note:</HD>
                    <P>
                        Under new rules effective Fall 2005, anyone wishing to make Amending Motions on the Technical Committee Reports (ROP and ROC) must signal their intention by submitting a Notice of Intent to Make a Motion by the Deadline stated in the ROC. 
                        <PRTPAGE P="18633"/>
                        Certified motions will then be posted on the NFPA website. Documents that receive notice of proper Amending Motions (Certified Amending Motions) will be presented for action at the Annual Association Technical Meeting. Documents that receive no motions will be forwarded directly to the Standards Council for action on issuance.
                    </P>
                </NOTE>
                <P>
                    For more information on these new rules and for up-to-date information on schedules and deadlines for processing NFPA Documents, check the NFPA Web site at 
                    <E T="03">http://www.nfpa.org</E>
                     or contact NFPA Codes and Standards Administration.
                </P>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Interested persons may submit proposals on or before the dates listed with the standards. </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Casey C. Grant, Secretary, Standards Council, NFPA, 1 Batterymarch Park, Quincy, Massachusetts 02269-9101. </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Casey C. Grant, Secretary, Standards Council, at above address, (617) 770-3000. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Background </HD>
                <P>The National Fire Protection Association (NFPA) develops building, fire, and electrical safety codes and standards. Federal agencies frequently use these codes and standards as the basis for developing Federal regulations concerning fire safety. Often, the Office of the Federal Register approves the incorporation by reference of these standards under 5 U.S.C. 552(a) and 1 CFR Part 51. </P>
                <P>When a Technical Committee begins the development of a new or revised NFPA code or standard, it enters one of two Revision Cycles available each year. The Revision Cycle begins with the Call for Proposals, that is, a public notice asking for any interested persons to submit specific written proposals for developing or revising the Document. The Call for Proposals is published in a variety of publications. Interested parties have approximately twenty weeks to respond to the Call for Proposals. </P>
                <P>Following the Call for Proposals period, the Technical Committee holds a meeting to consider and accept, reject or revise, in whole or in part, all the submitted Proposals. The committee may also develop its own Proposals. A document known as the Report on Proposals, or ROP, is prepared containing all the Public Proposals, the Technical Committees' action and each Proposal, as well as all Committee-generated Proposals. The ROP is then submitted for the approval of the Technical Committee by a formal written ballot. If the ROP does not receive approval by a two-thirds vote calculated in accordance with NFPA rules, the Report is returned to the committee for further consideration and is not published. If the necessary approval is received, the ROP is published in a compilation of Reports on Proposals issued by NFPA twice yearly for public review and comment, and the process continues to the next step. </P>
                <P>
                    The Reports on Proposals are sent automatically free of charge to all who submitted proposals and each respective committee member, as well as anyone else who requests a copy. All ROP's are also available for free downloading at 
                    <E T="03">http://www.nfpa.org</E>
                    . 
                </P>
                <P>Once the ROP becomes available, there is a 60-day comment period during which anyone may submit a Public Comment on the proposed changes in the ROP. The committee then reconvenes at the end of the comment period and acts on all Comments. </P>
                <P>As before, a two-thirds approval vote by written ballot of the eligible members of the committee is required for approval of actions on the Comments. All of this information is complied into a second Report, called the Report on Comments (ROC), which, like the ROP, is published and made available for public review for a seven-week period. </P>
                <P>The process of public input and review does not end with the publication of the ROP and ROC. Following the completion of the Proposal and Comment periods, there is yet a further opportunity for debate and discussion through the Technical Report Sessions that take place at the NFPA Annual Meeting. </P>
                <P>
                    The Technical Report Session provides an opportunity for the final Technical Committee Report (
                    <E T="03">i.e.</E>
                    , the ROP and ROC) on each proposed new or revised code or standard to be presented to the NFPA membership for the debate and consideration of motions to amend the Report. Before making an allowable motion at a Technical Report Session, the intended maker of the motion must file, in advance of the session, and within the published deadline, a Notice of Intent to Make a Motion. A Motions Committee appointed by the Standards Council then reviews all notices and certifies all amending motions that are proper. Only these Certified Amending Motions, together with certain allowable Follow-Up Motions (that is, motions that have become necessary as a result of previous successful amending motions) will be allowed at the Technical Report Session. 
                </P>
                <P>
                    For more information on dates/locations of NFPA Technical Committee meetings and NFPA Annual Technical Report Sessions, check the NFPA Web site at: 
                    <E T="03">http://www.nfpa.org/itemDetail.asp?categoryID=822&amp;itemID=22818</E>
                    . 
                </P>
                <P>The specific rules for the types of motions that can be made and who can make them are set forth in NFPA's Regulation Governing Committee Projects which should always be consulted by those wishing to bring an issue before the membership at a Technical Report Session. </P>
                <HD SOURCE="HD1">Request for Proposals </HD>
                <P>
                    Interested persons may submit proposals, supported by written data, views, or arguments to Casey C. Grant, Secretary, Standards Council, NFPA, 1 Batterymarch Park, Quincy, Massachusetts 02269-9101. Proposals should be submitted on forms available from the NFPA Codes and Standards Administration Office or on NFPA's Web site at 
                    <E T="03">http://www.nfpa.org</E>
                    . 
                </P>
                <P>Each person must include his or her name and address, identify the document and give reasons for the proposal. Proposals received before or by 5 p.m. local time on the closing date indicated would be acted on by the Committee. The NFPA will consider any proposal that it receives on or before the date listed with the code or standard. </P>
                <GPOTABLE COLS="3" OPTS="L2,tp0,i1" CDEF="xs80,r100,12">
                    <TTITLE>  </TTITLE>
                    <BOXHD>
                        <CHED H="1">Document—edition </CHED>
                        <CHED H="1">Document name </CHED>
                        <CHED H="1">
                            Proposal 
                            <LI>closing date </LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">NFPA 13—2007 </ENT>
                        <ENT>Standard for the Installation of Sprinkler Systems </ENT>
                        <ENT>10/5/2007 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NFPA 13D—2007 </ENT>
                        <ENT>Standard for the Installation of Sprinkler Systems in One- and Two-Family Dwellings and Manufactured Homes </ENT>
                        <ENT>10/5/2007 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NFPA 13R—2007 </ENT>
                        <ENT>Standard for the Installation of Sprinkler Systems in Residential Occupancies up to and Including Four Stories in Height </ENT>
                        <ENT>10/5/2007 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NFPA 14—2007 </ENT>
                        <ENT>Standard for the Installation of Standpipes and Hose Systems </ENT>
                        <ENT>5/25/2007 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NFPA 24—2007 </ENT>
                        <ENT>Standard for the Installation of Private Fire Service Mains and Their Appurtenances </ENT>
                        <ENT>10/5/2007 </ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="18634"/>
                        <ENT I="01">NFPA 52—2006 </ENT>
                        <ENT>Vehicular Fuel Systems Code </ENT>
                        <ENT>5/25/2007 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NFPA 53—2004 </ENT>
                        <ENT>Recommended Practice on Materials, Equipment and Systems Used in Oxygen-Enriched Atmospheres </ENT>
                        <ENT>5/25/2007 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NFPA 55—2005 </ENT>
                        <ENT>Standard for the Storage, Use, and Handling of Compressed Gases and Cryogenic Fluids in Portable and Stationary Containers, Cylinders, and Tanks </ENT>
                        <ENT>5/25/2007 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NFPA 72—2007 </ENT>
                        <ENT>National Fire Alarm Code® </ENT>
                        <ENT>11/2/2007 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NFPA 82—2004 </ENT>
                        <ENT>Standard on Incinerators and Waste and Linen Handling Systems and Equipment </ENT>
                        <ENT>5/25/2007 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NFPA 99—2005 </ENT>
                        <ENT>Standard for Health Care Facilities </ENT>
                        <ENT>11/26/2007 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NFPA 99B—2005 </ENT>
                        <ENT>Standard for Hypobaric Facilities </ENT>
                        <ENT>11/26/2007 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NFPA 99C—2005 </ENT>
                        <ENT>Standard on Gas and Vacuum Systems </ENT>
                        <ENT>11/26/2007 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NFPA 101A—2007 </ENT>
                        <ENT>Guide on Alternative Approaches to Life Safety </ENT>
                        <ENT>11/26/2007 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NFPA 150—2007 </ENT>
                        <ENT>Standard on Fire and Life Safety in Animal Housing Facilities </ENT>
                        <ENT>5/25/2007 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NFPA 211-2006 </ENT>
                        <ENT>Standard for Chimneys, Fireplaces, Vents, and Solid Fuel-Burning Appliances </ENT>
                        <ENT>5/25/2007 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NFPA 225—2005 </ENT>
                        <ENT>Model Manufactured Home Installation Standard </ENT>
                        <ENT>5/25/2007 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NFPA 255—2006 </ENT>
                        <ENT>Standard Method of Test of Surface Burning Characteristics of Building Materials </ENT>
                        <ENT>11/26/2007 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NFPA 291—2007 </ENT>
                        <ENT>Recommended Practice for Fire Flow Testing and Marking of Hydrants </ENT>
                        <ENT>10/5/2007 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NFPA 501—2005 </ENT>
                        <ENT>Standard on Manufactured Housing </ENT>
                        <ENT>5/25/2007 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NFPA 501A—2005 </ENT>
                        <ENT>Standard for Fire Safety Criteria for Manufactured Home Installations, Sites, and Communities </ENT>
                        <ENT>5/25/2007 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NFPA 750—2006 </ENT>
                        <ENT>Standard on Water Mist Fire Protection Systems </ENT>
                        <ENT>5/30/2008 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NFPA 850—2005 </ENT>
                        <ENT>Recommended Practice for Fire Protection for Electric Generating Plants and High Voltage Direct Current Converter Stations </ENT>
                        <ENT>5/25/2007 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NFPA 851—2005 </ENT>
                        <ENT>Recommended Practice for Fire Protection for Hydroelectric Generating Plants </ENT>
                        <ENT>5/25/2007 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NFPA 914—2007 </ENT>
                        <ENT>Code for Fire Protection of Historic Structures </ENT>
                        <ENT>5/25/2007 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NFPA 1201—2004 </ENT>
                        <ENT>Standard for Providing Emergency Services to the Public </ENT>
                        <ENT>11/26/2007 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NFPA 1250—2004 </ENT>
                        <ENT>Recommended Practice in Emergency Service Organization Risk Management </ENT>
                        <ENT>11/26/2007 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NFPA 1670—2004 </ENT>
                        <ENT>Standard on Operations and Training for Technical Search and Rescue Incidents </ENT>
                        <ENT>5/25/2007 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NFPA 1710—2004 </ENT>
                        <ENT>Standard for the Organization and Deployment of Fire Suppression Operations, Emergency Medical Operations, and Special Operations to the Public by Career Fire Departments </ENT>
                        <ENT>11/26/2007 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NFPA 1720—2004 </ENT>
                        <ENT>Standard for the Organization and Deployment of Fire Suppression Operations, Emergency Medical Operations and Special Operations to the Public by Volunteer Fire Departments </ENT>
                        <ENT>11/26/2007 </ENT>
                    </ROW>
                    <TNOTE>
                        * P = Proposed NEW drafts are available from NFPA’s Web site—
                        <E T="03">http://www.nfpa.org</E>
                         or may be obtained from NFPA's Codes and Standards Administration, 1 Batterymarch Park, Quincy, MA 02269. 
                    </TNOTE>
                </GPOTABLE>
                <SIG>
                    <DATED>Dated: April 5, 2007. </DATED>
                    <NAME>William Jeffrey, </NAME>
                    <TITLE>Director.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC> [FR Doc. E7-7078 Filed 4-12-07; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 3510-13-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE </AGENCY>
                <SUBAGY>National Institute of Standards and Technology </SUBAGY>
                <SUBJECT>National Fire Codes: Request for Comments on NFPA Technical Committee Reports </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Institute of Standards and Technology, Commerce. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        Since 1896, the National Fire Protection Association (NFPA) has accomplished its mission by advocating scientifically based consensus codes and standards, research, and education for safety related issues. NFPA's 
                        <E T="03">National Fire Codes</E>
                        ®, which holds over 270 documents, are administered by more than 225 Technical Committees comprised of approximately 7,000 volunteers and are adopted and used throughout the world. NFPA is a nonprofit membership organization with approximately 80,000 members from over 70 nations, all working together to fulfill the Association's mission. 
                    </P>
                    <P>The NFPA process provides ample opportunity for public participation in the development of its codes and standards. All NFPA codes and standards are revised and updated every three to five years in Revision Cycles that begin twice each year and that take approximately two years to complete. Each Revision Cycle proceeds according to a published schedule that includes final dates for all major events in the process. The process contains five basic steps that are followed both for developing new documents as well as revising existing documents. These steps are: Calling for Proposals; Publishing the Proposals in the Report on Proposals (ROP); Calling for Comments on the Committee's disposition of the Proposals and these Comments are published in the Report on Comments (ROC); having a Technical Report Session at the NFPA Annual Meeting; and finally, the Standards Council Consideration and Issuance of documents. </P>
                </SUM>
                <NOTE>
                    <HD SOURCE="HED">Note:</HD>
                    <P>Under new rules effective Fall 2005, anyone wishing to make Amending Motions on the Technical Committee Reports (ROP and ROC) must signal their intention by submitting a Notice of Intent to Make a Motion by the Deadline of April 4, 2008. Certified motions will be posted by May 4, 2008. Documents that receive notice of proper Amending Motions (Certified Amending Motions) will be presented for action at the Annual 2008 Association Technical Meeting. Documents that receive no motions will be forwarded directly to the Standards Council for action on issuance at its July 24, 2008 meeting.</P>
                </NOTE>
                <P>
                    For more information on these new rules and for up-to-date information on schedules and deadlines for processing NFPA Documents, check the NFPA Web site at 
                    <E T="03">http://www.nfpa.org</E>
                     or contact NFPA Codes and Standards Administration. 
                </P>
                <P>The purpose of this notice is to request comments on the technical reports that will be presented at NFPA's 2008 Annual Revision Cycle. The publication of this notice by the National Institute of Standards and Technology (NIST) on behalf of NFPA is being undertaken as a public service; NIST does not necessarily endorse, approve, or recommend any of the standards referenced in the notice. </P>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Forty-seven reports are published in the 2008 Annual Cycle Report on Proposals and will be available on June 22, 2007. Comments received on or before August 31, 2007, will be considered by the respective NFPA Committees before final action is taken on the proposals. </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        The 2008 Annual Revision Cycle Report on Proposals is available 
                        <PRTPAGE P="18635"/>
                        and downloadable from NFPA's Web site 
                        <E T="03">http://www/nfpa.org</E>
                         or by requesting a copy from the NFPA, Fulfillment Center, 11 Tracy Drive, Avon, Massachusetts 02322. Comments on the report should be submitted to Casey C. Grant, Secretary, Standards Council, NFPA, 1 Batterymarch Park, P.O. Box 9101, Quincy, Massachusetts 02269-9101. 
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Casey C. Grant, Secretary, Standards Council, NFPA, 1 Batterymarch Park, Quincy, Massachusetts 02269-9101, (617) 770-3000. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Background </HD>
                <P>The National Fire Protection Association (NFPA) develops building, fire, and electrical safety codes and standards. Federal agencies frequently use these codes and standards as the basis for developing Federal regulations concerning fire safety. Often, the Office of the Federal Register approves the incorporation by reference of these standards under 5 U.S.C. 552(a) and 1 CFR Part 51. </P>
                <HD SOURCE="HD1">Request for Comments </HD>
                <P>Interested persons may participate in these revisions by submitting written data, views, or arguments to Casey C. Grant, Secretary, Standards Council, NFPA, 1 Batterymarch Park, Quincy, Massachusetts 02269-9101. Commenters may use the forms provided for comments in the Reports on Proposals. Each person submitting a comment should include his or her name and address, identify the notice, and give reasons for any recommendations. Comments received on or before August 31, 2007, for the 2008 Annual Cycle Report on Proposals will be considered by the NFPA before final action is taken on the proposals. </P>
                <P>Copies of all written comments received and the disposition of those comments by the NFPA committees will be published as the 2008 Annual Cycle Report on Comments by February 23, 2008. A copy of the Report on Comments will be sent automatically to each commenter. Reports of the Technical Committees on documents that do not receive a Notice of Intent to Make a Motion will automatically be forwarded to the Standards Council for action on issuance. Action on the reports of the Technical Committees on documents that do receive a Notice of Intent to Make a Motion will be taken at the Annual Meeting, June 2-6, 2008, in Las Vegas, Nevada, by NFPA members.</P>
                <GPOTABLE COLS="3" OPTS="L2,p1,8/9,i1" CDEF="xs60,r100,xs32">
                    <TTITLE>2008 Annual Meeting Report on Proposals </TTITLE>
                    <TDESC>[P = Partial revision; W = Withdrawal; R = Reconfirmation; N = New; C = Complete Revision] </TDESC>
                    <ROW>
                        <ENT I="01">NFPA 1</ENT>
                        <ENT>
                            Uniform Fire Code
                            <E T="51">TM</E>
                        </ENT>
                        <ENT>P </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NFPA 12A</ENT>
                        <ENT>Standard on Halon 1301 Fire Extinguishing Systems</ENT>
                        <ENT>P </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NFPA 42</ENT>
                        <ENT>Code for the Storage of Pyroxylin Plastic</ENT>
                        <ENT>W </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NFPA 45</ENT>
                        <ENT>Standard on Fire Protection for Laboratories Using Chemicals</ENT>
                        <ENT>P </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NFPA 51B</ENT>
                        <ENT>Standard for Fire Prevention During Welding, Cutting, and Other Hot Work</ENT>
                        <ENT>P </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NFPA 54</ENT>
                        <ENT>National Fuel Gas Code</ENT>
                        <ENT>P </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NFPA 59A</ENT>
                        <ENT>Standard for the Production, Storage, and Handling of Liquefied Natural Gas (LNG)</ENT>
                        <ENT>P </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NFPA 70E</ENT>
                        <ENT>Standard for Electrical Safety in the Workplace</ENT>
                        <ENT>P </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NFPA 90A</ENT>
                        <ENT>Standard for the Installation of Air-Conditioning and Ventilating Systems</ENT>
                        <ENT>P </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NFPA 90B</ENT>
                        <ENT>Standard for the Installation of Warm Air Heating and Air-Conditioning Systems</ENT>
                        <ENT>P </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NFPA 92A</ENT>
                        <ENT>Standard for Smoke-Control Systems Utilizing Barriers and Pressure Differences</ENT>
                        <ENT>P </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NFPA 92B</ENT>
                        <ENT>Standard for Smoke Management Systems in Malls, Atria, and Large Spaces</ENT>
                        <ENT>P </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NFPA 101</ENT>
                        <ENT>Life Safety Code®</ENT>
                        <ENT>P </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NFPA 220</ENT>
                        <ENT>Standard on Types of Building Construction</ENT>
                        <ENT>P </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NFPA 221</ENT>
                        <ENT>Standard for High Challenge Fire Walls and Fire Barrier Walls</ENT>
                        <ENT>P </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NFPA 256</ENT>
                        <ENT>Standard Methods of Fire Tests of Roof Coverings</ENT>
                        <ENT>P </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NFPA 260</ENT>
                        <ENT>Standard Methods of Tests and Classification System for Cigarette Ignition Resistance of Components of Upholstered Furniture</ENT>
                        <ENT>P </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NFPA 261</ENT>
                        <ENT>Standard Method of Test for Determining Resistance of Mock-Up Upholstered Furniture Material Assemblies to Ignition by Smoldering Cigarettes</ENT>
                        <ENT>P </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NFPA 274</ENT>
                        <ENT>Standard Test Method to Evaluate Fire Performance Characteristics of Pipe Insulation</ENT>
                        <ENT>P </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NFPA 275</ENT>
                        <ENT>Standard Method of Tests for the Evaluation of Thermal Barriers Used Over Foam Plastic</ENT>
                        <ENT>N </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NFPA 289</ENT>
                        <ENT>Standard Method of Fire Test for Room Fire Growth Contribution of Individual Fuel Packages</ENT>
                        <ENT>N </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NFPA 290</ENT>
                        <ENT>Standard for Fire Testing of Passive Protection Materials for Use on LP-Gas Containers</ENT>
                        <ENT>P </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NFPA 306</ENT>
                        <ENT>Standard for the Control of Gas Hazards on Vessels</ENT>
                        <ENT>P </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NFPA 318</ENT>
                        <ENT>Standard for the Protection of Semiconductor Fabrication Facilities</ENT>
                        <ENT>P </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NFPA 400</ENT>
                        <ENT>Hazardous Chemical Code</ENT>
                        <ENT>N </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NFPA 403</ENT>
                        <ENT>Standard for Aircraft Rescue and Fire-Fighting Services at Airports</ENT>
                        <ENT>P </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NFPA 412</ENT>
                        <ENT>Standard for Evaluating Aircraft Rescue and Fire-Fighting Foam Equipment</ENT>
                        <ENT>P </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NFPA 430</ENT>
                        <ENT>Code for the Storage of Liquid and Solid Oxidizers</ENT>
                        <ENT>W </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NFPA 432</ENT>
                        <ENT>Code for the Storage of Organic Peroxide Formulations</ENT>
                        <ENT>W </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NFPA 434</ENT>
                        <ENT>Code for the Storage of Pesticides</ENT>
                        <ENT>W </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NFPA 450</ENT>
                        <ENT>Guide for Emergency Medical Services and Systems</ENT>
                        <ENT>P </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NFPA 484</ENT>
                        <ENT>Standard for Combustible Metals</ENT>
                        <ENT>P </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NFPA 490</ENT>
                        <ENT>Code for the Storage of Ammonium Nitrate</ENT>
                        <ENT>P </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NFPA 555</ENT>
                        <ENT>Guide on Methods for Evaluating Potential for Room Flashover</ENT>
                        <ENT>P </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NFPA 610</ENT>
                        <ENT>Guide for Emergency and Safety Operations at Motorsports Venues</ENT>
                        <ENT>C </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NFPA 703</ENT>
                        <ENT>Standard for Fire-Retardant Treated Wood and Fire-Retardant Coatings for Building Materials</ENT>
                        <ENT>P </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NFPA 705</ENT>
                        <ENT>Recommended Practice for a Field Flame Test for Textiles and Films</ENT>
                        <ENT>P </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NFPA 720</ENT>
                        <ENT>Standard for the Installation of Carbon Monoxide (CO) Warning Equipment in Dwelling Units</ENT>
                        <ENT>C </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NFPA 1002</ENT>
                        <ENT>Standard for Fire Apparatus Driver/Operator Professional Qualifications</ENT>
                        <ENT>P </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NFPA 1021</ENT>
                        <ENT>Standard for Fire Officer Professional Qualifications</ENT>
                        <ENT>P </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NFPA 1026</ENT>
                        <ENT>Standard for Incident Management Personnel Professional Qualifications</ENT>
                        <ENT>N </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NFPA 1031</ENT>
                        <ENT>Standard for Professional Qualifications for Fire Inspector and Plan Examiner</ENT>
                        <ENT>C </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NFPA 1033</ENT>
                        <ENT>Standard for Professional Qualifications for Fire Investigator</ENT>
                        <ENT>P </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NFPA 1143</ENT>
                        <ENT>Standard for Wildland Fire Management</ENT>
                        <ENT>P </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NFPA 1620</ENT>
                        <ENT>Recommended Practice for Pre-Incident Planning</ENT>
                        <ENT>C </ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="18636"/>
                        <ENT I="01">NFPA 1901</ENT>
                        <ENT>Standard for Automotive Fire Apparatus</ENT>
                        <ENT>C </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NFPA 5000</ENT>
                        <ENT>Building Construction and Safety Code®</ENT>
                        <ENT>P </ENT>
                    </ROW>
                </GPOTABLE>
                <SIG>
                    <DATED>Dated: April 5, 2007. </DATED>
                    <NAME>William Jeffrey, </NAME>
                    <TITLE>Director.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. E7-7076 Filed 4-12-07; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 3510-13-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>National Oceanic and Atmospheric Administration</SUBAGY>
                <DEPDOC>[I.D. 040607C]</DEPDOC>
                <SUBJECT>Endangered Species; File No. 1604</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> Notice; application for permit.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                         Notice is hereby given that the U.S. Fish and Wildlife Service (Dr. Chester Figiel, Principal Investigator), 5308 Spring Street, Warm Springs, GA 31830, has applied in due form for a permit to take shortnose sturgeon (
                        <E T="03">Acipenser brevirostrum</E>
                        ) for purposes of enhancement and scientific research.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P> Written, telefaxed, or e-mail comments must be received on or before May 14, 2007.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P> The application and related documents are available for review upon written request or by appointment in the following offices:</P>
                    <P>Permits, Conservation and Education Division, Office of Protected Resources, NMFS, 1315 East-West Highway, Room 13705, Silver Spring, MD 20910; phone (301)713-2289; fax (301)427-2521; and</P>
                    <P>Southeast Region, NMFS, 263 13th Avenue South, St. Petersburg, FL 33701; phone (727)824-5312; fax (727)824-5309.</P>
                    <P>Written comments or requests for a public hearing on this application should be mailed to the Chief, Permits, Conservation and Education Division, F/PR1, Office of Protected Resources, NMFS, 1315 East-West Highway, Room 13705, Silver Spring, MD 20910. Those individuals requesting a hearing should set forth the specific reasons why a hearing on this particular request would be appropriate.</P>
                    <P>Comments may also be submitted by facsimile at (301)427-2521, provided the facsimile is confirmed by hard copy submitted by mail and postmarked no later than the closing date of the comment period.</P>
                    <P>
                        Comments may also be submitted by e-mail. The mailbox address for providing email comments is 
                        <E T="03">NMFS.Pr1Comments@noaa.gov</E>
                        . Include in the subject line of the e-mail comment the following document identifier: File No. 1604.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Malcolm Mohead or Jennifer Skidmore, (301)713-2289.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    The subject permit is requested under the authority of the Endangered Species Act of 1973, as amended (ESA; 16 U.S.C. 1531 
                    <E T="03">et seq.</E>
                    ) and the regulations governing the taking, importing, and exporting of endangered and threatened species (50 CFR 222-226).
                </P>
                <P>
                    The proposed action would be issuance of an enhancement and scientific research permit (File No. 1604) to the FWS (Dr. Chester Figiel, Principal Investigator), pursuant to the ESA. The primary objective would be to utilize the available captive brood stock population to provide information needed for implementation of recovery efforts, as described in the “Final Recovery Plan for the Shortnose Sturgeon (
                    <E T="03">Acipenser brevirostrum</E>
                    )” (NMFS, 1998). Captive fish would be maintained, conditioned, spawned and the gametes and progeny used for scientific studies, such as cryo-preservation, genetics, culture techniques, behavioral studies, nutrition, and tagging techniques. An additional study characterizing the wild genetic strains of sturgeon in rivers of the Southeast Atlantic coast would be accomplished using tissue samples archived at the NOAA/NOS Laboratory in Charleston, South Carolina. The permit is requested for five years.
                </P>
                <SIG>
                    <DATED>Dated: April 6, 2007.</DATED>
                    <NAME>P. Michael Payne,</NAME>
                    <TITLE>Chief, Permits, Conservation and Education Division, Office of Protected Resources, National Marine Fisheries Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. E7-6970 Filed 4-12-07; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3510-22-S</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>National Oceanic and Atmospheric Administration</SUBAGY>
                <DEPDOC>[I.D. 040907B]</DEPDOC>
                <SUBJECT>Gulf of Mexico Fishery Management Council; Public Meeting</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>Notice of Closed Session of the Gulf Council via Conference Call.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Gulf of Mexico Fishery Management Council (Council) will convene via Conference Call in a closed session to select members to an Ad Hoc Recreational Red Snapper Advisory Panel, the Ecosystem Scientific and Statistical Committee, and an Ad Hoc Red Drum Scientific Review Panel.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The Conference Call will be held on Friday, April 27, 2007, from 10 am EDT to approximately 10:30 a.m. EDT.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Meeting address: The meeting will be held via Closed Session conference call.</P>
                    <P>
                        <E T="03">Council address</E>
                        : Gulf of Mexico Fishery Management Council, 2203 North Lois Avenue, Suite 1100, Tampa, Florida 33607.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Mr. Wayne Swingle, Executive Director, Gulf of Mexico Fishery Management Council; telephone: 813-348-1630.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The Gulf of Mexico Fishery Management Council (Council) will convene via closed session Conference Call to select members to an Ad Hoc Recreational Red Snapper Advisory Panel, the Ecosystem Scientific and Statistical Committee, and an Ad Hoc Red Drum Scientific Panel.</P>
                <SIG>
                    <DATED>Dated: April 9, 2007.</DATED>
                    <NAME>Tracey L. Thompson,</NAME>
                    <TITLE>Acting Director, Office of Sustainable Fisheries, National Marine Fisheries Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. E7-6995 Filed 4-12-07; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3510-22-S</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="18637"/>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>National Oceanic and Atmospheric Administration</SUBAGY>
                <DEPDOC>[I. D. 040907C]</DEPDOC>
                <SUBJECT>Gulf of Mexico Fishery Management Council; Public Meetings</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>Notice of public meeting.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Gulf of Mexico Fishery Management Council (Council) will convene its Socioeconomic Panel (SEP).</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The meeting will be convene at 8:30 am on Thursday, May 3, 2007, and conclude no later than 1 p.m. on Friday, May 4, 2007.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>The meeting will be held at the Grand Bay Miami Hotel, 2669 S. Bayshore Dr., Miami, FL 33133, 305-858-9600.</P>
                    <P>
                        <E T="03">Council address</E>
                        : Gulf of Mexico Fishery Management Council, 2203 North Lois Avenue, Suite 1100, Tampa, Florida 33607.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Dr. Assane Diagne, Economist, Gulf of Mexico Fishery Management Council; telephone: 813-348-1630.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The Gulf of Mexico Fishery Management Council (Council) will convene its Socioeconomic Panel (SEP) to discuss grouper allocation, Joint Reef Fish/Shrimp Amendment 27/14, an update on the recently implemented Red Snapper IFQ, and, recommendations of the Ad-hoc Grouper IFQ Advisory Panel. In addition, the SEP will elect its chair and vice-chair.</P>
                <P>A copy of the agenda and related materials can be obtained by calling the Council office at 813-348-1630.</P>
                <P>Although other non-emergency issues not on the agendas may come before the SEP for discussion, in accordance with the Magnuson-Stevens Fishery Conservation and Management Act (M-SFCMA), those issues may not be the subject of formal action during this meeting. Actions of the SEP will be restricted to those issues specifically identified in the agendas and any issues arising after publication of this notice that require emergency action under Section 305(c) of the M-SFCMA, provided the public has been notified of the Council's intent to take action to address the emergency.</P>
                <P>
                    These meetings are physically accessible to people with disabilities. Requests for sign language interpretation or other auxiliary aids should be directed to Tina Trezza at the Council (see 
                    <E T="02">ADDRESSES</E>
                    ) at least five working days prior to the meeting.
                </P>
                <SIG>
                    <DATED>Dated: April 9, 2007.</DATED>
                    <NAME>Tracey L. Thompson,</NAME>
                    <TITLE>Acting Director, Office of Sustainable Fisheries, National Marine Fisheries Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. E7-6996 Filed 4-12-07; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3510-22-S</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF DEFENSE</AGENCY>
                <SUBAGY>Office of the Secretary of Defense</SUBAGY>
                <DEPDOC>[DOD-2007-OS-0005]</DEPDOC>
                <SUBJECT>Notice Pursuant to Executive Order 12600 of Receipt of Freedom of Information Act (FOIA) Requests for Access to the Central Contractor Registration (CCR) Database</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Department of Defense, Business Transformation Agency.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This notice provides submitter's notice pursuant to Executive Order 12600 that the Department of Defense, Office of the Secretary of Defense, Business Transformation Agency (BTA) has received several FOIA requests for access to the Central Contractor Registration (CCR) database.</P>
                    <P>The CCR is an e-Gov initiative within the Integrated Acquisition Environment (IAE) and serves as the core system for the IAE's Business Partner Network (BRN). The Department of Defense manages the CCR on behalf of the IAE. The primary objective of the CCR is to provide a web-based application that provides a single source of vendor information in support of the contract award and the electronic payment process of the Federal Government. The CCR is also a registration system for grants and assistance awards. The CCR has 194 data fields, some of which are exempt from disclosure pursuant to Exemptions 2, and/or 4 and/or 6 of Freedom of Information Act (FOIA), 5 U.S.C. 552(b)(2), (b)(4) &amp; (b)(6). The following table contains a description of these data fields and their exempt status.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be received on or before June 12, 2007. Do not submit comments directly to the point of contact or mail your comments to any address other than what is shown below. Doing so will delay the posting of the submission.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may submit comments, identified by docket number and or RIN number and title, by any of the following methods:</P>
                    <P>
                        • 
                        <E T="03">Federal eRulemaking Portal: http://www.regulations.gov</E>
                        . Follow the instructions for submitting comments.
                    </P>
                    <P>
                        • 
                        <E T="03">Mail:</E>
                         Federal Docket Management System Office, 1160 Defense Pentagon, Washington, DC 20301-1160
                    </P>
                    <P>
                        <E T="03">Instructions:</E>
                         All submissions received must include the agency name and docket number or Regulatory Information Number (RIN) for this 
                        <E T="04">Federal Register</E>
                         document. The general policy for comments and other submissions from members of the public is to make these submissions available for public viewing on the Internet at 
                        <E T="03">http://regulations.gov</E>
                         as they are received without change, including any personal identifiers or contact information.
                    </P>
                </ADD>
                <SIG>
                    <DATED>April 9, 2007.</DATED>
                    <NAME>L.M. Bynum,</NAME>
                    <TITLE>Alternate OSD Federal Register Liaison Officer, DoD.</TITLE>
                </SIG>
                <GPOTABLE COLS="2" OPTS="L2,i1" CDEF="s100,xs150">
                    <TTITLE>FOIA Review of the CCR Data Fields </TTITLE>
                    <BOXHD>
                        <CHED H="1">Data field </CHED>
                        <CHED H="1">Exempt status </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">1) Data Universal Numbering System (DUNS)</ENT>
                        <ENT>5 U.S.C. 552(b)(4). </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">2) DUNS-Plus 4</ENT>
                        <ENT>5 U.S.C. 552(b)(4). </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">3) CAGE Code</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">4) CCR Extract Code</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">5) Registration Date</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">6) Renewal Date</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">7) Legal Business Name</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">8) DBA Name</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">9) Company Division</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">10) Division Number</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">11) Street Address (1)</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="18638"/>
                        <ENT I="01">12) Street Address (2)</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">13) City</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">14) State or Province</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">15) Postal Code</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">16) Country Code</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">17) Business Start Date</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">18) Fiscal Year End Close Date</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">19) Company Security Level</ENT>
                        <ENT>5 U.S.C. 552(b)(2) &amp; (b)(4). </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20) Employee Security Level</ENT>
                        <ENT>5 U.S.C. 552(b)(2) &amp; (b)(4). </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">21) Corporate URL</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">22) Organizational Type</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">23) State of Incorporation</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">24) Country of Incorporation</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">25) Business Types</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">26) SIC Code</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">27) NAICS Code</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">28) FSC Code</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">29) PSC Code</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">30) Credit Card (y/n)</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">31) Correspondence Flag</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">32) Mailing Address POC (FE)</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">33) Mailing Address Street Address (1)</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">34) Mailing Address Street Address (2)</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">35) Mailing Address City</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">36) Mailing Address Postal Code</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">37) Mailing Address Country Code</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">38) Mailing Address State/Province</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">39) Previous Business POC (B3)</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">40) Previous Street Address (1)</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">41) Previous Street Address (2)</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">42) Previous Business City</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">43) Previous Business Postal Code</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">44) Previous Business Country Code</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">45) Previous Business State/Province</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">46) Parent POC (B4)</ENT>
                        <ENT>5 U.S.C. 552(b)(4). </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">47) Parent DUNS Number</ENT>
                        <ENT>5 U.S.C. 552(b)(4). </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">48) Parent Street Address (1)</ENT>
                        <ENT>5 U.S.C. 552(b)(4). </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">49) Parent Street Address (2)</ENT>
                        <ENT>5 U.S.C. 552(b)(4). </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">50) Parent City</ENT>
                        <ENT>5 U.S.C. 552(b)(4). </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">51) Parent Postal Code</ENT>
                        <ENT>5 U.S.C. 552(b)(4). </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">52) Parent Country Code</ENT>
                        <ENT>5 U.S.C. 552(b)(4). </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">53) Parent State or Province</ENT>
                        <ENT>5 U.S.C. 552(b)(4). </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">54) Party Performance Cert POC (PV)</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">55) Party Performance Cert Street Address (1)</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">56) Party Performance Cert Street Address (2)</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">57) Party Performance Cert City</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">58) Party Performance Cert Postal Code</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">59) Party Performance Cert Country Code</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">60) Party Performance Cert State/Province</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">61) Government Parent POC (QW)</ENT>
                        <ENT>5 U.S.C. 552(b)(4). </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">62) Government Parent Street Address (1)</ENT>
                        <ENT>5 U.S.C. 552(b)(4). </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">63) Government Parent Street Address (2)</ENT>
                        <ENT>5 U.S.C. 552(b)(4). </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">64) Government Parent City</ENT>
                        <ENT>5 U.S.C. 552(b)(4). </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">65) Government Parent Postal Code</ENT>
                        <ENT>5 U.S.C. 552(b)(4). </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">66) Government Parent Country Code</ENT>
                        <ENT>5 U.S.C. 552(b)(4). </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">67) Government Parent State/Province</ENT>
                        <ENT>5 U.S.C. 552(b)(4). </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">68) Government Business POC (60)</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">69) Government Business Street Address (1)</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">70) Government Business Street Address (2)</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">71) Government Business City</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">72) Government Business Postal Code</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">73) Government Business Country Code</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">74) Government Business State or Province</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">75) Government Business U.S. Phone</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">76) Government Business U.S. Phone Ext</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">77) Government Business Non-U.S. Phone</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">78) Government Business Fax U.S. Only</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">79) Government Business E-mail</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">80) Alternate Government Business POC (60)</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">81) Alternate Government Business Street Address (1)</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">82) Alternate Government Business Street Address (1)</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">83) Alternate Government Business City</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="18639"/>
                        <ENT I="01">84) Alternate Government Parent Postal Code</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">85) Alternate Government Business Country Code</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">86) Alternate Government Parent State/Province</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">87) Alternate Government Business U.S. Phone</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">88) Alternate Government Business U.S. Phone Ext</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">89) Alternate Government Business Non-U.S. Phone</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">90) Alternate Government Business Fax U.S. Only</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">91) Alternate Government Business E-mail</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">92) Past Performance POC (R2)</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">93) Past Performance Street Address (1)</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">94) Past Performance Street Address (2)</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">95) Past Performance City</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">96) Past Performance Postal Code</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">97) Past Performance Country Code</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">98) Past Performance State or Province</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">99) Past Performance U.S. Phone</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">100) Past Performance U.S. Phone Ext</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">101) Past Performance Non-U.S. Phone</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">102) Past Performance Fax U.S. Only</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">103) Past Performance E-mail</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">104) Alternate Past Performance POC (R2)</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">105) Alternate Past Performance Street Address (1)</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">106) Alternate Past Performance Street Address (2)</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">107) Alternate Past Performance City</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">108) Alternate Past Performance Postal Code</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">109) Alternate Past Performance Country Code</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">110) Alternate Past Perf. State/Province</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">111) Alternate Past Performance U.S. Phone</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">112) Alternate Past Performance U.S. Phone Ext</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">113) Alternate Past Performance Non-U.S. Phone</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">114) Alternate Past Performance Fax Only</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">115) Alternate Past Performance E-mail</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">116) Elec. Business POC (ZR)</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">117) Elec. Business Street Address (1)</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">118) Elec. Business Street Address (2)</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">119) Elec. Business City</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">120) Elec. Business U.S. Phone</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">121) Elec. Business Country Code</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">122) Elec. Business State or Province</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">123) Elec. Business U.S. Phone</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">124) Elec. Business U.S. Phone Ext</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">125) Elec. Business Non-U.S. Phone</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">126) Elec. Business Fax U.S. Only</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">127) Elec. Business E-mail</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">128) Alternate Elec. Business POC</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">129) Alternate Elec. Business Street Address (1)</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">130) Alternate Elec. Business Street Address (2)</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">131) Alternate Elec. Business City</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">132) Alternate Elec. Business Postal Code</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">133) Alternate Elec. Business Country Code</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">134) Alternate Elec. Business State/Province</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">135) Alternate Elec. Business U.S. Phone</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">136) Alternate Elec. Business U.S. Phone Ext</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">137) Alternate Elec. Business Non-U.S. Phone</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">138) Alternate Elec. Business Fax U.S. Only</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">139) Alternate Elec. Business E-mail</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">140) Certifier POC (CE)</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">141) Certifier U.S. Phone</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">142) Certifier U.S. Phone Ext</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">143) Certifier Non-U.S. Phone</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">144) Certifier Fax U.S. Only</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">145) Certifier E-mail</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">146) Alternate Certifier POC (IC)</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">147) Alternate Certifier U.S. Phone</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">148) Alternate Certifier U.S. Phone Ext</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">149) Alternate Certifier Non-U.S. Phone</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">150) Alternate Certifier Fax U.S. Only</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">151) Alternate Certifier E-mail</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">152) Corporate Information POC (CN)</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">153) Corporate Information U.S. Phone</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">154) Corporate Information U.S. Phone Ext</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">155) Corporate Information Non-U.S. Phone</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="18640"/>
                        <ENT I="01">156) Corporate Information Fax U.S. Only</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">157) Corporate Information E-mail</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">158) Owner Information POC (OW)</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">159) Owner Information U.S. Phone</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">160) Owner Information U.S. Phone Ext</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">161) Owner Information Non-U.S. Phone</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">162) Owner Information Fax U.S. Only</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">163) Owner Information E-mail</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">164) EDI (y/n)</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">165) Tax Payer ID Number</ENT>
                        <ENT>5 U.S.C. 552(b)(2) &amp; (b)(4). </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">166) Average Number of Employees</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">167) Annual Revenue</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">168) Social Security Number</ENT>
                        <ENT>5 U.S.C. 552(b)(4) &amp; (b)(6). </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">169) Financial Institute</ENT>
                        <ENT>5 U.S.C. 552(b)(4). </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">170) Account Number</ENT>
                        <ENT>5 U.S.C. 552(b)(4). </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">171) ABA Routing ID</ENT>
                        <ENT>5 U.S.C. 552(b)(4). </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">172) Payment Type (c or s)</ENT>
                        <ENT>5 U.S.C. 552(b)(4). </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">173) Lockbox Number</ENT>
                        <ENT>5 U.S.C. 552(b)(4). </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">174) Authorization Date</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">175) EFT Waiver Y/N</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">176) ACH U.S. Phone</ENT>
                        <ENT>5 U.S.C. 552(b)(4). </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">177) ACH Non-U.S. Phone</ENT>
                        <ENT>5 U.S.C. 552(b)(4). </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">178) ACH Fax</ENT>
                        <ENT>5 U.S.C. 552(b)(4). </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">179) ACH E-mail</ENT>
                        <ENT>5 U.S.C. 552(b)(4). </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">180) Remit Information POC (RI)</ENT>
                        <ENT>5 U.S.C. 552(b)(4). </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">181) Remit Information Street Address (1)</ENT>
                        <ENT>5 U.S.C. 552(b)(4). </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">182) Remit Information Street Address (2)</ENT>
                        <ENT>5 U.S.C. 552(b)(4). </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">183) Remit Information City</ENT>
                        <ENT>5 U.S.C. 552(b)(4). </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">184) Remit Information State/Province</ENT>
                        <ENT>5 U.S.C. 552(b)(4). </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">185) Remit Information Postal Code</ENT>
                        <ENT>5 U.S.C. 552(b)(4). </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">186) Remit Information Country Code</ENT>
                        <ENT>5 U.S.C. 552(b)(4). </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">187) Accounts Receivables POC (AF)</ENT>
                        <ENT>5 U.S.C. 552(b)(4). </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">188) Accounts Receivables U.S. Phone</ENT>
                        <ENT>5 U.S.C. 552(b)(4). </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">189) Accounts Receivables U.S. Phone Ext</ENT>
                        <ENT>5 U.S.C. 552(b)(4). </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">190) Accounts Receivables Non-U.S. Phone</ENT>
                        <ENT>5 U.S.C. 552(b)(4). </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">191) Accounts Receivable Fax U.S. Only</ENT>
                        <ENT>5 U.S.C. 552(b)(4). </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">192) Accounts Receivable E-mail</ENT>
                        <ENT>5 U.S.C. 552(b)(4). </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">193) Marketing Prtner ID No. (MPIN)</ENT>
                        <ENT>5 U.S.C. 552(b)(4). </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">194) Current Reg Status</ENT>
                        <ENT>Not exempt under the FOIA. </ENT>
                    </ROW>
                </GPOTABLE>
            </PREAMB>
            <FRDOC> [FR Doc. E7-7010 Filed 4-12-07; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 5001-06-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF DEFENSE</AGENCY>
                <SUBAGY>Office of the Secretary</SUBAGY>
                <SUBJECT>Meeting of the Secretary of Defense's Defense Advisory Board for Employer Support of the Guard and Reserve (DAB-ESGR)</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Department of Defense.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of open meeting. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This notice announces a meeting of the DAB-ESGR. This meeting will focus on the status of DoD actions and recommendations from previous DAB meetings and relevant discussions on Reserve Affairs recruiting and review of DoD planning guidance for future mobilizations and targeted communications to employers and is open to the public.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>0900-1530 hrs, 26 April 2007.</P>
                </DATES>
                <PREAMHD>
                    <HD SOURCE="HED">Location:</HD>
                    <P>Assistant Secretary of Defense for Reserve Affairs conference room 2E223, the Pentagon.</P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">For Further Information Contact:</HD>
                    <P>
                        Interested attendees may contact MAJ Elaine M. Gullota at 703-696-1385 ext 540, or e-mail at 
                        <E T="03">Elaine.gullotta@osd.mil.</E>
                    </P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">Agenda:</HD>
                    <P> </P>
                </PREAMHD>
                <FP SOURCE="FP-2">0900 Convene.</FP>
                <FP SOURCE="FP-2">0905 Oath of Office (Mr. Wilson).</FP>
                <FP SOURCE="FP-2">0910 Review of Last Meeting Minutes.</FP>
                <FP SOURCE="FP-2">0930 Honorable Thomas E. Hall, Assistant Secretary of Defense Reserve Affairs.</FP>
                <FP SOURCE="FP-2">0940 Admiral Giambastiani, Vice Chairman, Joint Chiefs of Staff.</FP>
                <FP SOURCE="FP-2">1000 Honorable Gordon R. England, Deputy Secretary of Defense.</FP>
                <FP SOURCE="FP-2">1015 Major General Raymond Carpenter, Special Assistant to the Director, Army National Guard, Impact of DoD policy changes for future mobilizations.</FP>
                <FP SOURCE="FP-2">1100 Lieutenant General Jack C. Stultz, Chief, Army Reserve.</FP>
                <FP SOURCE="FP-2">1130 Lunch (Executive Dining Room, #4).</FP>
                <FP SOURCE="FP-2">1300 Ms. Kathy Naylor, Director Executive Leadership, Unisys, The Shared Resource-Communications and Outreach to Employers.</FP>
                <FP SOURCE="FP-2">1330 Mr. Gordon Summer, Executive Director ESGR.</FP>
                <FP SOURCE="FP-2">1345 Honorable David S.C. Chu, Under Secretary of Defense Personnel and Readiness.</FP>
                <FP SOURCE="FP-2">1400 Board Discussion.</FP>
                <FP SOURCE="FP-2">1500 Mr. Dave Janes, Chairman ESGR, Remarks.</FP>
                <FP SOURCE="FP-2">1515 Adjourn.</FP>
                <PREAMHD>
                    <HD SOURCE="HED">Location:</HD>
                    <P>Pentagon Room (2E223), OSD-RA.</P>
                </PREAMHD>
                <SIG>
                    <DATED>Dated: April 6, 2007.</DATED>
                    <NAME>L.M. Bynum,</NAME>
                    <TITLE>Alternate OSD Federal Register Liaison Officer, DoD.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 07-1829 Filed 4-12-07; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 5001-06-M</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="18641"/>
                <AGENCY TYPE="S">DEPARTMENT OF THE DEFENSE</AGENCY>
                <SUBAGY>Department of the Army; Corps of Engineers</SUBAGY>
                <SUBJECT>Intent To Prepare a Draft Supplemental Environmental Impact Statement for the Jacksonville Harbor Navigation Study, General Re-Evaluation Report, Located in Duval County, FL</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Department of the Army, U.S. Army of Corps of Engineers, DoD.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of intent. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The U.S. Army Corps of Engineers (Corps), Jacksonville District, intends to prepare a Draft Supplemental Environmental Impact Statement (DSEIS), for the Jacksonville Harbor Navigation Study, General Re-Evaluation Report. This action is a cooperative effort between the Corps and the Jacksonville Harbor Port Authority.</P>
                </SUM>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>U.S. Army Corps of Engineers, Planning Division, Environmental Branch, P.O. Box 4970, Jacksonville, FL 32232-0019.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Mr. Paul Stodola, by e-mail 
                        <E T="03">Paul.E.Stodola@saj02.usace.army.mil</E>
                         or by telephone at (904) 232-3271.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P SOURCE="NPAR">a. The Jacksonville Part Authority has requested that the Corps study the feasibility of further deepening the Port of Jacksonville. The proposed DSEIS for additional deepening would supplement the Jacksonville Harbor Navigation Improvements EIS completed in July 1996. Authorization for the study is contained in House Report 107-681 and the Senate explanatory statement as delineated in the Congressional Record of January 15, 2003, pages S492 and S546.</P>
                <P>
                    b. 
                    <E T="03">Objectives.</E>
                     The objectives of the study are to determine if light loading of ships, tidal delay, or other commercial navigation benefits exist to justify additional deepening below the existing 40-foot project depth from the entrance channel to river mile 20 and for Cuts F and G of the West Blount Island Channel; evaluate measures including wideners along the Trout River Cut Range, and Quarantine (Bartram) Island Upper Range which would reduce navigation concerns and improve ship traffic safety; examine the impact of channel deepening on the capacity of existing upland confined disposal facilities and the offshore dredge material disposal site; evaluate new upland confined disposal facilities, if required; determine if beneficial uses of dredged material such as manufactured soils, recycling of dredged material for construction fill, development of artificial reefs, or use of beach quality material for placement along adjacent beaches would provide appropriate alternatives for disposal of dredged material; evaluate the impact of deepening and widening measures on shoaling rates for existing and advanced harbor maintenance needs; examine the hydrodynamic and environmental effects of the deepening and widening measures on Chicopit Bay, White Shells Bay, Mill Cove and adjacent harbor shorelines; identify environmental and cultural resources in the study area and potential impacts from deepening or widening to those resources; identify the NED plan for Jacksonville Harbor which most efficiently and safely accommodates existing and larger commercial ship and barge traffic while avoiding or minimizing impacts to environmental resources.
                </P>
                <P>
                    c. 
                    <E T="03">Alternatives.</E>
                     The proposed alternatives include making no further improvements to the project (no action alternatives); deepening the project channel in 1 foot increments from the existing depth of 40 feet from  the entrance channel (mouth of St. Johns River) extending upstream to river mile 20; constructing channel wideners; and dredged material placement in upland disposal areas, artificial reefs, approved beach areas, and the designated Ocean Dredged Material Disposal Site.
                </P>
                <P>
                    d. 
                    <E T="03">Issues.</E>
                     The DEIS will consider the possible effects of blasting on aquatic resources, loss of wetlands from expansion of upland disposal areas at Bartram Island, as well as other project related impacts on protected species, water quality, fish and wildlife resources, cultural resources, essential fish habitat, socio-economic resources coastal processes, aesthetics and recreation, and other impacts identified through scoping, public involvement, and agency coordination.
                </P>
                <P>
                    e. 
                    <E T="03">Scoping Process.</E>
                     The scoping process as outlined by the Council on Environmental Quality would be utilized to involve Federal, State, and local agencies, and other interested persons and organizations. A scoping letter would be sent to the appropriate parties requesting comments and concerns regarding issues to consider during the study. Public scoping meetings would be held. Exact dates, times, and locations would be published in local papers.
                </P>
                <P>
                    f. 
                    <E T="03">Coordination.</E>
                     The proposed action is being coordinated with the U.S. Fish and Wildlife Service (FWS) and the National Marine Fisheries Service under Section 7 of the Endangered Species Act, with the FWS under the Fish and Wildlife Coordination Act, and with the State Historic Preservation Officer.
                </P>
                <P>
                    g. 
                    <E T="03">Other Environmental Review and Consultation.</E>
                     The proposed action would involve evaluation for compliance with guidelines pursuant to Section 404(b) of the Clean Water Act; application (to the State of Florida) for Water Quality Certification pursuant to Section 401 of the Clean Water Act; certification of state lands, easements, and rights of way; Essential Fish Habitat with National Marine Fisheries Service; and determination of Coastal Zone Management Act consistency.
                </P>
                <P>
                    h. 
                    <E T="03">Agency Role.</E>
                     The non-Federal sponsor (Jacksonville Port Authority) will provide extensive information and assistance on the resources to be impacted, mitigation measures, and alternatives.
                </P>
                <P>
                    i. 
                    <E T="03">DSEIS Preparation.</E>
                     It is estimated that the DSEIS will be available to the public on or about three years after completion of the Feasibility Scoping Meeting currently scheduled for September 2007.
                </P>
                <SIG>
                    <DATED>Dated: April 2, 2007.</DATED>
                    <NAME>Stuart J. Appelbaum,</NAME>
                    <TITLE>Chief, Planning Division.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 07-1835 Filed 4-12-07; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3710-AJ-M</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF DEFENSE </AGENCY>
                <SUBAGY>Department of the Army, Corps of Engineers </SUBAGY>
                <SUBJECT>Intent To Prepare a Legislative Environmental Impact Statement, for the Proposed Mississippi River—Gulf Outlet Deep Draft De-Authorization (3-D), LA </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Department of the Army, U.S. Army Corps of Engineers, DoD. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of intent. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This notice of intent (NOI) is for the Mississippi River—Gulf Outlet (MRGO) 3-D Project. This notice of intent addresses the Federally authorized navigation channel located in southeastern Louisiana. </P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Questions about the proposed action and Legislative Environmental Impact Statement can be answered by: Mr. Sean P. Mickal, 504 862-2319, CEMVN-PM-RS, P.O. Box 60267, New Orleans, LA 70160-0267. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    The MRGO is a Federally-authorized 36-foot deep, 500-foot bottom width waterway which allows deep-draft access to New Orleans area port facilities via a shorter route than using the Mississippi River. Congress authorized MRGO channel 
                    <PRTPAGE P="18642"/>
                    construction in the River and Harbor Act of 1956. Public Law 84-445, 70 Stat. 65 states: “Be it enacted by the Senate and House of Representatives of the United States of America Congress assembled, that the existing project for the Mississippi River, Baton Rouge to the Gulf of Mexico, is hereby modified to provide for the Mississippi River-Gulf Outlet to be constructed under the direction of the Secretary of the Army and supervision of the Chief of Engineers, substantially in accordance with the recommendation of the Chief of Engineers contained in House Document 245, Eighty-Second Congress, at an estimated cost of $88,000,000 * * .*” 
                </P>
                <P>The LEIS would accompany the MRGO 3-D report to Congress being prepared to aid in identifying a comprehensive plan for de-authorizing deep-draft navigation on the MRGO from the Gulf Intracoastal Waterway (GIWW) to the Gulf of Mexico. Public Law 109-234, the Emergency Supplemental Appropriations Act for Defense, the Global War on Terror, and Hurricane Recovery, 2006, reads in part: “* * * the Secretary of the Army, acting through the Chief of Engineers, utilizing $3,300,000 of the funds provided herein shall develop a comprehensive plan, at full Federal expense, to de-authorize deep-draft navigation on the Mississippi River-Gulf Outlet, Louisiana, extending from the Gulf of Mexico to the Gulf Intracoastal Waterway: Provided further, That, not later than 6 months after the date of enactment of this Act, the Secretary shall submit an interim report to Congress comprising the plan: Provided further, That the Secretary shall refine the plan, if necessary, to be fully consistent, integrated, and included in the final report to be issued in December 2007 for the Louisiana Coastal Protection and Restoration Plan.” </P>
                <P>
                    1. 
                    <E T="03">Proposed Action and Reasonable Alternatives:</E>
                     Congress has directed the Secretary of the Army, acting through the Chief of Engineers, to plan for de-authorization of deep-draft navigation on the MRGO. Congress has authorized the United States Army Corps of Engineers (USACE) to prepare a comprehensive plan to de-authorize deep-draft navigation on the MRGO channel and has also encouraged the USACE to identify any measures for hurricane and storm damage reduction. An Interim Report titled, Mississippi River Gulf Outlet, Deep-Draft De-Authorization, Interim Report to Congress, was submitted to Congress in December 2006. The Interim Report compared options for a comprehensive plan for de-authorization of deep-draft navigation on the MRGO. The Final Report and LEIS would identify a tentatively selected plan and that tentatively selected plan would be integrated with the on-going Louisiana Coastal Protection and Restoration Study (LACPR). 
                </P>
                <P>
                    <E T="03">Alternative 1 (Interim Report Option 2a)—Construct a Dam across the MRGO at Bayou La Loutre:</E>
                     The existing Congressional authorization for the MRGO channel would either be modified or a new authorization would be recommended to de-authorize deep-draft navigation and construct a dam. No additional Federal funds would be appropriated to maintain any navigation channel on the MRGO between the GIWW and the Gulf of Mexico; except authority may be requested to maintain existing wetland protection features along the MRGO. The dam would be constructed just south of Bayou La Loutre and would tie in with the southern Bayou La Loutre Ridge to completely block the MRGO channel. The structure would not allow passage of vessels traveling the length of the MRGO. Relic features, such as jetties and aids to navigation, would be considered for removal and/or reapplication. Construction of the closure would be completed within two years of authorization, pending receipt of Congressional appropriations. 
                </P>
                <P>
                    <E T="03">Alternative 2 (Interim Report Option 2a (phased))—Construct a Dam across the MRGO at Bayou La Loutre in Two Phases (Construct a Weir in Phase I; convert Weir to a full-closure dam in Phase II when depth of any portion of the channel measures 14 feet or less):</E>
                     The existing Congressional authorization for the MRGO channel would either be modified or a new authorization would be recommended to de-authorize deep-draft navigation and construct a dam. No additional Federal funds would be appropriated to maintain any navigation channel on the MRGO between the GIWW and the Gulf of Mexico; except authority may be requested to maintain existing wetland protection features along the MRGO. A dam would be constructed just south of Bayou La Loutre in two phases and would tie in with the southern Bayou La Loutre Ridge to totally block the MRGO channel. The first phase would be construction of a dam containing a weir 125-feet wide by 14 feet deep (The weir would be set at 14 feet to allow safe passage of 12-foot draft vessels). Once any reach of the channel shoaled in to a depth of less than 14-feet, the second phase of construction would begin. It is estimated that some reaches of the MRGO would become impassible to vessels greater than a 12-foot draft in approximately 2014. The second phase of construction would complete total closure of the MRGO by closing the weir. The completed structure would not allow passage of vessels traveling the length of the MRGO. Relic features, such as jetties and aids to navigation, would be considered for removal and/or reapplication. Phase one construction of the closure would be completed within two years of receipt of Congressional appropriations; and phase two would be completed when the depth of the navigation channel is less than 14 feet deep and Congressional appropriations are provided. 
                </P>
                <P>
                    <E T="03">Alternative 3 (Interim Report Option 3)—Cease All MRGO Navigation Channel Operations and Maintenance Dredging:</E>
                     The existing Congressional authorization for the MRGO channel would either be modified or a new authorization would be recommended to de-authorize deep-draft navigation. No additional Federal funds would be appropriated to maintain any navigation channel on the MRGO between the GIWW and the Gulf of Mexico; except authority may be requested to maintain existing wetland protection features along the MRGO. Relic features, such as jetties and aids to navigation, would be considered for removal and/or reapplication. Under this option, commercial and recreational shallow-draft vessels could still use the MRGO until the navigation channel shoals in to a depth prohibiting navigation. It is estimated that some reaches of the MRGO would become impassible to vessels greater than a 12-foot draft by approximately 2014. 
                </P>
                <P>
                    2. 
                    <E T="03">Stakeholder Involvement:</E>
                     Stakeholder involvement for this proposed action is integral to the project. Interested parties, concerned citizens, other state and Federal agencies, and private and not for profit or non-governmental organizations are strongly encouraged to participate in the development of the proposed action. Stakeholder meetings would be held throughout project development. Meeting announcements would be made as information becomes available. 
                </P>
                <P>
                    3. 
                    <E T="03">Significant Issues:</E>
                     The list of important resources and issues that would be evaluated in the EIS include, but are not limited to tidally influenced coastal wetlands (marshes and swamps), fisheries resources, wildlife resources, essential fish habitat, water quality, air quality, threatened and endangered species, recreation resources, and cultural resources. Socioeconomic items that would be evaluated in the EIS include navigation, business and industrial activity, employment, and community cohesion. 
                    <PRTPAGE P="18643"/>
                </P>
                <P>
                    4. 
                    <E T="03">Interagency Coordination and Cooperation:</E>
                     The following agencies have been informally invited to participate in the study on the LEIS: Minerals Management Service, National Marine Fisheries Service, Natural Resources Conservation Service, U.S. Environmental Protection Agency, U.S. Fish and Wildlife Service, U.S. Geological Service, Louisiana Department of Environmental Quality, Louisiana Department of Natural Resources, and the Louisiana Department of Wildlife and Fisheries. The U.S. Fish and Wildlife Service would provide a Fish and Wildlife Coordination Act Report. Coordination would be maintained with the U.S. Fish and Wildlife Service and the National Marine Fisheries Service regarding threatened and endangered species under their respective jurisdictional responsibilities. Coordination would be maintained with the National Marine Fisheries Service regarding essential fish habitat. Coordination would be maintained with the Natural Resources Conservation Service regarding prime and unique farmlands. Coordination would be maintained with the Advisory Counsel on Historic Preservation and the State Historic Preservation Officer. The Louisiana Department of Natural Resources would be consulted regarding consistency with the Coastal Zone Management Act. The Louisiana Department of Wildlife and Fisheries would be contacted concerning potential impacts to Natural and Scenic Streams. 
                </P>
                <P>
                    5. 
                    <E T="03">Environmental Consultation and Review:</E>
                     The U.S. Fish and Wildlife Service (USFWS) would be assisting in the documentation of existing conditions and assessment of effects of project alternatives through Fish and Wildlife Coordination Act consultation procedures. The USFWS would also provide a Fish and Wildlife Coordination Act report. Consultation would also be accomplished with the USFWS and the National Marine Fisheries Service (NMFS) concerning threatened and endangered species and their critical habitat. The NMFS would be consulted on the effects of this proposed action on Essential Fish Habitat. The draft EIS or a notice of its availability would be distributed to all interested agencies, organizations, and individuals. 
                </P>
                <P>
                    6. 
                    <E T="03">Public Scoping Meeting:</E>
                     Scoping meetings are not required (40 CFR 1506.8 Proposals for legislation (b)(1)) when preparing a LEIS. However, as indicated in Section 2, 
                    <E T="03">Stakeholder Involvement,</E>
                     an intensive public engagement program would continue throughout the study to solicit input from affected or interested parties. 
                </P>
                <P>
                    7. 
                    <E T="03">Estimated Date of Availability:</E>
                     The earliest date the LEIS is expected to be available is May of 2007. 
                </P>
                <SIG>
                    <DATED>Dated: April 4, 2007. </DATED>
                    <NAME>Richard P. Wagenaar, </NAME>
                    <TITLE>Colonel, U.S. Army, District Commander.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. E7-7086 Filed 4-12-07; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 3710-84-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">ENVIRONMENTAL PROTECTION AGENCY </AGENCY>
                <DEPDOC>[ER-FRL-6685-9] </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. </P>
                <P>An explanation of the ratings assigned to draft environmental impact statements  (EISs) was published in FR dated April 6, 2007 (72 FR 17156). </P>
                <HD SOURCE="HD1">Draft EISs </HD>
                <FP SOURCE="FP-1">EIS No. 20070018, ERP No. D-RUS-H05025-MO, Norborne Baseload Power Plant, Proposed Construction and Operation of a 660-megawatt Net Coal-Fired Power Plant, Carroll County, MO. </FP>
                <P>
                    <E T="03">Summary:</E>
                     EPA expressed environmental concerns about mercury emissions and the mercury risk assessment. EPA requested additional information on the mercury issue and recommended that ozone monitoring be continued throughout the ozone season. Rating EC2. 
                </P>
                <FP SOURCE="FP-1">EIS No. 20070028, ERP No. D-COE-K39104-CA, PROGRAMMATIC—Los Angeles River Revitalization Master Plan (LARRMP) Project, Implementation, Improving Natural Habitat, Water Quality, Recreation, Economic Values and Open Space, Owensmoth Avenue in Canoga Park (at the Confluence of Bell Creek and Arroyo Calabasas) and continues down stream to Washington Boulevard near the northern boundary of the City of Vernon, City of Los Angeles, Los Angeles County, CA. </FP>
                <P>
                    <E T="03">Summary:</E>
                     EPA does not object to the proposed action. Rating LO. 
                </P>
                <FP SOURCE="FP-1">EIS No. 20070039, ERP No. D-WPA-K08032-CA, Trinity Public Utilities District Direct Interconnection Project, Construct and Operate a 16-mile Long 60-Kilovolt Power Transmission Facilities, (DOE/EIS-0389, Trinity County, CA. </FP>
                <P>
                    <E T="03">Summary:</E>
                     EPA does not object to the proposed project. Rating LO. 
                </P>
                <FP SOURCE="FP-1">EIS No. 20070041, ERP No. D-AFS-L65532-OR, Five Buttes Project, Conduct Vegetation Management Activities, Implementation, Deschutes National Forest, Crescent Ranger District, Deschutes  County, OR. </FP>
                <P>
                    <E T="03">Summary:</E>
                     EPA does not object to the proposed action. Rating LO. 
                </P>
                <FP SOURCE="FP-1">EIS No. 20070048, ERP No. D-NOA-L64052-00, PROGRAMMATIC—Steller Sea Lion and Northern Fur Seal Research, Proposal to Disburse Funds and Issue Permit for Research, AK, WA, OR and CA. </FP>
                <P>
                    <E T="03">Summary:</E>
                     EPA expressed environmental concerns about unintentional lethal takes, mortality rates and impacts from research activities. EPA requested information on impact levels and tribal consultation. Rating EC2. 
                </P>
                <FP SOURCE="FP-1">EIS No. 20070006, ERP No. DS-DOE-D09800-PA, Gilberton Coal-to-Clean Fuels and Power Project, Construction and Operation a New Demonstration Plant, Updated Information to Correct Information regarding Carbon Dioxide (CO2) Emissions, Schuylkill County, PA. </FP>
                <P>
                    <E T="03">Summary:</E>
                     EPA requested that adaptive management provisions be considered to assess CO2 mitigation measures. Rating EC2. 
                </P>
                <HD SOURCE="HD1">Final EISs </HD>
                <FP SOURCE="FP-1">EIS No. 20070060, ERP No. F-AFS-F65063-WI, Twentymile Restoration Project Area, Restore Northern Hardwood Forests to an Uneven-aged Condition, Great Divide Ranger District, Chequamegon-Nicolet National Forest, Ashland and Bayfield Counties, WI. </FP>
                <P>
                    <E T="03">Summary:</E>
                     The Final EIS addressed EPA's comments, including information on habitat restoration; therefore, EPA does not object to the proposed project. 
                </P>
                <SIG>
                    <DATED>Dated: April 10, 2007 </DATED>
                    <NAME>Ken Mittelholtz, </NAME>
                    <TITLE>Environmental Protection Specialist, Office of Federal Activities.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. E7-7022 Filed 4-12-07; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 6560-50-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="18644"/>
                <AGENCY TYPE="S">ENVIRONMENTAL PROTECTION AGENCY </AGENCY>
                <DEPDOC>[ER-FRL-6685-8] </DEPDOC>
                <SUBJECT>Environmental Impacts 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>
                     Weekly receipt of Environmental Impact Statements Filed 04/02/2007 through 04/06/2007 Pursuant to 40 CFR 1506.9. 
                </P>
                <FP SOURCE="FP-1">EIS No. 20070135, Final EIS, AFS, ID, White/White Analysis Project, Preferred Alternative is 4, Vegetative Management and Watershed Improvement, Lolo Creek, Chamook Creek, White Creek, Mike White Creek, Nevada Creek, and Utah Creek, Lochsa Ranger District, Clearwater National Forest, Idaho and Clearwater County, ID, Wait Period Ends: 05/14/2007, Contact: Steve Bess 208-926-4274. </FP>
                <FP SOURCE="FP-1">EIS No. 20070136, Final EIS, COE, CA, Hemet/San Jacinto Integrated Recharge and Recovery Program,  Construction and Operation, U.S. Army COE Section 404 Permit,  Riverside County, CA, Wait Period Ends: 05/14/2007, Contact: Dr. Daniel Swenson 213-452-3414. </FP>
                <FP SOURCE="FP-1">EIS No. 20070137, Final EIS, AFS, ID, Aspen Range Timber Sale and Vegetation Treatment Project, Preferred Alternative is 5, Proposal to Treat Forested and Nonforested Vegetation, Caribou-Targhee National Forest, Soda Springs Ranger District, Caribou County, ID, Wait Period Ends: 05/14/2007, Contact: Doug Heyrend 208-547-4356. </FP>
                <FP SOURCE="FP-1">EIS No. 20070138, Final EIS, NPS, OH, Dayton Aviation Heritage National Historical Park, General Management Plan Amendment, Implementation, Dayton, OH, Wait Period Ends: 05/14/2007, Contact: Lawrence Blake 937-225-7705. </FP>
                <FP SOURCE="FP-1">EIS No. 20070139, Final EIS, MMS, 00, Gulf of Mexico Outer Continental Shelf Oil and Gas Lease  Sales: 2007-2012 Western Planning Area Sales 204, 207, 210, 215, and 218: Central Planning Area Sales 205, 206, 208, 213, 216, and 222, TX, LA, MS, AL and Fl, Wait Period Ends: 05/14/2007, Contact: Dr. Mary Boatman 703-787-1662. </FP>
                <FP SOURCE="FP-1">EIS No. 20070140, Draft EIS, NOA, 00, Programmatic—Toward an Ecosystem Approach for the Western Pacific Region: From Species-Based Fishery Management Plans to Place-Based Fishery Ecosystem Plans, Bottomfish and Seamount Groundfish, Coral Reef Ecosystems, Crustaceans, Precious Corals, Pelagics, Implementation, American Samoa, Commonwealth of the Northern Mariana Islands, Hawaii, U.S. Pacific Remote Island Area, Comment Period Ends: 05/29/2007, Contact: William Robinson 808-973-2200. </FP>
                <FP SOURCE="FP-1">EIS No. 20070141, Draft EIS, UAF, MA, Final Recommendations and Associated Actions for the 104th Fighter Wing Massachusetts Air National Guard, Base Realignment and Closure, Implementation, Westfield-Barnes Airport, Westfield, MA, Comment Period Ends: 06/01/2007, Contact: Robert Dogan 301-836-8859. </FP>
                <FP SOURCE="FP-1">EIS No. 20070142, Final EIS, BLM, WY, Maysdorf Coal Lease by Application (LBA) Tract, (Federal Coal Application WYW154432), Implementation, Campbell Counties, WY, Wait Period Ends: 05/14/2007, Contact: Nancy Doelger 307-261-7627. </FP>
                <FP SOURCE="FP-1">EIS No. 20070143, Final EIS, WPA, SD, White Wind Farm Project, Construct a Large Utility-Scale  Wind-Powered Electric Energy Generating Facility, Sherman Township, Brookings County, SD, Wait Period Ends: 05/14/2007,  Contact: Catherine Cunningham 720-962-7260. </FP>
                <HD SOURCE="HD1">Amended Notices </HD>
                <FP SOURCE="FP-1">EIS No. 20070003, Draft EIS, AFS, AK, Tongass Land and Resource Management Plan, Plan Amendment, Implementation, Tongass National Forest, AK, Comment Period Ends: 04/30/2007, Contact: Lee Kramer 907-586-8811, Ext 225, Revision to FR Notice Published 01/12/2007: Extending Comment Period from 4/10/2007 to 04/30/2007. </FP>
                <SIG>
                    <DATED>Dated: April 10, 2007. </DATED>
                    <NAME>Ken Mittelholtz, </NAME>
                    <TITLE>Environmental Protection Specialist, Office of Federal Activities.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. E7-7021 Filed 4-12-07; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 6560-50-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">ENVIRONMENTAL PROTECTION AGENCY</AGENCY>
                <DEPDOC>[EPA-HQ-OPP-2007-0260; FRL-8123-1]</DEPDOC>
                <SUBJECT>The Association of American Pesticide Control Officials (AAPCO)/State FIFRA Issues Research and Evaluation Group (SFIREG) Working Committee on Water Quality/Pesticide Disposal (WC/WQ/PD); Notice of Public Meeting</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>The Association of American Pesticide Control Officials (AAPCO)/State FIFRA Issues Research and Evaluation Group (SFIREG) Working Committee on Water Quality/Pesticide Disposal (WC/WQ/PD) will hold a 2-day meeting, beginning on April 30, 2007 and ending May 1, 2007. This notice announces the location and times for the meeting and sets forth the tentative agenda topics.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The meeting will be held on April 30, 2007 from 8.30 a.m. to 5 p.m. and 8:30 a.m. to 12 noon on May 1, 2007.</P>
                </DATES>
                <P>
                    To request accommodation of a disability, please contact the person listed under 
                    <E T="02">FOR FURTHER INFORMATON CONTACT</E>
                    , preferably at least 10 days prior to the meeting, to give EPA as much time as possible to process your request.
                </P>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>The meeting will be held at USEPA 2777 South Crystal Dr., One Potomac Yards (South Bldg.) 4th Floor Conference Center/South</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Georgia McDuffie, Field and External Affairs Division (7506P), Office of Pesticide Programs, Environmental Protection Agency, 1200 Pennsylvania Ave., NW., Washington, DC 20460-0001; telephone number: (703) 605-0195; fax number: (703) 308-1850; e-mail address: 
                        <E T="03">mcduffie.georgia@epa.gov</E>
                         or Philip H. Gray, SFIREG Executive Secretary, P.O. Box 1249, Hardwick, VT 05843-1249; telephone number: (802) 472-6956; fax (802) 472-6957; e-mail address: 
                        <E T="03">aapco@plainfield.bypass.com</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 interested in SFIREG information exchange relationship with EPA regarding important issues related to human health, environmental exposure to pesticides, and insight into EPA's decision-making process are invited and encouraged to attend the meetings and participate as appropriate.” Potentially affected entities may include, but are not limited to: Those persons who are or may be required to conduct testing of chemical substances under the Federal Food, Drug and Cosmetic Act (FFDCA), or the Federal Insecticide, Fungicide, and Rodenticide Act (FIFRA).</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 a docket for this action under docket 
                    <PRTPAGE P="18645"/>
                    identification (ID) number EPA-HQ-OPP-2006-0260. Publicly available docket materials are available either in the electronic docket at 
                    <E T="03">http://www.regulations.gov</E>
                    , or, if only available in hard copy, at the Office of Pesticide Programs (OPP) Regulatory Public Docket in Rm. S-4400, One Potomac Yard (South Bldg.), 2777 S. Crystal Dr., Arlington, VA. The hours of operation of this Docket Facility are from 8:30 a.m. to 4 p.m., Monday through Friday, excluding legal holidays. The Docket Facility telephone number is (703) 305-5805.
                </P>
                <HD SOURCE="HD1">II. Tentative Agenda</HD>
                <P>1. Chemigation PRN 87-1: Subsurface Drip Irrigation and Water Quality Concerns</P>
                <P>2. Pesticide Degradates</P>
                <P>3. Drinking Water Levels of Comparison and State Review Triggers for New Active Ingredients</P>
                <P>4. Safe Drinking Water Act and OPP Interaction on Maximum Contaminant Levels in Public Drinking Water Supplies</P>
                <P>5. Draft Protocols for State Retrieval of Registration Data</P>
                <P>6. Container Recycling: State Survey and Draft Rule</P>
                <P>7. SFIREG WQ/PD State Reporting Form: Results and Future</P>
                <P>8. Exposure Modeling Public Meeting: Activities Report</P>
                <P>9. Performance Measures, “Pesticides of Interest” List, On-line Reporting</P>
                <P>10. ASIWPCA-SFIREG Partnerships</P>
                <P>11. SFIREG WQ/PD Committee Structure and Member Term Expirations</P>
                <P>12. Federal Aquatic Life Benchmarks Update</P>
                <P>13. Sate-level Aquatic Life Criteria Development</P>
                <P>14. Atrazine Issues: Eco-monitoring, Scientific Advisory Panel Update,State-Federal Program Interaction</P>
                <P>15. EPA Updates:</P>
                <P>a. Office of Pesticide Programs Update</P>
                <P>b. Office of Enforcement Compliance Assurance Update</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects</HD>
                    <P>Environmental protection.</P>
                </LSTSUB>
                <SIG>
                    <DATED>Dated: April 5, 2007.</DATED>
                    <NAME> Kevin Keaney,</NAME>
                    <TITLE>Director, Field External Affairs Division, Office of Pesticide Programs</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. E7-6945 Filed 4-12-07; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6560-50-S</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">ENVIRONMENTAL PROTECTION AGENCY</AGENCY>
                <DEPDOC>[EPA-HQ-OPP-2007-0005; FRL-8121-1]</DEPDOC>
                <SUBJECT>Notice of Receipt of Requests to Voluntarily Cancel Certain Pesticide Registrations</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 request by registrants to voluntarily cancel certain pesticide registrations and providing a public comment period.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Unless a request is withdrawn by October 10, 2007 or May 14, 2007 for registrations for which the registrant requested a waiver of the 180-day comment period, orders will be issued canceling these registrations. The Agency will consider withdrawal requests postmarked no later than October 10, 2007 or May 14, 2007, whichever is applicable. Comments must be received on or before October 10, 2007 or May 14, 2007, for those registrations where the 180-day comment period has been waived.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Submit your comments and your withdrawal request, identified by docket identification (ID) number EPA-HQ-OPP-2007-0005, by one of the following methods:</P>
                    <P>
                        • 
                        <E T="03">Federal eRulemaking Portal</E>
                        : 
                        <E T="03">http://www.regulations.gov</E>
                        . Follow the on-line instructions for submitting comments.
                    </P>
                    <P>
                        • 
                        <E T="03">Mail</E>
                        : Office of Pesticide Programs (OPP) Regulatory Public Docket (7502P), Environmental Protection Agency, 1200 Pennsylvania Ave., NW., Washington, DC 20460-0001. Written withdrawal requests should be to the Attention of: John Jamula, Information Technology and Resources Management Division (7502P), at the address above.
                    </P>
                    <P>
                        • 
                        <E T="03">Delivery</E>
                        : OPP Regulatory Public Docket (7502P), Environmental Protection Agency, Rm. S-4400, One Potomac Yard (South Building), 2777 S. Crystal Drive, Arlington, VA. Deliveries are only accepted during the Docket's normal hours of operation (8:30 a.m. to 4 p.m., Monday through Friday, excluding legal holidays). Special arrangements should be made for deliveries of boxed information. The Docket telephone number is (703) 305-5805.
                    </P>
                    <P>
                        <E T="03">Instructions</E>
                        : Direct your comments to docket ID number EPA-HQ-OPP-2007-0005. EPA's policy is that all comments received will be included in the docket without change and may be made available on-line at 
                        <E T="03">http://www.regulations.gov</E>
                        , including any personal information provided, unless the comment includes information claimed to be Confidential Business Information (CBI) or other information whose disclosure is restricted by statute. Do not submit information that you consider to be CBI or otherwise protected through regulations.gov or e-mail. The Federal regulations.gov website is an “anonymous access” system, which means EPA will not know your identity or contact information unless you provide it in the body of your comment. If you send an e-mail comment directly to EPA without going through regulations.gov, your e-mail address will be automatically captured and included as part of the comment that is placed in the docket and made available on the Internet. If you submit an electronic comment, EPA recommends that you include your name and other contact information in the body of your comment and with any disk or CD-ROM you submit. 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. Electronic files should avoid the use of special characters, any form of encryption, and be free of any defects or viruses.
                    </P>
                    <P>
                        <E T="03">Docket</E>
                        : All documents in the docket are listed in the docket index. Although listed in the index, some information is not publicly available, e.g., CBI or other information whose disclosure is restricted by statute. Certain other material, such as copyrighted material, is not placed on the Internet and will be publicly available only in hard copy form. Publicly available docket materials are available either in the electronic docket at 
                        <E T="03">http://www.regulations.gov</E>
                        , or, if only available in hard copy, at the OPP Regulatory Public Docket in Rm. S-4400, One Potomac Yard (South Building), 2777 S. Crystal Drive, Arlington, VA. The hours of operation of this Docket Facility are from 8:30 a.m. to 4 p.m., Monday through Friday, excluding legal holidays. The Docket telephone number is (703) 305-5805.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        John Jamula, Information Technology and Resources Management Division (7502P), Office of Pesticide Programs, Environmental Protection Agency, 1200 Pennsylvania Ave., NW., Washington, DC 20460-0001; telephone number: (703) 305-6426; e-mail address: 
                        <E T="03">jamula.john@epa.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <PRTPAGE P="18646"/>
                <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. What Should I Consider as I Prepare My Comments for EPA?</HD>
                <P>
                    1. 
                    <E T="03">Submitting CBI</E>
                    . Do not submit this information to EPA through regulations.gov or e-mail. Clearly mark the part or all of the information that you claim to be CBI. For CBI information in a disk or CD ROM that you mail to EPA, 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 claimed as CBI. In addition to one complete version of the comment that includes 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. Information so marked will not be disclosed except in accordance with procedures set forth in 40 CFR part 2.
                </P>
                <P>
                    2. 
                    <E T="03">Tips for preparing your comments</E>
                    . When submitting comments, remember to:
                </P>
                <P>
                    i. Identify the document by docket ID number and other identifying information (subject heading, 
                    <E T="04">Federal Register</E>
                     date and page number).
                </P>
                <P>ii. Follow directions. The Agency may ask you to respond to specific questions or organize comments by referencing a Code of Federal Regulations (CFR) part or section number.</P>
                <P>iii. Explain why you agree or disagree; suggest alternatives and substitute language for your requested changes.</P>
                <P>iv. Describe any assumptions and provide any technical information and/or data that you used.</P>
                <P>v. If you estimate potential costs or burdens, explain how you arrived at your estimate in sufficient detail to allow for it to be reproduced.</P>
                <P>vi. Provide specific examples to illustrate your concerns and suggest alternatives.</P>
                <P>vii. Explain your views as clearly as possible, avoiding the use of profanity or personal threats.</P>
                <P>viii. Make sure to submit your comments by the comment period deadline identified.</P>
                <HD SOURCE="HD1">II. What Action is the Agency Taking?</HD>
                <P>This notice announces receipt by the Agency of applications from registrants to cancel 72 pesticide products registered under section 3 or 24(c) of FIFRA. These registrations are listed in sequence by registration number (or company number and 24(c) number) in the following Table 1:</P>
                <GPOTABLE COLS="3" OPTS="L2,i1" CDEF="s25,r60,r90">
                    <TTITLE>
                        <E T="04">Table 1.—Registrations With Pending Requests for Cancellation</E>
                    </TTITLE>
                    <BOXHD>
                        <CHED H="1">Registration no.</CHED>
                        <CHED H="1">Product Name</CHED>
                        <CHED H="1">Chemical Name</CHED>
                    </BOXHD>
                    <ROW RUL="s">
                        <ENT I="01" O="xl">000100 AL-03-0004</ENT>
                        <ENT O="xl">Tilt Fungicide</ENT>
                        <ENT O="xl">Propiconazole</ENT>
                    </ROW>
                    <ROW RUL="n,n,s">
                        <ENT I="01" O="xl">000100 AL-04-0002</ENT>
                        <ENT O="xl">Quilt Fungicide</ENT>
                        <ENT O="xl">Propiconazole</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="x1"> </ENT>
                        <ENT O="x1"> </ENT>
                        <ENT O="xl">Azoxystrobin</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="xl">000100 CA-96-0012</ENT>
                        <ENT O="xl">Mefenoxam EC</ENT>
                        <ENT O="xl">D-Alanine, N-(2,6-dimethylphenyl)-N-(methoxyacetyl)-, methyl ester</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="xl">000100 CO-02-0005</ENT>
                        <ENT O="xl">Actara</ENT>
                        <ENT O="xl">Thiamethoxam</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="xl">000100 ID-02-0004</ENT>
                        <ENT O="xl">Actara</ENT>
                        <ENT O="xl">Thiamethoxam</ENT>
                    </ROW>
                    <ROW RUL="n,n,s">
                        <ENT I="01" O="xl">000100 ID-05-0007</ENT>
                        <ENT O="xl">Quilt Fungicide</ENT>
                        <ENT O="xl">Propiconazole</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="x1"> </ENT>
                        <ENT O="x1"> </ENT>
                        <ENT O="xl">Azoxystrobin</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="xl">000100 ID-95-0012</ENT>
                        <ENT O="xl">Tilt Fungicide</ENT>
                        <ENT O="xl">Propiconazole</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="xl">000100 ID-98-0004</ENT>
                        <ENT O="xl">Tilt Fungicide</ENT>
                        <ENT O="xl">Propiconazole</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="xl">000100 IN-98-0003</ENT>
                        <ENT O="xl">Tilt Fungicide</ENT>
                        <ENT O="xl">Propiconazole</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="xl">000100 MI-03-0005</ENT>
                        <ENT O="xl">Dual Magnum Herbicide</ENT>
                        <ENT O="xl">S-Metolachlor</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="xl">000100 MI-04-0007</ENT>
                        <ENT O="xl">Dual Magnum Herbicide</ENT>
                        <ENT O="xl">S-Metolachlor</ENT>
                    </ROW>
                    <ROW RUL="n,n,s">
                        <ENT I="01" O="xl">000100 OK-04-0001</ENT>
                        <ENT O="xl">Quilt Fungicide</ENT>
                        <ENT O="xl">Propiconazole</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="x1"> </ENT>
                        <ENT O="x1"> </ENT>
                        <ENT O="xl">Azoxystrobin</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="xl">000100 TX-06-0019</ENT>
                        <ENT O="xl">Envoke Herbicide</ENT>
                        <ENT O="xl">2-Pyridinesulfonamide, N-[[(4,6-dimethoxy-2-pyrimidinyl)amino]carbonyl]-3-(2,2,2-trifluoroet</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="xl">000100 WA-01-0030</ENT>
                        <ENT O="xl">Actara 25 WG</ENT>
                        <ENT O="xl">Thiamethoxam</ENT>
                    </ROW>
                    <ROW RUL="n,n,s">
                        <ENT I="01" O="xl">000100 WA-04-0026</ENT>
                        <ENT O="xl">Quilt Fungicide</ENT>
                        <ENT O="xl">Propiconazole</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <PRTPAGE P="18647"/>
                        <ENT I="01" O="x1"> </ENT>
                        <ENT O="x1"> </ENT>
                        <ENT O="xl">Azoxystrobin</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="xl">000100 WA-95-0033</ENT>
                        <ENT O="xl">Tilt Fungicide</ENT>
                        <ENT O="xl">Propiconazole</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="xl">000100 WA-98-0018</ENT>
                        <ENT O="xl">Tilt Fungicide</ENT>
                        <ENT O="xl">Propiconazole</ENT>
                    </ROW>
                    <ROW RUL="n,n,s">
                        <ENT I="01" O="xl">000239-02342</ENT>
                        <ENT O="xl">Weed Killer M</ENT>
                        <ENT O="xl">2,4-D, dimethylamine salt</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="x1"> </ENT>
                        <ENT O="x1"> </ENT>
                        <ENT O="xl">Mecoprop, dimethylamine salt</ENT>
                    </ROW>
                    <ROW RUL="n,n,s">
                        <ENT I="01" O="xl">000239-02485</ENT>
                        <ENT O="xl">Weed-B-Gon Intermediate</ENT>
                        <ENT O="xl">2,4-D, dimethylamine salt</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="x1"> </ENT>
                        <ENT O="x1"> </ENT>
                        <ENT O="xl">Mecoprop, dimethylamine salt</ENT>
                    </ROW>
                    <ROW RUL="n,n,s">
                        <ENT I="01" O="xl">000239-02581</ENT>
                        <ENT O="xl">Weed-B-Gon Ready Spray Lawn Weed Killer</ENT>
                        <ENT O="xl">2,4-D, dimethylamine salt</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="x1"> </ENT>
                        <ENT O="x1"> </ENT>
                        <ENT O="xl">Mecoprop, dimethylamine salt</ENT>
                    </ROW>
                    <ROW RUL="n,n,s">
                        <ENT I="01" O="xl">000239-02621</ENT>
                        <ENT O="xl">Weed-B-Gon Lawn Weed Killer Formula T</ENT>
                        <ENT O="xl">Benzoic acid, 3,6-dichloro-2-methoxy-, compd with N-methylmethanamine (1:1)</ENT>
                    </ROW>
                    <ROW RUL="n,n,s">
                        <ENT I="01" O="x1"> </ENT>
                        <ENT O="x1"> </ENT>
                        <ENT O="xl">MCPA, dimethylamine salt</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="x1"> </ENT>
                        <ENT O="x1"> </ENT>
                        <ENT O="xl">Mecoprop, dimethylamine salt</ENT>
                    </ROW>
                    <ROW RUL="n,n,s">
                        <ENT I="01" O="xl">000239-02623</ENT>
                        <ENT O="xl">Triamine Jet Weeder</ENT>
                        <ENT O="xl">2,4-D, dimethylamine salt</ENT>
                    </ROW>
                    <ROW RUL="n,n,s">
                        <ENT I="01" O="x1"> </ENT>
                        <ENT O="x1"> </ENT>
                        <ENT O="xl">Dimethylamine 2-(2,4-dichlorophenoxy)propionate</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="x1"> </ENT>
                        <ENT O="x1"> </ENT>
                        <ENT O="xl">Mecoprop, dimethylamine salt</ENT>
                    </ROW>
                    <ROW RUL="n,n,s">
                        <ENT I="01" O="xl">000239-02634</ENT>
                        <ENT O="xl">Weed-B-Gon Weed Killer Formula II</ENT>
                        <ENT O="xl">Benzoic acid, 3,6-dichloro-2-methoxy-, compd with N-methylmethanamine (1:1)</ENT>
                    </ROW>
                    <ROW RUL="n,n,s">
                        <ENT I="01" O="x1"> </ENT>
                        <ENT O="x1"> </ENT>
                        <ENT O="xl">MCPA, dimethylamine salt</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="x1"> </ENT>
                        <ENT O="x1"> </ENT>
                        <ENT O="xl">Mecoprop, dimethylamine salt</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="xl">000241 WA-92-0015</ENT>
                        <ENT O="xl">Prowl 3.3 EC Herbicide</ENT>
                        <ENT O="xl">Pendimethalin</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="xl">000241 WA-96-0019</ENT>
                        <ENT O="xl">Prowl 3.3 EC Herbicide</ENT>
                        <ENT O="xl">Pendimethalin</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="xl">000241 WA-96-0020</ENT>
                        <ENT O="xl">Avenge Wild Oat Herbicide</ENT>
                        <ENT O="xl">Difenzoquat methyl sulfate</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="xl">000241 WA-96-0021</ENT>
                        <ENT O="xl">Assert Herbicide</ENT>
                        <ENT O="xl">Imazamethabenz</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="xl">000264 WA-90-0009</ENT>
                        <ENT O="xl">Gustafson LSP Flowable Fungicide</ENT>
                        <ENT O="xl">Thiabendazole</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="xl">000400-00049</ENT>
                        <ENT O="xl">Alanap-L</ENT>
                        <ENT O="xl">Naptalam, sodium salt</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="xl">000400-00155</ENT>
                        <ENT O="xl">Harvade-5F</ENT>
                        <ENT O="xl">Dimethipin</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="xl">000400-00398</ENT>
                        <ENT O="xl">Harvade-25F</ENT>
                        <ENT O="xl">Dimethipin</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="xl">000400-00432</ENT>
                        <ENT O="xl">Harvade Technical</ENT>
                        <ENT O="xl">Dimethipin</ENT>
                    </ROW>
                    <ROW RUL="n,n,s">
                        <ENT I="01" O="xl">000400-00505</ENT>
                        <ENT O="xl">Leafless</ENT>
                        <ENT O="xl">Dimethipin</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="x1"> </ENT>
                        <ENT O="x1"> </ENT>
                        <ENT O="xl">Thidiazuron</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="xl">000432-01288</ENT>
                        <ENT O="xl">Baygon Technical</ENT>
                        <ENT O="xl">Propoxur</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="xl">000464-00709</ENT>
                        <ENT O="xl">Ucarcide 115 Antimicrobial</ENT>
                        <ENT O="xl">Glutaraldehyde</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="xl">000769-00638</ENT>
                        <ENT O="xl">Smcp Granular Dy-Kil-20 Non-Selective Weed &amp; Grass Kill</ENT>
                        <ENT O="xl">Diuron</ENT>
                    </ROW>
                    <ROW RUL="n,n,s">
                        <PRTPAGE P="18648"/>
                        <ENT I="01" O="xl">000875-00090</ENT>
                        <ENT O="xl">Per-Vad Low Foam Liquid Acid Sanitizer</ENT>
                        <ENT O="xl">Phosphoric acid</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="x1"> </ENT>
                        <ENT O="x1"> </ENT>
                        <ENT O="xl">Sulfonated oleic acid, sodium salt</ENT>
                    </ROW>
                    <ROW RUL="n,n,s">
                        <ENT I="01" O="xl">001381-00089</ENT>
                        <ENT O="xl">Midland Hy Py Fogging Stock Spray</ENT>
                        <ENT O="xl">Piperonyl butoxide</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="x1"> </ENT>
                        <ENT O="x1"> </ENT>
                        <ENT O="xl">Pyrethrins</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="xl">005481-00009</ENT>
                        <ENT O="xl">Alco Fly Fighter Double Strength Fly Bait</ENT>
                        <ENT O="xl">Dichlorvos</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="xl">005481-00341</ENT>
                        <ENT O="xl">Alco Flea Collar for Dogs-Black.</ENT>
                        <ENT O="xl">Dichlorvos</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="xl">005481-00342</ENT>
                        <ENT O="xl">Alco Flea Collar for Cats - White</ENT>
                        <ENT O="xl">Dichlorvos</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="xl">005481-00343</ENT>
                        <ENT O="xl">Alco Flea Collar for Dogs - Clear</ENT>
                        <ENT O="xl">Dichlorvos</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="xl">005481-00345</ENT>
                        <ENT O="xl">Alco Flea Collar for Cats-Clear.</ENT>
                        <ENT O="xl">Dichlorvos</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="xl">005481-00346</ENT>
                        <ENT O="xl">Alco Flea Collar for Dogs - Glitters</ENT>
                        <ENT O="xl">Dichlorvos</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="xl">005481-00347</ENT>
                        <ENT O="xl">Alco Flea Collar for Cats-Glitters.</ENT>
                        <ENT O="xl">Dichlorvos</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="xl">005905-00523</ENT>
                        <ENT O="xl">Propanil 60D</ENT>
                        <ENT O="xl">Propanil</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="xl">010163 OR-99-0056</ENT>
                        <ENT O="xl">Botran 75 W-Fungicide</ENT>
                        <ENT O="xl">Dicloran</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="xl">010163 WA-95-0015</ENT>
                        <ENT O="xl">Imidan 70-WP Agricultural Insecticide</ENT>
                        <ENT O="xl">Phosmet</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="xl">011603-00028</ENT>
                        <ENT O="xl">Bromacil Technical</ENT>
                        <ENT O="xl">Bromacil</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="xl">019713 OR-90-0023</ENT>
                        <ENT O="xl">Drexel Diuron 4l Herbicide</ENT>
                        <ENT O="xl">Diuron</ENT>
                    </ROW>
                    <ROW RUL="n,n,s">
                        <ENT I="01" O="xl">034913-00017</ENT>
                        <ENT O="xl">Knockout Granular Weed Killer</ENT>
                        <ENT O="xl">Diuron</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="x1"> </ENT>
                        <ENT O="x1"> </ENT>
                        <ENT O="xl">Sulfometuron</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="xl">035935-00032</ENT>
                        <ENT O="xl">Clopyralid Technical</ENT>
                        <ENT O="xl">Clopyralid</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="xl">055260 OR-04-0025</ENT>
                        <ENT O="xl">Syllit Flow Fungicide</ENT>
                        <ENT O="xl">Dodine</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="xl">056228-00008</ENT>
                        <ENT O="xl">Pigeon Bait Strychnine Corn</ENT>
                        <ENT O="xl">Strychnine</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="xl">056228-00027</ENT>
                        <ENT O="xl">1.6% Strychnine Paste</ENT>
                        <ENT O="xl">Strychnine</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="xl">059639 WA-01-0006</ENT>
                        <ENT O="xl">Cobra Herbicide</ENT>
                        <ENT O="xl">Lactofen</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="xl">061282 OR-01-0018</ENT>
                        <ENT O="xl">Hopkins Zinc Phosphide Pellets</ENT>
                        <ENT O="xl">Zinc phosphide (Zn3P2)</ENT>
                    </ROW>
                    <ROW RUL="n,n,s">
                        <ENT I="01" O="xl">061483-00092</ENT>
                        <ENT O="xl">Patriot Plus Insecticide Ear Tag</ENT>
                        <ENT O="xl">Diazinon</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="x1"> </ENT>
                        <ENT O="x1"> </ENT>
                        <ENT O="xl">Tetrachlorvinphos</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="xl">062719-00096</ENT>
                        <ENT O="xl">Balan 2.5G</ENT>
                        <ENT O="xl">Benfluralin</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="xl">062719-00127</ENT>
                        <ENT O="xl">Balan Dry Flowable</ENT>
                        <ENT O="xl">Benfluralin</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="xl">062719-00146</ENT>
                        <ENT O="xl">Turf Fertilizer contains Balan 0.92%</ENT>
                        <ENT O="xl">Benfluralin</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="xl">062719-00147</ENT>
                        <ENT O="xl">Turf Fertilizer contains Balan 1.15%</ENT>
                        <ENT O="xl">Benfluralin</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="xl">062719-00148</ENT>
                        <ENT O="xl">Turf Fertilizer contains Balan 1.25%</ENT>
                        <ENT O="xl">Benfluralin</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="xl">062719 AZ-00-0001</ENT>
                        <ENT O="xl">Goal 2XL Herbicide</ENT>
                        <ENT O="xl">Oxyfluorfen</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="xl">062719 OR-94-0035</ENT>
                        <ENT O="xl">Lorsban 4E-HF</ENT>
                        <ENT O="xl">Chlorpyrifos</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <PRTPAGE P="18649"/>
                        <ENT I="01" O="xl">066222 AZ-02-0009</ENT>
                        <ENT O="xl">Thiodan 3 EC Insecticide</ENT>
                        <ENT O="xl">Endosulfan</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="xl">066222 WA-05-0003</ENT>
                        <ENT O="xl">Rimon 0.83 EC</ENT>
                        <ENT O="xl">Novaluron</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="xl">066330-00217</ENT>
                        <ENT O="xl">Dicofol 4 EC</ENT>
                        <ENT O="xl">Dicofol</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="xl">068098 WA-98-0014</ENT>
                        <ENT O="xl">Mycoshield Brand of Agricultural Terramycin</ENT>
                        <ENT O="xl">Calcium oxytetracycline</ENT>
                    </ROW>
                    <ROW RUL="n,n,s">
                        <ENT I="01" O="xl">070627-00039</ENT>
                        <ENT O="xl">Johnson Wax Professional Contact Insecticide</ENT>
                        <ENT O="xl">d-trans-Chrysanthemum monocarboxylic ester of dl-2-allyl-4-hydroxy-3-methyl-2-cyclopenten-1-</ENT>
                    </ROW>
                    <ROW RUL="n,n,s">
                        <ENT I="01" O="x1"> </ENT>
                        <ENT O="x1"> </ENT>
                        <ENT O="xl">4,7-Methano-1H-isoindole-1,3(2H)-dione, 2-(2-ethylhexyl)-3a,4,7,7a-tetrahydro-</ENT>
                    </ROW>
                    <ROW RUL="n,n,s">
                        <ENT I="01" O="x1"> </ENT>
                        <ENT O="x1"> </ENT>
                        <ENT O="xl">Piperonyl butoxide</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="x1"> </ENT>
                        <ENT O="x1"> </ENT>
                        <ENT O="xl">Pyrethrins</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="xl">071579 WA-98-0008</ENT>
                        <ENT O="xl">Harvade-5f</ENT>
                        <ENT O="xl">Dimethipin</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01" O="xl">072106-00002</ENT>
                        <ENT O="xl">Evergreen Lawn Food with Weed Control 12-4-4</ENT>
                        <ENT O="xl">2,4-D, dimethylamine salt</ENT>
                    </ROW>
                </GPOTABLE>
                <P>A request to waive the 180-day comment period has been received for the following registrations: 432-1288; 769-638; 5481-9; 5481-341; 5481-342; 5481-343; 5481-345 5481-346; 5481-347. Therefore, the 30-day comment period will apply for these registrations.</P>
                <P>
                    Unless a request is withdrawn by the registrant by October 10, 2007 or by May 14, 2007 for those registrations with a 30-day comment period, orders will be issued canceling all of these registrations. A person may submit comments to EPA as provided in 
                    <E T="02">ADDRESSES</E>
                     and Unit I. of the 
                    <E T="02">SUPPLEMENTARY INFORMATION</E>
                     above. However, because FIFRA section 6(f)(1)(A) allows a registrant to request cancellation of its pesticide registrations at any time, users or anyone else desiring retention of those pesticides listed in Table 1 may want to contact the applicable registrant in Table 2 directly during this period to request that the registrant retain the pesticide registration or to discuss the possibility of transferring the registration. A user seeking to apply for its own registration of that pesticide may submit comments requesting EPA not to cancel a registration until its “me-too” registration is granted.
                </P>
                <P>
                    Table 2 of this unit includes the names and 
                    <E T="02">ADDRESSES</E>
                     of record for all registrants of the products in Table 1 of this unit, in sequence by EPA company number:
                </P>
                <GPOTABLE COLS="2" OPTS="L2,i1" CDEF="s45,r120">
                    <TTITLE>
                        <E T="04">Table 2.—Registrants Requesting Voluntary Cancellation</E>
                    </TTITLE>
                    <BOXHD>
                        <CHED H="1">EPA Company No.</CHED>
                        <CHED H="1">Company Name and Address</CHED>
                    </BOXHD>
                    <ROW RUL="s">
                        <ENT I="01" O="xl">000100</ENT>
                        <ENT O="xl">Syngenta Crop Protection, Inc., Attn: Regulatory Affairs, Po Box 18300, Greensboro, NC 274198300</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="xl">000239</ENT>
                        <ENT O="xl">The Ortho Business Group, d/b/a The Scotts Co., Po Box 190, Marysville, OH 43040</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="xl">000241</ENT>
                        <ENT O="xl">BASF Corp., Po Box 13528, Research Triangle Park, NC 277093528</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="xl">000264</ENT>
                        <ENT O="xl">Bayer Cropscience LP, 2 T.W. Alexander Drive, Research Triangle Park, NC 27709</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="xl">000400</ENT>
                        <ENT O="xl">Chemtura USA Corp., 199 Benson Rd. (2-4), Middlebury, CT 06749</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="xl">000432</ENT>
                        <ENT O="xl">Bayer Environmental Science, A Business Group of Bayer Cropscience LP, Po Box 12014, Research Triangle Park, NC 27709</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="xl">000464</ENT>
                        <ENT O="xl">Dow Chemical Co., The, Attn: George Paul, 1803 Building, Midland, MI 48674</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="xl">000769</ENT>
                        <ENT O="xl">Value Gardens Supply, LLC, d/b/a Value Garden Supply, Po Box 585, Saint Joseph, MO 64502</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="xl">000875</ENT>
                        <ENT O="xl">Johnsondiversey, Inc., 8310 16th Street, Sturtevant, WI 53177</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="xl">001381</ENT>
                        <ENT O="xl">Agriliance, LLC, Po Box 64089, St. Paul, MN 551640089</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="xl">005481</ENT>
                        <ENT O="xl">Amvac Chemical Corp., Attn: Jon C. Wood, 4695 Macarthur Ct., Suite 1250, Newport Beach, CA 926601706</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <PRTPAGE P="18650"/>
                        <ENT I="01" O="xl">005905</ENT>
                        <ENT O="xl">Helena Chemical Co., 225 Schilling Blvd., Suite 300, Collierville, TN 38017</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="xl">010163</ENT>
                        <ENT O="xl">Gowan Co, Po Box 5569, Yuma, AZ 853665569</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="xl">011603</ENT>
                        <ENT O="xl">Makhteshim-Agan of North America Inc., Agent For: Agan Chem Mfg, Ltd, 4515 Falls of Neuse Rd Ste 300, Raleigh, NC 27609</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="xl">019713</ENT>
                        <ENT O="xl">Drexel Chemical Co., Po Box 13327, Memphis, TN 381130327</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="xl">034913</ENT>
                        <ENT O="xl">SSI Maxim Co., Inc., PO Box 1954, Kilgore, TX 75663</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="xl">035935</ENT>
                        <ENT O="xl">Nufarm Limited, Agent For: Nufarm Limited, PO Box 13439, Rtp, NC 27709</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="xl">055260</ENT>
                        <ENT O="xl">Ceres International LLC, Agent For: Agriphar S.A., 1087 Heartsease Drive, West Chester, PA 19382</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="xl">056228</ENT>
                        <ENT O="xl">U.S. Department of Agriculture, Animal and Plant Health Inspection Service, 4700 River Rd, Unit 149, Riverdale, MD 20737</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="xl">059639</ENT>
                        <ENT O="xl">Valent U.S.A. Corp., PO Box 8025, Walnut Creek, CA 94596</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="xl">061282</ENT>
                        <ENT O="xl">Hacco, Inc., 110 Hopkins Drive, Randolph, WI 539561316</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="xl">061483</ENT>
                        <ENT O="xl">KMG-Bernuth, Inc., PO Box 80, Ellwood, KS 66024</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="xl">062719</ENT>
                        <ENT O="xl">Dow Agrosciences LLC, 9330 Zionsville Rd 308/2E, Indianapolis, IN 462681054</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="xl">066222</ENT>
                        <ENT O="xl">Makhteshim-Agan of North America Inc., 4515 Falls of Neuse Rd Ste 300, Raleigh, NC 27609</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="xl">066330</ENT>
                        <ENT O="xl">Arysta Lifescience North America Corp., 15401 Weston Parkway, Suite 150, Cary, NC 27513</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="xl">068098</ENT>
                        <ENT O="xl">Mt. Adams Orchard Corp., PO Box 1588, Yakima, WA 98907</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="xl">070627</ENT>
                        <ENT O="xl">Johnsondiversey, Inc., PO Box 902, Sturtevant, WI 53177</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01" O="xl">071579</ENT>
                        <ENT O="xl">Association of Basin Nurseries, PO Box 1339, Wenatchee, WA 98807</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01" O="xl">072106</ENT>
                        <ENT O="xl">Waupaca Northwoods LLC, d/b/a Waupaca Materials, Po Box 569, Waupaca, WI 54981</ENT>
                    </ROW>
                </GPOTABLE>
                <HD SOURCE="HD1">III. What is the Agency's Authority for Taking this Action?</HD>
                <P>
                    Section 6(f)(1)(A) of FIFRA provides that a registrant of a pesticide product may at any time request that any of its pesticide registrations be canceled. 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>
                     and provide for a 30-day public comment period. In addition, where a pesticide is registered for a minor agricultural use and the Administrator determines that cancellation or termination of that use would adversely affect the availability of the pesticide for use, FIFRA section 6(f)(1)(C) requires EPA to provide a 180-day period before approving or rejecting the section 6(f) request unless:
                </P>
                <P>1. The registrant requests a waiver of the 180-day period, or</P>
                <P>2. The Administrator determines that continued use of the pesticide would pose an unreasonable adverse effect on the environment.</P>
                <HD SOURCE="HD1">IV. Procedures for Withdrawal of Request</HD>
                <P>
                    Registrants who choose to withdraw a request for cancellation must submit such withdrawal in writing to the person listed under 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                    , postmarked before October 10, 2007 or before May 14, 2007 for those registrations where the 180-day comment period has been waived. This written withdrawal of the request for cancellation will apply only to the applicable FIFRA section 6(f)(1) request listed in this notice. If the product(s) have been subject to a previous cancellation action, the effective date of cancellation and all other provisions of any earlier cancellation action are controlling. The withdrawal request must also include a commitment to pay any reregistration fees due, and to fulfill any applicable unsatisfied data requirements.
                </P>
                <HD SOURCE="HD1">V. Provisions for Disposition of Existing Stocks</HD>
                <P>
                    The effective date of cancellation will be the date of the cancellation order. The orders effecting these requested cancellations will generally permit a registrant to sell or distribute existing stocks for 1 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>
                    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. 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 the EPA-approved label and labeling of the affected product. Exception to these general rules will be made in specific 
                    <PRTPAGE P="18651"/>
                    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.
                </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects</HD>
                    <P>Environmental protection, Pesticides and pests.</P>
                </LSTSUB>
                <SIG>
                    <DATED>Dated: April 3, 2007.</DATED>
                    <NAME>Robert Forrest,</NAME>
                    <TITLE>Acting Director, Information Technology and Resources Management Division, Office of Pesticide Programs.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. E7-7019 Filed 4-12-07; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6560-50-S</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">ENVIRONMENTAL PROTECTION AGENCY </AGENCY>
                <DEPDOC>[FRL-8298-4] </DEPDOC>
                <SUBJECT>Proposed Peripheral Party Settlement Agreement Pursuant to Section 122(h)(1) of the Comprehensive Environmental Response, Compensation, and Liability Act for the Continental Steel Corporation Site </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Environmental Protection Agency (“EPA”). </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice; request for public comment on proposed CERCLA 122(h)(1) agreement with Steve Hart, for the Continental Steel Corporation Superfund Site. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>In accordance with section 122(i)(1) of the Comprehensive Environmental Response, Compensation and Liability Act of 1984, as amended (“CERCLA”), notification is hereby given of a proposed administrative agreement concerning the Continental Steel Corporation hazardous waste site in Kokomo, Indiana (the “Site”). EPA proposes to enter into this agreement under the authority of section 122(h) and 107 of CERCLA, and with the approval of the United States Department of Justice, pursuant to the authority of the Attorney General of the United States to compromise and settle claims of the United States. The proposed agreement has been executed by Steve Hart, the owner of a portion of the Site that does not require remediation (the “Settling Party”). </P>
                    <P>Under the proposed agreement, the Settling Party will provide an irrevocable right of access to his property for staging of trailers and equipment needed during the course of Site cleanup and will make certain clean fill available to be used at the Site, if necessary, to resolve EPA's claims against it for response costs incurred and to be incurred by EPA at the Site. EPA has incurred and will continue to incur response costs performing response actions to investigate and mitigate potential imminent and substantial endangerments to human health or the environment presented or threatened by hazardous substances present at the Site. </P>
                    <P>For thirty days following the date of publication of this notice, the Environmental Protection Agency will receive written comments relating to this proposed agreement. EPA will consider all comments received and may decide not to enter this proposed agreement if comments disclose facts or considerations which indicate that the proposed agreement is inappropriate, improper or inadequate. </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments on the proposed agreement must be received by EPA on or before May 14, 2007. </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Comments should be addressed to the Docket Clerk, U.S. Environmental Protection Agency, Region 5, 77 West Jackson Boulevard, Chicago, Illinois 60604-3590, and should refer to: In the Matter of Continental Steel Corporation Site, U.S. EPA Docket No. V-W-07C-867. </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Thomas J. Krueger, U.S. Environmental Protection Agency, Office of Regional Counsel, C-14J, 77 West Jackson Boulevard, Chicago, Illinois 60604-3590, (312) 886-0562. </P>
                    <P>A copy of the proposed administrative settlement agreement may be obtained in person or by mail from the EPA's Region 5 Office of Regional Counsel, 77 West Jackson Boulevard, Chicago, Illinois 60604-3590. Additional background information relating to the settlement is available for review at the EPA's Region 5 Office of Regional Counsel. </P>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>The Comprehensive Environmental Response, Compensation, and Liability Act, as amended, 42 U.S.C. 9601-9675. </P>
                    </AUTH>
                    <SIG>
                        <NAME>Douglas Ballotti, </NAME>
                        <TITLE>Acting Director, Superfund Division, Region 5.</TITLE>
                    </SIG>
                </FURINF>
            </PREAMB>
            <FRDOC> [FR Doc. E7-7016 Filed 4-12-07; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 6560-50-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">FEDERAL HOUSING FINANCE BOARD </AGENCY>
                <DEPDOC>[No. 2007-N-05] </DEPDOC>
                <SUBJECT>Federal Home Loan Bank Members Selected for Community Support Review </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Housing Finance Board. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Federal Housing Finance Board (Finance Board) is announcing the Federal Home Loan Bank (Bank) members it has selected for the 2006-07 fifth quarter review cycle under the Finance Board's community support requirements regulation. This notice also prescribes the deadline by which Bank members selected for review must submit Community Support Statements to the Finance Board. </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Bank members selected for the review cycle under the Finance Board's community support requirements regulation must submit completed Community Support Statements to the Finance Board on or before May 25, 2007. </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Bank members selected for the 2006-07 fifth quarter review cycle under the Finance Board's community support requirements regulation must submit completed Community Support Statements to the Finance Board either by regular mail at the Federal Housing Finance Board, Office of Supervision, Community Investment and Affordable Housing, 1625 Eye Street, NW., Washington, DC 20006, or by electronic mail at 
                        <E T="03">fitzgeralde@fhfb.gov.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Emma J. Fitzgerald, Program Analyst, Office of Supervision, Community Investment and Affordable Housing, by telephone at 202/408-2874, by electronic mail at 
                        <E T="03">fitzgeralde@fhfb.gov,</E>
                         or by regular mail at the Federal Housing Finance Board, 1625 Eye Street, NW., Washington, DC 20006. 
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Selection for Community Support Review </HD>
                <P>
                    Section 10(g)(1) of the Federal Home Loan Bank Act (Bank Act) requires the Finance Board to promulgate regulations establishing standards of community investment or service Bank members must meet in order to maintain access to long-term advances. See 12 U.S.C. 1430(g)(1). The regulations promulgated by the Finance Board must take into account factors such as the Bank member's performance under the Community Reinvestment Act of 1977 (CRA), 12 U.S.C. 2901 et seq., and record of lending to first-time 
                    <PRTPAGE P="18652"/>
                    homebuyers. See 12 U.S.C. 1430(g)(2). Pursuant to section 10(g) of the Bank Act, the Finance Board has promulgated a community support requirements regulation that establishes standards a Bank member must meet in order to maintain access to long-term advances, and review criteria the Finance Board must apply in evaluating a member's community support performance. See 12 CFR part 944. The regulation includes standards and criteria for the two statutory factors—CRA performance and record of lending to first-time homebuyers. 12 CFR 944.3. Only members subject to the CRA must meet the CRA standard. 12 CFR 944.3(b). All members, including those not subject to CRA, must meet the first-time homebuyer standard. 12 CFR 944.3(c). 
                </P>
                <P>Under the rule, the Finance Board selects approximately one-eighth of the members in each Bank district for community support review each calendar quarter. 12 CFR 944.2(a). The Finance Board will not review an institution's community support performance until it has been a Bank member for at least one year. Selection for review is not, nor should it be construed as, any indication of either the financial condition or the community support performance of the member. </P>
                <P>
                    Each Bank member selected for review must complete a Community Support Statement and submit it to the Finance Board by the May 25, 2007 deadline prescribed in this notice. 12 CFR 944.2(b)(1)(ii) and (c). On or before April 27, 2007, each Bank will notify the members in its district that have been selected for the 2006-07 fifth quarter community support review cycle that they must complete and submit to the Finance Board by the deadline a Community Support Statement. 12 CFR 944.2(b)(2)(i). The member's Bank will provide a blank Community Support Statement Form, which also is available on the Finance Board's Web site: 
                    <E T="03">http://www.fhfb.gov.</E>
                    Upon request, the member's Bank also will provide assistance in completing the Community Support Statement. 
                </P>
                <P>The Finance Board has selected the following members for the 2006-07 fifth quarter community support review cycle: </P>
                <GPOTABLE COLS="2" OPTS="L2,tp0,p1,7/8,i1" CDEF="s100,r50">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1"> </CHED>
                        <CHED H="1"> </CHED>
                    </BOXHD>
                    <ROW EXPSTB="01" RUL="s">
                        <ENT I="21">
                            <E T="02">Federal Home Loan Bank of Boston—District 1</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="01">People's Bank </ENT>
                        <ENT>Bridgeport, CT </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Farmington Savings Bank </ENT>
                        <ENT>Farmington, CT </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Liberty Bank </ENT>
                        <ENT>Middletown, CT </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Naugatuck Savings Bank </ENT>
                        <ENT>Naugatuck, CT </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Citizens National Bank </ENT>
                        <ENT>Putnam, CT </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">The Simsbury Bank and Trust Company, Inc </ENT>
                        <ENT>Simsbury, CT </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Windsor Federal Savings and Loan Association </ENT>
                        <ENT>Windsor, CT </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Down East Federal Credit Union </ENT>
                        <ENT>Baileyville, ME </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">PeoplesChoice Credit Union </ENT>
                        <ENT>Biddeford, ME </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Ocean Communities Federal Credit Union </ENT>
                        <ENT>Biddeford, ME </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">The First, N.A </ENT>
                        <ENT>Damariscotta, ME </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Gardiner Savings Institution, FSB </ENT>
                        <ENT>Gardiner, ME </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Machias Savings Bank </ENT>
                        <ENT>Machias, ME </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Katahdin Federal Credit Union </ENT>
                        <ENT>Millinocket, ME </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Hanscom Federal Credit Union </ENT>
                        <ENT>Bedford, MA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">University Credit Union </ENT>
                        <ENT>Boston, MA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Tremont Credit Union </ENT>
                        <ENT>Boston, MA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HarborOne Credit Union </ENT>
                        <ENT>Brockton, MA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Dedham Co-operative Bank </ENT>
                        <ENT>Dedham, MA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Everett Credit Union </ENT>
                        <ENT>Everett, MA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Workers' Credit Union </ENT>
                        <ENT>Fitchburg, MA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Framingham Co-operative Bank </ENT>
                        <ENT>Framingham, MA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Dean Co-operative Bank </ENT>
                        <ENT>Franklin, MA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Benjamin Franklin Bank </ENT>
                        <ENT>Franklin, MA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Greenfield Savings Bank </ENT>
                        <ENT>Greenfield, MA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">UMassFive College Federal Credit Union </ENT>
                        <ENT>Hadley, MA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Economy Co-operative Bank </ENT>
                        <ENT>Merrimac, MA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Mayflower Co-operative Bank </ENT>
                        <ENT>Middleboro, MA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Millbury Federal Credit Union </ENT>
                        <ENT>Millbury, MA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">First Citizens' Federal Credit Union </ENT>
                        <ENT>New Bedford, MA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">North Shore Bank, A Co-Operative Bank </ENT>
                        <ENT>Peabody, MA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Berkshire Bank </ENT>
                        <ENT>Pittsfield, MA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">The Pittsfield Cooperative Bank </ENT>
                        <ENT>Pittsfield, MA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Sharon Co-operative Bank </ENT>
                        <ENT>Sharon, MA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Slade's Ferry Trust Company </ENT>
                        <ENT>Somerset, MA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Central Bank </ENT>
                        <ENT>Somerville, MA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Savers Co-operative Bank </ENT>
                        <ENT>Southbridge, MA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">StonehamBank—A Co-operative Bank </ENT>
                        <ENT>Stoneham, MA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">The Martha's Vineyard Co-op Bank of Tisbury</ENT>
                        <ENT> Tisbury, MA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Ware Co-operative Bank </ENT>
                        <ENT>Ware, MA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">United Bank </ENT>
                        <ENT>West Springfield, MA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Westfield Bank </ENT>
                        <ENT>Westfield, MA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Winthrop Federal Credit Union </ENT>
                        <ENT>Winthrop, MA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Connecticut River Bank N.A</ENT>
                        <ENT> Charlestown, NH </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Claremont Savings Bank </ENT>
                        <ENT>Claremont, NH </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Triangle Credit Union </ENT>
                        <ENT>Nashua, NH </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Sugar River Savings Bank </ENT>
                        <ENT>Newport, NH </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Lake Sunapee Bank, fsb</ENT>
                        <ENT> Newport, NH </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Service Credit Union </ENT>
                        <ENT>Portsmouth, NH </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Piscataqua Savings Bank </ENT>
                        <ENT>Portsmouth, NH </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">The Washington Trust Company </ENT>
                        <ENT>Westerly, RI </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">The Bank of Bennington </ENT>
                        <ENT>Bennington, VT </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Factory Point National Bank </ENT>
                        <ENT>Manchester Center, VT </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Heritage Family Credit Union </ENT>
                        <ENT>Rutland, VT </ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01">Passumpsic Savings Bank </ENT>
                        <ENT>St. Johnsbury, VT </ENT>
                    </ROW>
                    <ROW EXPSTB="01" RUL="s">
                        <ENT I="21">
                            <E T="02">Federal Home Loan Bank of New York—District 2</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="01">American Savings Bank of NJ</ENT>
                        <ENT> Bloomfield, NJ </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Clifton Savings Bank, S.L.A</ENT>
                        <ENT> Clifton, NJ </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Sussex Bank </ENT>
                        <ENT>Franklin, NJ </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">First Hope Bank, NA</ENT>
                        <ENT> Hope, NJ </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Magyar Bank </ENT>
                        <ENT>New Brunswick, NJ </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Lusitania Savings Bank </ENT>
                        <ENT>Newark, NJ </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Roebling Bank </ENT>
                        <ENT>Roebling, NJ </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Monroe Savings Bank, SLA</ENT>
                        <ENT> Williamstown, NJ </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Franklin Savings Bank </ENT>
                        <ENT>Woodstown, NJ </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Ponce De Leon Federal Bank </ENT>
                        <ENT>Bronx, NY </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Fulton Savings Bank </ENT>
                        <ENT>Fulton, NY </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Astoria Federal Savings &amp; Loan Association </ENT>
                        <ENT>Lake Success, NY </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Pittsford Federal Credit Union </ENT>
                        <ENT>Mendon, NY </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">First Federal Savings of Middletown </ENT>
                        <ENT>Middletown, NY </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Amalgamated Bank, </ENT>
                        <ENT>New York, NY </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">United Orient Bank </ENT>
                        <ENT>New York, NY </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">The Bank of Castile</ENT>
                        <ENT> Perry, NY </ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01">Northfield Savings Bank </ENT>
                        <ENT>Staten Island, NY </ENT>
                    </ROW>
                    <ROW EXPSTB="01" RUL="s">
                        <ENT I="21">
                            <E T="02">Federal Home Loan Bank of Pittsburgh—</E>
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="21">
                            <E T="02">District 3</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="01">Wilmington Savings Fund Society, FSB</ENT>
                        <ENT> Wilmington, DE </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">C &amp; G Savings Bank </ENT>
                        <ENT>Altoona, PA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Ambler Savings Bank </ENT>
                        <ENT>Ambler, PA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">First Star Savings Bank </ENT>
                        <ENT>Bethlehem, PA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">First FS&amp;LA of Bucks County</ENT>
                        <ENT> Bristol, PA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Alliance Bank </ENT>
                        <ENT>Broomall, PA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Sharon Savings Bank </ENT>
                        <ENT>Darby, PA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ESB Bank </ENT>
                        <ENT>Ellwood City, PA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">County Savings Bank </ENT>
                        <ENT>Essington, PA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Bank of Hanover and Trust Company </ENT>
                        <ENT>Hanover, PA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Hatboro Federal Savings</ENT>
                        <ENT> Hatboro, PA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Fox Chase Bank </ENT>
                        <ENT>Hatboro, PA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">William Penn Bank, FSB</ENT>
                        <ENT> Levittown, PA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Willow Financial</ENT>
                        <ENT> Maple Glen, PA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">First Keystone Bank </ENT>
                        <ENT>Media, PA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Morton Savings Bank </ENT>
                        <ENT>Morton, PA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Nesquehoning Savings Bank </ENT>
                        <ENT>Nesquehoning, PA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Third Federal Bank </ENT>
                        <ENT>Newtown, PA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Malvern Federal Savings Bank </ENT>
                        <ENT>Paoli, PA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">First Savings Bank of Perkasie</ENT>
                        <ENT> Perkasie, PA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Asian Bank </ENT>
                        <ENT>Philadelphia, PA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Washington Savings Association</ENT>
                        <ENT> Philadelphia, PA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Second FS&amp;LA of Philadelphia</ENT>
                        <ENT> Philadelphia, PA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Pennsylvania Business Bank </ENT>
                        <ENT>Philadelphia, PA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Progressive Home FS&amp;LA</ENT>
                        <ENT> Pittsburgh, PA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">The Quakertown National Bank </ENT>
                        <ENT>Quakertown, PA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Mercer County State Bank </ENT>
                        <ENT>Sandy Lake, PA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Penn Security Bank and Trust Company </ENT>
                        <ENT>Scranton, PA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">North Penn Bank </ENT>
                        <ENT>Scranton, PA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Slovenian S&amp;LA of Canonsburg, Pa</ENT>
                        <ENT> Strabane, PA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">First National Bank of Chester County</ENT>
                        <ENT> West Chester, PA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Stonebridge Bank </ENT>
                        <ENT>West Chester, PA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">First Century Bank, N.A.</ENT>
                        <ENT> Bluefield, WV </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Pioneer Community Bank </ENT>
                        <ENT>Iaeger, WV </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Bank of Mount Hope, Inc.</ENT>
                        <ENT>Mount Hope, WV </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Community Bank of Parkersburg</ENT>
                        <ENT> Parkersburg, WV </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">First Neighborhood Bank </ENT>
                        <ENT>Spencer, WV </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Pleasants County Bank </ENT>
                        <ENT>St. Marys, WV </ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01">Poca Valley Bank </ENT>
                        <ENT>Walton, WV </ENT>
                    </ROW>
                    <ROW EXPSTB="01" RUL="s">
                        <ENT I="21">
                            <E T="02">Federal Home Loan Bank of Atlanta—District 4</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="01">Covington County Bank </ENT>
                        <ENT>Andalusia, AL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">United Bank </ENT>
                        <ENT>Atmore, AL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Cullman Savings Bank </ENT>
                        <ENT>Cullman, AL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Peoples Bank of North Alabama </ENT>
                        <ENT>Cullman, AL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">First American Bank </ENT>
                        <ENT>Decatur, AL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">The Citizens Bank </ENT>
                        <ENT>Enterprise, AL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BankTrust of Alabama </ENT>
                        <ENT>Eufala, AL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">EvaBank </ENT>
                        <ENT>Eva, AL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">New South Federal Savings Bank </ENT>
                        <ENT>Irondale, AL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Merchants Bank </ENT>
                        <ENT>Jackson, AL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Farmers and Merchants Bank </ENT>
                        <ENT>Lafayette, AL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Southwest Bank of Alabama </ENT>
                        <ENT>McIntosh, AL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BankTrust </ENT>
                        <ENT>Mobile, AL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Community Spirit Bank </ENT>
                        <ENT>Red Bay, AL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Valley State Bank </ENT>
                        <ENT>Russellville, AL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">The Peoples Bank and Trust Company </ENT>
                        <ENT>Selma, AL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Sweet Water State Bank </ENT>
                        <ENT>Sweet Water, AL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SouthFirst Bank </ENT>
                        <ENT>Sylacauga, AL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">The First National Bank of Talladega</ENT>
                        <ENT> Talladega, AL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">First United Security Bank </ENT>
                        <ENT>Thomasville, AL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">City First Bank of DC, N.A</ENT>
                        <ENT> Washington, DC </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Citrus and Chemical Bank </ENT>
                        <ENT>Bartow, FL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Mackinac Savings Bank, FSB</ENT>
                        <ENT> Boynton Beach, FL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">First Bank of Clewiston</ENT>
                        <ENT> Clewiston, FL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Olde Cypress Community Bank </ENT>
                        <ENT>Clewiston, FL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">First National Bank of Crestview</ENT>
                        <ENT> Crestview, FL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Regent Bank </ENT>
                        <ENT>Davie, FL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Dunnellon State Bank </ENT>
                        <ENT>Dunnellon, FL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Landmark Bank, N.A</ENT>
                        <ENT> Fort Lauderdale, FL </ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="18653"/>
                        <ENT I="01">Old Florida Bank </ENT>
                        <ENT>Fort Myers, FL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">First City Bank of Florida</ENT>
                        <ENT> Fort Walton Beach, FL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Desjardins Bank, National Association</ENT>
                        <ENT> Hallandale Beach, FL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Florida Community Bank </ENT>
                        <ENT>Immokalee, FL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">The Bank of Inverness</ENT>
                        <ENT> Inverness, FL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Monticello Bank </ENT>
                        <ENT>Jacksonville, FL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Community First Credit Union of Florida </ENT>
                        <ENT>Jacksonville, FL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">First Guaranty Bank and Trust Company </ENT>
                        <ENT>Jacksonville, FL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Publix Employees Federal Credit Union </ENT>
                        <ENT>Lakeland, FL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">First Federal Savings Bank of Florida</ENT>
                        <ENT> Live Oak, FL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Helm Bank </ENT>
                        <ENT>Miami, FL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Commercial Bank of Florida</ENT>
                        <ENT> Miami, FL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Eastern National Bank </ENT>
                        <ENT>Miami, FL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">American National Bank </ENT>
                        <ENT>Oakland Park, FL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CNL Bank </ENT>
                        <ENT>Orlando, FL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Peoples First Community Bank </ENT>
                        <ENT>Panama City, FL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Tropical Financial Credit Union </ENT>
                        <ENT>Pembroke Pines, FL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Century Bank, a Federal Savings Bank </ENT>
                        <ENT>Sarasota, FL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Highlands Independent Bank </ENT>
                        <ENT>Sebring, FL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Eastern Financial Florida Credit Union </ENT>
                        <ENT>South Florida, FL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Raymond James Bank, FSB</ENT>
                        <ENT> St. Petersburg, FL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">United Southern Bank </ENT>
                        <ENT>Umatilla, FL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Marine Bank and Trust</ENT>
                        <ENT> Vero Beach, FL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Sterling Bank </ENT>
                        <ENT>West Palm Beach, FL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Montgomery Bank &amp; Trust</ENT>
                        <ENT> Ailey, GA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Citizens Trust Bank </ENT>
                        <ENT>Atlanta, GA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">First Bank of Georgia</ENT>
                        <ENT> Augusta, GA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">United Community Bank </ENT>
                        <ENT>Blairsville, GA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">First National Bank of Georgia</ENT>
                        <ENT> Buchanan, GA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Bank of Chickamauga</ENT>
                        <ENT> Chickamauga, GA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">The Peoples Bank </ENT>
                        <ENT>Eatonton, GA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Pinnacle Bank </ENT>
                        <ENT>Elberton, GA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Gainesville Bank and Trust</ENT>
                        <ENT> Gainesville, GA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">First Citizens Bank </ENT>
                        <ENT>Glennville, GA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">South Georgia Bank </ENT>
                        <ENT>Glennville, GA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SunMark Community Bank </ENT>
                        <ENT>Hawkinsville, GA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Community Trust Bank </ENT>
                        <ENT>Hiram, GA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Northeast Georgia Bank </ENT>
                        <ENT>Lavonia, GA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Peoples Bank </ENT>
                        <ENT>Lithonia, GA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">The Community Bank </ENT>
                        <ENT>Loganville, GA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Family Bank </ENT>
                        <ENT>Pelham, GA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">The Citizens National Bank of Quitman</ENT>
                        <ENT> Quitman, GA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Wilcox County State Bank </ENT>
                        <ENT>Rochelle, GA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Citizens First Bank </ENT>
                        <ENT>Rome, GA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Farmers and Merchants Community Bank </ENT>
                        <ENT>Senoia, GA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Quantum National Bank </ENT>
                        <ENT>Suwanee, GA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Citizens Bank &amp; Trust </ENT>
                        <ENT>Trenton, GA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Farmers and Merchants Bank </ENT>
                        <ENT>Washington, GA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">First Piedmont Bank </ENT>
                        <ENT>Winder, GA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Vigilant Federal Savings Bank </ENT>
                        <ENT>Baltimore, MD </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Hull Federal Savings Bank </ENT>
                        <ENT>Baltimore, MD </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Ideal Federal Savings Bank </ENT>
                        <ENT>Baltimore, MD </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">State Employees Credit Union </ENT>
                        <ENT>Baltimore, MD </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Bay-Vanguard Federal Savings Bank </ENT>
                        <ENT>Baltimore, MD </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">TMB Federal Credit Union </ENT>
                        <ENT>Cabin John, MD </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Cecil Bank </ENT>
                        <ENT>Elkton, MD </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">County National Bank </ENT>
                        <ENT>Glen Burnie, MD </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Susquehanna Bank </ENT>
                        <ENT>Hagerstown, MD </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">FedChoice Federal Credit Union </ENT>
                        <ENT>Lanham, MD </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">North Arundel Savings Bank, FSB</ENT>
                        <ENT> Pasadena, MD </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Provident State Bank, Inc</ENT>
                        <ENT>Preston, MD </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">First National Bank and Trust Company </ENT>
                        <ENT>Asheboro, NC </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Randolph Bank &amp; Trust Company </ENT>
                        <ENT>Asheboro, NC </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Mechanics and Farmers Bank </ENT>
                        <ENT>Durham, NC </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Gateway Bank &amp; Trust Company </ENT>
                        <ENT>Elizabeth City, NC </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Macon Bank </ENT>
                        <ENT>Franklin, NC </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Carolina Bank </ENT>
                        <ENT>Greensboro, NC </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Hertford Savings Bank, SSB</ENT>
                        <ENT> Hertford, NC </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">The Little Bank </ENT>
                        <ENT>Kinston, NC </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Industrial Federal Savings Bank </ENT>
                        <ENT>Lexington, NC </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Lexington State Bank </ENT>
                        <ENT>Lexington, NC </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">First Savings and Loan Association </ENT>
                        <ENT>Mebane, NC </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">American Community Bank </ENT>
                        <ENT>Monroe, NC </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Mount Gilead Savings and Loan Association </ENT>
                        <ENT>Mount Gilead, NC </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">State Employees' Credit Union </ENT>
                        <ENT>Raleigh, NC </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Taylorsville Savings Bank, SSB </ENT>
                        <ENT>Taylorsville, NC </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Anson Bank &amp; Trust Company </ENT>
                        <ENT>Wadesboro, NC </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Waccamaw Bank </ENT>
                        <ENT>Whiteville, NC </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Cooperative Bank </ENT>
                        <ENT>Wilmington, NC </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Home Federal Savings and Loan Association </ENT>
                        <ENT>Bamberg, SC </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Bank of Greeleyville </ENT>
                        <ENT>Greeleyville, SC </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">GrandSouth Bank </ENT>
                        <ENT>Greenville, SC </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Countybank </ENT>
                        <ENT>Greenwood, SC </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Greer State Bank </ENT>
                        <ENT>Greer, SC </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">First National Bank of South Carolina </ENT>
                        <ENT>Holly Hill, SC </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Kingstree Federal Savings &amp; Loan Association </ENT>
                        <ENT>Kingstree, SC </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">The Bank of Clarendon </ENT>
                        <ENT>Manning, SC </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Southcoast Community Bank </ENT>
                        <ENT>Mt. Pleasant, SC </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Anderson Brothers Bank </ENT>
                        <ENT>Mullins, SC </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Pickens Savings &amp; Loan Association, F.A</ENT>
                        <ENT>Pickens, SC </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Bank of Travelers Rest </ENT>
                        <ENT>Travelers Rest, SC </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NAPUS </ENT>
                        <ENT>Alexandria, VA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">The Blue Grass Valley Bank </ENT>
                        <ENT>Blue Grass, VA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">The Bank of Southside Virginia </ENT>
                        <ENT>Carson, VA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Second Bank &amp; Trust </ENT>
                        <ENT>Culpeper, VA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Apple Federal Credit Union </ENT>
                        <ENT>Fairfax, VA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Imperial Savings and Loan Association </ENT>
                        <ENT>Martinsville, VA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Navy Federal Credit Union </ENT>
                        <ENT>Merrifield, VA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Bank of the Commonwealth </ENT>
                        <ENT>Norfolk, VA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Lee Bank and Trust Company </ENT>
                        <ENT>Pennington Gap, VA </ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01">The Marathon Bank </ENT>
                        <ENT>Winchester, VA </ENT>
                    </ROW>
                    <ROW EXPSTB="01" RUL="s">
                        <ENT I="21">
                            <E T="02">Federal Home Loan Bank of Cincinnati—District 5</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="01">Town &amp; Country Bank &amp; Trust Company </ENT>
                        <ENT>Bardstown, KY </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Wilson &amp; Muir Bank and Trust Company </ENT>
                        <ENT>Bardstown, KY </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Bank of Cadiz and Trust Company </ENT>
                        <ENT>Cadiz, KY </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Bank of Columbia </ENT>
                        <ENT>Columbia, KY </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">The Harrison Deposit Bank and Trust Company </ENT>
                        <ENT>Cynthiana, KY </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Kentucky National Bank </ENT>
                        <ENT>Elizabethtown, KY </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Farmers Bank </ENT>
                        <ENT>Hardinsburg, KY </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Hancock Bank and Trust Company </ENT>
                        <ENT>Hawesville, KY </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Peoples Bank &amp; Trust Company of Hazard </ENT>
                        <ENT>Hazard, KY </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Heritage Bank </ENT>
                        <ENT>Hopkinsville, KY </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Planters Bank, Inc. </ENT>
                        <ENT>Hopkinsville, KY </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Bank of Jamestown </ENT>
                        <ENT>Jamestown, KY </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">THE BANK—Oldham County, Inc </ENT>
                        <ENT>LaGrange, KY </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Leitchfield Deposit Bank and Trust Company </ENT>
                        <ENT>Leitchfield, KY </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Central Bank &amp; Trust Company, Inc </ENT>
                        <ENT>Lexington, KY </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">L&amp;N Federal Credit Union </ENT>
                        <ENT>Louisville, KY </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Farmers Bank &amp; Trust of Marion </ENT>
                        <ENT>Marion, KY </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Monticello Banking Company </ENT>
                        <ENT>Monticello, KY </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">South Central Bank of Daviess County, Inc </ENT>
                        <ENT>Owensboro, KY </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">The Salt Lick Deposit Bank </ENT>
                        <ENT>Owingsville, KY </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Blue Grass Federal Savings and Loan Association </ENT>
                        <ENT>Paris, KY </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">First Commonwealth Bank of Prestonsburg, Inc </ENT>
                        <ENT>Prestonsburg, KY </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Fort Knox National Bank </ENT>
                        <ENT>Radcliff, KY </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Belpre Savings Bank </ENT>
                        <ENT>Belpre, OH </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">The Farmers Citizens Bank </ENT>
                        <ENT>Bucyrus, OH </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Union Savings Bank </ENT>
                        <ENT>Cincinnati, OH </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Eagle Savings Bank </ENT>
                        <ENT>Cincinnati, OH </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Charter One Bank, N.A </ENT>
                        <ENT>Cleveland, OH </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">First Community Bank </ENT>
                        <ENT>Columbus, OH </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Conneaut Savings Bank </ENT>
                        <ENT>Conneaut, OH </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CF Bank </ENT>
                        <ENT>Fairlawn, OH </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">The Fort Jennings State Bank </ENT>
                        <ENT>Fort Jennings, OH </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">The Hamler State Bank </ENT>
                        <ENT>Hamler, OH </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Morgan Bank, N.A </ENT>
                        <ENT>Hudson, OH </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">The Fahey Banking Company of Marion </ENT>
                        <ENT>Marion, OH </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Citizens National Bank of McConnelsville </ENT>
                        <ENT>McConnelsville, OH </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">The American Savings Bank </ENT>
                        <ENT>Middletown, OH </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">First National Bank of New Holland </ENT>
                        <ENT>New Holland, OH </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">First National Bank </ENT>
                        <ENT>Orrville, OH </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">The Republic Banking Company </ENT>
                        <ENT>Republic, OH </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Mutual Federal Savings Bank </ENT>
                        <ENT>Sidney, OH </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">The Peoples Savings and Loan Company </ENT>
                        <ENT>West Liberty, OH </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">The Union Banking Company </ENT>
                        <ENT>West Mansfield, OH </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Farmers State Bank </ENT>
                        <ENT>West Salem, OH </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">The Wilmington Savings Bank </ENT>
                        <ENT>Wilmington, OH </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Brighton Bank </ENT>
                        <ENT>Brighton, TN </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Highland Federal Savings and Loan Association </ENT>
                        <ENT>Crossville, TN </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Security Federal Bank </ENT>
                        <ENT>Elizabethton, TN </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Cumberland Bank </ENT>
                        <ENT>Franklin, TN </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">The Lauderdale County Bank </ENT>
                        <ENT>Halls, TN </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Carroll Bank &amp; Trust </ENT>
                        <ENT>Huntingdon, TN </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">First National Bank </ENT>
                        <ENT>Manchester, TN </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">The Coffee County Bank </ENT>
                        <ENT>Manchester, TN </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Memphis Area Teachers' Credit Union </ENT>
                        <ENT>Memphis, TN </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Johnson County Bank </ENT>
                        <ENT>Mountain City, TN </ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01">Home Banking Company </ENT>
                        <ENT>Selmer, TN </ENT>
                    </ROW>
                    <ROW EXPSTB="01" RUL="s">
                        <ENT I="21">
                            <E T="02">Federal Home Loan Bank of Indianapolis—District 6</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="01">Bedford Federal Savings Bank </ENT>
                        <ENT>Bedford, IN </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">FNC Bank </ENT>
                        <ENT>Brookville, IN </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Decatur Bank and Trust Company, NA </ENT>
                        <ENT>Decatur, IN </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">United Fidelity Bank </ENT>
                        <ENT>Evansville, IN </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Fowler State Bank </ENT>
                        <ENT>Fowler, IN </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">First Federal Savings Bank </ENT>
                        <ENT>Huntington, IN </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Campbell &amp; Fetter Bank </ENT>
                        <ENT>Kendallville, IN </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">United Community Bank </ENT>
                        <ENT>Lawrenceburg, IN </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">River Valley Financial Bank </ENT>
                        <ENT>Madison, IN </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MarkleBank </ENT>
                        <ENT>Markle, IN </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">First State Bank of Middlebury </ENT>
                        <ENT>Middlebury, IN </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Citizens Financial Bank </ENT>
                        <ENT>Munster, IN </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Your Community Bank </ENT>
                        <ENT>New Albany, IN </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Ameriana Bank and Trust, SB </ENT>
                        <ENT>New Castle, IN </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">AmericanTrust FSB </ENT>
                        <ENT>Peru, IN </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Spencer County Bank </ENT>
                        <ENT>Santa Claus, IN </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Jackson County Bank </ENT>
                        <ENT>Seymour, IN </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Shelby County Bank </ENT>
                        <ENT>Shelbyville, IN </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Terre Haute Savings Bank </ENT>
                        <ENT>Terre Haute, IN </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Frances Slocum Bank &amp; Trust Company, N.A </ENT>
                        <ENT>Wabash, IN </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Homestead Savings Bank </ENT>
                        <ENT>Albion, MI </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Ann Arbor Commerce Bank </ENT>
                        <ENT>Ann Arbor, MI </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Charlevoix State Bank </ENT>
                        <ENT>Charlevoix, MI </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Dearborn Federal Savings Bank </ENT>
                        <ENT>Dearborn, MI </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Option 1 Credit Union </ENT>
                        <ENT>East Lansing, MI </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Firstbank-Lakeview </ENT>
                        <ENT>Lakeview, MI </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NuUnion Credit Union </ENT>
                        <ENT>Lansing, MI </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Capital National Bank </ENT>
                        <ENT>Lansing, MI </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Independent Bank-South Michigan </ENT>
                        <ENT>Leslie, MI </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">State Savings Bank </ENT>
                        <ENT>Manistique, MI </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Mason State Bank </ENT>
                        <ENT>Mason, MI </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Community Federal Credit Union </ENT>
                        <ENT>Plymouth, MI </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Team One Credit Union </ENT>
                        <ENT>Saginaw, MI </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Sidney State Bank </ENT>
                        <ENT>Sidney, MI </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Flagstar Bank, FSB </ENT>
                        <ENT>Troy, MI </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LaSalle Bank Midwest National Association </ENT>
                        <ENT>Troy, MI </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Research Federal Credit Union </ENT>
                        <ENT>Warren, MI </ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01">Firstbank-West Branch </ENT>
                        <ENT>West Branch, MI </ENT>
                    </ROW>
                    <ROW EXPSTB="01" RUL="s">
                        <PRTPAGE P="18654"/>
                        <ENT I="21">
                            <E T="02">Federal Home Loan Bank of Chicago—District 7</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="01">Oxford Bank and Trust </ENT>
                        <ENT>Addison, IL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Heartland Bank &amp; Trust Company </ENT>
                        <ENT>Bloomington, IL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Peoples Bank of Kankakee County </ENT>
                        <ENT>Bourbonnais, IL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Bridgeview Bank and Trust </ENT>
                        <ENT>Bridgeview, IL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">United Community Bank </ENT>
                        <ENT>Chatham, IL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Amalgamated Bank of Chicago </ENT>
                        <ENT>Chicago, IL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Community Bank of Lawndale </ENT>
                        <ENT>Chicago, IL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Austin Bank of Chicago </ENT>
                        <ENT>Chicago, IL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Foster Bank </ENT>
                        <ENT>Chicago, IL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Flower Bank, fsb </ENT>
                        <ENT>Chicago, IL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Burling Bank </ENT>
                        <ENT>Chicago, IL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">First Savings Bank of Hegewisch </ENT>
                        <ENT>Chicago, IL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">State Bank of Countryside </ENT>
                        <ENT>Countryside, IL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">First Savings Bank of Danville </ENT>
                        <ENT>Danville, IL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Washington Savings Bank </ENT>
                        <ENT>Effingham, IL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Midland State Bank </ENT>
                        <ENT>Effingham, IL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">First American Bank </ENT>
                        <ENT>Elk Grove Village, IL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Forest Park National Bank &amp; Trust Company </ENT>
                        <ENT>Forest Park, IL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Union Savings Bank </ENT>
                        <ENT>Freeport, IL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Central Bank Illinois </ENT>
                        <ENT>Geneseo, IL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Bank of Gibson City </ENT>
                        <ENT>Gibson City, IL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Northside Community Bank </ENT>
                        <ENT>Gurnee, IL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Parkway Bank &amp; Trust Company </ENT>
                        <ENT>Harwood Heights, IL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">North Central Bank </ENT>
                        <ENT>Hennepin, IL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">State Bank of Herscher </ENT>
                        <ENT>Herscher, IL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">The Farmers State Bank and Trust Company </ENT>
                        <ENT>Jacksonville, IL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">First FS&amp;LA of Kewanee </ENT>
                        <ENT>Kewanee, IL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Logan County Bank </ENT>
                        <ENT>Lincoln, IL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Twin Oaks Savings Bank </ENT>
                        <ENT>Marseilles, IL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Citizens Community Bank </ENT>
                        <ENT>Mascoutah, IL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Middletown State Bank </ENT>
                        <ENT>Middleton, IL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Blackhawk State Bank </ENT>
                        <ENT>Milan, IL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">First State Bank </ENT>
                        <ENT>Monticello, IL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BankPlus, fsb </ENT>
                        <ENT>Morton, IL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">George Washington Savings Bank </ENT>
                        <ENT>Oak Lawn, IL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">The First National Bank of Ogden </ENT>
                        <ENT>Ogden, IL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">The First National Bank of Okawville </ENT>
                        <ENT>Okawville, IL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">The Edgar County Bank &amp; Trust Company </ENT>
                        <ENT>Paris, IL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">First Federal Savings and Loan Association of Pekin </ENT>
                        <ENT>Pekin, IL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">First National Bank in Pinckneyville </ENT>
                        <ENT>Pinckneyville, IL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">State Street Bank &amp; Trust Company </ENT>
                        <ENT>Quincy, IL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Mercantile Trust and Savings Bank </ENT>
                        <ENT>Quincy, IL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">North County Savings Bank </ENT>
                        <ENT>Red Bud, IL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">First Savanna Savings Bank </ENT>
                        <ENT>Savanna, IL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">First State Bank of Shannon-Polo </ENT>
                        <ENT>Shannon, IL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Security Bank </ENT>
                        <ENT>Springfield, IL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Stillman BancCorp, N.A </ENT>
                        <ENT>Stillman Valley, IL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">UnionBank </ENT>
                        <ENT>Treator, IL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">The National Bank &amp; Trust Company </ENT>
                        <ENT>Sycamore, IL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Alpha Community Bank </ENT>
                        <ENT>Toluca, IL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Citizens First State Bank of Walnut </ENT>
                        <ENT>Walnut, IL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">The Hill Dodge Banking Company </ENT>
                        <ENT>Warsaw, IL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">State Bank of Waterloo </ENT>
                        <ENT>Waterloo, IL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Cardunal Savings Bank, FSB </ENT>
                        <ENT>West Dundee, IL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">American Bank and Trust Company </ENT>
                        <ENT>Davenport, IA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">First American Credit Union </ENT>
                        <ENT>Beloit, WI </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Jackson County Bank </ENT>
                        <ENT>Black River Falls, WI </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">State Bank of Cross Plains </ENT>
                        <ENT>Cross Plains, WI </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Advantage Community Bank </ENT>
                        <ENT>Dorchester, WI </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">AM Community Credit Union </ENT>
                        <ENT>Kenosha, WI </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Time Federal Savings Bank </ENT>
                        <ENT>Medford, WI </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">M&amp;I Marshall &amp; Ilsley Bank </ENT>
                        <ENT>Milwaukee, WI </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Marine Bank </ENT>
                        <ENT>Pewaukee, WI </ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01">Tomahawk Community Bank SSB </ENT>
                        <ENT>Tomahawk, WI </ENT>
                    </ROW>
                    <ROW EXPSTB="01">
                        <ENT I="21">
                            <E T="02">Federal Home Loan Bank of</E>
                        </ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="21">
                            <E T="02">Des Moines—District 8</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="01">Peoples Trust &amp; Savings Bank </ENT>
                        <ENT>Adel, IA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Security State Bank </ENT>
                        <ENT>Anamosa, IA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Farmers Trust and Savings Bank </ENT>
                        <ENT>Buffalo Center, IA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Linn Area Credit Union </ENT>
                        <ENT>Cedar Rapids, IA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">United Security Savings Bank, F.S.B </ENT>
                        <ENT>Cedar Rapids, IA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Bank Iowa </ENT>
                        <ENT>Clarinda, IA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Clear Lake Bank and Trust Company </ENT>
                        <ENT>Clear Lake, IA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Gateway State Bank </ENT>
                        <ENT>Clinton, IA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">C U.S. Bank </ENT>
                        <ENT>Cresco, IA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Denver Savings Bank </ENT>
                        <ENT>Denver, IA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">DeWitt Bank &amp; Trust Company </ENT>
                        <ENT>DeWitt, IA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Premier Bank </ENT>
                        <ENT>Dubuque, IA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Liberty Trust &amp; Savings Bank </ENT>
                        <ENT>Durant, IA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Farmers Trust &amp; Savings Bank </ENT>
                        <ENT>Earling, IA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Hardin County Savings Bank </ENT>
                        <ENT>Eldora, IA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Bank Plus </ENT>
                        <ENT>Estherville, IA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NorthStar Bank </ENT>
                        <ENT>Estherville, IA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Libertyville Savings Bank </ENT>
                        <ENT>Fairfield, IA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Fort Madison Bank &amp; Trust Company </ENT>
                        <ENT>Fort Madison, IA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Security Savings Bank </ENT>
                        <ENT>Gowrie, IA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Midstates Bank </ENT>
                        <ENT>Harlan, IA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Hills Bank and Trust Company </ENT>
                        <ENT>Hills, IA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">First State Bank </ENT>
                        <ENT>Ida Grove, IA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Peoples Savings Bank </ENT>
                        <ENT>Indianola, IA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Iowa Falls State Bank </ENT>
                        <ENT>Iowa Falls, IA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Kerndt Brothers Savings Bank </ENT>
                        <ENT>Lansing, IA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">First State Bank </ENT>
                        <ENT>Lynnville, IA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">First National Bank of Manning </ENT>
                        <ENT>Manning, IA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Valley Bank &amp; Trust </ENT>
                        <ENT>Mapleton, IA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Maquoketa State Bank </ENT>
                        <ENT>Maquoketa, IA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Maynard Savings Bank </ENT>
                        <ENT>Maynard, IA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Union State Bank </ENT>
                        <ENT>Monona, IA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Mount Vernon Bank and Trust Company </ENT>
                        <ENT>Mount Vernon, IA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Wayland State Bank </ENT>
                        <ENT>Mt. Pleasant, IA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Community Bank </ENT>
                        <ENT>Muscatine, IA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Horizon Bank </ENT>
                        <ENT>Oskaloosa, IA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">First National Bank Midwest </ENT>
                        <ENT>Oskaloosa, IA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Pella State Bank </ENT>
                        <ENT>Pella, IA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">First State Bank </ENT>
                        <ENT>Riceville, IA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Peoples Bank </ENT>
                        <ENT>Rock Valley, IA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Union State Bank </ENT>
                        <ENT>Rockwell City, IA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Rolfe State Bank </ENT>
                        <ENT>Rolfe, IA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">First Community Bank </ENT>
                        <ENT>Sidney, IA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">St. Ansgar State Bank </ENT>
                        <ENT>St. Ansgar, IA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Victor State Bank </ENT>
                        <ENT>Victor, IA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Washington State Bank </ENT>
                        <ENT>Washington, IA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Citizens State Bank </ENT>
                        <ENT>Waukon, IA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">West Iowa Bank </ENT>
                        <ENT>West Bend, IA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">State Savings Bank </ENT>
                        <ENT>West Des Moines, IA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Fidelity Bank </ENT>
                        <ENT>West Des Moines, IA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">GuideOne Mutual Insurance Company </ENT>
                        <ENT>West Des Moines, IA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Wilton Savings Bank </ENT>
                        <ENT>Wilton, IA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">White Rock Bank </ENT>
                        <ENT>Cannon Falls, MN </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Currie State Bank </ENT>
                        <ENT>Currie, MN </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">State Bank of Danvers </ENT>
                        <ENT>Danvers, MN </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">State Bank of Delano </ENT>
                        <ENT>Delano, MN </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Voyager Bank </ENT>
                        <ENT>Eden Prairie, MN </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">First Security Bank-Evansville </ENT>
                        <ENT>Evansville, MN </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">1st United Bank </ENT>
                        <ENT>Faribault, MN </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Border State Bank </ENT>
                        <ENT>Greenbush, MN </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Citizens State Bank of Hayfield </ENT>
                        <ENT>Hayfield, MN </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Farmers State Bank of Hoffman </ENT>
                        <ENT>Hoffman, MN </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Fortress Bank Minnesota </ENT>
                        <ENT>Houston, MN </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Security State Bank of Howard Lake </ENT>
                        <ENT>Howard Lake, MN </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Key Community Bank </ENT>
                        <ENT>Inver Grove Heights, MN </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">First Security Bank—Lake Benton </ENT>
                        <ENT>Lake Benton, MN </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Lake City Federal Bank </ENT>
                        <ENT>Lake City, MN </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Lake Area Bank </ENT>
                        <ENT>Lindstrom, MN </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Inter Savings Bank, fsb </ENT>
                        <ENT>Maple Grove, MN </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">First National Bank of Moose Lake </ENT>
                        <ENT>Moose Lake, MN </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">United Prairie Bank </ENT>
                        <ENT>Mountain Lake, MN </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">State Bank of New Prague </ENT>
                        <ENT>New Prague, MN </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ProGrowth Bank </ENT>
                        <ENT>Nicollet, MN </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Midwest Bank NA </ENT>
                        <ENT>Parkers Prairie, MN </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">The First National Bank of Pine City </ENT>
                        <ENT>Pine City, MN </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Sterling State Bank </ENT>
                        <ENT>Rochester, MN </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Premier Bank Rochester </ENT>
                        <ENT>Rochester, MN </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Citizens State Bank of Roseau </ENT>
                        <ENT>Roseau, MN </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Bremer Bank, N.A </ENT>
                        <ENT>St. Cloud, MN </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">St. James Federal Savings and Loan Association </ENT>
                        <ENT>St. James, MN </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">The Nicollett County Bank of Saint Peter </ENT>
                        <ENT>St. Peter, MN </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Farmers State Bank of Trimont </ENT>
                        <ENT>Trimont, MN </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">The First National Bank of Walker </ENT>
                        <ENT>Walker, MN </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Roundbank </ENT>
                        <ENT>Waseca, MN </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Flagship Bank Winsted </ENT>
                        <ENT>Winsted, MN </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">First Independent Bank of Wood Lake </ENT>
                        <ENT>Wood Lake, MN </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Citizens Bank of Amsterdam </ENT>
                        <ENT>Amsterdam, MO </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Community State Bank of Missouri </ENT>
                        <ENT>Bowling Green, MO </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Pony Express Bank </ENT>
                        <ENT>Braymer, MO </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Citizens Union State Bank &amp; Trust </ENT>
                        <ENT>Clinton, MO </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">First National Bank &amp; Trust Company </ENT>
                        <ENT>Columbia, MO </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Meramec Valley Bank </ENT>
                        <ENT>Ellisville, MO </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">New Era Bank </ENT>
                        <ENT>Fredericktown, MO </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Bank Star One </ENT>
                        <ENT>Fulton, MO </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Central Trust Bank </ENT>
                        <ENT>Jefferson City, MO </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Macon-Atlanta State Bank </ENT>
                        <ENT>Macon, MO </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Regional Missouri Bank </ENT>
                        <ENT>Marceline, MO </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Nodaway Valley Bank </ENT>
                        <ENT>Maryville, MO </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Independent Farmers Bank </ENT>
                        <ENT>Maysville, MO </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Heritage State Bank </ENT>
                        <ENT>Nevada, MO </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Southwest Community Bank </ENT>
                        <ENT>Ozark, MO </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Palmyra State Bank </ENT>
                        <ENT>Palmyra, MO </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Farley State Bank </ENT>
                        <ENT>Parkville, MO </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Perry State Bank </ENT>
                        <ENT>Perry, MO </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Citizens Community Bank </ENT>
                        <ENT>Pilot Grove, MO </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Pulaski Bank </ENT>
                        <ENT>Saint Louis, MO </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Bank of Salem </ENT>
                        <ENT>Salem, MO </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">The Merchants &amp; Farmers Bank of Salisbury </ENT>
                        <ENT>Salisbury, MO </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Excel Bank </ENT>
                        <ENT>Sedalia, MO </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">The Signature Bank </ENT>
                        <ENT>Springfield, MO </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Empire Bank </ENT>
                        <ENT>Springfield, MO </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Liberty Bank </ENT>
                        <ENT>Springfield, MO </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Bank Star of the Bootheel </ENT>
                        <ENT>Steele, MO </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">The Tipton Latham Bank, N.A </ENT>
                        <ENT>Tipton, MO </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Bank of Washington </ENT>
                        <ENT>Washington, MO </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">West Plains Savings &amp; Loan </ENT>
                        <ENT>West Plains, MO </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">The First and Farmers Bank </ENT>
                        <ENT>Portland, ND </ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01">First International Bank &amp; Trust </ENT>
                        <ENT>Watford City, ND </ENT>
                    </ROW>
                    <ROW EXPSTB="01" RUL="s">
                        <ENT I="21">
                            <E T="02">Federal Home Loan Bank of Dallas—District 9</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="01">SOUTHBank, A Federal Savings Bank </ENT>
                        <ENT>Huntsville, AL </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Community Bank </ENT>
                        <ENT>Cabot, AR </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Hot Springs Bank &amp; Trust Company </ENT>
                        <ENT>Clarksville, AR </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Bank of Eureka Springs </ENT>
                        <ENT>Eureka Springs, AR </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">First National Bank of Fort Smith </ENT>
                        <ENT>Fort Smith, AR </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">First National Bank </ENT>
                        <ENT>Hot Springs, AR </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Bank of Lake Village </ENT>
                        <ENT>Lake Village, AR </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Bank of the Ozarks </ENT>
                        <ENT>Little Rock, AR </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">First State Bank </ENT>
                        <ENT>Lonoke, AR </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Arvest Bank </ENT>
                        <ENT>Lowell, AR </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Union Bank of Mena </ENT>
                        <ENT>Mena, AR </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Evolve Bank &amp; Trust </ENT>
                        <ENT>Parkin, AR </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Bank of Salem </ENT>
                        <ENT>Salem, AR </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Simmons First Bank of Searcy </ENT>
                        <ENT>Searcy, AR </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">First Security Bank of Searcy </ENT>
                        <ENT>Searcy, AR </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Fidelity Bank </ENT>
                        <ENT>Baton Rouge, LA </ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="18655"/>
                        <ENT I="01">State Investors Bank </ENT>
                        <ENT>Metairie, LA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Globe Homestead Savings Bank </ENT>
                        <ENT>Metairie, LA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Home Federal Savings and Loan Association </ENT>
                        <ENT>Shreveport, LA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Citizens B&amp;T Company of Vivian LA, Inc </ENT>
                        <ENT>Vivian, LA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">First Southern Bank </ENT>
                        <ENT>Columbia, MS </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">First Delta Federal Credit Union </ENT>
                        <ENT>Marks, MS </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Pioneer Bank </ENT>
                        <ENT>Roswell, NM </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">First National Bank of Santa Fe </ENT>
                        <ENT>Santa Fe, NM </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">International Bank of Commerce—Brownsville </ENT>
                        <ENT>Brownsville, TX </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">American Bank, N.A </ENT>
                        <ENT>Corpus Christi, TX </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Guaranty Bank </ENT>
                        <ENT>Dallas, TX </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">State Bank and Trust Company</ENT>
                        <ENT>Dallas, TX </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">The Bank &amp; Trust, S.S.B </ENT>
                        <ENT>Del Rio, TX </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Government Employees Credit Union </ENT>
                        <ENT>El Paso, TX </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Bank of the West </ENT>
                        <ENT>El Paso, TX </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">OmniBank, N.A </ENT>
                        <ENT>Houston, TX </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">New Era Life Insurance Company </ENT>
                        <ENT>Houston, TX </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Amegy Bank of Texas, NA </ENT>
                        <ENT>Houston, TX </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">The First National Bank of Hughes Springs </ENT>
                        <ENT>Hughes Springs, TX </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">International Bank of Commerce</ENT>
                        <ENT> Laredo, TX </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Liberty Bank </ENT>
                        <ENT>North Richland Hills, TX </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Interstate Bank, ssb</ENT>
                        <ENT> Perryton, TX </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Cypress Bank FSB</ENT>
                        <ENT> Pittsburg, TX </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Benchmark Bank </ENT>
                        <ENT>Plano, TX </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ViewPoint Bank </ENT>
                        <ENT>Plano, TX </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">First National Bank in Quanah</ENT>
                        <ENT> Quanah, TX </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Peoples State Bank </ENT>
                        <ENT>Rocksprings, TX </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Crockett National Bank </ENT>
                        <ENT>San Angelo, TX </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Frost National Bank </ENT>
                        <ENT>San Antonio, TX </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Citizens Bank </ENT>
                        <ENT>Slaton, TX </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">First Community Bank The Woodlands </ENT>
                        <ENT>Tomball, TX </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Southside Bank </ENT>
                        <ENT>Tyler, TX </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">First Victoria National Bank </ENT>
                        <ENT>Victoria, TX </ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01">International Bank of Commerce-Zapata</ENT>
                        <ENT> Zapata, TX </ENT>
                    </ROW>
                    <ROW EXPSTB="01" RUL="s">
                        <ENT I="21">
                            <E T="02">Federal Home Loan Bank of Topeka—District 10</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="01">FirstBank of Avon </ENT>
                        <ENT>Avon, CO </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Canon National Bank </ENT>
                        <ENT>Canon City, CO </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Ent Federal Credit Union </ENT>
                        <ENT>Colorado Springs, CO </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">The Citizens State Bank of Cortez </ENT>
                        <ENT>Cortez, CO </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Guaranty Bank and Trust Company </ENT>
                        <ENT>Denver, CO </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">FirstBank of Vail </ENT>
                        <ENT>Vail, CO </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Community State Bank </ENT>
                        <ENT>Coffeyville, KS </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">The Liberty Savings Association, FSA </ENT>
                        <ENT>Fort Scott, KS </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">The City State Bank </ENT>
                        <ENT>Fort Scott, KS </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">First National Bank </ENT>
                        <ENT>Independence, KS </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">First Federal S&amp;L Independence </ENT>
                        <ENT>Independence, KS </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MidAmerican Bank &amp; Trust Company </ENT>
                        <ENT>Leavenworth, KS </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Kansas State Bank of Manhattan </ENT>
                        <ENT>Manhattan, KS </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Stockgrowers State Bank </ENT>
                        <ENT>Maple Hill, KS </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Citizens State Bank of Marysville </ENT>
                        <ENT>Marysville, KS </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Montezuma State Bank </ENT>
                        <ENT>Montezuma, KS </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Kansas State Bank </ENT>
                        <ENT>Overbrook, KS </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Solutions Bank </ENT>
                        <ENT>Overland Park, KS</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">1st Financial Bank </ENT>
                        <ENT>Overland Park, KS </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">First National Bank in Pratt </ENT>
                        <ENT>Pratt, KS </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Rose Hill Bank </ENT>
                        <ENT>Rose Hill, KS </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">The Bennington State Bank </ENT>
                        <ENT>Salina, KS </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Security State Bank </ENT>
                        <ENT>Scott City, KS </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">First National Bank of Scott City </ENT>
                        <ENT>Scott City, KS </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Centera Bank </ENT>
                        <ENT>Sublette, KS </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">First Federal Savings &amp; Loan Association of WaKeeney </ENT>
                        <ENT>WaKeeney, KS </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">First National Bank of Wamego </ENT>
                        <ENT>Wamego, KS </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Fidelity Bank </ENT>
                        <ENT>Wichita, KS </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">First National Bank and Trust </ENT>
                        <ENT>Fullerton, NE </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Geneva State Bank </ENT>
                        <ENT>Geneva, NE </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Equitable Bank </ENT>
                        <ENT>Grand Island, NE </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Home FS&amp;LA of Grand Island, Nebraska </ENT>
                        <ENT>Grand Island, NE </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Harvard State Bank </ENT>
                        <ENT>Harvard, NE </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Hershey State Bank </ENT>
                        <ENT>Hershey, NE </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Platte Valley State Bank and Trust Company, Inc </ENT>
                        <ENT>Kearney, NE </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Nebraska National Bank </ENT>
                        <ENT>Kearney, NE </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Bank of Keystone </ENT>
                        <ENT>Keystone, NE </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Home FS&amp;LA of Nebrasksa </ENT>
                        <ENT>Lexington, NE </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Lincoln Federal Savings Bank </ENT>
                        <ENT>Lincoln, NE </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Security Federal Savings </ENT>
                        <ENT>Lincoln, NE </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Sherman County Bank </ENT>
                        <ENT>Loup City, NE </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">First National Bank Northeast </ENT>
                        <ENT>Lyons, NE </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">The Bank of Madison </ENT>
                        <ENT>Madison, NE </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Madison County Bank </ENT>
                        <ENT>Madison, NE </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BankFirst </ENT>
                        <ENT>Norfolk, NE </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">First National Bank </ENT>
                        <ENT>North Platte, NE </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Nebraskaland National Bank </ENT>
                        <ENT>North Platte, NE </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Pender State Bank </ENT>
                        <ENT>Pender, NE </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Midwest Bank, N.A </ENT>
                        <ENT>Pierce, NE </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Town &amp; Country Bank </ENT>
                        <ENT>Ravenna, NE </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Sidney Federal Savings &amp; Loan Association </ENT>
                        <ENT>Sidney, NE </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Dakota County State Bank </ENT>
                        <ENT>South Sioux City, NE </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Springfield State Bank </ENT>
                        <ENT>Springfield, NE </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Bank of St. Edward </ENT>
                        <ENT>St. Edward, NE </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Tecumseh Federal Bank </ENT>
                        <ENT>Tecumseh, NE </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">First National Bank of Utica </ENT>
                        <ENT>Utica, NE </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Farmers State Bank </ENT>
                        <ENT>Wallace, NE </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Saline State Bank </ENT>
                        <ENT>Wilber, NE </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Citizens National Bank </ENT>
                        <ENT>Wisner, NE </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">66 Federal Credit Union </ENT>
                        <ENT>Bartlesville, OK </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Bank of Cordell </ENT>
                        <ENT>Cordell, OK </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Bank of Hydro </ENT>
                        <ENT>Hydro, OK </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Armstrong Bank </ENT>
                        <ENT>Muskogee, OK </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">The Citizens State Bank </ENT>
                        <ENT>Okemah, OK </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">First Enterprise Bank </ENT>
                        <ENT>Oklahoma City, OK </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Union Bank, n.a </ENT>
                        <ENT>Oklahoma City, OK </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">The First National Bank </ENT>
                        <ENT>Texhoma, OK </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Grand Bank </ENT>
                        <ENT>Tulsa, OK </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Community Bank &amp; Trust Company </ENT>
                        <ENT>Tulsa, OK </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Energy One Federal Credit Union </ENT>
                        <ENT>Tulsa, OK </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">First Bank &amp; Trust Company </ENT>
                        <ENT>Wagoner, OK </ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01">Canadian State Bank </ENT>
                        <ENT>Yukon, OK </ENT>
                    </ROW>
                    <ROW EXPSTB="01" RUL="s">
                        <ENT I="21">
                            <E T="02">Federal Home Loan Bank of San Francisco—District 11</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="01">BankUSA </ENT>
                        <ENT>Phoenix, AZ </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Fremont Investment &amp; Loan </ENT>
                        <ENT>Anaheim, CA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Vista Federal Credit Union </ENT>
                        <ENT>Burbank, CA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Eastern International Bank </ENT>
                        <ENT>Los Angeles, CA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Chevron Federal Credit Union </ENT>
                        <ENT>Oakland, CA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Wescom Central Credit Union </ENT>
                        <ENT>Pasadena, CA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">La Jolla Bank, F.S.B </ENT>
                        <ENT>Rancho Santa Fe, CA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Redding Bank of Commerce </ENT>
                        <ENT>Redding, CA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">San Diego County Credit Union </ENT>
                        <ENT>San Diego, CA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">California Bank &amp; Trust </ENT>
                        <ENT>San Diego, CA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">United Commercial Bank </ENT>
                        <ENT>San Francisco, CA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Luther Burbank Savings </ENT>
                        <ENT>Santa Rosa, CA </ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01">Community Banks of Northern California </ENT>
                        <ENT>Tracy, CA </ENT>
                    </ROW>
                    <ROW EXPSTB="01" RUL="s">
                        <ENT I="21">
                            <E T="02">Federal Home Loan Bank of Seattle—District 12</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="01">First Bank </ENT>
                        <ENT>Ketchikan, AK </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Territorial Savings Bank </ENT>
                        <ENT>Honolulu, HI </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Central Pacific Bank </ENT>
                        <ENT>Honolulu HI </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Home Federal Bank </ENT>
                        <ENT>Nampa, ID</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Valley Bank of Helena </ENT>
                        <ENT>Helena, MT </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">American Bank </ENT>
                        <ENT>Livingston, MT </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Northwest Community Credit Union </ENT>
                        <ENT>Eugene, OR </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LibertyBank </ENT>
                        <ENT>Eugene, OR </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Chetco Federal Credit Union </ENT>
                        <ENT>Harbor, OR </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">West Coast Bank </ENT>
                        <ENT>Lake Oswego, OR </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">PremierWest Bank </ENT>
                        <ENT>Medford, OR </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SummitOne Credit Union </ENT>
                        <ENT>Ogden, UT </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Centennial Bank </ENT>
                        <ENT>Ogden, UT </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Zions Bank </ENT>
                        <ENT>Salt Lake City, UT </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Mountain America Federal Credit Union </ENT>
                        <ENT>West Jordan, UT </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Kitsap Community Federal Credit Union </ENT>
                        <ENT>Bremerton, WA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Summit Bank </ENT>
                        <ENT>Burlington, WA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">VentureBank </ENT>
                        <ENT>Lacey, WA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Spokane Teachers Credit Union </ENT>
                        <ENT>Liberty Lake, WA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Cowlitz Bank </ENT>
                        <ENT>Longview, WA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Heritage Bank </ENT>
                        <ENT>Olympia, WA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Viking Community Bank </ENT>
                        <ENT>Seattle, WA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Wheatland Bank </ENT>
                        <ENT>Spokane, WA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">TAPCO Credit Union </ENT>
                        <ENT>Tacoma, WA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Sound Banking Company </ENT>
                        <ENT>Tacoma, WA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Banner Bank </ENT>
                        <ENT>Walla Walla, WA </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Security First Bank </ENT>
                        <ENT>Cheyenne, WY </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Cowboy State Bank </ENT>
                        <ENT>Ranchester, WY </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Bank of Wyoming </ENT>
                        <ENT>Thermopolis, WY </ENT>
                    </ROW>
                </GPOTABLE>
                <HD SOURCE="HD1">II. Public Comments </HD>
                <P>To encourage the submission of public comments on the community support performance of Bank members, on or before April 27, 2007, each Bank will notify its Advisory Council and nonprofit housing developers, community groups, and other interested parties in its district of the members selected for community support review in the 2006-07 fifth quarter review cycle. 12 CFR 944.2(b)(2)(ii). In reviewing a member for community support compliance, the Finance Board will consider any public comments it has received concerning the member. 12 CFR 944.2(d). To ensure consideration by the Finance Board, comments concerning the community support performance of members selected for the 2006-07 fifth quarter review cycle must be delivered to the Finance Board on or before the May 25, 2007 deadline for submission of Community Support Statements. </P>
                <SIG>
                    <NAME>Neil R. Crowley, </NAME>
                    <TITLE>Acting General Counsel.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. E7-6142 Filed 4-12-07; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 6725-01-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">FEDERAL RESERVE SYSTEM</AGENCY>
                <SUBJECT>Change in Bank Control Notices; Acquisition of Shares of Bank or Bank Holding Companies</SUBJECT>
                <P>The notificants listed below have applied under the Change in Bank Control Act (12 U.S.C. 1817(j)) and § 225.41 of the Board’s Regulation Y (12 CFR 225.41) to acquire a bank or bank holding company. The factors that are considered in acting on the notices are set forth in paragraph 7 of the Act (12 U.S.C. 1817(j)(7)).</P>
                <P>
                    The notices are available for immediate inspection at the Federal 
                    <PRTPAGE P="18656"/>
                    Reserve Bank indicated. The notices also will be available for inspection at the office of the Board of Governors. Interested persons may express their views in writing to the Reserve Bank indicated for that notice or to the offices of the Board of Governors. Comments must be received not later than April 27, 2007.
                </P>
                <P>
                    <E T="04">A. Federal Reserve Bank of St. Louis</E>
                     (Glenda Wilson, Community Affairs Officer) 411 Locust Street, St. Louis, Missouri 63166-2034:
                </P>
                <P>
                    <E T="03">1. Rebecca Mason Irvine, Louisville, Kentucky, James Edward Mason, Elizabethtown, Kentucky, and Deborah Mason Garner, New Albany, Indiana, as a group acting in concert,</E>
                     to acquire control of Magnolia Bancshares, Inc., Hodgenville, Kentucky and Bank of Magnolia, Magnolia, Kentucky.
                </P>
                <SIG>
                    <P>Board of Governors of the Federal Reserve System, April 9, 2007.</P>
                    <NAME>Robert deV. Frierson,</NAME>
                    <TITLE>Deputy Secretary of the Board.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. E7-6987 Filed 4-12-07; 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 May 7, 2007.</P>
                <P>
                    <E T="04">A. Federal Reserve Bank of Atlanta</E>
                     (Andre Anderson, Vice President) 1000 Peachtree Street, N.E., Atlanta, Georgia 30309:
                </P>
                <P>
                    <E T="03">1. Old Southern Bancorp, Inc.,</E>
                     to become a bank holding company by acquiring 100 percent of the voting shares of Old Southern Bank both of Orlando, Florida.
                </P>
                <P>
                    <E T="04">B. Federal Reserve Bank of St. Louis</E>
                     (Glenda Wilson, Community Affairs Officer) 411 Locust Street, St. Louis, Missouri 63166-2034:
                </P>
                <P>
                    <E T="03">1. Renasant Corporation, Tupelo, Mississippi;</E>
                     to merge with Capital Bancorp, Inc., Nashville, Tennessee, and thereby indirectly acquire Capital Bank and Trust Company, Nashville, Tennessee.
                </P>
                <P>
                    <E T="04">C. Federal Reserve Bank of Dallas</E>
                     (W. Arthur Tribble, Vice President) 2200 North Pearl Street, Dallas, Texas 75201-2272:
                </P>
                <P>
                    <E T="03">1. South Plains Financial, Inc. Employee Stock Ownership Plan, Lubbock, Texas;</E>
                     to acquire 30.7 percent of the voting shares of South Plains Financial, Inc., Lubbock, Texas, and thereby indirectly acquire South Plains Delaware Financial Corporation, Dover, Delaware, City Bank, Lubbock, Texas, Zia Financial Corporation, and City Bank New Mexico, both of Ruidoso, New Mexico.
                </P>
                <SIG>
                    <P>Board of Governors of the Federal Reserve System, April 9, 2007.</P>
                    <NAME>Robert deV. Frierson,</NAME>
                    <TITLE>Deputy Secretary of the Board.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. E7-6988 Filed 4-12-07; 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 April 30, 2007.</P>
                <P>
                    <E T="04">A. Federal Reserve Bank of Boston</E>
                     (Richard Walker, Community Affairs Officer) P.O. Box 55882, Boston, Massachusetts 02106-2204:
                </P>
                <P>
                    <E T="03">1. BankFive, MHC, and BankFive Corporation, both of Fall River, Massachusetts;</E>
                     to acquire 100 percent of the voting shares, and thereby merge with New Bedford Community Bancorp and acquire Luzo Community Bank, both of New Bedford, Massachusetts.
                </P>
                <P>
                    <E T="04">B. Federal Reserve Bank of Chicago</E>
                     (Patrick M. Wilder, Assistant Vice President) 230 South LaSalle Street, Chicago, Illinois 60690-1414:
                </P>
                <P>
                    <E T="03">1. GC Bancorp, Inc., Chicago, Illinois;</E>
                     to become a bank holding company by acquiring 100 percent of the voting shares of Gold Coast Bank, Chicago, Illinois.
                </P>
                <P>In connection with this application Applicant also has applied to engage de novo in extending credit and servicing loans, pursuant to section 225.28 (b)(1) of Regulation Y.</P>
                <SIG>
                    <P>Board of Governors of the Federal Reserve System, April 10, 2007.</P>
                    <NAME>Robert deV. Frierson,</NAME>
                    <TITLE>Deputy Secretary of the Board.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. E7-7035 Filed 4-12-07; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6210-01-S</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="18657"/>
                <AGENCY TYPE="N">DEPARTMENT OF HEALTH AND HUMAN SERVICES </AGENCY>
                <SUBAGY>Office of the Secretary </SUBAGY>
                <DEPDOC>[Document Identifier: OS-4040-0003] [30-Day Notice] </DEPDOC>
                <SUBJECT>Agency Information Collection Activities: Proposed Collection; Comment Request </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of the Secretary, HHS. </P>
                    <P>In compliance with the requirement of section 3506(c)(2)(A) of the Paperwork Reduction Act of 1995, the Office of the Secretary (OS), Department of Health and Human Services, is publishing the following summary of a proposed collection 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>
                        <E T="03">Type of Information Collection Request:</E>
                         Revision. 
                    </P>
                    <P>
                        <E T="03">Title of Information Collection:</E>
                         SF-424 Short Organizational. 
                    </P>
                    <P>
                        <E T="03">Form/OMB No.:</E>
                         OS-4040-0003. 
                    </P>
                    <P>
                        <E T="03">Use:</E>
                         The SF-424 (short) is a simplified, alternative government-wide data set and application cover page for use by Federal grant-making agencies. Agencies may use the SF-424 (short) for grant programs not requiring all the data that is required on the SF-424 core data set and form. This information collection request also includes two additional government-wide forms, the Key Contacts form and the Project Abstract form, each of which can be used in conjunction with the SF-424 to collect supplemental applicant data. 
                    </P>
                    <P>The form will include one change to one field—the Social Security Number (SSN). The SSN field will remain optional. The SSN field will be changed to pre-populate the first five digits with “000-00-” The applicant will only enter the last four digits of the SSN. This change ensures the entire SSN will not be collected or stored. This change will not increase the collection burden to the applicant. </P>
                    <P>
                        <E T="03">Frequency:</E>
                         Recordkeeping on Occasion. 
                    </P>
                    <P>
                        <E T="03">Affected Public:</E>
                         Individuals or Households. 
                    </P>
                    <P>
                        <E T="03">Annual Number of Respondents:</E>
                         8276. 
                    </P>
                    <P>
                        <E T="03">Total Annual Responses:</E>
                         8549. 
                    </P>
                    <P>
                        <E T="03">Average Burden per Response:</E>
                         25 minutes. 
                    </P>
                    <P>
                        <E T="03">Total Annual Hours:</E>
                         3562. 
                    </P>
                    <P>
                        To obtain copies of the supporting statement and any related forms for the proposed paperwork collections referenced above, e-mail your request, including your address, phone number, OMB number, and OS document identifier, to 
                        <E T="03">Sherette.funncoleman@hhs.gov</E>
                        , or call the Reports Clearance Office on (202) 690-6162. Written comments and recommendations for the proposed information collections must be received within 30 days of this notice directly to the Desk Officer at the address below: 
                    </P>
                    <P>
                        <E T="03">OMB Desk Officer:</E>
                         John Kraemer, OMB Human Resources and Housing Branch, 
                        <E T="03">Attention:</E>
                         (OMB #4040-0003), New Executive Office Building, Room 10235, Washington, DC 20503. 
                    </P>
                </AGY>
                <SIG>
                    <DATED>Dated: April 5, 2007. </DATED>
                    <NAME>Mary Oliver-Anderson, </NAME>
                    <TITLE>Paperwork Reduction Act Reports Clearance Officer,  Office of the Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC> [FR Doc. E7-7002 Filed 4-12-07; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4150-17-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES </AGENCY>
                <SUBAGY>Office of the Secretary </SUBAGY>
                <DEPDOC>[Document Identifier: OS-0990-0162] [60-Day Notice] </DEPDOC>
                <SUBJECT>Agency Information Collection Activities: Proposed Collection; Comment Request </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of the Secretary, HHS. </P>
                    <P>In compliance with the requirement of section 3506(c)(2)(A) of the Paperwork Reduction Act of 1995, the Office of the Secretary (OS), Department of Health and Human Services, is publishing the following summary of a proposed collection 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>
                        <E T="03">Type of Information Collection Request:</E>
                         Reinstatement with change of a previously approved collection. 
                    </P>
                    <P>
                        <E T="03">Title of Information Collection:</E>
                         State Medicaid Fraud Control Units' Reports. 
                    </P>
                    <P>
                        <E T="03">Form/OMB No.:</E>
                         0990-0162. 
                    </P>
                    <P>
                        <E T="03">Use:</E>
                         We are requesting Office of Management and Budget approval for the collection of information to specifically comply with the requirements in Title 19 of the Social Security Act at 1903(q) and 42 CFR1007.15 and 1007.17. (see attached), in accordance with the Paperwork Reduction Act. The particular information collected consists of forty-eight annual reports and forty-eight application requests for federal certification/recertification. This information is submitted yearly to the Office of Inspector General (OIG) by the forty-eight established State Medicaid Fraud Control Units (Units). The OIG uses this collection to assess and determine the Units' eligibility for continued participation in the federal Medicaid fraud control grant program. 
                    </P>
                    <P>
                        <E T="03">Frequency:</E>
                         Annually. 
                    </P>
                    <P>
                        <E T="03">Affected Public:</E>
                         State, Local or Tribal Government. 
                    </P>
                    <P>
                        <E T="03">Annual Number of Respondents:</E>
                         98. 
                    </P>
                    <P>
                        <E T="03">Total Annual Responses:</E>
                         98. 
                    </P>
                    <P>
                        <E T="03">Average Burden per Response:</E>
                         2790 hours. 
                    </P>
                    <P>
                        <E T="03">Total Annual Hours:</E>
                         4557. 
                    </P>
                    <P>
                        To obtain copies of the supporting statement and any related forms for the proposed paperwork collections referenced above, e-mail your request, including your address, phone number, OMB number, and OS document identifier, to 
                        <E T="03">Sherette.funncoleman@hhs.gov</E>
                        , or call the Reports Clearance Office on (202) 690-6162. Written comments and recommendations for the proposed information collections must be received within 60 days, and directed to the OS Paperwork Clearance Officer at the following address: 
                    </P>
                    <P>
                        Department of Health and Human Services, Office of the Secretary, Assistant Secretary for Resources and Technology, Office of Resources Management, 
                        <E T="03">Attention:</E>
                         Sherrette Funn-Coleman (0990-0162), Room 537-H, 200 Independence Avenue, SW., Washington, DC 20201. 
                    </P>
                </AGY>
                <SIG>
                    <DATED>Dated: April 5, 2007. </DATED>
                    <NAME>Mary Oliver-Anderson, </NAME>
                    <TITLE>Paperwork Reduction Act Reports Clearance Officer, Office of the Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. E7-7003 Filed 4-12-07; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4152-01-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="18658"/>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES </AGENCY>
                <SUBAGY>Office of the Secretary </SUBAGY>
                <DEPDOC>[Document Identifier: OS-4040-0005] [30-Day Notice] </DEPDOC>
                <SUBJECT>Agency Information Collection Activities: Proposed Collection; Comment Request </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of the Secretary, HHS. </P>
                    <P>In compliance with the requirement of section 3506(c)(2)(A) of the Paperwork Reduction Act of 1995, the Office of the Secretary (OS), Department of Health and Human Services, is publishing the following summary of a proposed collection 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>
                        <E T="03">Type of Information Collection Request:</E>
                         Revision. 
                    </P>
                    <P>
                        <E T="03">Title of Information Collection:</E>
                         SF-424 Individual. 
                    </P>
                    <P>
                        <E T="03">Form/OMB No.:</E>
                         OS-4040-0005. 
                    </P>
                    <P>
                        <E T="03">Use:</E>
                         The SF-424 (individual) is a simplified, alternative government-wide data set and application cover page for use by Federal grant-making agencies that award grants to individuals. The form will include one change to one field—the Social Security Number (SSN). The SSN field will remain optional. The SSN field will be changed to pre-populate the first five digits with “000-00-” The applicant will only enter the last four digits of the SSN. This change ensures the entire SSN will not be collected or stored. This change will not increase the collection burden to the applicant. 
                    </P>
                    <P>
                        <E T="03">Frequency:</E>
                         Recordkeeping on Occasion. 
                    </P>
                    <P>
                        <E T="03">Affected Public:</E>
                         Individuals or Households. 
                    </P>
                    <P>
                        <E T="03">Annual Number of Respondents:</E>
                         5827. 
                    </P>
                    <P>
                        <E T="03">Total Annual Responses:</E>
                         6949. 
                    </P>
                    <P>
                        <E T="03">Average Burden per Response:</E>
                         25 minutes. 
                    </P>
                    <P>
                        <E T="03">Total Annual Hours:</E>
                         2895. 
                    </P>
                    <P>
                        To obtain copies of the supporting statement and any related forms for the proposed paperwork collections referenced above, e-mail your request, including your address, phone number, OMB number, and OS document identifier, to 
                        <E T="03">Sherette.funncoleman@hhs.gov</E>
                         , or call the Reports Clearance Office on (202) 690-6162. Written comments and recommendations for the proposed information collections must be received within 30 days of this notice directly to the Desk Officer at the address below: 
                    </P>
                    <P>
                        <E T="03">OMB Desk Officer:</E>
                         John Kraemer, OMB Human Resources and Housing Branch, 
                        <E T="03">Attention:</E>
                         (OMB #4040-0005), New Executive Office Building, Room 10235, Washington, DC 20503. 
                    </P>
                </AGY>
                <SIG>
                    <DATED>Dated: April 5, 2007. </DATED>
                    <NAME>Mary Oliver-Anderson, </NAME>
                    <TITLE>Paperwork Reduction Act Reports Clearance Officer, Office of the Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. E7-7004 Filed 4-12-07; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4150-17-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES </AGENCY>
                <SUBAGY>Centers for Medicare &amp; Medicaid Services </SUBAGY>
                <DEPDOC>[Document Identifier: CMS-10227, CMS-1561 and 1561A, CMS-2728, CMS-10221, CMS-R-290, and CMS-R-26] </DEPDOC>
                <SUBJECT>Agency Information Collection Activities: Proposed Collection; Comment Request </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Centers for Medicare &amp; Medicaid Services. </P>
                </AGY>
                <P>In compliance with the requirement of section 3506(c)(2)(A) of the Paperwork Reduction Act of 1995, the Centers for Medicare &amp; Medicaid Services (CMS) 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>
                     Existing collection in use without an OMB Control Number; 
                    <E T="03">Title of Information Collection:</E>
                     PACE State Plan Amendment Pre-print; 
                    <E T="03">Form Number:</E>
                     CMS-10227 (OMB#: 0938-New); 
                    <E T="03">Use:</E>
                     The Balanced Budget Act of 1997 created section 1934 of the Social Security Act that established the Program for the All-Inclusive Care for the Elderly (PACE). The legislation established the PACE program as a Medicaid State plan option serving the frail and elderly in the home and community. In accordance with the rule published in the November 24, 1999 
                    <E T="04">Federal Register</E>
                     (64 FR 66271), if a State elects to offer PACE as an optional Medicaid benefit, it must complete a State Plan Amendment described as Enclosures #3, 4, 5, 6 and 7. In State Medicaid Director letters dated March 23, 1998 and November 9, 2000, CMS advised States that it had provided a suggested pre-print and supplemental pages for a State to express its intention to elect PACE as an option to its State plans. As pre-print packet Enclosures #3-7 were suggested and not required, CMS did not believe at the time that a suggested form required clearance from OMB. The PACE regulation 42 CFR part 460 was first published in the 
                    <E T="04">Federal Register</E>
                     as an interim final rule on November 24, 1999. The final PACE rule was published on December 8, 2006. CMS is seeking OMB approval to use Enclosures #3, 4, 5, 6 and 7. The information is used by CMS to affirm that the State elects to offer PACE an optional State plan service and the specifications of eligibility, payment and enrollment for the program; 
                    <E T="03">Frequency:</E>
                     Reporting—Once; 
                    <E T="03">Affected Public:</E>
                     State, Local or Tribal Governments; 
                    <E T="03">Number of Respondents:</E>
                     56; 
                    <E T="03">Total Annual Responses:</E>
                     56 possible responses but we have only received 20 thus far; 
                    <E T="03">Total Annual Hours:</E>
                     1,120. 
                </P>
                <P>
                    2. 
                    <E T="03">Type of Information Collection Request:</E>
                     Extension without change of a currently approved collection; 
                    <E T="03">Title of Information Collection:</E>
                     Health Insurance Benefit Agreement and Supporting Regulations at 42 CFR 489; 
                    <E T="03">Form Numbers:</E>
                     CMS-1561 and 1561A (OMB#: 0938-0832); 
                    <E T="03">Use:</E>
                     Applicants to the Medicare program are required to agree to provide services in accordance with Federal requirements. The CMS-1561 and 1561A are essential for CMS to ensure that applicants are in compliance with the requirements. Applicants will be required to sign the completed form and provide operational information to CMS to assure that they continue to meet the requirements after approval; 
                    <E T="03">Frequency:</E>
                     Reporting—Other: all new applicants must complete; 
                    <E T="03">Affected Public:</E>
                     State, Local or Tribal Governments, Business or Other for profit and Not-for-profit institutions; 
                    <E T="03">Number of Respondents:</E>
                     3300; 
                    <E T="03">
                        Total 
                        <PRTPAGE P="18659"/>
                        Annual Responses:
                    </E>
                     3300; 
                    <E T="03">Total Annual Hours:</E>
                     275. 
                </P>
                <P>
                    3. 
                    <E T="03">Type of Information Collection Request:</E>
                     Extension of a currently approved collection; 
                    <E T="03">Title of Information Collection:</E>
                     End Stage Renal Disease Medical Evidence Report Medicare Entitlement and/or Patient Registration; 
                    <E T="03">Form Number:</E>
                     CMS-2728 (OMB#: 0938-0046); 
                    <E T="03">Use:</E>
                     The End Stage Renal Disease Medical Evidence (CMS-2728) is completed for all ESRD patients either by the first treatment facility or by a Medicare-approved ESRD facility when it is determined by a physician that the patient's condition has reached that stage of renal impairment that a regular course of kidney dialysis or a kidney transplant is necessary to maintain life. 
                </P>
                <P>
                    The data reported on the CMS-2728 is used by the Federal Government, ESRD Networks, treatment facilities, researchers and others to monitor and assess the quality and type of care provided to end stage renal beneficiaries. The data collection captures the specific medical information required to determine the Medicare medical eligibility of End Stage Renal Disease claimants. It also collects data for research and policy on this population. 
                    <E T="03">Frequency:</E>
                     Reporting—Once; 
                    <E T="03">Affected Public:</E>
                     Individuals or households, Business or other-for-profit, Not-for-profit institutions; 
                    <E T="03">Number of Respondents:</E>
                     100,000; 
                    <E T="03">Total Annual Responses:</E>
                     100,000; 
                    <E T="03">Total Annual Hours:</E>
                     75,000. 
                </P>
                <P>
                    4. 
                    <E T="03">Type of Information Collection Request:</E>
                     New collection; 
                    <E T="03">Title of Information Collection:</E>
                     Worksheet for Recording Results of Medicare Site Visits of Independent Diagnostic Testing Facilities (IDTFs) Form; 
                    <E T="03">Form Number:</E>
                     CMS-10221 (OMB#: 0938-New); 
                    <E T="03">Use:</E>
                     Prior to enrolling in Medicare, independent diagnostic testing facilities (IDTFs) must undergo a site visit as required under 42 CFR 410.33. The purpose of the site visit is to ensure that the IDTF is in compliance with the provisions of 42 CFR 410.33, as well as all other applicable Federal, State and local laws and regulations. It is also used to verify the information the IDTF furnished on its CMS-855B enrollment application. 
                </P>
                <P>
                    Section 410.33 contains a significant number of standards that IDTFs must meet in order to enroll in Medicare. Compliance with the standards further ensures that only qualified and legitimate IDTFs can bill Medicare. This is especially important in light of concerns about recent fraudulent activity by some IDTFs. We are submitting the “Worksheet for Recording Results of Medicare Site Visits of Independent Diagnostic Testing Facilities (IDTFs),” for OMB approval. The purpose of this document is to ensure that the individuals performing IDTF site visits take into account both new and existing IDTF standards in a consistent fashion. 
                    <E T="03">Frequency:</E>
                     Reporting—On occasion; 
                    <E T="03">Affected Public:</E>
                     Business or other-for-profit, Not-for-profit institutions; 
                    <E T="03">Number of Respondents:</E>
                     2,000; 
                    <E T="03">Total Annual Responses:</E>
                     2,000; 
                    <E T="03">Total Annual Hours:</E>
                     4,000. 
                </P>
                <P>
                    5. 
                    <E T="03">Type of Information Collection Request:</E>
                     Extension of a currently approved collection; 
                    <E T="03">Title of Information Collection:</E>
                     Medicare Program: Process for Making National Coverage Determinations; 
                    <E T="03">Form Number:</E>
                     CMS-R-290 (OMB#: 0938-0776); 
                    <E T="03">Use:</E>
                     On September 26, 2003 (68 FR 55634), we published a notice that described how we revised the process we use to make Medicare coverage decisions including decisions regarding whether new technology and services can be covered. In accordance with section IV.B of the aforementioned notice, CMS' Revised Process for Making National Coverage Determinations, we require an individual or entity to make a formal request for a national coverage determination. Upon receipt of a formal request and adequate supporting documentation, we will make a determination based on the evidence presented, to cover the device or service or not to cover the device or service where it is not supported by the medical evidence. We are resubmitting this information collection request (ICR) to the Office of Management and Budget as an extension of the currently approved collection. We have not made any material modifications to the ICR since the last submission. 
                    <E T="03">Frequency:</E>
                     Recordkeeping and Reporting—On occasion; 
                    <E T="03">Affected Public:</E>
                     Business or other-for-profit, Not-for-profit institutions; 
                    <E T="03">Number of Respondents:</E>
                     200; 
                    <E T="03">Total Annual Responses:</E>
                     200; 
                    <E T="03">Total Annual Hours:</E>
                     8,000. 
                </P>
                <P>
                    6. 
                    <E T="03">Type of Information Collection Request:</E>
                     Extension without change of a currently approved collection; 
                    <E T="03">Title of Information Collection:</E>
                     Information Collection Requirements (ICRs) Contained in the Clinical Laboratory Improvement Amendments (CLIA) Regulations 42 CFR part 493.801, 493.803, 493.1232, 493.1233, 493.1234, 493.1235, 493.1236, 493.1239, 493.1241, 493.1242, 493.1249, 493.1251, 493.1252, 439.1253, 493.1254, 493.1255, 493.1256, 493.1261, 493.1262, 493.1263, 493.1269, 493.1273, 493.1274, 493.1278, 493.1283, 493.1289, 493.1291, and 493.1299; 
                    <E T="03">Form Numbers:</E>
                     CMS-R-26 (OMB#: 0938-0612); 
                    <E T="03">Use:</E>
                     The ICRs referenced in 42 CFR part 493 outline the requirements necessary to determine an entity's complicance with CLIA. CLIA requires laboratories that perform testing on human beings to meet performance requirements (quality standards) in order to be certified by the Department of Health and Human Services (HHS). HHS conducts inspections to determine a laboratory's compliance with CLIA requirements. CLIA implements the certificate, laboratory standards and inspection requirements; 
                    <E T="03">Frequency:</E>
                     Reporting—As needed; 
                    <E T="03">Affected Public:</E>
                     State, Local or Tribal Governments, Federal Government, Business or Other for profit and Not-for-profit institutions; 
                    <E T="03">Number of Respondents:</E>
                     168,688; 
                    <E T="03">Total Annual Responses:</E>
                     756,241; 
                    <E T="03">Total Annual Hours:</E>
                     11,363,680. 
                </P>
                <P>
                    To obtain copies of the supporting statement and any related forms for the proposed paperwork collections referenced above, access CMS' Web Site address at 
                    <E T="03">http://www.cms.hhs.gov/PaperworkReductionActof1995</E>
                    , or E-mail your request, including your address, phone number, OMB number, and CMS document identifier to 
                    <E T="03">Paperwork@cms.hhs.gov</E>
                    , or call the Reports Clearance Office on (410) 786-1326. 
                </P>
                <P>To be assured consideration, comments and recommendations for the proposed information collections must be received at the address below, no later than 5 p.m. on June 12, 2007. </P>
                <P>CMS, Office of Strategic Operations and Regulatory Affairs, Division of Regulations Development—A, Attention: Melissa Musotto, Room C4-26-05, 7500 Security Boulevard, Baltimore, Maryland 21244-1850. </P>
                <SIG>
                    <DATED>Dated: April 6, 2007. </DATED>
                    <NAME>Michelle Shortt, </NAME>
                    <TITLE>Director, Regulations Development Group, Office of Strategic Operations and Regulatory Affairs.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. E7-6990 Filed 4-12-07; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4120-01-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>Food and Drug Administration</SUBAGY>
                <DEPDOC>[Docket No. 2007N-0015]</DEPDOC>
                <SUBJECT>Agency Information Collection Activities; Submission for Office of Management and Budget Review; Comment Request; Adoption of the Food and Drug Administration Food Code by Local, State, and Tribal Governments</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Food and Drug Administration, HHS.</P>
                </AGY>
                <ACT>
                    <PRTPAGE P="18660"/>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Food and Drug Administration (FDA) is announcing that a proposed collection of information has been submitted to the Office of Management and Budget (OMB) for review and clearance under the Paperwork Reduction Act of 1995.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Fax written comments on the collection of information by May 14, 2007.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>To ensure that comments on the information collection are received, OMB recommends that written comments be faxed to the Office of Information and Regulatory Affairs, OMB, Attn: FDA Desk Officer, FAX: 202-395-6974.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Jonna Capezzuto, Office of the Chief Information Officer (HFA-250), Food and Drug Administration, 5600 Fishers Lane, Rockville, MD 20857, 301-827-4659.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>In compliance with 44 U.S.C. 3507, FDA has submitted the following proposed collection of information to OMB for review and clearance.</P>
                <HD SOURCE="HD1">Adoption of the Food and Drug Administration Food Code by Local, State, and Tribal Governments (OMB Control Number 0910-0448)—Extension</HD>
                <P>FDA has developed its model Food Code to assist and promote consistent implementation of national food safety regulatory policy among the local, State, and tribal governmental agencies that have primary responsibility for the regulation or oversight of retail level food operations. The FDA Food Code provides a scientifically sound technical and legal basis for regulating the retail segment of the food industry. Authority for providing such assistance is derived from section 311(a) of the Public Health Service Act (42 U.S.C. 243(a)). Under 31 U.S.C. 1535, FDA provides assistance to other Federal agencies such as the Indian Health Service.</P>
                <P>Nationwide adoption of the model FDA Food Code is an important step toward the agency's goal for consistent, scientifically sound, and risk-based food safety standards and practices. A current, comprehensive, and accurate inventory of food code adoptions by States and U.S. territories, local, and tribal governments is necessary to determine the status of up-to-date protection of the U.S. population and to identify areas where assistance to these governments may promote the adoption of regulations based on the FDA Food Code.</P>
                <P>This collection effort, which began in 2001, has had remarkable success with 97 percent participation from State and territorial governmental agencies. FDA contracted with the Association of Food and Drug Officials (AFDO) to conduct the initial survey using the OMB approved survey form. The rulemaking process that local, State, territorial, and tribal governmental agencies must follow to adopt the model FDA Food Code is often a long and complicated process that can extend for several years. For this reason, many agencies have reported that they are still in the rulemaking process to adopt or update their food codes. Thus, FDA believes that extension of OMB approval of the survey is needed in order to keep the current database accurate and up-to-date. AFDO will collect the information electronically and/or telephonically and will be able to provide respondents with previous survey responses already in the database.</P>
                <P>
                    <E T="03">Description of Respondents</E>
                    : States and U.S. territories, local, and tribal governmental agencies.
                </P>
                <P>
                    In the 
                    <E T="04">Federal Register</E>
                     of January 26, 2007 (72 FR 3862), FDA published a 60-day notice requesting public comment on the information collection provisions. We received one comment, which was non-responsive to our request for comments on the proposed information collection.
                </P>
                <GPOTABLE COLS="6" OPTS="L4,nj,i2" CDEF="xl50,15,18,15,15,15">
                    <TTITLE>
                        <E T="04">Table 1.—Estimated Annual Reporting Burden</E>
                        <SU>1</SU>
                    </TTITLE>
                    <BOXHD>
                        <CHED H="1">Food Code Survey</CHED>
                        <CHED H="1">
                            No. of
                            <LI>Respondents</LI>
                        </CHED>
                        <CHED H="1">
                            Annual Frequency
                            <LI>per Response</LI>
                        </CHED>
                        <CHED H="1">
                            Total Annual
                            <LI>Responses</LI>
                        </CHED>
                        <CHED H="1">
                            Hours per
                            <LI>Response</LI>
                        </CHED>
                        <CHED H="1">Total Hours</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Respondents</ENT>
                        <ENT>75</ENT>
                        <ENT>4</ENT>
                        <ENT>300</ENT>
                        <ENT>1</ENT>
                        <ENT>300</ENT>
                    </ROW>
                    <TNOTE>
                        <SU>1</SU>
                        There are no capital costs or operating and maintenance costs associated with this collection of information.
                    </TNOTE>
                </GPOTABLE>
                <P>This estimate is based on FDA's experience and the number of updates received in the past 3 years. FDA has reduced the estimated number of annual respondents from 150 to 75. FDA estimates that 75 respondents will provide four quarterly updates each, resulting in an estimated 300 total annual responses. The agency estimates that each quarterly update will take about 1 hour. Of the 75 respondents, those who amend their regulations with changes unrelated to the risk factors and interventions, and those who are not adopting model FDA Food Code provisions, but are incorporating certain Conference for Food Protection recommendations only, will likely need only annual contact.</P>
                <SIG>
                    <DATED>Dated: April 9, 2007.</DATED>
                    <NAME>Jeffrey Shuren,</NAME>
                    <TITLE>Assistant Commissioner for Policy.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. E7-6983 Filed 4-12-07; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4160-01-S</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>Food and Drug Administration</SUBAGY>
                <DEPDOC>[Docket No. 2006N-0525]</DEPDOC>
                <SUBJECT>Supplements and Other Changes to an Approved Application; Public Meeting; Reopening of Comment Period</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P> Food and Drug Administration, HHS.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P> Notice; reopening of comment period.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                         The Food and Drug Administration (FDA) is reopening until May 18, 2007, the comment period for a notice of public meeting that published in the 
                        <E T="04">Federal Register</E>
                         of January 5, 2007 (72 FR 574). In the notice, FDA announced a February 7, 2007, meeting to solicit input on issues that the agency should consider if it decides to propose revisions to its regulations regarding chemistry, manufacturing, and controls (CMC) supplements and other changes to approved marketing applications for human drugs. FDA is reopening the comment period in light of continued public interest in this topic.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P> Submit written or electronic comments by May 18, 2007.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                         Submit written comments to the Division of Dockets Management (HFA-305), Food and Drug 
                        <PRTPAGE P="18661"/>
                        Administration, 5630 Fishers Lane, rm. 1061, Rockville, MD 20852. Submit electronic comments to 
                        <E T="03">http://www.fda.gov/dockets/ecomments</E>
                        .
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        David J. Cummings, Center for Drug Evaluation and Research, Food and Drug Administration, 10903 New Hampshire Ave., Bldg. 21, rm. 3525, Rockville, MD 20993-0002, 301-796-2400, e-mail: 
                        <E T="03">David.Cummings@fda.hhs.gov</E>
                        .
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Background</HD>
                <P>On February 7, 2007, FDA held a public meeting to solicit comments on issues that FDA should consider if it decides to propose revisions to § 314.70 (21 CFR 314.70) regarding CMC supplements and other changes to approved marketing applications for human drugs. In the notice announcing the public meeting (72 FR 574), FDA stated that current § 314.70 categorizes postapproval CMC changes and their associated reporting requirements without consideration of the applicant's risk management activities or internal quality systems and practices; therefore, § 314.70 reflects a rules-based, or prescriptive, approach to regulating postapproval manufacturing changes. Current § 314.70 may create regulatory burdens and costs that discourage beneficial manufacturing changes and may not support a desirable level of innovation, modernization, and flexibility for the industry as described in FDA's pharmaceutical current good manufacturing practices for the 21st century initiative (CGMP Initiative). Consistent with the agency's risk-based approach to regulating pharmaceutical manufacturing described in the CGMP Initiative, FDA is considering possible revisions to § 314.70 to allow for more manufacturing changes to be made without prior FDA approval using a firm's internal change control system and to allow for consideration of risk-based approaches based on manufacturing process understanding, including prior knowledge of similar products, and overall quality systems to provide an enhanced risk-based approach to the CMC regulatory process.</P>
                <P>Interested persons were given until March 7, 2007, to submit written or electronic comments to the agency related to the focus of the public meeting. As a result of continued public interest, FDA is reopening the comment period until May 18, 2007, to allow interested persons additional time to submit comments.</P>
                <HD SOURCE="HD1">II. Request for Comments</HD>
                <P>
                    Interested persons may submit to the Division of Dockets Management (see 
                    <E T="02">ADDRESSES</E>
                    ) written or electronic comments related to this topic (see 
                    <E T="02">DATES</E>
                    ). All relevant data and information should be submitted with the written comments. Submit a single copy of electronic comments or two paper copies of any mailed comments, except that individuals may submit one copy. Comments are to be identified with Docket No. 2006N-0525. Received comments may be seen in the Division of Dockets Management between 9 a.m. and 4 p.m., Monday through Friday.
                </P>
                <SIG>
                    <DATED>Dated: April 5, 2007.</DATED>
                    <NAME>Jeffrey Shuren,</NAME>
                    <TITLE>Assistant Commissioner for Policy.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. E7-6985 Filed 4-12-07; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4160-01-S</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES </AGENCY>
                <SUBAGY>Health Resources and Services Administration </SUBAGY>
                <SUBJECT>Agency Information Collection Activities: Proposed Collection: Comment Request </SUBJECT>
                <P>In compliance with the requirement for opportunity for public comment on proposed data collection projects (section 3506(c)(2)(A) of Title 44, United States Code, as amended by the Paperwork Reduction Act of 1995, Pub. L. 104-13), the Health Resources and Services Administration (HRSA) publishes periodic summaries of proposed projects being developed for submission to the Office of Management and Budget (OMB) under the Paperwork Reduction Act of 1995. To request more information on the proposed project or to obtain a copy of the data collection plans and draft instruments, call the HRSA Reports Clearance Officer on (301) 443-1129. </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. </P>
                <HD SOURCE="HD1">Proposed Project: Bureau of Primary Health Care (BPHC) Uniform Data System (OMB No. 0915-0193) Revision for 2008 </HD>
                <P>The Uniform Data System (UDS) contains the annual reporting requirements for the cluster of primary care grantees funded by the Health Resources and Services Administration (HRSA). The UDS includes reporting requirements for grantees of the following primary care programs: Community Health Centers, Migrant Health Centers, Health Care for the Homeless, Public Housing Primary Care, and other grantees under Section 330. The authorizing statute is section 330 of the Public Health Service Act, as amended. </P>
                <P>HRSA collects data in the UDS which is used to ensure compliance with legislative mandates and to report to Congress and policymakers on program accomplishments. To meet these objectives, BPHC requires a core set of data collected annually that is appropriate for monitoring and evaluating performance and reporting on annual trends. The 2008 calendar year UDS will be revised in several ways. Certain UDS tables are being proposed for elimination or modification to streamline data collection and reporting. A limited number of clinical measures will be added for reporting quality of care, health outcomes, and disparities data. In addition, the tool used to report calendar year UDS data will be changed to a Web-based tool. </P>
                <P>Estimates of Annualized Reporting Burden are as Follows:</P>
                <GPOTABLE COLS="5" OPTS="L2,i1,tp0," CDEF="s50,12,12,12,12">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Type of report </CHED>
                        <CHED H="1">
                            Number of 
                            <LI>respondents </LI>
                        </CHED>
                        <CHED H="1">
                            Responses per 
                            <LI>respondent </LI>
                        </CHED>
                        <CHED H="1">
                            Hours per 
                            <LI>response </LI>
                        </CHED>
                        <CHED H="1">Total burden hours </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Universal report </ENT>
                        <ENT>1076 </ENT>
                        <ENT>1 </ENT>
                        <ENT>30 </ENT>
                        <ENT>32,280 </ENT>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="01">Grant report</ENT>
                        <ENT>240 </ENT>
                        <ENT>1 </ENT>
                        <ENT>18 </ENT>
                        <ENT>4,320 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Total </ENT>
                        <ENT>1076 </ENT>
                        <ENT/>
                        <ENT/>
                        <ENT>36,600 </ENT>
                    </ROW>
                </GPOTABLE>
                <PRTPAGE P="18662"/>
                <P>Send comments to Susan G. Queen, PhD, HRSA Reports Clearance Officer, Room 10-33, Parklawn Building, 5600 Fishers Lane, Rockville, MD 20857. Written comments should be received within 60 days of this notice. </P>
                <SIG>
                    <DATED>Dated: April 6, 2007. </DATED>
                    <NAME>Caroline Lewis, </NAME>
                    <TITLE>Acting Associate Administrator for Administration and Financial Management. </TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. E7-6991 Filed 4-12-07; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4165-15-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES </AGENCY>
                <SUBAGY>Health Resources and Services Administration </SUBAGY>
                <SUBJECT>Agency Information Collection Activities: Submission For OMB Review; Comment Request </SUBJECT>
                <P>Periodically, the Health Resources and Services Administration (HRSA) publishes abstracts of information collection requests under review by the Office of Management and Budget (OMB), in compliance with the Paperwork Reduction Act of 1995 (44 U.S.C. Chapter 35). To request a copy of the clearance requests submitted to OMB for review, call the HRSA Reports Clearance Office on (301) 443-1129. </P>
                <P>The following request has been submitted to OMB for review under the Paperwork Reduction Act of 1995: </P>
                <HD SOURCE="HD1">Proposed Project: The Health Education Assistance Loan Program: Physician's Certification of Borrower's Total and Permanent Disability Form (OMB No. 0915-0204 Extension) </HD>
                <P>The Health Education Assistance Loan (HEAL) program provided federally-insured loans to students in schools of allopathic medicine, osteopathic medicine, dentistry, veterinary medicine, optometry, podiatric medicine, pharmacy, public health, allied health or chiropractic, and graduate students in health administration or clinical psychology through September 30, 1998. Eligible lenders, such as banks, savings and loan associations, credit unions, pension funds, State agencies, HEAL schools, and insurance companies, were permitted to refinance HEAL loans which were insured by the Federal Government against loss due to borrower's death, disability, bankruptcy, and default until the authority to refinance HEAL loans expired on September 30, 2004. The basic purpose of the program was to assure the availability of funds for loans to eligible students who needed to borrow money to pay for their educational loans. Currently, the program monitors the Federal liability and assists in default prevention activities. The HEAL borrower, the borrower's physician, and the holder of the loan completes the Physician's Certification form to certify that the HEAL borrower meets the total and permanent disability provisions. </P>
                <P>The Department uses this form to obtain detailed information about disability claims which includes the following: (1) The borrower's consent to release medical records to the Department of Health and Human Services and to the holder of the borrower's HEAL loans, (2) pertinent information supplied by the certifying physician, (3) the Physician's Certification that the borrower is unable to engage in any substantial gainful activity because of a medically determined impairment that is expected to continue for a long and indefinite period of time or to result in death, and (4) information from the lender on the unpaid balance. Failure to submit the required documentation will result in disapproval of a disability claim. </P>
                <P>The estimate of burden for the Physician's Certification form is as follows: </P>
                <GPOTABLE COLS="06" OPTS="L2,tp0,i1" CDEF="s50,12,12,12,12,12">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Type of respondent</CHED>
                        <CHED H="1">
                            Number of 
                            <LI>respondents</LI>
                        </CHED>
                        <CHED H="1">Responses per respondent</CHED>
                        <CHED H="1">
                            Number of 
                            <LI>responses</LI>
                        </CHED>
                        <CHED H="1">Minutes per response</CHED>
                        <CHED H="1">Total burden hours</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Borrower</ENT>
                        <ENT>80</ENT>
                        <ENT>1</ENT>
                        <ENT>80</ENT>
                        <ENT>5</ENT>
                        <ENT>7</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Physician</ENT>
                        <ENT>80</ENT>
                        <ENT>1</ENT>
                        <ENT>80</ENT>
                        <ENT>30</ENT>
                        <ENT>40</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Loan Holder</ENT>
                        <ENT>17</ENT>
                        <ENT>5</ENT>
                        <ENT>85</ENT>
                        <ENT>10</ENT>
                        <ENT>14</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Total</ENT>
                        <ENT>177</ENT>
                        <ENT/>
                        <ENT>245</ENT>
                        <ENT/>
                        <ENT>61</ENT>
                    </ROW>
                </GPOTABLE>
                <P>Written comments and recommendations concerning the proposed information collection should be sent within 30 days of this notice to: Karen Matsuoka, Health Resources and Services Administration, Human Resources and Housing Branch, OMB, New Executive Office Building, Room 10235, Washington, DC 20503. </P>
                <SIG>
                    <DATED>Dated: April 6, 2007. </DATED>
                    <NAME>Caroline Lewis, </NAME>
                    <TITLE>Acting Associate Administrator for Administration and Financial Management.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC> [FR Doc. E7-6992 Filed 4-12-07; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4165-15-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>Health Resources and Services Administration</SUBAGY>
                <SUBJECT>National Vaccine Injury Compensation Program; List of Petitions Received</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Health Resources and Services Administration, HHS.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Health Resources and Services Administration (HRSA) is publishing this notice of petitions received under the National Vaccine Injury Compensation Program (“the Program”), as required by Section 2112(b)(2) of the Public Health Service (PHS) Act, as amended. While the Secretary of Health and Human Services is named as the respondent in all proceedings brought by the filing of petitions for compensation under the Program, the United States Court of Federal Claims is charged by statute with responsibility for considering and acting upon the petitions.</P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>For information about requirements for filing petitions, and the Program is general, contact the Clerk, United States Court of Federal Claims, 717 Madison Place, NW., Washington, DC 20005, (202) 357-6400. For information on HRSA's role in the Program, contact the Director, National Vaccine Injury Compensation Program, 5600 Fishers Lane, Room 11C-26, Rockville, MD 20857; (301) 443-6593.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    The Program provides a system of no-fault compensation for certain individuals who have been injured by specified childhood vaccines. Subtitle 2 of Title XXI of the PHS Act, 42 U.S.C. 300aa-10 
                    <E T="03">et seq.</E>
                    , provides that those seeking 
                    <PRTPAGE P="18663"/>
                    compensation are to file a petition with the U.S. Court of Federal Claims and to serve a copy of the petition on the Secretary of Health and Human Services, who is named as the respondent in each proceeding. The Secretary has delegated his responsibility under the Program to HRSA. The Court is directed by statute to appoint special masters who take evidence, conduct hearings as appropriate, and make initial decisions as to eligibility for, and amount of, compensation. 
                </P>
                <P>A petition may be filed with respect to injuries, disabilities, illnesses, conditions, and deaths resulting from vaccines described in the Vaccine Injury Table (the Table) set forth at Section 2114 of the PHS Act or as set forth at 42 CFR 100.3, as applicable. This Table lists for each covered childhood vaccine the conditions which may lead to compensation and, for each condition, the time period for occurrence of the first symptom or manifestation of onset or of significant aggravation after vaccine administration. Compensation may also be awarded for conditions not listed in the Table and for conditions that are manifested outside the time periods specified in the Table, but only if the petitioner shows that the condition was caused by one of the listed vaccines. </P>
                <P>
                    Section 2112(b)(2) of the PHS Act, 42 U.S.C. 300aa-12(b)(2), requires that the Secretary publish in the 
                    <E T="04">Federal Register</E>
                     a notice of each petition filed. Set forth below is a list of petitions received by HRSA on October 1, 2006, through December 31, 2006. 
                </P>
                <P>Section 2112(b)(2) also provides that the special master “shall afford all interested persons an opportunity to submit relevant, written information” relating to the following: </P>
                <P>1. The existence of evidence “that there is not a preponderance of the evidence that the illness, disability, injury, condition, or death described in the petition is due to factors unrelated to the administration of the vaccine described in the petition,” and </P>
                <P>2. Any allegation in a petition that the petitioner either: </P>
                <P>(a) “Sustained, or had significantly aggravated, any illness, disability, injury, or condition not set forth in the Table but which was caused by” one of the vaccines referred to in the Table, or </P>
                <P>(b) “Sustained, or had significantly aggravated, any illness, disability, injury, or condition set forth in the Vaccine Injury Table the first symptom or manifestation of the onset or significant aggravation of which did not occur within the time period set forth in the Table but which was caused by a vaccine” referred to in the Table. </P>
                <P>
                    This notice will also serve as the special master's invitation to all interested persons to submit written information relevant to the issues described above in the case of the petitions listed below. Any person choosing to do so should file an original and three (3) copies of the information with the Clerk of the U.S. Court of Federal Claims at the address listed above (under the heading 
                    <E T="02">For Further Information Contact</E>
                    ), with a copy to HRSA addressed to Director, Division of Vaccine Injury Compensation Program, Healthcare Systems Bureau, 5600 Fishers Lane, Room 11C-26, Rockville, MD 20857. The Court's caption (Petitioner's Name v. Secretary of Health and Human Services) and the docket number assigned to the petition should be used as the caption for the written submission. Chapter 35 of title 44, United States Code, related to paperwork reduction, does not apply to information required for purposes of carrying out the Program. 
                </P>
                <HD SOURCE="HD1">List of Petitions </HD>
                <FP SOURCE="FP-1">1. Jon Rooney, Bath, Maine, Court of Federal Claims Number 06-0684V. </FP>
                <FP SOURCE="FP-1">2. Haleh Niazmand on behalf of Keyon Ellis, Cedar Rapids, Iowa, Court of Federal Claims Number 06-0692V.</FP>
                <FP SOURCE="FP-1">3. Erich Fortenberry on behalf of Nahaley Fortenberry, Lawton, Oklahoma, Court of Federal Claims Number 06-0693V.</FP>
                <FP SOURCE="FP-1">4. Roberta and Robert Schoeneman on behalf of Nicole Marie Schoeneman, Stony Brook, New York, Court of Federal Claims Number 06-0703V.</FP>
                <FP SOURCE="FP-1">5. Jane Daus, Monrovia, Maryland, Court of Federal Claims Number 06-0705V. </FP>
                <FP SOURCE="FP-1">6. Wayne Pestka on behalf of Kelsey Lynn Short, Deceased, Waconia, Minnesota, Court of Federal Claims Number 06-0708V. </FP>
                <FP SOURCE="FP-1">7. Juanita Coleman, Warren, Michigan, Court of Federal Claims Number 06-0710V. </FP>
                <FP SOURCE="FP-1">8. Nancy Westermann, Springfield, Massachusetts, Court of Federal Claims Number 06-0711V. </FP>
                <FP SOURCE="FP-1">9. Paige Ingle-Pang, Birmingham, Alabama, Court of Federal Claims Number 06-0713V. </FP>
                <FP SOURCE="FP-1">10. Gary Mericle, Jacksonville, Florida, Court of Federal Claims Number 06-0719V. </FP>
                <FP SOURCE="FP-1">11. Christopher Black, Chattanooga, Tennessee, Court of Federal Claims Number 06-0720V. </FP>
                <FP SOURCE="FP-1">12. Marie Elena Navarro and Patrick James Furman on behalf of Celia Dorothy Furman, Deceased, Plattsburgh, New York, Court of Federal Claims Number 06-0722V. </FP>
                <FP SOURCE="FP-1">13. Dean Dayton, South Ogden, Utah, Court of Federal Claims Number 06-0724V. </FP>
                <FP SOURCE="FP-1">14. Esfandiar Santini and Laurie Omidvar on behalf of Aydien Cliff Omidvar, Oceanside, California, Court of Federal Claims Number 06-0725V. </FP>
                <FP SOURCE="FP-1">15. Thomas Bigelow, Jr., Grand Rapids, Michigan, Court of Federal Claims Number 06-0727V. </FP>
                <FP SOURCE="FP-1">16. Elizabeth and Jeffrey Wilkins on behalf of James Wilkins, Minneapolis, Minnesota, Court of Federal Claims Number 06-0728V. </FP>
                <FP SOURCE="FP-1">17. Ruth and Richard DeMars on behalf of Anna DeMars, Portage, Michigan, Court of Federal Claims Number 06-0729V. </FP>
                <FP SOURCE="FP-1">18. Carrie and Matthew Nance on behalf of Katherine Nance, North Canton, Ohio, Court of Federal Claims Number 06-0730V. </FP>
                <FP SOURCE="FP-1">19. Michelle Robinson, Columbia, South Carolina, Court of Federal Claims Number 06-0737V. </FP>
                <FP SOURCE="FP-1">20. Pamela and Craig Hayes on behalf of Hailey Hayes, Beaumont, Texas, Court of Federal Claims Number 06-0738V. </FP>
                <FP SOURCE="FP-1">21. Wanda and Marty Wright on behalf of Alicia Hendrick, West Union, Iowa, Court of Federal Claims Number 06-0750V. </FP>
                <FP SOURCE="FP-1">22. Tara and Bruce Miller on behalf of William Miller, St. Cloud, Minnesota, Court of Federal Claims Number 06-0753V. </FP>
                <FP SOURCE="FP-1">23. Anne Carow on behalf of Anne Carow, Austin, Texas, Court of Federal Claims Number 06-0754V. </FP>
                <FP SOURCE="FP-1">24. William Walker, Binghampton, New York, Court of Federal Claims Number 06-0756V. </FP>
                <FP SOURCE="FP-1">25. Robert Lauder on behalf of Krista Lauder, Deceased, Pittsburgh, Pennsylvania, Court of Federal Claims Number 06-0758V. </FP>
                <FP SOURCE="FP-1">26. Noel Schneider on behalf of Spencer Schneider, Somers Point, New Jersey, Court of Federal Claims Number 06-0759V. </FP>
                <FP SOURCE="FP-1">27. Natalia Glaser on behalf of Marius Glaser, Boston, Massachusetts, Court of Federal Claims Number 06-0764V. </FP>
                <FP SOURCE="FP-1">28. Christine and Gregory Pifer on behalf of Garrett Pifer, Deceased, Tampa, Florida, Court of Federal Claims Number 06-0765V. </FP>
                <FP SOURCE="FP-1">29. Janice Crabtree and Jeffrey Ambroziak on behalf of Colby Ambroziak, Boston, Massachusetts, Court of Federal Claims Number 06-0767V. </FP>
                <FP SOURCE="FP-1">
                    30. Valerie and Lawrence Parker on behalf of Benjamin Parker, Sarasota, Florida, Court of Federal Claims Number 06-0768V. 
                    <PRTPAGE P="18664"/>
                </FP>
                <FP SOURCE="FP-1">31. Charles Abendroth, San Jose, California, Court of Federal Claims Number 06-0769V. </FP>
                <FP SOURCE="FP-1">32. Courtney Grooms on behalf of Ayon Conway, Deceased, Columbia, South Carolina Court of Federal Claims Number 06-0773V. </FP>
                <FP SOURCE="FP-1">33. Brigitte Mueller, Beverly Hills, California, Court of Federal Claims Number 06-0775V. </FP>
                <FP SOURCE="FP-1">34. Earl Stewart, Santa Barbara, California, Court of Federal Claims Number 06-0777V. </FP>
                <FP SOURCE="FP-1">35. Brooke and John Potthast on behalf of James Sommerville Potthast, Arlington, Virginia,  Court of Federal Claims Number 06-0782V. </FP>
                <FP SOURCE="FP-1">36. Vache and Naira Karapetian on behalf of Thomas Karapetian, Torrance, California, Court of Federal Claims Number 06-0783V. </FP>
                <FP SOURCE="FP-1">37. Elizabeth Hanley, Independence, Kansas, Court of Federal Claims Number 06-0784V. </FP>
                <FP SOURCE="FP-1">38. Donald Patterson, Marietta, Georgia, Court of Federal Claims Number 06-0785V. </FP>
                <FP SOURCE="FP-1">39. Alison Reddy and David Abel on behalf of Asher Abel, Portland, Oregon, Court of Federal Claims Number 06-0788V. </FP>
                <FP SOURCE="FP-1">40. Linda Garrett, Zanesville, Ohio, Court of Federal Claims Number 06-0790V. </FP>
                <FP SOURCE="FP-1">41. David Martin, Clover, South Carolina, Court of Federal Claims Number 06-0793V. </FP>
                <FP SOURCE="FP-1">42. Mary and Hugh Simpson on behalf of Mary Simpson, Baltimore, Maryland, Court of Federal Claims Number 06-0794V. </FP>
                <FP SOURCE="FP-1">43. Janice and Robert Bevill on behalf of Victoria Bevill,  Merrimack, New Hampshire, Court of Federal Claims Number 06-0795V. </FP>
                <FP SOURCE="FP-1">44. Janice and Robert Bevill on behalf of Christina Bevil, Merrimack, New Hampshire, Court of Federal Claims Number 06-0808V.</FP>
                <FP SOURCE="FP-1">45. Janice and Robert Bevill on behalf of Robert Christopher Bevill, Merrimack, New Hampshire, Court of Federal Claims Number 06-0809V.</FP>
                <FP SOURCE="FP-1">46. Angela Jaegers on behalf of Brittany Cordes, Cleveland, Ohio, Court of Federal Claims Number 06-0819V. </FP>
                <FP SOURCE="FP-1">47. Robert Pereira, Anchorage, Alaska, Court of Federal Claims Number 06-0820V.</FP>
                <FP SOURCE="FP-1">48. Stephanie and Ralph White on behalf of Averie Elaine White, Jacksonville, Florida, Court of Federal Claims Number 06-0821V. </FP>
                <FP SOURCE="FP-1">49. Michelle and Leo Wentz on behalf of Lincoln Wentz,  Mansfield, Texas, Court of Federal Claims Number 06-0824V. </FP>
                <FP SOURCE="FP-1">50. Carol Jakes on behalf of Dreyton Jakes,  Tracy, California, Court of Federal Claims Number 06-0831V. </FP>
                <FP SOURCE="FP-1">51. Lesli and Michael Ridgway on behalf of Max Ridgway, Bedford, Texas, Court of Federal Claims Number 06-0834V. </FP>
                <FP SOURCE="FP-1">52. Nancy Hughes and Martin Grabstein on behalf of Matthew Grabstein, Lake Success, New York, Court of Federal Claims Number 06-0836V.</FP>
                <FP SOURCE="FP-1">53. Debra and Stephen Shockley on behalf of Stephen A.L. Shockley, Lake Success, New York,  Court of Federal Claims Number 06-0839V. </FP>
                <FP SOURCE="FP-1">54. Lynna Teller on behalf of Naiya Namoki,  Chinle, Arizona, Court of Federal Claims Number 06-0840V. </FP>
                <FP SOURCE="FP-1">55. Mary Margaret and Justin Cain on behalf of Joshua Andrew Cain, Babson Park, Florida, Court of Federal Claims Number 06-0841V. </FP>
                <FP SOURCE="FP-1">56. Mary Margaret and Justin Cain on behalf of Elijah Luke Cain, Babson Park, Florida, Court of Federal Claims Number 06-0842V.</FP>
                <FP SOURCE="FP-1">57. Sharon and Randall Raybuck on behalf of Malachi Raybuck,  Alliance, Ohio, Court of Federal Claims Number 06-0846V. </FP>
                <FP SOURCE="FP-1">58. Sherry Lerwick on behalf of Braden Lerwick, Okinawa, Japan, XX, Court of Federal Claims Number 06-0847V.</FP>
                <FP SOURCE="FP-1">59. Abraham Barron, Topeka, Kansas, Court of Federal Claims Number 06-0855V.</FP>
                <FP SOURCE="FP-1">60. Else and David Tennessen on behalf of Zachary David Tennessen,  Lexington, South   Carolina, Court of Federal Claims Number 06-0862V.</FP>
                <FP SOURCE="FP-1">61. Valerie and Justin Bell on behalf of Justin Jay Garza, Cookeville, Tennessee, Court of Federal Claims Number 06-0863V. </FP>
                <FP SOURCE="FP-1">62. Karen and Timothy Barnette on behalf of Claire Barnette, Southhaven, Mississippi, Court of Federal Claims Number 06-0868V. </FP>
                <FP SOURCE="FP-1">63. Cindy Needham and John Ordille on behalf of Lucas Ordille,  Absecon, New Jersey, Court of Federal Claims Number 06-0869V. </FP>
                <FP SOURCE="FP-1">64. Jeanette O'Dell on behalf of Trent O'Dell, Stone Mountain, Georgia, Court of Federal Claims Number 06-0870V.</FP>
                <FP SOURCE="FP-1">65. Lisa and Todd Rudley on behalf of Max Rudley, Lake Success, New York, Court of Federal Claims Number 06-0878V. </FP>
                <FP SOURCE="FP-1">66. Kathy Leddick, Troy, Michigan, Court of Federal Claims Number 06-0890V.</FP>
                <FP SOURCE="FP-1">67. Elizabeth Snow, LaGrange, Indiana, Court of Federal Claims Number 06-0895V.</FP>
                <FP SOURCE="FP-1">68. Karl Sackinger on behalf of Gabriel Sackinger, Thousand Oaks, California, Court of Federal Claims Number 06-0902V.</FP>
                <FP SOURCE="FP-1">69. Jody and Larry Wright on behalf of Lora Wright, Springfield, Missouri, Court of Federal Claims Number 06-0906V.</FP>
                <FP SOURCE="FP-1">70. Amy and Thomas Wilhelm on behalf of Reese Wilhelm, Lake Success, New York, Court of Federal Claims Number 06-0927V. </FP>
                <SIG>
                    <DATED>Dated: April 6, 2007. </DATED>
                    <NAME>Elizabeth M. Duke, </NAME>
                    <TITLE>Administrator.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC> [FR Doc. E7-6984 Filed 4-12-07; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4165-15-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
                <SUBAGY>Coast Guard</SUBAGY>
                <DEPDOC>[Docket No. USCG-2007-27810]</DEPDOC>
                <SUBJECT>National Maritime Security Advisory Committee</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>U.S. Coast Guard, DHS.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Committee management; notice of open teleconference Federal Advisory Committee meeting.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The National Maritime Security Advisory Committee (NMSAC) will conduct a meeting by teleconference to discuss the DHS Strategy to Enhance International Supply Chain Security.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The teleconference call will take place Thursday, May 3, 2007 from 2 p.m. to 3:30 p.m. EDT.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        The call will be held in room 5222, U.S. Coast Guard Headquarters, 2100 Second St., SW., Washington, DC. Public participation is limited to monitoring the teleconference only, except at the time allotted by the chairperson for public comment; special note, the number of teleconference lines is limited and available on a first-come, first served basis. For call-in information contact Mr. Ike Eisentrout using the contact information below. Requests to have topic related written material distributed to each member of the committee prior to the meeting should reach the contact person at the address below by April 25, 2007. Send written material by mail or electronic mail according to the instructions below. Comments must be identified by docket number USCG-2007-27810 and may be submitted by 
                        <E T="03">one</E>
                         of the following methods:
                    </P>
                    <P>
                        • 
                        <E T="03">Federal eRulemaking Portal: http://www.regulations.gov</E>
                        . Follow the instructions for submitting comments.
                    </P>
                    <P>
                        • 
                        <E T="03">E-mail: NMSAC@uscg.mil.</E>
                         Include the docket number in the subject line of the message.
                    </P>
                    <P>• Fax: 202-372-1905.</P>
                    <P>
                        • Mail: National Maritime Security Advisory Committee, c/o Mr. Ike Eisentrout, CG-3PCP-1, Room 5302, 
                        <PRTPAGE P="18665"/>
                        2100 2nd Street, SW., Washington, DC 20593.
                    </P>
                    <P>
                        <E T="03">Instructions:</E>
                         All submissions received must include the words “National Maritime Security Advisory Committee, Department of Homeland Security” and the docket number for this action. Comments received will be posted without alteration at 
                        <E T="03">http://www.regulations.gov,</E>
                         including any personal information provided.
                    </P>
                    <P>
                        <E T="03">Docket:</E>
                         For access to the docket to read background documents or comments received by the NMSAC, go to 
                        <E T="03">http://www.regulations.gov</E>
                        .
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Mr. Ike Eisentrout, CG-3PCP-1/NMSAC, Room 5302, 2100 2nd Street, SW., Washington, DC 20593, telephone number 202-372-1119, e-mail 
                        <E T="03">brian.k.eisentrout@uscg.mil</E>
                         and fax number 202-372-1905.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>Notice of this meeting is given under the Federal Advisory Committee Act, 5 U.S.C. App. 2.</P>
                <P>From 2 p.m. EDT to 3:30 p.m. EDT, May 3, 2007 the committee will meet via teleconference for the purpose of discussing and approving the NMSAC's comments and recommendations on the review of the DHS Strategy to Enhance International Supply Chain Security. The chairperson of the NMSAC shall conduct the teleconference meeting in a way that will, in the chair's judgment, facilitate the orderly conduct of business. Please note that the teleconference may end early if all business is completed.</P>
                <P>
                    <E T="03">Agenda:</E>
                     (Agenda is tentative).
                </P>
                <P>
                    <E T="03">May 3, 2007 teleconference meeting:</E>
                     a. Discuss and approve the committee's final comments and recommendations on the DHS Strategy to Enhance International Supply Chain Security.
                </P>
                <P>b. The Chairperson will announce the time allotted for public comments and discussion.</P>
                <P>
                    The teleconference call meeting is open to the public. Please note that the meeting call may end early if all business is finished. Security requires that any member of the public who wishes to attend the public session in person on May 3, 2007 at Coast Guard Headquarters provide his or her name and date of birth no later than 4 p.m. EDT, Monday, April 30, 2007, to Mr. Ike Eisentrout at 
                    <E T="03">NMSAC@uscg.mil,</E>
                     or via phone at (202) 372-1119. Please list the docket number and NMSAC Teleconference in the subject line on all e-mail messages. Photo identification will be required for entry into the building.
                </P>
                <P>
                    <E T="03">Information on Services for Individuals with Disabilities:</E>
                     For information on facilities or services for individuals with disabilities or to request special assistance at the meeting, contact Mr. Ike Eisentrout as soon as possible.
                </P>
                <SIG>
                    <DATED>Dated: April 10, 2007.</DATED>
                    <NAME>T.L. Burke,</NAME>
                    <TITLE>Commander, U.S. Coast Guard Office of Port &amp; Facility Activities.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC> [FR Doc. E7-7072 Filed 4-12-07; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-15-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF HOUSING AND URBAN DEVELOPMENT </AGENCY>
                <DEPDOC>[Docket No. FR-5125-N-15] </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>
                <EFFDATE>
                    <HD SOURCE="HED">EFFECTIVE DATE:</HD>
                    <P>April 13, 2007. </P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Kathy Ezzell, Department of Housing and Urban Development, Room 7262, 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 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.), HUD publishes a Notice, on a weekly basis, identifying unutilized, underutilized, excess and surplus Federal buildings and real property that HUD has reviewed for suitability for use to assist the homeless. Today's Notice is for the purpose of announcing that no additional properties have been determined suitable or unsuitable this week. 
                </P>
                <SIG>
                    <DATED>Dated: April 5, 2007. </DATED>
                    <NAME>Mark R. Johnston, </NAME>
                    <TITLE>Deputy Assistant Secretary for Special Needs.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. E7-6768 Filed 4-12-07; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4210-67-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF THE INTERIOR </AGENCY>
                <SUBAGY>Bureau of Land Management </SUBAGY>
                <DEPDOC>[NV-057-1630-NU] </DEPDOC>
                <SUBJECT>Notice of 30-Day Extension of the Public Comment Period for a Proposed Shooting Closure on Selected Public Lands Managed by the Bureau of Land Management in Nye County, 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 extension. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        On Friday, March 2, 2007, the Bureau of Land Management's Las Vegas Field Office published a 
                        <E T="04">Federal Register</E>
                         Notice (72FR9583) soliciting public comments through April 2, 2007, regarding a proposed shooting closure on approximately 11,000 acres of selected BLM-managed public lands in Nye County, Nevada. This Notice hereby extends that public comment period 30 days. 
                    </P>
                    <P>
                        <E T="03">Date and Time:</E>
                         Written public comments may be mailed or hand delivered to the Bureau of Land Management, Las Vegas Field Office, 4701 North Torrey Pines Drive, Las Vegas, Nevada 89130. Comments also may be submitted electronically at the Federal eRulemaking Portal: 
                        <E T="03">http://www.regulations.gov.</E>
                         All comments must be received by Wednesday, May 2, 2007. 
                    </P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>The Office of the Chief Ranger of Law Enforcement, Bureau of Land Management, Las Vegas Field Office, 4701 North Torrey Pines Drive, Las Vegas, Nevada 89130, telephone number (702) 515-5000. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The BLM plans to establish a shooting closure under the authority of 43 CFR 8364.1, which allows BLM Field Managers to establish closures for the protection of persons, property, and public lands and resources. This provision allows the BLM to issue closures of less than national effect without codifying the rules in the Code of Federal Regulations. </P>
                <P>The closure is intended to ensure the safety of people and property adjacent to selected public lands and to prevent environmental degradation. The closure is the result of a cooperative effort to assure public safety by the Nye County Sheriff's office, the Nye County Commissioners and the BLM in response to concerns by local residents. This closure does not apply to hunting under the laws and regulations of the State of Nevada. </P>
                <P>
                    Public lands affected are within the following described area: Township 21 
                    <PRTPAGE P="18666"/>
                    Range 53 Sections 14, 15, 22, 23, 24, 25, 26, 27, 34, 35, 36; Township 21 Range 54 Sections 21, 22, 27, 28, 29, 30 and 31, 32, 33, 34, Township 22 Range 53 Sections 1, 2 and 12; Township 22 Range 54 Sections 5, 6 and 7, Mount Diablo Meridian, Nevada. Maps Depicting the area affected by this closure order are available for public inspection at the BLM Las Vegas Field Office. 
                </P>
                <P>
                    Maps of the closure are attached and will be posted at 
                    <E T="03">http://www.nv.blm.gov/vegas.</E>
                     Maps will also be available in the Town of Pahrump at the Nye County Sheriff's Office, the Nye County Commission office and the library. Maps are available to the public by contacting the BLM Las Vegas Field Office at 4701 N. Torrey Pines Drive, Las Vegas, NV 89130-2301. 
                </P>
                <SIG>
                    <DATED>Dated: March 22, 2007. </DATED>
                    <NAME>Juan Palma, </NAME>
                    <TITLE>Manager, BLM Las Vegas Field Office.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. E7-7023 Filed 4-12-07; 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>[NV-952-07-1420-BJ] </DEPDOC>
                <SUBJECT>Filing of Plats of Survey; Nevada </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Bureau of Land Management, Department of the Interior. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The purpose of this notice is to inform the public and interested State and local government officials of the filing of Plats of Survey in Nevada. </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        <E T="03">Effective Dates:</E>
                         Filing is effective at 10 a.m. on the date indicated below. 
                    </P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>David D. Morlan, Chief, Branch of Geographic Sciences, Bureau of Land Management (BLM), Nevada State Office, 1340 Financial Blvd.,  P.O. Box 12000, Reno, Nevada 89520, 775-861-6541. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P SOURCE="NPAR">1. The Plat of Survey of the following described lands was officially filed at the Nevada State Office, Reno, Nevada, on January 17, 2007: </P>
                <P>The plat, representing the dependent resurvey of a portion of the east boundary and a portion of the subdivisional lines, and the subdivision of section 27, Township 20 South, Range 56 East, Mount Diablo Meridian, Nevada, under Group No. 818, was accepted January 12, 2007. </P>
                <P>This survey was executed to meet certain administrative needs of the U.S. Forest Service. </P>
                <P>2. The Plat of Survey of the following described lands was officially filed at the Nevada State Office, Reno, Nevada, on March 8, 2007. </P>
                <P>The plat representing the entire survey record of the survey of a portion of the east boundary of Township 15 South, Range 62 East, Mount Diablo Meridian, Nevada, under Group No. 820, was accepted March 6, 2007. </P>
                <P>This survey was executed to meet certain administrative needs of the U.S. Fish and Wildlife Service. </P>
                <P>3. The Plat of Survey of the following described lands was officially filed at the Nevada State Office, Reno, Nevada, on March 15, 2007. </P>
                <P>The plat representing the dependent resurvey of the Fifth Standard Parallel South, through a portion of Range 54 East, and a portion of the subdivisional lines, and the subdivision of section 2, Township 21 South, Range 54 East, Mount Diablo Meridian, Nevada, executed under Group No. 799, was accepted March 14, 2007. </P>
                <P>This survey was executed to meet certain administrative needs of the Bureau of Land Management. </P>
                <P>4. The above-listed surveys are now the basic record for describing the lands for all authorized purposes. These surveys have been placed in the open files in the BLM Nevada State Office and are available to the public as a matter of information. Copies of the surveys may be furnished to the public upon payment of the appropriate fees. </P>
                <SIG>
                    <DATED>Dated: April 5, 2007. </DATED>
                    <NAME>David D. Morlan, </NAME>
                    <TITLE>Chief Cadastral Surveyor, Nevada.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC> [FR Doc. E7-6981 Filed 4-12-07; 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>[NV-930-1430-ET; NVN-83210] </DEPDOC>
                <SUBJECT>Notice of Proposed Withdrawal and Opportunity for Public Meeting; Nevada </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Bureau of Land Management, Interior. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Secretary of Interior proposes to withdraw on behalf of the Bureau of Land Management (BLM) approximately 729.78 acres of public lands for a period of 5 years to protect lands within Gold Point and Ione Townsites for planning purposes, and in aid of special legislation to be introduced before the current Congress. This notice temporarily segregates the lands for up to 2 years from location and entry under the United States mining laws while the 5-year withdrawal application is being processed. </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments and requests for a public meeting must be received by July 12, 2007. </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Comments and meeting requests should be sent to the Assistant Field Manager, BLM, Tonopah Field Station, 1553 South Main Street, P.O. Box 911, Tonopah, Nevada 89049. </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Wendy Seley, BLM, Tonopah Field Station, (775) 482-7800, or at the above address or Jacqueline Gratton, BLM, Nevada State Office, (775) 861-6532, or P.O. Box 12000, Reno, Nevada 89520. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The applicant is the BLM at the address stated above. The petition/application requests the Secretary of the Interior to withdraw, for 5 years, the following described public lands from location and entry under the United States mining laws, subject to valid existing rights:</P>
                <EXTRACT>
                    <HD SOURCE="HD1">Mount Diablo Meridian </HD>
                    <FP SOURCE="FP-2">T. 13 N., R. 39 E., </FP>
                    <FP SOURCE="FP1-2">
                        Sec. 32, E
                        <FR>1/2</FR>
                        SE
                        <FR>1/4</FR>
                        SE
                        <FR>1/4</FR>
                        ; 
                    </FP>
                    <FP SOURCE="FP1-2">
                        Sec. 33, NE
                        <FR>1/4</FR>
                        SE
                        <FR>1/4</FR>
                         and S
                        <FR>1/2</FR>
                        S
                        <FR>1/2</FR>
                        ; 
                    </FP>
                    <FP SOURCE="FP1-2">
                        Sec. 34, lots 9 to 26, inclusive, S
                        <FR>1/2</FR>
                        NW
                        <FR>1/4</FR>
                        .
                    </FP>
                    <P>The areas described aggregate 442.01 acres in Nye County.</P>
                    <FP SOURCE="FP-2">
                        T. 7 S., R. 41
                        <FR>1/2</FR>
                         E., 
                    </FP>
                    <FP SOURCE="FP1-2">
                        Sec. 3, SE
                        <FR>1/4</FR>
                        NW
                        <FR>1/4</FR>
                        , N
                        <FR>1/2</FR>
                        NE
                        <FR>1/4</FR>
                        SW
                        <FR>1/4</FR>
                        , SW
                        <FR>1/4</FR>
                        NE
                        <FR>1/4</FR>
                        SW
                        <FR>1/4</FR>
                        , W
                        <FR>1/2</FR>
                        SW
                        <FR>1/4</FR>
                        , W
                        <FR>1/2</FR>
                        SE
                        <FR>1/4</FR>
                        SW
                        <FR>1/4</FR>
                        , SE
                        <FR>1/4</FR>
                        SE
                        <FR>1/4</FR>
                        SW
                        <FR>1/4</FR>
                        , and SW
                        <FR>1/4</FR>
                        SW
                        <FR>1/4</FR>
                        SE
                        <FR>1/4</FR>
                        ; 
                    </FP>
                    <FP SOURCE="FP1-2">
                        Sec. 4, SE
                        <FR>1/4</FR>
                        SE
                        <FR>1/4</FR>
                        ; 
                    </FP>
                    <FP SOURCE="FP1-2">Sec. 9, lot 1; </FP>
                    <FP SOURCE="FP1-2">
                        Sec. 10, N
                        <FR>1/2</FR>
                        NW
                        <FR>1/4</FR>
                        NW
                        <FR>1/4</FR>
                        NE
                        <FR>1/4</FR>
                        , N
                        <FR>1/2</FR>
                        NE
                        <FR>1/4</FR>
                        NE
                        <FR>1/4</FR>
                        NW
                        <FR>1/4</FR>
                        , NW
                        <FR>1/4</FR>
                        NE
                        <FR>1/4</FR>
                        NW
                        <FR>1/4</FR>
                        , and N
                        <FR>1/2</FR>
                        NW
                        <FR>1/4</FR>
                        NW
                        <FR>1/4</FR>
                        .
                    </FP>
                    <P>The areas described aggregate 287.77 acres in Esmeralda County.</P>
                </EXTRACT>
                <P>The BLM petition/application has been approved by the Assistant Secretary, Land and Minerals Management. Therefore, it constitutes a withdrawal proposal of the Secretary of the Interior (43 CFR 2310.1-3(e)). </P>
                <P>The purpose of the withdrawal is to protect the status quo of the lands in aid of special legislation proposed to be introduced before the current Congress. </P>
                <P>The application will be processed in accordance with the regulations set forth in 43 CFR part 2300. </P>
                <P>The use of a right-of-way, interagency, or a cooperative agreement would not adequately constrain non-discretionary uses which could adversely affect the passage of the proposed legislation. </P>
                <P>No water rights would be needed to fulfill the purpose of this withdrawal. </P>
                <P>
                    Records relating to the application may be examined by interested parties 
                    <PRTPAGE P="18667"/>
                    at the address of the BLM office stated above. 
                </P>
                <P>For a period of 90 days from the date of publication of this notice, all persons who wish to submit comments, suggestions, or objections in connection with the proposed withdrawal may present their views in writing to the BLM Tonopah Field Station, at the address noted above. Facsimiles, telephone calls, and electronic mails are unacceptable means of notification. </P>
                <P>Comments, including names and street addresses of respondents, will be available for public review at the BLM Tonopah Field Station, at the address noted above during regular business hours 8 a.m. to 4:30 p.m., Monday through Friday, except holidays. Before including your address, phone number, e-mail address, or other personal identifying information in your comments be advised that your entire comment—including your personal identifying information—may be made publicly available at any time. While you can ask us in your comment to withhold your personal identifying information from public review, we cannot guarantee that we will be able to do so. </P>
                <P>
                    Notice is hereby given that an opportunity for a public meeting is afforded in connection with the proposed withdrawal. All interested persons who desire a public meeting for the purpose of being heard on the proposed withdrawal must submit a written request to the BLM Assistant Field Manager within 90 days from the date of publication of this notice. If the authorized officer determines that a public meeting will be held, a notice of the time and place will be published in the 
                    <E T="04">Federal Register</E>
                     at least 30 days before the scheduled date of the meeting. 
                </P>
                <EXTRACT>
                    <FP>(Authority: 43 CFR 2310.3-1)</FP>
                </EXTRACT>
                <SIG>
                    <DATED>Dated: April 11, 2007. </DATED>
                    <NAME>Patrick Gubbins, </NAME>
                    <TITLE>Acting Deputy State Director, Natural Resources, Lands &amp; Planning. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC> [FR Doc. E7-7200 Filed 4-12-07; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4310-HC-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF THE INTERIOR </AGENCY>
                <SUBAGY>Minerals Management Service </SUBAGY>
                <SUBJECT>Outer Continental Shelf (OCS), Western and Central Gulf of Mexico (GOM), Oil and Gas Lease Sales for Years 2007-2012 </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Minerals Management Service (MMS), Interior. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of availability (NOA) of the final environmental impact statement. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The MMS has prepared a final environmental impact statement (EIS) on tentatively scheduled 2007-2012 oil and gas leasing proposals in the Western and Central GOM, off the States of Texas, Louisiana, Mississippi, and Alabama. </P>
                </SUM>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P>
                        The NOA is published pursuant to the regulations (40 CFR 1501.7) implementing the provisions of the National Environmental Policy Act (NEPA) of 1969 as amended (42 U.S.C. 4321 
                        <E T="03">et seq.</E>
                         (1988)). 
                    </P>
                </AUTH>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>Federal regulations allow for several proposals to be analyzed in one EIS (40 CFR 1502.4). Since each sale proposal and projected activities are very similar each year for each sale area, the MMS has prepared a single EIS (multisale EIS) for the five Western and six Central GOM lease sales scheduled for 2007-2012 in the proposed OCS Oil and Gas Leasing Program: 2007-2012. Although this EIS addresses 11 proposed lease sales, at the completion of this EIS process, decisions will be made only for proposed Lease Sale 204 in the Western Planning Area (WPA) and proposed Lease Sale 205 in the Central Planning Area (CPA). Subsequent to these first sales, a NEPA review will be conducted for each of the other proposed lease sales in the 2007-2012 Leasing Program. Formal consultation with other Federal Agencies, the affected states, and the public will be carried out to assist in the determination of whether or not the information and analyses in the original multisale EIS are still valid. These consultations and NEPA reviews will be completed before decisions are made on the subsequent sales. </P>
                <P>
                    <E T="03">EIS Availability:</E>
                     To obtain a single printed or CD-ROM copy of the Final EIS, you may contact the Minerals Management Service, Gulf of Mexico OCS Region, Public Information Office (MS 5034), 1201 Elmwood Park Boulevard, Room 114, New Orleans, Louisiana 70123-2394 (1-800-200-GULF). An electronic copy of the Final EIS is available at the MMS's Internet Web site at 
                    <E T="03">http://www.gomr.mms.gov/homepg/regulate/environ/nepa/nepaprocess.html.</E>
                     Several libraries along the Gulf Coast have been sent copies of the Final EIS. To find out which libraries, and their locations, have copies of the Final EIS for review, you may contact the MMS's Public Information Office or visit the MMS Internet Web site at 
                    <E T="03">http://www.gomr.mms.gov/homepg/regulate/environ/libraries.html</E>
                    . 
                </P>
                <P>
                    <E T="03">Comments:</E>
                     Federal, State, and local government agencies and other interested parties are requested to send their written comments on the Final EIS in one of the following two ways: 
                </P>
                <P>1. In written form enclosed in an envelope labeled “Comments on the Multisale EIS” and mailed (or hand carried) to the Regional Supervisor, Leasing and Environment (MS 5410), Minerals Management Service, Gulf of Mexico OCS Region, 1201 Elmwood Park Boulevard, New Orleans, Louisiana 70123-2394. </P>
                <P>
                    2. Electronically to the MMS e-mail address: 
                    <E T="03">environment@mms.gov</E>
                    . 
                </P>
                <P>Comments should be submitted no later than May 14, 2007. </P>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Minerals Management Service, Mr. Dennis Chew, Gulf of Mexico OCS Region, 1201 Elmwood Park Boulevard, New Orleans, Louisiana 70123-2394, (504) 736-2793. </P>
                    <SIG>
                        <DATED>Dated: March 13, 2007. </DATED>
                        <NAME>Chris C. Oynes, </NAME>
                        <TITLE>Associate Director for Offshore Minerals Management.</TITLE>
                    </SIG>
                </FURINF>
            </SUPLINF>
            <FRDOC>[FR Doc. E7-7031 Filed 4-12-07; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4310-MR-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">INTERNATIONAL TRADE COMMISSION </AGENCY>
                <DEPDOC>[USITC SE-07-006] </DEPDOC>
                <SUBJECT>Government in the Sunshine Act Meeting Notice </SUBJECT>
                <PREAMHD>
                    <HD SOURCE="HED">Agency Holding the Meeting:</HD>
                    <P>United States International Trade Commission. </P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">Time and Date:</HD>
                    <P>April 19, 2007 at 11 a.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-921 (Review) (Folding Gift Boxes from China)—briefing and vote. (The Commission is currently scheduled to transmit its determination and Commissioners' opinions to the Secretary of Commerce on or before April 30, 2007.) </P>
                    <P>
                        5. Inv. Nos. 731-TA-707-709 (Second Review) (Certain Seamless Carbon and Alloy Steel Standard, Line, and Pressure Pipe from Argentina, Brazil, and Germany)—briefing and vote. (The Commission is currently scheduled to transmit its determination and Commissioners' opinions to the Secretary of Commerce on or before May 2, 2007). 
                        <PRTPAGE P="18668"/>
                    </P>
                    <P>6. 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>
                    <P>By order of the Commission.</P>
                    <DATED>Issued: April 10, 2007. </DATED>
                    <NAME>Marilyn R. Abbott, </NAME>
                    <TITLE>Secretary to the Commission. </TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 07-1868 Filed 4-11-07; 12:55 pm] </FRDOC>
            <BILCOD>BILLING CODE 7020-02-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF JUSTICE </AGENCY>
                <DEPDOC>[OMB Number 1103-0016] </DEPDOC>
                <SUBJECT>Justice Management Division; Agency Information Collection Activities: Proposed Collection; Comments Requested</SUBJECT>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>60-day notice of information collection under review: certification of identity.</P>
                </ACT>
                <P>The Department of Justice (DOJ), Justice Management Division, has submitted the following information collection request to the Office of Management and Budget (OMB) for review and approval in accordance with the Paperwork Reduction Act of 1995. The proposed information collection is published to obtain comments from the public and affected agencies. Comments are encouraged and will be accepted for “sixty days” until June 12, 2007. This process is conducted in accordance with 5 CFR 1320.10.</P>
                <P>If you have comments especially on the estimated public burden or associated response time, suggestions, or need a copy of the proposed information collection instrument with instructions or additional information, please contact Stephen K. Myers, 1331 Pennsylvania Avenue, NW., Washington, DC 20530. </P>
                <P>Written comments and suggestions from the public and affected agencies concerning the proposed collection of information are encouraged. Your comments should address one or more of the following four points:</P>
                <FP SOURCE="FP-1">—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;</FP>
                <FP SOURCE="FP-1">—Evaluate the accuracy of the agencies estimate of the burden of the proposed collection of information, including the validity of the methodology and assumptions used;</FP>
                <FP SOURCE="FP-1">—Enhance the quality, utility, and clarity of the information to be collected; and </FP>
                <FP SOURCE="FP-1">—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.g., permitting electronic submission of responses.</FP>
                <P>Overview of this information collection:</P>
                <P>
                    (1) 
                    <E T="03">Type of Information Collection:</E>
                     Extension of a currently approved collection.
                </P>
                <P>
                    (2) 
                    <E T="03">Title of the Form/Collection:</E>
                     Certification of Identity.
                </P>
                <P>
                    (3) 
                    <E T="03">Agency form number, if any, and the applicable component of the Department of Justice sponsoring the collection:</E>
                     Form DOJ-361. Facilities and Administrative Services Staff, Justice Management Division, U.S. Department of Justice.
                </P>
                <P>
                    (4) 
                    <E T="03">Affected public who will be asked or required to respond, as well as brief abstract: Primary:</E>
                     American Citizens. 
                    <E T="03">Other:</E>
                     Federal Government. The information collection will be used by the Department to identify individuals requesting certain records under the Privacy Act. Without this form an individual cannot obtain the information requested.
                </P>
                <P>
                    (5) 
                    <E T="03">An estimate of the total number of respondents and the amount of time estimated for an average respondent to respond:</E>
                     It is estimated that 27,000 respondents will complete each form within approximately 30 minutes
                </P>
                <P>
                    (6) 
                    <E T="03">An estimate of the total public burden (in hours) associated with the collection:</E>
                     There are an estimated total of 13,500 annual burden hours associated with this collection.
                </P>
                <P>If additional information is required contact: Lynn Bryant, Department Clearance Officer, United States Department of Justice, Justice Management Division, Policy and Planning Staff, Patrick Henry Building, Suite 1600, 601 D Street, NW., Washingon, DC 20530.</P>
                <SIG>
                    <DATED>Dated: April 10, 2007.</DATED>
                    <NAME>Lynn Bryant,</NAME>
                    <TITLE>Department Clearance Officer, PRA, Department of Justice.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 07-1857 Filed 4-12-07; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4410-FY-M</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF JUSTICE </AGENCY>
                <SUBAGY>Drug Enforcement Administration </SUBAGY>
                <DEPDOC>[OMB Number 1117-0013] </DEPDOC>
                <SUBJECT>Agency Information Collection Activities: Proposed Collection; Comments Requested </SUBJECT>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>60-Day Notice of Information Collection Under Review; Application for Permit to Import Controlled Substances for Domestic and/or Scientific Purposes pursuant to 21 U.S.C. 952 DEA Form 357. </P>
                </ACT>
                <P>The Department of Justice (DOJ), Drug Enforcement Administration (DEA), has submitted the following information collection request to the Office of Management and Budget (OMB) for review and approval in accordance with the Paperwork Reduction Act of 1995. The proposed information collection is published to obtain comments from the public and affected agencies. Comments are encouraged and will be accepted until June 12, 2007. This process is conducted in accordance with 5 CFR 1320.10. </P>
                <P>If you have comments, especially on the estimated public burden or associated response time, suggestions, or need a copy of the proposed information collection instrument with instructions or additional information, please contact Mark W. Caverly, Chief, Liaison and Policy Section, Office of Diversion Control, Drug Enforcement Administration, Washington, DC 20537. </P>
                <P>Written comments and suggestions from the public and affected agencies concerning the proposed collection of information are encouraged. Your comments should address one or more of the following four points: </P>
                <FP SOURCE="FP-1">—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; </FP>
                <FP SOURCE="FP-1">—Evaluate the accuracy of the agencies estimate of the burden of the proposed collection of information, including the validity of the methodology and assumptions used; </FP>
                <FP SOURCE="FP-1">—Enhance the quality, utility, and clarity of the information to be collected; and </FP>
                <FP SOURCE="FP-1">—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.g., permitting electronic submission of responses. </FP>
                <PRTPAGE P="18669"/>
                <P>Overview of this Information Collection:</P>
                <P>
                    (1) 
                    <E T="03">Type of Information Collection:</E>
                     Renewal of an existing collection. 
                </P>
                <P>
                    (2) 
                    <E T="03">Title of the Form/Collection:</E>
                     Application for Permit to Import Controlled Substances for Domestic and/or Scientific Purposes pursuant to 21 U.S.C. 952 (DEA Form 357). 
                </P>
                <P>
                    (3) 
                    <E T="03">Agency form number, if any, and the applicable component of the Department sponsoring the collection:</E>
                </P>
                <P>
                    <E T="03">Form number:</E>
                     DEA Form 357. 
                </P>
                <P>
                    <E T="03">Component:</E>
                     Office of Diversion Control, Drug Enforcement Administration, U.S. Department of Justice. 
                </P>
                <P>
                    (4) 
                    <E T="03">Affected public who will be asked or required to respond, as well as a brief abstract:</E>
                </P>
                <P>
                    <E T="03">Primary:</E>
                     Business or other for-profit. 
                </P>
                <P>
                    <E T="03">Other:</E>
                     None. 
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     Title 21, CFR, Section 1312.11 requires any registrant who desires to import certain controlled substances into the United States to have an import permit. In order to obtain the permit, an application must be made to the Drug Enforcement Administration on DEA Form 357. 
                </P>
                <P>
                    (5) 
                    <E T="03">An estimate of the total number of respondents and the amount of time estimated for an average respondent to respond:</E>
                     47 respondents, 406 responses, .25 hour per response. A respondent may submit multiple responses. A respondent will take an estimate of 15 minutes to complete each form. 
                </P>
                <P>
                    (6) 
                    <E T="03">An estimate of the total public burden (in hours) associated with the collection:</E>
                     101.50 annual burden hours. 
                </P>
                <P>
                    <E T="03">If additional information is required contact:</E>
                     Lynn Bryant, Department Clearance Officer, United States Department of Justice, Justice Management Division, Policy and Planning Staff, Patrick Henry Building, Suite 1600, 601 D Street, NW., Washington, DC 20530. 
                </P>
                <SIG>
                    <DATED>Dated: April 10, 2007. </DATED>
                    <NAME>Lynn Bryant, </NAME>
                    <TITLE>Department Clearance Officer, PRA, Department of Justice.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC> [FR Doc. E7-7080 Filed 4-12-07; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4410-09-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF JUSTICE </AGENCY>
                <SUBAGY>Office of Justice Programs; National Institute of Justice </SUBAGY>
                <DEPDOC>[OMB Number 1121-0310] </DEPDOC>
                <SUBJECT>Agency Information Collection Activities; Proposed Collection; Comment Requested </SUBJECT>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>30-day notice of information collection under review: Evaluation of Impacts of Federal Casework Programs. </P>
                </ACT>
                <P>
                    The Department of Justice, Office of Justice Programs, National Institute of Justice (NIJ) has submitted the following information collection request to the Office of Management and Budget (OMB) for review and approval in accordance with the Paperwork Reduction Act of 1995. The proposed information collection is published to obtain comments from the public and affected agencies. This proposed information collection was previously published in the 
                    <E T="04">Federal Register</E>
                     Volume 72, Number 27, pages 6289-6290, on February 9, 2007, allowing for a 60-day comment period. 
                </P>
                <P>The purpose of this notice is to allow for an additional 30 days for public comment until May 14, 2007. This process is conducted in accordance with 5 CFR 1320.10. </P>
                <P>Written comments and/or suggestions regarding the items contained in this notice, especially the estimated public burden and associated response time, should be directed to the Office of Management and Budget, Office of Information and Regulatory Affairs, Attention Department of Justice Desk Officer, Washington, DC 20503. Additionally, comments may be submitted to OMB via facsimile to (202) 395-5806. Written comments and suggestions from the public and affected agencies concerning the proposed collection of information are encouraged. Your comments should address one or more of the following four points: </P>
                <FP SOURCE="FP-1">—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; </FP>
                <FP SOURCE="FP-1">—Evaluate the accuracy of the agencies' estimate of the burden of the proposed collection of information, including the validity of the methodology and assumptions used; </FP>
                <FP SOURCE="FP-1">—Enhance the quality, utility, and clarity of the information to be collected; and </FP>
                <FP SOURCE="FP-1">
                    —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. 
                </FP>
                <P>Overview of this information collection:</P>
                <P>
                    (1) 
                    <E T="03">Type of Information Collection:</E>
                     New collection. 
                </P>
                <P>
                    (2) 
                    <E T="03">Title of the Form/Collection:</E>
                     Evaluation of Impact of Federal Casework Programs—
                </P>
                <P>Prosecutor Survey; </P>
                <P>Law Enforcement Survey; </P>
                <P>*Lab Personnel Survey. </P>
                <P>*There are three versions of the lab survey, each tailored to the respective type of lab. </P>
                <P>(3) Not Applicable. </P>
                <P>(4) Affected public who will be asked or required to respond are: Prosecutors, Law Enforcement Officials, and Forensic Laboratory personnel from agencies within the jurisdiction represented by the grantees. The National Institute of Justice uses this information to assess the impacts and cost-effectiveness of the Forensic Casework DNA Backlog Programs over time and to diagnose performance problems in current casework programs. This evaluation will help decision makers be better informed to not only diagnose program performance problems, but also to better understand whether the benefits of DNA collection and testing are in fact an effective public safety and crime control practice. </P>
                <P>(5) An estimate of the total number of respondents and the amount of time needed for an average respondent to respond is broken down as follows: </P>
                <P>
                    Law Enforcement—200 respondents, average burden time 120 minutes—
                    <E T="03">400 hours total</E>
                    . 
                </P>
                <P>
                    Prosecutors—200 respondents, average burden time 90 minutes—
                    <E T="03">300 hours total</E>
                    . 
                </P>
                <P>
                    Lab personnel—135 respondents average burden 120 minutes—
                    <E T="03">270 hours total</E>
                    . 
                </P>
                <P>(6) An estimate of the total public burden (in hours) associated with the collection: </P>
                <P>The estimated total public burden associated with this collection is 970 hours. </P>
                <P>If additional information is required, contact: Lynn Bryant, Department Clearance Officer, United States Department of Justice, Policy and Planning Staff, Justice Management Division, Patrick Henry Building, Suite 1600, 601 D Street, NW., Washington, DC 20530. </P>
                <SIG>
                    <PRTPAGE P="18670"/>
                    <DATED>Dated: April 9, 2007. </DATED>
                    <NAME>Lynn Bryant, </NAME>
                    <TITLE>Department Clearance Officer, PRA Department of Justice.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. E7-7058 Filed 4-12-07; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4410-18-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF JUSTICE </AGENCY>
                <SUBAGY>Office of Justice Programs </SUBAGY>
                <DEPDOC>[OMB Number 1121-0166] </DEPDOC>
                <SUBJECT>Agency Information Collection Activities: Extension of a Currently Approved Collection: Comments Requested </SUBJECT>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>30-Day Notice of Information Collection Under Review: Extension of a currently approved collection. Bureau of Justice Assistance Application Form: Public Safety Officers Disability Benefits.</P>
                </ACT>
                <P>
                    The Department of Justice (DOJ), Office of Justice Programs (OJP) has submitted the following information collection request to the Office of Management and Budget (OMB) for review and approval in accordance with the Paperwork Reduction Act of 1995. The proposed collection information is published to obtain comments from the public and affected agencies. This proposed information collection was previously published in the 
                    <E T="04">Federal Register</E>
                     Volume 72, Number 32, pages 7677-7678 on February 16, 2007, allowing for a 60 day comment period. The purpose of this notice is to allow for an additional 30 days for public comment until May 14, 2007. This process is conducted in accordance with 5 CFR 1320.10. 
                </P>
                <P>Written comments and/or suggestions regarding the items contained in this notice, especially the estimated public burden and associated response time, should be directed to the Office of Management and Budget, Office of Information and Regulatory Affairs, Attention Department of Justice Desk Officer, Washington, DC 20503. Additionally, comments may be submitted to OMB via facsimile to (202) 395-5806. Comments may also be submitted to M. Pressley, Bureau of Justice Assistance, Office of Justice Programs, U.S. Department of Justice, 810 7th Street, NW., Washington, DC 20531 via facsimile to (202) 305-1367. </P>
                <P>Written comments and suggestions from the public and affected agencies concerning the proposed collection of information are encouraged. Your comments should address one or more of the following four points:</P>
                <FP SOURCE="FP-1">—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; </FP>
                <FP SOURCE="FP-1">—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; </FP>
                <FP SOURCE="FP-1">—Enhance the quality, utility, and clarity of the information to be collected; and </FP>
                <FP SOURCE="FP-1">
                    —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. 
                </FP>
                <P>Overview of this information collection: </P>
                <P>
                    (1) 
                    <E T="03">Type of Information Collection:</E>
                     Extension of a currently approved collection. 
                </P>
                <P>
                    (2) 
                    <E T="03">Title of the Form/Collection:</E>
                     Public Safety Officers Disability Benefits. 
                </P>
                <P>
                    (3) 
                    <E T="03">Agency form number, if any, and the applicable component of the Department of Justice sponsoring the collection:</E>
                     OJP FORM 3650/7 Public Safety Officers Disability Benefits. 
                </P>
                <P>
                    (4) 
                    <E T="03">Affected public who will be asked or required to respond, as well as a brief abstract:</E>
                </P>
                <P>
                    <E T="03">Primary:</E>
                     Dependents of public safety officers who were killed or permanently and totally disabled in the line of duty. 
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     The Public Safety Officers' Benefits Act of 1976 (PSOB), 42 U.S.C. 3796, authorizes the Bureau of Justice Assistance, Office of Justice Programs to pay a benefit to claimant public safety officers found to have been permanently and totally disabled as the direct result of a catastrophic line of duty injury sustained on or after November 29, 1990. 
                </P>
                <P>
                    <E T="03">Others:</E>
                     None. 
                </P>
                <P>
                    (5) 
                    <E T="03">An estimate of the total number of respondents and the amount of time needed for an average respondent to respond is as follows:</E>
                     It is estimated that no more than 75 respondents will apply a year. Each application takes approximately 120 minutes to complete. 
                </P>
                <P>
                    (6) 
                    <E T="03">An estimate of the total public burden (in hours) associated with the collection: Total Annual Reporting Burden:</E>
                     75 × 120 minutes per application = 9,000 minutes/by 60 minutes per hour = 150 hours. 
                </P>
                <P>If additional information is required, please contact, Lynn Bryant, Clearance Officer, United States Department of Justice, Justice Management Division, Policy and Planning Staff, Patrick Henry Building, Suite 1600, 601 D Street, NW., Washington, DC 20530. </P>
                <SIG>
                    <DATED>Dated: April 10, 2007. </DATED>
                    <NAME>Lynn Bryant, </NAME>
                    <TITLE>Department Clearance Officer, PRA,  United States Department of Justice.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC> [FR Doc. E7-7083 Filed 4-12-07; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4410-18-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF LABOR</AGENCY>
                <SUBAGY>Veterans' Employment and Training Service</SUBAGY>
                <SUBJECT>Homeless Veterans' Reintegration Program (HVRP) National Technical Assistance Center Cooperative Agreement(s) for Program Year (PY) 2007 Solicitation for Cooperative Agreement(s) Solicitation #07-08 Period of Performance is PY 2007, July 1, 2007 Through June 30, 2008</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Veterans' Employment and Training Service, Department of Labor.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of funding availability.</P>
                </ACT>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Applications are due on May 14, 2007.</P>
                </DATES>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>(Applicants For a Cooperative Agreement Should Read This Notice In Its Entirety): The U.S. Department of Labor (USDOL), Veterans' Employment and Training Service (VETS), announces a cooperative agreement competition under 38 U.S.C. Section 2021, as added by Section 5 of Public Law 107-95, the Homeless Veterans Comprehensive Assistance Act of 2001 (HVCAA). Section 2021 authorizes programs to expedite the reintegration of homeless veterans into the labor force.</P>
                    <P>
                        In order to assist the USDOL-VETS in carrying out 38 U.S.C. 2021, it is announcing the availability of funds for a cooperative agreement to assist in developing a National Technical Assistance Center (NTAC) for the Homeless Veterans' Reintegration Program (HVRP). The primary objective of the HVRP NTAC will be to provide general technical assistance on veterans' homelessness programs and issues to existing HVRP grantees (approximately 80 grantees nationwide), potential HVRP applicants, employers, Veterans Service Organizations, Federal, State, and local agency partners, non-profit organizations (including faith-based and community organizations), the general public, and other interested stakeholders. Successful applicant(s) will assist USDOL-VETS by providing general technical assistance and guidance to eligible HVRP entities relating to assistance for homeless 
                        <PRTPAGE P="18671"/>
                        veterans under the HVRP and related programs that assist homeless veterans.
                    </P>
                    <P>Applicants will also be responsible for developing, conducting, and documenting extensive outreach efforts to national, state, and local employers to increase their awareness of HVRP and its objectives in order to increase job opportunities for homeless veterans. Applicants will also be responsible for assisting USDOL-VETS by contacting current HVRP grantees in order to extract, document, and share at least 20 best HVRP practices with other HVRP grantees and potential applicants. Finally, applicants will assist USDOL-VETS by conducting general research and studies as determined by USDOL-VETS.</P>
                    <P>Entities that are interested in assisting USDOL-VETS in providing technical assistance are to be aware that historically the HVRP annually receives thousands of nationwide inquiries via telephone, written correspondence, and e-mail concerning homeless veterans and HVRP in general. The awardee(s) will be responsible for answering 100 percent of these technical assistance inquiries.</P>
                    <P>Applicants are to be aware of and assist USDOL-VETS and their grantees in implementing the HVRP objectives: (1) To provide services to assist in reintegrating homeless veterans into meaningful employment within the labor force, and (2) to stimulate the development of effective service delivery systems that will address the complex problems facing homeless veterans.</P>
                    <P>Under this solicitation for cooperative agreement(s) covering Program Year (PY) 2007, VETS anticipates that up to $500,000 will be available for a cooperative agreement award(s) up to a maximum total award of $500,000. Depending on the quality and content of the applications received, USDOL-VETS expects to award one (1) to (2) cooperative agreements. This notice contains all of the necessary information and forms to apply for funding. The period of performance for this PY 2007 cooperative agreement(s) will be July 1, 2007 through June 30, 2008. Two (2) optional years of additional funding may be available, depending upon Congressional appropriations, the agency's decision to exercise the optional year(s) of funding, and awardee(s) satisfactory technical and financial performance.</P>
                    <HD SOURCE="HD1">I. Funding Opportunity Description </HD>
                    <P>The U.S. Department of Labor (USDOL), Veterans' Employment and Training Service (VETS), announces a cooperative agreement competition under 38 U.S.C. Section 2021, as added by Section 5 of Public Law 107-95, the Homeless Veterans Comprehensive Assistance Act of 2001 (HVCAA). Section 2021 authorizes programs to expedite the reintegration of homeless veterans into the labor force. In order to assist the USDOL-VETS in carrying out 38 U.S.C. 2021, it is announcing the availability of funds for a cooperative agreement to assist in developing a National Technical Assistance Center (NTAC) for the Homeless Veterans' Reintegration Program (HVRP). The HVRP NTAC primary objective will to provide general technical assistance and guidance to existing HVRP grantees (approximately 80 grantees nationwide), potential HVRP applicants, employers, Veterans Service Organizations, Federal, State, and local agency partners, non-profit organizations (including faith-based and community organizations), the general public, and other interested stakeholders seeking information on veterans' homelessness programs, issues, concerns, and referrals for additional information and assistance. </P>
                    <P>This USDOL-VETS cooperative agreement(s) anticipates substantial involvement between USDOL-VETS and the awardee(s) during the performance of this project. Involvement will include collaboration and participation by USDOL-VETS in the overall direction of the project throughout the period of the award(s). The USDOL-VETS will provide expertise and guidance in decisions involving strategic planning (including development of a proactive plan to deliver technical assistance to existing HVRP grantees), allocation of resources, key personnel decisions, development and revision of public information materials, and analysis and implementation of evaluation findings. </P>
                    <HD SOURCE="HD2">1. Program Concept and Emphasis </HD>
                    <P>In order to increase the quality and quantity of HVRP applications received, U.S. DOL-VETS will provide successful applicant(s) with general guidelines on how to gather and electronically disseminate technical assistance and guidance to eligible HVRP entities. In order to assist and increase capacity building of existing HVRP grantees, successful applicant(s) will be responsible for instructing and assisting current HVRP grantees on identifying additional funding resources for similar and/or complimentary homeless veterans programs. </P>
                    <P>Guidance will be provided to successful awardee(s) as they assist USDOL-VETS by developing, conducting, and documenting extensive outreach efforts to national, state, and local employers to increase their awareness of HVRP and its objectives in order to potentially increase job opportunities for homeless veterans. </P>
                    <P>Guidance will be provided to successful awardee(s) as they assist USDOL-VETS by interviewing current HVRP grantees (via face-to-face, telephone, written correspondence, or e-mail communications) in order to extract, document, publish, and share their best practices with other HVRP grantees and potential HVRP grantees. </P>
                    <P>Entities that are interested in assisting USDOL-VETS in providing technical assistance are to be aware that historically the HVRP receives several thousand nationwide inquiries yearly via telephone, written correspondence, and e-mail concerning homeless veterans and HVRP in general. The awardee(s) will be responsible for answering 100 percent of these technical assistance inquiries. </P>
                    <P>
                        In order to provide timely information and updates, it is recommended that successful applicant(s) have an Internet-based Web site (or develop a website within 30 calendar days of receiving an award) with clearly stated information relative to homelessness, veterans, and homeless veterans' issues, concerns. Successful applicant(s) will plan to gather and electronically disseminate technical assistance information through this Web site and identify additional resources for assistance that can be readily assessed by current HVRP grantees, potential applicants, Veterans Service Organizations, non-profit organizations (including faith-based and community organizations), Federal, State, and local agency partners, the general public, and other interested stakeholders. USDOL-VETS will provide suggestions and guidance to the awardee(s) the structure and content of the website and will seek authorization to link to the successful awardee(s) webpage directly from the USDOL-VETS Web page at 
                        <E T="03">http://www.dol.gov/vets</E>
                         as a resource for HVRP technical assistance purposes. 
                    </P>
                    <P>Applicants are to assist USDOL-VETS in implementing the HVRP objectives: (1) To provide services to assist in reintegrating homeless veterans into meaningful employment within the labor force, and (2) to stimulate the development of effective service delivery systems addressing the complex problems facing homeless veterans. </P>
                    <HD SOURCE="HD2">2. Scope and Program Design </HD>
                    <P>
                        Successful applicants will assist U.S. DOL-VETS in improving the awareness of HVRP and increasing the quality of the general technical assistance 
                        <PRTPAGE P="18672"/>
                        provided to existing HVRP grantees. Successful applicants will assist U.S. DOL-VETS in providing outreach to national, state, and local employers for the purpose of increasing employer awareness of the HVRP and its objectives in order to increase job opportunities for homeless veterans. Successful applicants will assist USDOL-VETS by interviewing existing HVRP grantees in an effort to extract at least twenty (20) HVRP best practices and summarize their efforts in Word or WordPerfect format to be accessible at both the applicants and the U.S. DOL-VETS Web sites. 
                    </P>
                    <P>Successful applicant(s) must plan to support the travel and associated costs of sending at least one (1) representative to periodic meetings with USDOL-VETS staff in Washington, DC (at least twice per year). Successful applicant(s) will assist U.S. DOL-VETS by planning to attend and provide general HVRP information at conference(s) sponsored by the USDOL-VETS and other USDOL agency partners such as the Employment and Training Administration, the Office of Disability Employment Policy, Office of Faith-Based and Community Initiatives, and other federal agency partners such as the Department of Veterans' Affairs, Department of Housing and Urban Development, and Department of Health and Human Services, and various other social service provider organizations that target similar grantees that provide services to homeless persons, veterans, and homeless veterans. </P>
                    <HD SOURCE="HD1">II. Award Information </HD>
                    <HD SOURCE="HD2">1. Type of Funding Instrument </HD>
                    <P>Successful applicant(s) will be granted a one (1) year cooperative agreement award with optional funding for an additional two (2) years depending on successful performance and the availability of funds. </P>
                </SUM>
                <NOTE>
                    <HD SOURCE="HED">Note:</HD>
                    <P>Selection of an organization as an awardee(s) does not constitute final approval of the application and budget as submitted. Before or shortly after the actual cooperative agreement is awarded, USDOL may enter into negotiations about such items as program components, staffing, and funding levels, and administrative systems in place to support the cooperative agreement implementation. If the negotiations do not result in a mutually acceptable submission, the Grant Officer reserves the right to terminate the negotiation and decline to fund the application or terminate the award.</P>
                </NOTE>
                <P>
                    2. 
                    <E T="03">Funding Levels:</E>
                     The total funding available for this Cooperative Agreement(s) to assist USDOL-VETS in developing a National Technical Assistance Center for HVRP purposes is up to $500,000. Depending on the quality and content of the applications received, it is anticipated that one (1) or two (2) awards will be made under this solicitation. Awards are expected to range from $75,000 to a maximum of $500,000. The Department of Labor reserves the right to negotiate the amounts to be awarded under this competition. Please be advised that proposals will be evaluated in part on cost/value and that requests exceeding $500,000 will be considered non-responsive and will not be evaluated. If there are any residual programmatic funds, the Department of Labor reserves the right to select for funding the next highest scoring applicant(s) on the competitive list developed for this solicitation up to one (1) year after the initial performance period begins or June 30, 2008. 
                </P>
                <P>
                    3. 
                    <E T="03">Period of Performance:</E>
                     The period of performance will be for the twelve (12) month period of July 1, 2007 to June 30, 2008, unless modified in writing by the Grant Officer. It is expected that successful applicant(s) will begin program operations under this solicitation on July 1, 2007. All program funds must be obligated by June 30, 2008; a limited amount of funds may be obligated and reserved for any follow-up activities and closeout. 
                </P>
                <P>
                    4. 
                    <E T="03">Optional Year Funding:</E>
                     Should Congress appropriate additional funds for HVRP purposes, VETS may consider up to two (2) additional years of optional funding. The Government does 
                    <E T="03">not</E>
                    , however, guarantee optional year funding for any awardee(s). In deciding whether to exercise any optional year(s) of funding, VETS will consider awardee(s) performance during the previous period of operations as follows: 
                </P>
                <P>A. The awardee(s) will be responsible for providing timely responses (within 5 working days) to at least 85% of all the technical assistance inquiries received and within 10 working days for the remaining 15% of inquiries received. </P>
                <P>B. The awardee(s) must have complied with all terms identified in the Solicitation for Cooperative Agreement(s), award document, and General and Special Provisions; and </P>
                <P>C. All program and fiscal reports must have been submitted to the Grant Officer Technical Representative by the established due dates and the awardee(s) must verify these reports for accuracy purposes. </P>
                <HD SOURCE="HD1">III. Eligibility Information </HD>
                <P>
                    1. 
                    <E T="03">Eligible Applicants:</E>
                     Applications for funds will be accepted from non-profit organizations, including faith-based and community organizations. 
                </P>
                <P>• If claiming 501(c)(3) status, the Internal Revenue Service statement indicating 501(c)(3) status approval must be submitted. </P>
                <P>• However, entities organized under Section 501(c)(4) of the Internal Revenue Code are not eligible to receive funds under this announcement. Section 18 of the Lobbying Disclosure Act of 1995, Public Law 104-65, 109 Stat. 691 (2 U.S.C. 1611) prohibits instituting an award, grant, or loan of federal funds to 501(c)(4) entities that engage in lobbying. </P>
                <P>
                    2. 
                    <E T="03">Cost Sharing:</E>
                     Cost sharing and matching funds are not required. 
                </P>
                <HD SOURCE="HD2">3. Other Eligibility Criteria </HD>
                <P>Legal rules pertaining to inherently religious activities by organization that receive Federal Financial Assistance. Neutral, non-religious criteria that neither favor nor disfavor religion will be employed in the selection of award recipient(s) and must be employed by awardee(s). The government is generally prohibited from providing direct financial assistance for inherently religious activities. These award funds may not be used for religious instruction, worship, prayer, proselytizing or their inherently religious activities. In this context, the term direct financial assistance means financial assistance that is provided directly by a government entity or an intermediate organization, as opposed to financial assistance that an organization receives as the result of the genuine and independent private choice of a beneficiary. In other contexts, the term “direct” financial assistance may be used to refer to financial assistance that an organization receives directly from the Federal government (also known as “discretionary” assistance), as opposed to assistance that it receives from a State or local government (also known as “indirect” or “block” grant assistance). The term “direct” has the former meaning throughout this paragraph. </P>
                <HD SOURCE="HD1">IV. Application and Submission Information </HD>
                <P>
                    1. 
                    <E T="03">Address to Request an Application and Amendments:</E>
                     This Solicitation for Cooperative Agreement(s), together with its attachments, includes all the information needed to apply. Additional application packages and amendments to this solicitation may be obtained from the VETS Web site address at 
                    <E T="03">http://www.dol.gov/vets</E>
                    , the Federal Grant Opportunities Web site address at 
                    <E T="03">http://www.grants.gov</E>
                    , and from the 
                    <E T="04">Federal Register</E>
                     Web site address at 
                    <E T="03">http://www.gpoaccess.gov/fr/index.html</E>
                    . The 
                    <E T="04">Federal Register</E>
                     may also be obtained from your nearest 
                    <PRTPAGE P="18673"/>
                    government office or library. Additional copies of the standard forms can be downloaded from: 
                    <E T="03">http://www.whitehouse.gov/omb/grants/grants_forms.html</E>
                    . 
                </P>
                <P>
                    <E T="03">All applications must be addressed to:</E>
                     Department of Labor, Procurement Services Center, Attention: Cassandra Mitchell, Reference Solicitation #07-08, 200 Constitution Avenue, NW., Room S-4307, Washington, DC 20210, Phone Number: (202) 693-4570 (this is not a toll-free number). 
                </P>
                <P>
                    • Applicants are encouraged to apply online at 
                    <E T="03">www.grants.gov.</E>
                     Applicants submitting proposals online are requested to refrain from mailing a hard copy application as well. It is strongly recommended that applicants using 
                    <E T="03">www.grants.gov</E>
                     immediately initiate and complete the “Get Started” registration steps at 
                    <E T="03">http://www.grants.gov/GetStarted.</E>
                     These steps may take multiple days to complete, and this time should be factored into plans for electronic submission in order to avoid facing unexpected delays that could result in the rejection of an application. If submitting electronically through 
                    <E T="03">www.grants.gov</E>
                     it would be appreciated if the application submitted is saved as .doc, .pdf, or .txt files. 
                </P>
                <P>• Except as provided in Section IV.3., any application received after the deadline will be considered as non-responsive and will not be evaluated. </P>
                <P>
                    2. 
                    <E T="03">Content and Form of Application:</E>
                     The application must include the name, address, telephone number, fax number, and e-mail address (if applicable) of a key contact person at the applicant's organization in case questions should arise. To be considered 
                    <E T="03">responsive</E>
                     to this solicitation the application must consist of three (3) separate and distinct sections: the Executive Summary, the Technical Proposal, and the Cost Proposal. The information provided in these three (3) sections is essential to demonstrate an understanding of the programmatic and fiscal contents of the cooperative agreement proposal(s). 
                </P>
                <P>
                    A complete application packages must not exceed 50 single-sided pages (8
                    <FR>1/2</FR>
                    ″ × 11″), double-spaced, 12-point font, typed pages (all attachments are included in the 50 page maximum). Any pages over the 50-page limit will not be read or evaluated. Major sections and sub-sections of the application must be divided and clearly identified (e.g. with tab dividers), and all pages must be numbered. To be considered responsive, cooperative agreement applications must include: 
                </P>
                <P>• An original, blue ink-signed, and two (2) copies of the cover letter. </P>
                <P>• An original and two (2) copies of the Executive Summary (see below). </P>
                <P>• An original and two (2) copies of the Technical Proposal [see below] </P>
                <P>• An original and two (2) copies of the Cost Proposal (see below) that includes an original, blue ink-signed, Application for Federal Assistance, SF-424 (Appendix A), a Budget Narrative, Budget Information Sheet SF-424A (Appendix B), an original, blue ink-signed, Assurances and Certifications Signature Page (Appendix C), a Direct Cost Description for Applicants and Sub-applicants (Appendix E), a completed Survey on Ensuring Equal Opportunity for Applicants (Appendix F), and the applicant's specific financial and/or audit statement dated within the last 18 months (audit and financial statements do not count towards the 50 page limitation). </P>
                <P>
                    <E T="03">A. Section 1—Executive Summary:</E>
                     A one to two page “Executive Summary” reflecting the applicant's proposed overall strategy, timeline, and outcomes to be achieved in their cooperative agreement proposal is required. The Executive Summary should include: 
                </P>
                <P>• An overview of the applicant's proposed plan to assist U.S. DOL-VETS in implementing a nation-wide technical assistance strategy and employer outreach effort, program design, process, methods, and proposed projects in providing technical assistance and information to various entities. </P>
                <P>• The applicant's experience in providing technical assistance and guidance on a nation-wide basis to assist homeless veterans or a similar group of persons. </P>
                <P>• Describe the measures of success for the plan. A summary of anticipated outcomes, goals, number of technical assistance responses provided, outreach methods, number of employers provided HVRP information, customers served, cost effectiveness, results-oriented model, benefits, and value added by the project. </P>
                <P>
                    B. 
                    <E T="03">Section 2—Technical Proposal</E>
                     must not exceed 15 pages of single-sided 12-pitch font and one inch left, right, top, and bottom margins and does count towards the 50 page maximum. 
                </P>
                <P>
                    <E T="03">Required Content:</E>
                     Applicants must be responsive to the Rating Criteria contained in Section V(1) and address all of the rating factors as thoroughly as possible in the narrative in order to be found technically acceptable under this solicitation. The technical proposal consists of a narrative proposal that demonstrates and describes the methodologies used in assisting U.S. DOL-VETS in implementing and managing technical assistance provided for HVRP purposes; in extracting, gathering, documenting, and publicizing twenty (20) HVRP grantee best practices; in assisting USDOL-VETS by developing and implementing a nation-wide employer outreach component to inform employers about HVRP in order to increase employment opportunities for homeless veterans. Applicants will indicate their availability and capability to assisting USDOL-VETS by conducting general research and studies as determined by USDOL-VETS.
                </P>
                <P>
                    <E T="03">The applicant(s) must describe:</E>
                     Organizational capability to provide required program activities including: key staff skills, experience, biographies, history, knowledge, qualifications, and capabilities; office locations, and organizational chart providing similar information. It is preferred that the awardee(s) be a well-established social service provider to veterans, homeless individuals, homeless veterans, or other similar type participants and not in the initial start-up phase or process. The applicant's relevant current and prior experience (within the last three-year period) in operating technical assistance grants, cooperative agreements, and/or contracts is to be clearly described, if applicable. 
                </P>
                <P>
                    <E T="03">Measures of Success</E>
                    —Applicants must describe the measures of success for the proposed plan. Applicants must describe their proposed outcomes, goals, number served, result-oriented model, feedback mechanism, performance accountability, evaluation and improvement, and the proposed system to monitor the implementation of program activities and achievement of stated project objectives. 
                </P>
                <P>
                    C. 
                    <E T="03">Section 3—The Cost Proposal must contain the following:</E>
                     Applicants can expect that the cost proposal will be reviewed to ensure that the costs proposed are allocable, allowable, and reasonable. The cost proposal must contain: 
                </P>
                <P>(1) Standard Form SF-424, “Application for Federal Assistance” (with the original signed in blue-ink) (Appendix A) must be completed; </P>
                <P>The Catalog of Federal Domestic Assistance number for this program is 17.805 and it must be entered on the SF-424, in Block 11. </P>
                <P>
                    The organizational unit section of Block 8 of the SF-424 must contain the Dun and Bradstreet Number (DUNS) of the applicant. Beginning October 1, 2003, all applicants for Federal funding opportunities are required to include a DUNS number with their application. 
                    <E T="03">See</E>
                     OMB Notice of Final Policy Issuance, 68 FR 38402 (June 27, 2003). Applicants' DUNS number is to be entered into Block 8 of SF-424. The DUNS number is a nine-digit identification number that uniquely 
                    <PRTPAGE P="18674"/>
                    identifies business entities. There is no charge for obtaining a DUNS number. To obtain a DUNS number call 1-866-705-5711 or access the following Web site: 
                    <E T="03">http://www.dunandbradstreet.com/.</E>
                     Requests for exemption from the DUNS number requirement must be made to the Office of Management and Budget. If no DUNS number is provided then the application will be considered non-responsive. 
                </P>
                <P>(2) Standard Form SF-424A “Budget Information Sheet” (Appendix B) must be included; </P>
                <P>(3) As an attachment to SF-424A, the applicant must provide a detailed cost breakout of each line item on the Budget Information Sheet. Please label this page or pages the “Budget Narrative” and ensure that costs reported on the SF-424A correspond accurately with the Budget Narrative; </P>
                <P>
                    <E T="03">The Budget Narrative must include, at a minimum:</E>
                </P>
                <P>
                    • 
                    <E T="03">Personnel Costs</E>
                    —Applicants must provide a breakout of all personnel costs by position, title, annual salary rates, and percent of time of each position to be devoted to the proposed project by completing the “Direct Cost Descriptions for Applicants and Sub-Applicants” form (Appendix E); 
                </P>
                <P>
                    • 
                    <E T="03">Fringe Benefits</E>
                    —Applicants must provide an explanation and breakout of fringe benefit rates and associated charges that exceed 35% of salaries and wages; 
                </P>
                <P>
                    • 
                    <E T="03">Explanation of Costs and Methodologies</E>
                    —Applicants must provide an explanation of the purpose and composition of, and methodology used to derive the costs of each of the following: Personnel costs, fringe benefits, travel, equipment, supplies, contracts, and any other costs. The applicant must include costs of any required travel described in this Solicitation. Planned travel expenditures may not exceed 20% of the total HVRP funds requested. Mileage charges may not exceed 48.5 cents per mile or the current Federal rate; 
                </P>
                <P>
                    • 
                    <E T="03">Equipment Purchases</E>
                    —Applicants must provide a description/specification of, and justification for, equipment purchases, if any. Tangible, non-expendable, personal property having a useful life of more than one year and a unit acquisition cost of $5,000 or more per unit must be specifically identified. 
                </P>
                <P>
                    • 
                    <E T="03">Other Funds</E>
                    —Applicants must describe other funding sources to include matching funds, leveraged funds, and in-kind services. Matching funds are not required for this HVRP-NTAC cooperative agreement(s). When resources such as matching funds, leveraged funds, and/or the value of in-kind contributions are made available, please describe in Section B of the Budget Information Sheet. 
                </P>
                <P>(4) A completed Assurance and Certification signature page (Appendix C) (signed in blue ink) must be submitted; </P>
                <P>(5) A completed Direct Cost Descriptions for Applicants and Sub-Applicants (Appendix D) must be submitted; </P>
                <P>
                    (6) All applicants must submit evidence of satisfactory financial management capability, which must include recent (within the last 18 months) program-specific financial and/or audit statements (does 
                    <E T="03">not</E>
                     count towards the 50 page limitation). All successful awardee(s) are required to utilize Generally Accepted Accounting Practices (GAAP), maintain a separate accounting for these cooperative agreement funds, and have a checking account; 
                </P>
                <P>(7) All applicants must include, as a separate appendix, a list of all employment and training related government grants, cooperative agreements, and contracts that they have had in the past three (3) years, including grant/contract officer contact information. VETS reserves the right to have a USDOL representative review and verify this data; </P>
                <P>(8) A completed Survey on Ensuring Equal Opportunity for Applicants (Appendix F) must be provided. </P>
                <P>
                    3. 
                    <E T="03">Submission Dates and Times</E>
                     (Acceptable Methods of Submission): Application packages must be received at the designated place by the date and time specified or it will not be considered. Any application received at the Office of Procurement Services after 5 p.m. ET, May 14, 2007, will not be considered unless it is received before the award is made and: 
                </P>
                <P>• It is determined by the Government that the late receipt was due solely to mishandling by the Government after receipt at the U.S. Department of Labor at the address indicated; or </P>
                <P>• It was sent by registered or certified mail not later than the fifth calendar day before May 14, 2007; or </P>
                <P>• It was sent by U.S. Postal Service Express Mail Next Day Service—Post Office to Addressee, not later than 5 p.m. at the place of mailing two (2) working days, excluding weekends and Federal holidays, prior to May 14, 2007. </P>
                <P>
                    The only acceptable evidence to establish the date of mailing of a late application sent by registered or certified mail is the U.S. Postal Service postmark on the envelope or wrapper and on the original receipt from the U.S. Postal Service. If the postmark is not legible, an application received after the above closing time and date will be processed as if mailed late. “Postmark” means a printed, stamped or otherwise placed impression (
                    <E T="03">not</E>
                     a postage meter machine impression) that is readily identifiable without further action as having been applied and affixed by an employee of the U.S. Postal Service on the date of mailing. Therefore applicants should request that the postal clerk place a legible hand cancellation “bull's-eye” postmark on both the receipt and the envelope or wrapper. Applications cannot be accepted by e-mail or facsimile machine. 
                </P>
                <P>The only acceptable evidence to establish the date of mailing of a late application sent by U.S. Postal Service Express Mail Next Day Service—Post Office to Addressee is the date entered by the Post Office clerk on the “Express Mail Next Day Service—Post Office to Addressee” label and the postmark on the envelope or wrapper and on the original receipt from the U.S. Postal Service. “Postmark” has the same meaning as defined above. Therefore, applicants should request that the postal clerk place a legible hand cancellation “bull's-eye” postmark on both the receipt and the envelope or wrapper. </P>
                <P>The only acceptable evidence to establish the time of receipt at the U.S. Department of Labor is the date/time stamp of the Procurement Services Center on the application wrapper or other documentary evidence or receipt maintained by that office. Applications sent by other delivery services, such as Federal Express, UPS, etc., will also be accepted. </P>
                <P>All applicants are advised that U.S. mail delivery in the Washington, DC area has been erratic due to security concerns. All applicants must take this into consideration when preparing to meet the application deadline, as you assume the risk for ensuring a timely submission, that is, if, because of these mail problems, the Department does not receive an application or receives it too late to give proper consideration, even if it was timely mailed, the Department is not required to consider the application. </P>
                <P>
                    4. 
                    <E T="03">Intergovernmental Review:</E>
                     Not Applicable. 
                </P>
                <P>
                    5. 
                    <E T="03">Funding Restrictions:</E>
                </P>
                <P>A. Proposals exceeding $500,000 will be considered non-responsive and will not be evaluated. </P>
                <P>B. Pre-award costs will not be reimbursed unless specifically agreed upon in writing by the Department of Labor. </P>
                <P>
                    C. Entities described in Section 501(c)(4) of the Internal Revenue Code that engage in lobbying activities are not eligible to receive funds under this announcement because Section 18 of 
                    <PRTPAGE P="18675"/>
                    the Lobbying Disclosure Act of 1995, Public Law No. 104-65, 109 Stat. 691, prohibits the award of Federal funds to these entities. 
                </P>
                <HD SOURCE="HD3">D. Limitations on Administrative and Indirect Costs </HD>
                <P>
                    • Administrative costs, which consist of all direct and indirect costs associated with the supervision and management of the program, are limited to and may not exceed 20% of the total cooperative agreement award. Indirect costs claimed by the applicant must be based on a federally approved rate. A copy of the current negotiated approved and signed indirect cost negotiation agreement must be submitted with the application. Furthermore, indirect costs are considered a part of administrative costs for HVRP purposes and, therefore, may not exceed 20% of the total cooperative agreement award. If the applicant does not presently have an approved indirect cost rate, a proposed rate with justification may be submitted. Successful applicants will be required to negotiate an acceptable and allowable rate within 90 days of cooperative agreement award with the appropriate USDOL Regional Office of Cost Determination or with the applicant's cognizant agency for indirect cost rates (
                    <E T="03">See</E>
                     Office of Management and Budget Web site at: 
                    <E T="03">http://www.whitehouse.gov/omb/grants/attach.html</E>
                    .
                </P>
                <HD SOURCE="HD1">V. Application Review Information </HD>
                <P>Cooperative Agreement applications will be evaluated on the applicant's capability to perform the work, technical approach, individual staff experience and qualifications, and applicant's past performance as described below in Section V.1. Based on these evaluations, a Competitive Range consisting of the most highly rated proposals will be established. </P>
                <P>Applicants are advised that the Grant Officer will make the selection of award(s) for a cooperative agreement after a careful evaluation of the proposals by a panel of evaluators chosen by USDOL-VETS and the Grant Officer. Each panelist will evaluate the proposals for technical acceptability using a range of scores assigned to each factor as described below in Section V.1. The scores for each area in Section V.I. below will then be added and ranked in numerical order. The grant review panel will score each applicant's proposal based on the grant applicant's responses to the overall requirements as outlined in this Solicitation for Cooperative Agreement(s) and the selection criteria in Section V.I., and recommend a proposal(s) based on the highest score. </P>
                <P>
                    1. 
                    <E T="03">Application Evaluation Criteria:</E>
                     Applications may receive up to 100 total points based on the following criteria: 
                </P>
                <P>A. Applicant's Overall Plan and Capability to assist USDOL-VETS by developing and maintaining a HVRP National Technical Assistance Center under a Cooperative Agreement (30 points) </P>
                <P>The Government will evaluate each applicant's overall plan and capability to assist USDOL-VETS by developing and maintaining a HVRP National Technical Assistance Center on the basis of its proposed strategy for providing technical assistance on a nation-wide or similar basis. In making this evaluation, the government will consider an applicant's: (1) Knowledge of the content of the work in terms of constituent activities, their inputs and outputs, and their interrelationships and interdependencies; (2) recognition of the appropriate sequence and realistic duration of the work activities; (3) knowledge of the appropriate types of resources required to perform the work activities; (4) familiarity with the difficulties, uncertainties, and risks associated with the work; and (5) knowledge of the personnel qualifications necessary to the performance of the work. </P>
                <P>B. Technical Approach (25 points). </P>
                <P>The applicant's technical approach should reflect a clear understanding of the HVRP program and innovative approaches in assisting the USDOL-VETS in successful accomplishment of all phases of this Solicitation for Cooperative Agreement(s), specifically, operational plan, design, implementation, project management and monitoring, and reporting. The applicant should demonstrate a clear understanding of each phase, task, and subtask. </P>
                <P>The Government will evaluate the applicant's knowledge and ability, based upon a clear understanding and articulation of the components of the HVRP, to assist U.S. DOL-VETS in promoting awareness of the HVRP in a positive, knowledgeable manner to other social service providers, local, state, and national employers, as well as to the general public. Applicants must provide a description of approaches (with examples) that the applicant would use in assisting U.S. DOL-VETS in developing and implementing a National Technical Assistance Center for HVRP purposes. The applicant must demonstrate active communications and strong relationships with other organizations providing services to veterans and homeless veterans or other similar type group of persons. </P>
                <P>The Government will review the following factors:</P>
                <P>• The applicant's proposed work plan addresses all of the tasks and subtasks listed in this Solicitation for Cooperative Agreement(s). </P>
                <P>• The applicant's proposed sequencing, scheduling, and timely completion of tasks/subtasks by phases demonstrates an understanding of the objectives and the applicant's critical role in assisting the government in implementation of the HVRP objectives. </P>
                <P>• The applicants' understanding of its role in assisting USDOL-VETS in providing general technical assistance and guidance to HVRP grantees, potential applicants, Veterans Service Organizations, non-profit organizations (including faith-based and community organizations), other federal agencies, the general public, and other interested stakeholders. </P>
                <P>• The applicant's understanding of its role in relation to parties other than USDOL-VETS federal and contractor staff, i.e., employers, organizations that support veterans, State Workforce Agencies, the Disabled Veterans' Outreach Program and Local Veterans' Employment Representative staff, Workforce Development programs, and other USDOL-VETS contractors and consultants. </P>
                <P>C. Individual Staff Experience and Qualifications (25 points). </P>
                <P>This section of the proposal must provide sufficient information to judge the quality and competence of staff proposed to assist USDOL-VETS in developing and maintaining the National Technical Assistance Center for HVRP purposes and to assure that it meets the required qualifications. Successful applicants will have staff that already possess (or are capable of acquiring within a short time period) knowledge of homeless veterans, the HVRP program, and other related programs for veterans and homeless veterans (such as: The Department of Veterans Affairs Grants and Per Diem Programs, Department of Housing and Urban Development grant programs and their Continuums of Care, Stand Down Events, etc.). The proposal must include the current employment status of personnel proposed to work under this cooperative agreement, i.e., whether these personnel are currently employed by the applicant or whether their employment is dependent upon award and planned recruitment. </P>
                <P>
                    The Government, in its evaluation of the applicant's proposal, will place considerable emphasis on the applicant's commitment of personnel qualified for the work involved in accomplishing the assigned tasks. 
                    <PRTPAGE P="18676"/>
                    Accordingly, the following information must be furnished: 
                </P>
                <P>1. The names of the proposed Project Director and other staff to be assigned under this Cooperative Agreement; </P>
                <P>2. A resume for all professional personnel which must include the individual's current employment status and previous work experience, including position title, dates in position, duties performed, employing organization, education, and training. </P>
                <P>D. Applicant's Past Performance (20 Points). </P>
                <P>Successful applicants must describe their past experience in providing technical assistance on a nation-wide basis (or similar basis) concerning the homeless veteran population, the HVRP program, Stand Down Events, and/or other similar type programs for veterans and homeless veterans or other similar type persons. Applicants must describe their role, duties, and responsibilities and to what extent they were involved in providing technical assistance on a nation-wide (or similar basis) on programs for veterans, homeless veterans, or other similar type persons. The application review panel and the Grant Officer will determine the relevance and extent of past performance information provided by each applicant. </P>
                <HD SOURCE="HD2">2. Review and Selection Process </HD>
                <P>Applications will be reviewed by a Department of Labor application review panel using the point scoring system specified above in Section V(1). The application review panel will assign a score after objectively and carefully evaluating each responsive application and all responsive applications will be ranked based on this score. The ranking will be the primary means of identifying applicants as potential awardee(s). The application review panel will establish a competitive range, based upon the proposal evaluation, for the purpose of selecting qualified applicants. For this solicitation, the minimum acceptable score for consideration is 70, but the competitive range may be set higher. </P>
                <P>The Grant Officer will make a final selection based on the application review panel findings and application scores. The application review panel's findings and recommendations are solely advisory in nature and not binding on the Grant Officer. </P>
                <P>A cost realism analysis will be performed by the application review panel. The purpose of this analysis is to screen all applicant cost proposals to ensure expenses are allocable, allowable, and reasonable. Determinations of allowable costs will be made in accordance with the applicable Federal cost principles, e.g., Non-Profit Organizations—OMB Circular A-122. Unallowable costs are those charges to an award that a grantor agency or its representatives determine are not to be allowed in accordance with the applicable Federal Cost Principles or other conditions contained in the cooperative agreement award. If the application review panel concludes that the cost proposal contains an expense(s) that is not allocable, allowable, and/or reasonable, they will inform the Grant Officer and he/she may request a revision to the application. </P>
                <P>The Government reserves the right to ask the applicant for clarification on any aspect of the cooperative agreement application. The Grant Officer may consult with Department of Labor staff on any potential awardee(s) concerns. The Grant Officer's determination for award under this solicitation is the final agency action. </P>
                <HD SOURCE="HD3">Anticipated Announcement and Award Dates </HD>
                <P>Announcement of this award is expected to occur by June 20, 2007. The cooperative agreement(s) will be awarded by no later than July 1, 2007. </P>
                <HD SOURCE="HD1">VI. Award Administration Information </HD>
                <HD SOURCE="HD2">1. Award Notices </HD>
                <P>A. The Notice of Award signed by the Grant Officer is the authorizing document and will be provided through postal mail and/or by electronic means to the authorized representative listed on the SF-424 Application for Federal Assistance. Notice that an organization has been selected as an award recipient does not constitute final approval of the application and budget as submitted. Before the actual cooperative agreement award, the Grant Officer and/or the Grant Officer's Technical Representative may enter into negotiations concerning such items as program components, funding levels, and administrative systems. If the negotiations do not result in an acceptable submittal, the Grant Officer reserves the right to terminate the negotiation and decline to fund the proposal. </P>
                <P>B. A post-award conference will be held within forty-five (45) days of the cooperative agreement award(s) in Washington, DC with the USDOL-VETS Grant Officer Technical Representative. The associated travel costs for this one (1) day meeting is to be included as a part of the applicant's budget proposal. Both program and administrative matters will be reviewed and discussed. </P>
                <P>Successful cooperative agreement awardee(s) are required to budget and plan to attend the post-award conference for all grantees awarded PY 2007 HVRP funds through another competition under SGA #07-07 and for those HVRP grantees awarded second and third optional year funding. The applicant(s) awarded a cooperative agreement to assist the USDOL-VETS in developing and maintaining the National Technical Assistance Center for HVRP purposes must attend and participate in the National HVRP Post-Award Training Conference that is expected to be held in August 2007. The site of the National HVRP Post-Award Training Conference has not yet been determined, however, for planning and budgeting purposes, applicants should allot four (4) days and use Denver, CO as the potential conference site. The successful awardee(s) are to propose a plan to develop and deliver specific training, with prior USDOL-VETS approval, at the National HVRP Post-Award Training Conference. Costs associated with attending this conference for up to three (3) awardee representatives will be allowed as long as they are incurred in accordance with Federal travel regulations. </P>
                <HD SOURCE="HD2">2. Administrative and National Policy Requirements </HD>
                <P>All awardee(s) must comply with the provisions of Title 38 U.S.C. and its regulations, as applicable. </P>
                <HD SOURCE="HD3">A. Administrative Program Requirements </HD>
                <P>All awardee(s), including faith-based organizations, will be subject to applicable Federal laws (including provisions of appropriations law), regulations, and the applicable Office of Management and Budget (OMB) Circulars. The successful awardee(s) under this Solicitation for a Cooperative Agreement will be subject to the following administrative standards and provisions, if applicable: </P>
                <P>• 29 CFR part 2—General Participation in Department of Labor Programs by Faith-Based and Community Organizations; Equal Treatment of All Department of Labor Program Participants and Beneficiaries. </P>
                <P>• 29 CFR part 30—Equal Employment Opportunity in Apprenticeship and Training. </P>
                <P>• 29 CFR part 31—Nondiscrimination in Federally Assisted Programs of the Department of Labor—Effectuation of Title VI of the Civil Rights Act of 1964. </P>
                <P>• 29 CFR part 32—Nondiscrimination on the Basis of Handicap in Programs or Activities Receiving Federal Financial Assistance. </P>
                <P>
                    • 29 CFR part 33—Enforcement of Nondiscrimination on the Basis of 
                    <PRTPAGE P="18677"/>
                    Handicap in Programs or Activities Conducted by the Department of Labor. 
                </P>
                <P>• 29 CFR part 35—Nondiscrimination on the Basis of Age in Programs and Activities Receiving Federal Financial Assistance from the Department of Labor. </P>
                <P>• 29 CFR part 36—Nondiscrimination on the Basis of Sex in Education Programs or Activities Receiving Federal Assistance. </P>
                <P>• 29 CFR part 37—Implementation of the Nondiscrimination and Equal Opportunity Provisions of the Workforce Investment Act of 1998. </P>
                <P>• 29 CFR part 93—New Restrictions on Lobbying. </P>
                <P>• 29 CFR part 94—Government-wide Requirements for Drug-Free Workplace (Financial Assistance). </P>
                <P>• 29 CFR part 95—Grants and Agreements with Institutions of Higher Education, Hospitals, and other Non-Profit Organizations, and with Commercial Organizations. </P>
                <P>• 29 CFR part 96—Audit Requirements for Grants, Contracts and Other Agreements. </P>
                <P>• 29 CFR part 98—Government-wide Debarment and Suspension (Non procurement). </P>
                <P>• 29 CFR part 99_Audit of States, Local Governments, and Non-Profit Organizations. </P>
                <P>• Applicable cost principles and audit requirements under OMB Circulars A-21, A-87, A-110, A-122, A-133, and 48 CFR part 31. </P>
                <P>• In accordance with Section 18 of the Lobbying Disclosure Act of 1995, Public Law 104-65 (2 U.S.C. 1611), non-profit entities incorporated under 501(c)(4) that engage in lobbying activities are not eligible to received Federal funds and grants. </P>
                <P>• 38 U.S.C. 4215—Requirements for priority of service for veterans in all Department of Labor training programs. </P>
                <P>
                    3. 
                    <E T="03">Reporting and Monitoring</E>
                    —USDOL-VETS is responsible for ensuring the effective implementation of this Cooperative Agreement, in accordance with the provisions of this announcement and the terms of the Cooperative Agreement award document. The awardee(s) must fully cooperate with USDOL-VETS staff while they conduct periodic on-site project reviews. Reviews will focus on timely project implementation, performance in meeting the Cooperative Agreement's objectives, tasks and responsibilities, expenditure of funds on allowable activities, and overall administration of project activities. The awardee(s) must agree to fully cooperate with monitoring personnel and make available performance and financial records on all parts of project activity, including participant employment and wage data, and to provide access to personnel, as specified by the Grant Officer Technical Representative. 
                </P>
                <P>The awardee(s) will be required to submit periodic financial and programmatic accomplishment reports to their respective Grant Officer Technical Representative (GOTR) as described below: </P>
                <HD SOURCE="HD3">A. Quarterly Financial Reports </HD>
                <P>No later than 30 days after the end of each Federal fiscal quarter (October 30th, January 30th, April 30th, and July 30th) the awardee(s) must report outlays, program income, and other financial information on a Federal fiscal quarterly basis using SF-269, Financial Status Report, and submit a copy of the HHS/PMS 272 draw down report to their GOTR. These required quarterly financial reports must cite the assigned grant number and be electronically submitted to the Department of Labor's E-Grants Reporting System. </P>
                <HD SOURCE="HD3">B. Quarterly Program Reports </HD>
                <P>No later than 30 days after the end of each Federal fiscal quarter (October 30th, January 30th, April 30th, and July 30th) awardee(s) must submit a Quarterly Technical Narrative Performance Report to the GOTR that contains the following: </P>
                <P>(1) A comprehensive description of actual technical assistance and employer outreach activities conducted and the status of progress on identifying and drafting twenty (20) HVRP grantee best practices as compared to the planned goals for the reporting period; </P>
                <P>(2) An explanation for variances of plus or minus 15% of planned program and/or expenditure goals, to include: Identification of corrective action that will be taken to meet the planned goals, if required; and a timetable for accomplishment of the corrective action. </P>
                <P>These quarterly technical performance reports must cite the assigned grant number and may be submitted to the GOTR electronically via e-mail. </P>
                <HD SOURCE="HD3">C. 90-Day Final Report </HD>
                <P>An outline of the final report is due to the GOTR forty-five (45) days prior to the expiration of the cooperative agreement (May 15th) before the expiration of the (each) period of performance. No later than 120 days after the (each) period of performance (October 30th), the awardee(s) must submit a final narrative technical performance report to their Grant Officer Technical Representative showing results and performance as of the 90th day after the award period, and containing the following: </P>
                <P>(1) Final Financial Status Report SF-269 data entered into the Department of Labor's E-grants reporting system (that zeros out all unliquidated obligations); and </P>
                <P>(2) Final Technical Performance Report that describes the outcomes, technical assistance provided, employer outreach activities conducted as compared to the planned activities, the final twenty (20) HVRP grantee best practices document in Word or .pdf format (if not provided earlier), and a narrative description of the overall activities performed, lessons learned, and recommendations for programmatic improvement(s). </P>
                <P>The final financial and technical performance reports must cite the assigned grant number and may be submitted to the Grant Officer Technical Representative electronically via e-mail. </P>
                <P>
                    <E T="03">Agency Contact:</E>
                     All questions regarding this solicitation should be directed to Cassandra Mitchell, e-mail address: 
                    <E T="03">mitchell.cassandra_dol.gov</E>
                    , at telephone number: (202) 693-4570 (note this is not a toll-free number). To obtain further information on the Homeless Veterans' Reintegration Program of the U.S. Department of Labor, visit the USDOL-VETS Web site at 
                    <E T="03">http://www.dol.gov/vets</E>
                    . Individuals with hearing impairments may call 1-800-670-7008 (TTY/TDD). 
                </P>
                <HD SOURCE="HD1">VII. Other Information </HD>
                <HD SOURCE="HD2">A. Acknowledgement of USDOL Funding </HD>
                <P>
                    1. 
                    <E T="03">Printed Materials:</E>
                     In all circumstances, the following must be displayed on printed materials prepared by the awardee(s) while in receipt of USDOL funding: “Preparation of this item was funded by the United States Department of Labor under Grant No. [insert the appropriate grant number].” 
                </P>
                <P>• All printed materials must also include the following notice: “This document does not necessarily reflect the views or policies of the U.S. Department of Labor, nor does mention of trade names, commercial products, or organizations imply endorsement by the U.S. Government.” </P>
                <P>
                    2. 
                    <E T="03">Public references to cooperative agreement award(s):</E>
                     When issuing statements, press releases, requests for proposals, bid solicitations, and other documents describing projects or programs funded in whole or in part with Federal money, all awardees receiving Federal funds must clearly state: 
                </P>
                <P>
                    • The percentage of the total costs of the program or project, which will be financed with Federal money; 
                    <PRTPAGE P="18678"/>
                </P>
                <P>• The dollar amount of Federal financial assistance for the project or program; and </P>
                <P>• The percentage and dollar amount of the total costs of the project or program that will be financed by non-governmental sources. </P>
                <P>B. Use of USDOL Logo: In consultation with USDOL, VETS, the awardee(s) must acknowledge USDOL's role as described below: </P>
                <P>• The USDOL logo may be applied to USDOL-funded material prepared for distribution, including posters, videos, pamphlets, research documents, national survey results, impact evaluations, best practice reports, and other publications of global interest. The awardee(s) must consult with USDOL on whether the logo may be used on any such items prior to final draft or final preparation for distribution. In no event will the USDOL logo be placed on any item until USDOL has given the awardee(s) permission to use the logo on the item. </P>
                <P>• All documents must include the following notice: ``This documentation does not necessarily reflect the views or policies of the U.S. Department of Labor, nor does mention of trade names, commercial products, or organizations imply endorsement by the U.S. Government.''</P>
                <P>C. OMB Information Collection No. 1205-0458, Expires September 30, 2009. According to the Paperwork Reduction Act of 1995, no persons are required to respond to a collection of information unless such collection displays a valid OMB control number. Public reporting burden for this collection of information is estimated to average 20 hours per response, including time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding the burden estimated or any other aspect of this collection of information, including suggestions for reducing this burden, to the U.S. Department of Labor, to the attention of Cassandra Mitchell, 200 Constitution Avenue, NW., Room S-4307, Washington, DC 20210. </P>
                <P>This information is being collected for the purpose of awarding a grant. The information collected through this “Solicitation for Grant Applications” will be used by the Department of Labor to ensure that grants are awarded to the applicant best suited to perform the functions of the grant. Submission of this information is required in order for the applicant to be considered for award of this grant. Unless otherwise specifically noted in this announcement, information submitted in the respondent's application is not considered to be confidential. </P>
                <P>
                    <E T="03">Resources for the Applicant:</E>
                     The Department of Labor maintains a number of Web-based resources that may be of assistance to applicants. The Web page for the USDOL-VETS at 
                    <E T="03">http://www.dol.gov/vets/programs/main.htm</E>
                     is a valuable source of information including the program highlights and brochures, glossary of terms, frequently used acronyms, general and special provisions, power point presentations on how to apply for HVRP funding, On-Site Monitoring Visits, etc. The Interagency Council on Homeless at Web page 
                    <E T="03">http://www.ich.gov</E>
                     has information from various departments that assist homeless persons including updated information on local community ten (10) year plans to end homelessness and continuum of care plans. Applicants may also review “VETS' Guide to Competitive and Discretionary Grants” located at Web page 
                    <E T="03">http://www.dol.gov/vets/grants/Final_VETS_Guide-linked.pdf</E>
                    . For a basic understanding of the application process and basic responsibilities of receiving Federal funds, please see “Guidance for Faith-Based and Community Organizations on Partnering with the Federal Government” at Web pages 
                    <E T="03">http://www.whitehouse.gov/government/fbci</E>
                     and 
                    <E T="03">http://www.dol.gov/cfbci.</E>
                </P>
                <P>
                    <E T="03">Appendices:</E>
                     (Located on U.S. Department of Labor, Veterans' Employment and Training Service Web page 
                    <E T="03">http://www.dol.gov/vets</E>
                     follow link for the applicable solicitation listed under announcements).
                </P>
                <FP SOURCE="FP-1">Appendix A: Application for Federal Assistance SF-424. </FP>
                <FP SOURCE="FP-1">Appendix B: Budget Information Sheet SF-424A. </FP>
                <FP SOURCE="FP-1">Appendix C: Assurances and Certifications Signature Page. </FP>
                <FP SOURCE="FP-1">Appendix D: Direct Cost Descriptions for Applicants and Sub-Applicants. </FP>
                <FP SOURCE="FP-1">Appendix E: Survey on Ensuring Equal Opportunity for Applicants. </FP>
                <SIG>
                    <NAME>Lisa Harvey, </NAME>
                    <TITLE>Grant Officer.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC> [FR Doc. E7-7027 Filed 4-12-07; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4510-79-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF LABOR </AGENCY>
                <SUBAGY>Veterans' Employment and Training Service </SUBAGY>
                <SUBJECT>Urban and Non-Urban Homeless Veterans' Reintegration Program (HVRP) Grants for Program Year (PY) 2007 Solicitation for Grant Applications #07-07, Period of Performance Is PY 2007, July 1, 2007 Through June 30, 2008; Catalog of Federal Domestic Assistance #17.805 </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Veterans' Employment and Training Service, Labor. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of funding availability. </P>
                </ACT>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Applications are due on May 14, 2007. </P>
                </DATES>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>(Applicants For Grant Funds Should Read This Notice In Its Entirety): The U.S. Department of Labor (USDOL), Veterans' Employment and Training Service (VETS), announces a grant competition under 38 U.S.C. Section 2021, as added by Section 5 of Public Law 107-95, the Homeless Veterans Comprehensive Assistance Act of 2001 (HVCAA). Section 2021 requires the Secretary of Labor to conduct, directly or through grant or contract, such programs as the Secretary determines appropriate to expedite the reintegration of homeless veterans into the labor force. </P>
                    <P>Both Urban and Non-Urban areas serving homeless veterans will be considered for funding under this HVRP solicitation. Urban areas are those that serve a high concentration of homeless veterans in the metropolitan areas of the 75 U.S. cities largest in population and the metropolitan area of San Juan, Puerto Rico, and are listed in Appendix G. Non-Urban areas are those areas that serve homeless veterans that are not listed on Appendix G. Applicants must indicate whether they are applying for an Urban or Non-Urban grant award on their grant application. </P>
                    <P>
                        HVRP grants are intended to address two objectives: (1) To provide services to assist in reintegrating homeless veterans into meaningful employment within the labor force, and (2) to stimulate the development of effective service delivery systems that will address the complex problems facing homeless veterans. Successful applicants will design programs that assist eligible veterans by providing job placement services, job training, counseling, supportive services, and other assistance to expedite the reintegration of homeless veterans into the labor force. Successful programs will also be designed to be flexible in addressing the universal as well as the 
                        <PRTPAGE P="18679"/>
                        local or regional problems that have had a negative impact on homeless veterans reentering the workforce. 
                    </P>
                    <P>Under this solicitation covering PY 2007, VETS anticipates that up to $8,200,000 will be available, with a maximum award of $300,000 for grants that serve Urban areas and $200,000 for grants that serve Non-Urban areas. VETS expects to award grants in both the Urban and Non-Urban categories. The number of grants to be awarded in each category will be announced after selections are made as the grants are awarded based on merit of the application and the applicants. Awards are expected to range from $75,000 to a maximum of $200,000 for grants that serve Non-Urban areas and from $75,000 to a maximum of $300,000 for grants that serve Urban areas. This notice contains all of the necessary information and forms to apply for grant funding. The period of performance for these PY 2007 grants will be July 1, 2007 through June 30, 2008. Two (2) optional years of additional funding may be available, subject to the availability funding, to the agency's decision to exercise the option year(s) of funding, and to satisfactory grantee and sub-awardee(s) performance. </P>
                    <HD SOURCE="HD1">I. Funding Opportunity Description </HD>
                    <P>The U.S. Department of Labor (USDOL), Veterans' Employment and Training Service (VETS), announces a grant competition under 38 U.S.C. Section 2021, as added by Section 5 of Public Law 107-95, the Homeless Veterans Comprehensive Assistance Act of 2001 (HVCAA) . Section 2021 requires the Secretary of Labor (the Secretary) to conduct, directly or through grant or contract, such programs as the Secretary determines appropriate to provide job training, counseling, and placement services (including job readiness, literacy training, and skills training) to expedite the reintegration of homeless veterans into the labor force. </P>
                    <HD SOURCE="HD2">1. Program Concept and Emphasis </HD>
                    <P>HVRP grants are intended to address two objectives: (a) to provide services to assist in reintegrating homeless veterans into meaningful employment within the labor force, and (b) to stimulate the development of effective service delivery systems that will address the complex problems facing homeless veterans. </P>
                    <P>For this Program Year (PY) 2007 grant solicitation, VETS seeks applicants that will provide services through a client-centered case management approach that will network with Federal, State, and local resources for veteran support programs. Successful applicants will have clear strategies and obtainable goals for employment and retention of employment for homeless veterans. Successful applicants will design programs that assist eligible veterans by providing job placement services, job training, counseling, mentoring, supportive services, and other assistance to expedite the reintegration of homeless veterans into the labor force. Successful applicants will also design programs that are flexible in addressing the universal as well as the local or regional problems that have had a negative impact on homeless veterans reentering the workforce. The HVRP in PY 2007 will seek to continue to strengthen development of effective service delivery systems, to provide comprehensive services “through a client-centered case management approach” that addresses complex problems facing eligible veterans trying to transition into gainful employment, and to improve strategies for employment and retention in employment. </P>
                    <HD SOURCE="HD2">2. Project Awareness Program Information and Orientation Activities </HD>
                    <P>In order to promote networking between the HVRP-funded program and local service providers (and thereby eliminate gaps or duplication in services and enhance the provision of assistance to participants), the grantee and sub-awardee(s) must provide project orientation workshops and program awareness activities that it determines are the most feasible for the types of providers listed below. Grantees and sub-awardee(s) are encouraged to propose strategies for incorporating small faith-based and community organizations (defined as organizations with social services budgets of $500,000 or less and ten (10) or fewer full-time employees) into their outreach plans. Project orientation workshops conducted by grantees and sub-awardee(s) have been an effective means of sharing information and informing the community of the availability of other services; they are encouraged but it is not mandatory. Grantees and sub-awardee(s) will have the flexibility to attend service provider meetings, seminars, and conferences, to outstation staff, and to develop individual service contracts as well as to involve other agencies in program planning. </P>
                    <P>
                        <E T="03">The grantee and sub-awardee(s) will be responsible for providing project awareness, program information, and orientation activities to the following:</E>
                    </P>
                    <P>A. Direct providers of services to homeless veterans, including shelter and soup kitchen operators, to make them aware of the services available to homeless veterans to make them job-ready and to aid their placement into jobs; </P>
                    <P>B. Federal, State, and local agencies such as the Housing and Urban Development (HUD), Social Security Administration (SSA), Department of Veterans Affairs (DVA), State Workforce Agencies (SWAs) and local One-Stop Career Centers (which integrate Workforce Investment Act (WIA) and other employment and training services), mental health services, and healthcare detoxification facilities; to familiarize them with the nature and needs of homeless veterans; and </P>
                    <P>C. Civic and private sector groups, in particular veterans' service organizations, support groups, job training and employment services, and community-based organizations (including faith-based organizations), to provide information on homeless veterans and their needs. </P>
                    <P>The grantee and sub-awardee(s) will also be responsible for participating in “Stand Down” events. A “Stand Down” is an event held in a locality, usually for one (1) to three (3) days, where services are provided to homeless veterans along with shelter, meals, clothing, employment services, and medical attention. This type of event is mostly a volunteer effort, which is organized within a community and brings service providers together such as the Department of Veterans Affairs, Disabled Veterans' Outreach Program Specialists (DVOP) and Local Veterans' Employment Representatives (LVER) staff from the State Workforce Agencies (SWAs), Veteran Service Organizations, military personnel, civic leaders, and a variety of other interested persons, groups, and organizations. Many services are provided on-site with referrals also made for continued assistance after the Stand Down event. These events can often be the catalyst that enables homeless veterans to get back into mainstream society. The Department of Labor has supported replication of these events and many have been held throughout the nation. </P>
                    <P>
                        <E T="03">In areas where an HVRP is operating, grantees and sub-awardee(s) are expected and encouraged to participate fully and offer their services for all locally planned Stand Down event(s).</E>
                         Toward this end, up to $8,000 of the requested HVRP grant funds may be used to supplement the Stand Down efforts, where funds are not otherwise available, and may be requested and explained in the budget narrative. 
                        <PRTPAGE P="18680"/>
                    </P>
                    <HD SOURCE="HD2">3. Scope of Program Design </HD>
                    <P>
                        <E T="03">In addition to the activities described above, the project design must include the following services:</E>
                    </P>
                    <P>A. Outreach, intake, assessment, peer counseling or mentoring to the degree practical, employment services, and follow-up support services to enhance retention in employment. Program staff providing outreach services should have experience in dealing with, and an understanding of the needs of, homeless veterans. Outreach activities must include and coordinate with the DVOP and LVER staff in the SWAs or in the workforce investment systems' One-Stop Career Centers, Veterans' Workforce Investment Program (VWIP), the Department of Veterans Affairs (DVA), and Department of Housing and Urban Development (HUD) and their local Continuum of Care. </P>
                    <P>B. Provision of or referral to employment services such as: Job search workshops; job counseling; assessment of skills; resume writing techniques; interviewing skills; subsidized trial employment (work experience); job development services; job placement into unsubsidized employment; and job placement follow-up services to enhance retention in employment. </P>
                    <P>C. Provision of or referral to training services such as: Basic skills instruction; remedial education activities; life skills and money management training; on-the-job training; classroom training; vocational training; specialized and/or licensing training programs; and other formal training programs as deemed appropriate to benefit the participant. At least 80% of the enrolled HVRP participants must participate in training activities. </P>
                    <P>D. Grantees and sub-awardee(s) must perform preliminary assessment of each participant's eligibility for DVA service-connected disability, compensation, and/or pension benefits. As appropriate, grantees and sub-awardee(s) will work with the veterans' service organizations or refer the participants to DVA in order to file a claim for compensation or pension. Grantees and sub-awardee(s) will track the progress of claims and report outcomes in individual participant case management records.</P>
                    <P>E. Coordination with veterans' services programs, including: DVOPs and LVERs in the workforce investment system's One-Stop Career Centers as well as VWIP grantees; DVA services, including its Health Care for Homeless Veterans, Domiciliary Care, Regional Benefits Assistance Program, and Transitional Housing under Homeless Provider Grant and Per Diem programs; and HUD and their local Continuum of Care. </P>
                    <P>F. Networking, collaborating, and coordinating efforts with veterans' service organizations such as: The American Legion; Disabled American Veterans; Veterans of Foreign Wars; Vietnam Veterans of America; The American Veterans (AMVETS); etc. to ensure participants apply for and/or receive other veterans' benefits that they may be eligible for. </P>
                    <P>G. Referral as necessary to health care, counseling, and rehabilitative services including, but not limited to: Alcohol and drug rehabilitation, therapeutic services; Post Traumatic Stress Disorder (PTSD) services; and mental health services as well as coordination with McKinney-Vento Homeless Assistance Act (MVHAA) programs for health care for the homeless; and health care programs under the Homeless Veterans Comprehensive Assistance Act (HVCAA) of 2001. </P>
                    <P>H. Referral to housing assistance, as appropriate, provided by: HUD and their local Continuum of Care; local shelters; Federal Emergency Management Administration (FEMA) food and shelter programs; transitional housing programs and single room occupancy housing programs funded under MVHAA and HVCAA, and permanent housing programs for disabled homeless persons funded under MVHAA and HVCAA. </P>
                    <HD SOURCE="HD2">4. Performance Measures </HD>
                    <P>For purposes of assessing performance of grantees selected under this SGA, VETS will focus on two performance measures described below. However, grantees also will be required to report additional performance information, as required in the provided DOL guidance on Common Measures and as described below. All performance outcomes will be reported quarterly using an Internet-based reporting system for HVRP, with access provided to successful grantees after the award process has been completed. </P>
                    <P>There are two (2) outcome measures with established performance targets for HVRP grants. The first outcome measure is the placement rate with a performance target for grantees and sub-awardee(s) to meet a minimum placement (now referred to as entered employment under Common Measures definitions) rate of 66%. This is determined by dividing the number of participants who entered employment (or employed after their Exit Quarter) by the number of participants exited. Under Common Measures, a person is considered to have exited the program if they have secured a job and/or not received job search or employment service (other than follow-up and retention services) for at least one (1) quarter or over 90 days. Job retention and counseling services do not count as a “service” that would prevent a person from being exited from the program. See further definitions below. While the percentage of HVRP participants who enter employment is an important outcome, it is also necessary to evaluate and measure the program's longer-term results, through the 90-day, 180-day, and 270-day employment retention follow-up periods after a HVRP participant enters employment. The second outcome measure is retention following placement with a performance target for grantees and sub-awardee(s) to meet a minimum rate of retention of 59%. This is determined by dividing the number of participants retained in employment for 180-days divided by the total number of participants who entered employment two (2) quarters previously. Note: For example, awardees should not have a reported retention rate before the third quarter, since it requires at least 180-days by the definition after a person enters employment and 90-days to be considered exited from the program for the awardee to be able to post job retention. While there is no performance target established for retention at 90-days following entered employment, grantees are required to collect and report the rate of retention in employment at that point. </P>
                    <P>The Common Measures Technical Assistance Guide for Competitive Grantees (Appendix H) describes in detail the specific data grantees will be required to collect and report on utilizing the Common Measures definitions, methodologies, and reporting requirements. Appendix H and the Recommended Format for Common Measures Planned Quarterly Technical Performance Goals (Appendix D) are provided to assist applicants in determining their planned goals. </P>
                    <HD SOURCE="HD2">5. Results-Oriented Model </HD>
                    <P>
                        No specific model is mandatory, but successful applicants will design a program that is responsive to the needs of the local community and achieves the HVRP objectives. The HVRP objectives are to successfully reintegrate homeless veterans into the workforce and to stimulate the development of effective service delivery systems that will address the complex problems facing homeless veterans. Under the Government Performance and Results Act (GPRA), Congress and the public are looking for program results. 
                        <PRTPAGE P="18681"/>
                    </P>
                    <P>The applicant's program should be based on a results-oriented model. The first phase of activity should consist of the level of outreach necessary to introduce the program to eligible homeless veterans. Outreach also includes establishing contact with other agencies that encounter homeless veterans. Once the eligible homeless veterans have been identified, an assessment must be made of each individual's abilities, interests, needs, and barriers to employment. In some cases, participants may require referrals to services such as rehabilitation, drug or alcohol treatment, or a temporary shelter before they can be enrolled into the HVRP program. Once the eligible homeless veteran is stabilized, the assessment must concentrate on the employability of the individual and whether the individual is to be enrolled into the HVRP program. </P>
                    <P>A determination should be made as to whether the HVRP participant would benefit from pre-employment preparation such as resume writing, job search workshops, related employment counseling, and case management, or possibly an initial entry into the job market through temporary jobs. Additionally, sheltered work environments such as the Department of Veterans Affairs Compensated Work Therapy Program, classroom training, and/or on-the-job training must be evaluated. Such services should be noted in an Individual Employment Plan (IEP) to facilitate the staff's successful monitoring of the participant's progress. Entry into full-time employment or a specific job-training program should follow, in keeping with the overall objective of HVRP, to bring the participant closer to self-sufficiency. The grantee should provide or arrange for these supportive services that will enable the HVRP participant to successfully perform all the activities specified in the IEP. </P>
                    <P>Job development, a crucial part of the employability process, usually occurs when there are no competitive job openings that the HVRP participant is qualified to apply for; therefore, a job opportunity with an employer is created, developed, and customized specifically for that HVRP participant. HVRP participants who are ready to enter employment and are in need of intensive case management services for employment purposes are to be referred to the DVOP and LVER staff at a One-Stop Career Center. DVOP and LVER staff are able to provide HVRP participants the following services: job development, employment services, case management for employment purposes, and career counseling. Most DVOP and LVER staff received training in case management for employment purposes at the National Veterans' Training Institute. All DVOP and LVER staff provides employment-related services to veterans who are most at a disadvantage in the labor market. VETS recommends all HVRP grantees work hand-in-hand with DVOP/LVER and other One-Stop Career Center staff to achieve economies of resources and to avoid duplication of services. DVOP/LVER staff may also be able to provide grantees and sub-awardee(s) valuable assistance in tracking participants within their State wage record management information system for follow-up purposes at 90-, 180-, and 270-days after a participant enters employment. </P>
                    <P>The applicant's program must include tracking of program participants. Participant tracking should begin with the referral to supportive services and training activities and continue at placement into employment and through the 90-day, 180-day, and 270-day follow-up periods after the participant enters employment. It is important that the grantee and sub-awardee(s) maintain contact with veterans after placement to ensure that employment-related problems are addressed. The 90-day, 180-day, and 270-day follow-ups are fundamental to assessing program results. Grantees and sub-awardee(s) need to budget for 90-day, 180-day, and 270-day follow-up activity so that it can be performed for those participants who enter employment at or near the end of the grant performance period. All grantees and sub-awardee(s), prior to the end of the grant performance period, must obligate sufficient funds to ensure that follow-up activities are completed. Such results will be reported in the final technical performance report. </P>
                    <HD SOURCE="HD1">II. Award Information </HD>
                    <HD SOURCE="HD2">1. Type of Funding Instrument </HD>
                    <P>One-year grants with optional funding for an additional two years will be awarded. </P>
                </SUM>
                <NOTE>
                    <HD SOURCE="HED">Note:</HD>
                    <P>Selection of an organization as a grantee does not constitute final approval of the grant application and budget as submitted. Before or shortly after the actual grant is awarded, USDOL may enter into negotiations about such items as program components, staffing, and funding levels, and administrative systems in place to support grant implementation. If the negotiations do not result in a mutually acceptable submission, the Grant Officer reserves the right to terminate the negotiation and decline to fund the application or terminate the award.</P>
                </NOTE>
                <HD SOURCE="HD2">2. Funding Levels </HD>
                <P>Under this solicitation covering Program Year (PY) 2007, VETS anticipates that up to $8,200,000 will be available, with a maximum award of $300,000 for grants that serve Urban areas and $200,000 for grants that serve Non-Urban areas. VETS expects to award grants in both the Urban and Non-Urban categories. The number of grants to be awarded in each category will be announced after selections are made as the grants are awarded based on merit of the application and the applicants. Awards are expected to range from $75,000 to a maximum of $200,000 for grants that serve Non-Urban areas and from $75,000 to a maximum of $300,000 for grants that serve Urban areas. Applicants must indicate in writing whether they are applying for an Urban or Non-Urban grant award on their grant application. The Department of Labor reserves the right to negotiate the amounts to be awarded under this competition. Please be advised that requests exceeding $200,000 that plan to serve Non-Urban areas and $300,000 that plan to serve Urban areas will be considered non-responsive and will not be evaluated. If there are any residual programmatic funds, the Department of Labor reserves the right to select for funding the next highest scoring applicant(s) on the competitive list developed for this SGA up to June 30, 2008. </P>
                <HD SOURCE="HD2">3. Period of Performance </HD>
                <P>The period of performance will be for the twelve (12) month period of July 1, 2007 through June 30, 2008, unless modified by the Grant Officer. It is expected that successful applicants will begin program operations under this solicitation on July 1, 2007. All program funds must be obligated by the grantee by June 30, 2008; a limited amount of funds may be obligated and reserved for follow-up activities and closeout. </P>
                <HD SOURCE="HD2">4. Optional Year Funding </HD>
                <P>
                    Should Congress appropriate additional funds for this purpose, VETS may consider up to two (2) additional years of optional funding. The Government does 
                    <E T="03">not,</E>
                     however, guarantee optional year funding for any grantee or sub-awardee(s). In deciding whether to exercise any optional year(s) of funding, VETS will consider grantee and sub-awardee(s) performance during the previous period of operations as follows: 
                </P>
                <P>
                    A. The grantee and sub-awardee(s) must meet, at minimum, 90% of planned cumulative goals for Federal expenditures, enrollments, placements 
                    <PRTPAGE P="18682"/>
                    into employment, and training by the end of the third quarter; and 
                </P>
                <P>B. The grantee and sub-awardee(s) must have complied with all terms identified in the Solicitation for Grant Application (SGA), grant award document, and General and Special Grant Provisions; and </P>
                <P>C. All program and fiscal reports must have been submitted by the established due dates and the grantee and sub-awardee(s) must verify these reports for accuracy purposes. </P>
                <HD SOURCE="HD1">III. Eligibility Information </HD>
                <HD SOURCE="HD2">1. Eligible Applicants </HD>
                <P>Applications for funds will be accepted from State and local Workforce Investment Boards, local public agencies, for-profit/commercial entities, and non-profit organizations, including faith-based and community organizations. Applicants must have a familiarity with the area and population to be served and the ability to administer an effective and timely program. </P>
                <P>
                    <E T="03">Eligible applicants will generally fall into one of the following categories:</E>
                </P>
                <P>• State and local Workforce Investment Boards (WIBs), established under Sections 111 and 117 of the Workforce Investment Act. </P>
                <P>• Public agencies, meaning any public agency of a State or of a general purpose political subdivision of a State that has the power to levy taxes and spend funds, as well as general corporate and police powers. (This typically refers to cities and counties.) A State agency may propose in its application to serve one or more of the jurisdictions located in its State. This does not preclude a city or county agency from submitting an application to serve its own jurisdiction. </P>
                <P>• For-profit/commercial entities. </P>
                <P>• Non-profit organizations (including faith-based and community organizations). If claiming 501(c)(3) status, the Internal Revenue Service statement indicating 501(c)(3) status approval must be submitted. </P>
                <P>Note that entities organized under Section 501(c)(4) of the Internal Revenue Code are not eligible to receive funds under this announcement. Section 18 of the Lobbying Disclosure Act of 1995, Public Law 104-65, 109 Stat. 691 (2 U.S.C. 1611) prohibits instituting an award, grant, or loan of federal funds to 501(c)(4) entities that engage in lobbying. </P>
                <HD SOURCE="HD2">2. Cost Sharing </HD>
                <P>
                    Cost sharing and matching funds are 
                    <E T="03">not</E>
                     required. However, we do encourage grantees and sub-awardee(s) to maximize the resources available to the HVRP program and its participants. 
                </P>
                <HD SOURCE="HD2">3. Other Eligibility Criteria </HD>
                <P>A. Both Urban and Non-Urban areas serving homeless veterans will be considered for funding under this HVRP solicitation. Urban areas are those that serve a high concentration of homeless veterans in the metropolitan areas of the 75 U.S. cities largest in population and the metropolitan area of San Juan, Puerto Rico, and are listed in Appendix G. Non-Urban areas are those areas that serve homeless veterans that are not listed on Appendix G. </P>
                <P>B. The proposal must include a participant outreach component that uses DVOP/LVER staff and/or trained outreach staff. Programs must be “employment-focused.” An “employment-focused” program is a program directed toward: (1) Increasing the employability of homeless veterans through training or arranging for the provision of services that will enable them to reintegrate into the labor force and (2) matching homeless veterans with potential employers and/or entrepreneurial opportunities. </P>
                <P>C. Applicants are encouraged to utilize, through partnerships or sub-awards, experienced public agencies, private non-profit organizations, private businesses, faith-based and community organizations, and colleges and universities (especially those with traditionally high enrollments of minorities) that have an understanding of unemployment and the barriers to employment unique to homeless veterans, a familiarity with the area to be served, linkages with the One-Stop Career Center(s), and the capability to effectively provide the necessary services. </P>
                <P>
                    D. 
                    <E T="03">Legal Rules Pertaining to Inherently Religious Activities by Organizations that Receive Federal Financial Assistance:</E>
                     Neutral, non-religious criteria that neither favor nor disfavor religion will be used in the selection of grant recipients and must be employed by Grantees or in the selection of sub-awardee(s). The U.S. Government is generally prohibited from providing “direct” financial assistance for inherently religious activities. The Grantee may be a faith-based organization or work with a partner with religious institutions; however, “direct” Federal financial assistance provided under this grant may not be used for religious instruction, worship, prayer, proselytizing or other inherently religious activities. In this context, the term “direct financial assistance” means financial assistance that is provided directly by a government entity or an intermediate organization, as opposed to financial assistance that an organization receives as the result of the genuine, independent, private choice of a beneficiary. 29 CFR part 2, Subpart D governs the treatment in government programs of religious organizations and religious activities. The Grantee and sub-awardee(s) are expected to be aware of and observe the regulations of this subpart. 
                </P>
                <P>
                    E. To be eligible for enrollment as a participant under this HVRP grant an individual must be homeless 
                    <E T="03">and</E>
                     a veteran defined as follows: 
                </P>
                <P>
                    • The term “homeless or homeless 
                    <E T="03">individual</E>
                    ” includes persons who lack a fixed, regular, and adequate nighttime residence. It also includes persons whose primary nighttime residence is a supervised public or privately operated shelter designed to provide temporary living accommodations; an institution that provides a temporary residence for individuals intended to be institutionalized; or a public or private place not designed for, or ordinarily used as, a regular sleeping accommodation for human beings. [42 U.S.C. 11302(a)]. Inadequate nighttime residence examples include: sleeping in the streets, in the woods, in public parks, in cars, on outside benches, under bridges, in tents, in caves, under a lean-to, etc. Inadequate nighttime residence does 
                    <E T="03">not</E>
                     include living with relatives or friends. 
                </P>
                <P>
                    • The term “
                    <E T="03">veteran</E>
                    ” means a person who served in the active military, naval, or air service, and who was discharged or released under conditions other than dishonorable. [38 U.S.C. 101(2)]. 
                </P>
                <HD SOURCE="HD1">IV. Application and Submission Information </HD>
                <HD SOURCE="HD2">1. Address To Request an Application and Amendments </HD>
                <P>
                    This SGA, together with its attachments, includes all the information needed to apply. Additional application packages and amendments to this SGA may be obtained from the VETS Web site address at 
                    <E T="03">www.dol.gov/vets</E>
                    , the Federal Grant Opportunities Web site address at 
                    <E T="03">http://www.grants.gov</E>
                    , and from the Federal Register Web site address at 
                    <E T="03">http://www.gpoaccess.gov/fr/index.html.</E>
                     The 
                    <E T="04">Federal Register</E>
                     may also be obtained from your nearest government office or library. Additional copies of the standard forms can be downloaded from: 
                    <E T="03">http://www.whitehouse.gov/omb/grants/grants_forms.html.</E>
                </P>
                <P>
                    All mailed applications must be addressed to: Department of Labor, Procurement Services Center, Attention: 
                    <PRTPAGE P="18683"/>
                    Cassandra Mitchell, Reference SGA #07-07, 200 Constitution Avenue, NW., Room S-4307, Washington, DC 20210, Phone Number: (202) 693-4570 (this is not a toll-free number). 
                </P>
                <P>
                    • Applicants are encouraged to apply online at 
                    <E T="03">www.grants.gov.</E>
                     Applicants submitting proposals online are requested to refrain from mailing a hard copy application as well. It is strongly recommended that applicants using 
                    <E T="03">www.grants.gov</E>
                     immediately initiate and complete the “Get Started” registration steps at 
                    <E T="03">http://www.grants.gov/GetStarted.</E>
                     These steps may take multiple days to complete, and this time should be factored into plans for electronic submission in order to avoid facing unexpected delays that could result in the rejection of an application. If submitting electronically through 
                    <E T="03">www.grants.gov</E>
                     it would be appreciated if the application submitted is saved as .doc, .pdf, or .txt files. 
                </P>
                <P>• Except as provided in Section IV.3., any application received after the deadline (hard copy or electronic) will be considered as non-responsive and will not be evaluated. </P>
                <HD SOURCE="HD2">2. Content and Form of Application </HD>
                <P>
                    The application must include the name, address, telephone number, fax number, and e-mail address (if applicable) of a key contact person (program and fiscal) at the applicant's organization in case questions should arise. To be considered 
                    <E T="03">responsive</E>
                     to this solicitation the application must consist of three (3) separate and distinct sections: The Executive Summary, the Technical Proposal, and the Cost Proposal. The information provided in these three (3) sections is essential to demonstrate an understanding of the programmatic and fiscal contents of the grant proposal. 
                </P>
                <P>
                    A complete grant application package must not exceed 75 single-sided pages (8
                    <FR>1/2</FR>
                    ″ x 11″), double-spaced, 12-point font, typed pages (all attachments are included in the 75 page maximum). Any pages over the 75-page limit will not be reviewed. Major sections and sub-sections of the application should be divided and clearly identified (e.g. with tab dividers), and all pages must be numbered. To be considered responsive grant applications are to include (electronic submissions thru 
                    <E T="03">www.grants.gov</E>
                     will not require copies): 
                </P>
                <P>• An original, blue ink-signed, and two (2) copies of the cover letter. </P>
                <P>• An original and two (2) copies of the Executive Summary (see below). </P>
                <P>• An original and two (2) copies of the Technical Proposal (see below) that includes a completed Recommended Format for Common Measures Planned Technical Performance Goals Form (Appendix D). Also include all attachments with the technical proposal, such as the applicant's information showing outcomes of employment and training programs that it has had in the past three (3) years in terms of enrollments and participants who have entered into employment. If Appendix D or a similar form with all the required performance goals data is not included, the application will be considered non-responsive and will not be evaluated. </P>
                <P>• An original and two (2) copies of the Cost Proposal (see below) that includes an original, blue ink-signed, Application for Federal Assistance, SF-424 (Appendix A), a Budget Narrative, Budget Information Sheet SF-424A (Appendix B), an original, blue ink-signed, Assurances and Certifications Signature Page (Appendix C), a Direct Cost Description for Applicants and Sub-applicants (Appendix E), a completed Survey on Ensuring Equal Opportunity for Applicants (Appendix F), and the applicant's grant specific financial and/or audit statement dated within the last 18 months (audit and financial statements do not count towards the 75 page limitation). </P>
                <P>
                    A. 
                    <E T="03">Section 1—Executive Summary:</E>
                     A one to two page “Executive Summary” reflecting the grantee's and sub-awardee(s) proposed overall strategy, timeline, and outcomes to be achieved in their grant proposal is required. The Executive Summary is to include: 
                </P>
                <P>• The proposed area to be served (Urban or Non-Urban) through the activities of this grant application. </P>
                <P>• The grantee's experience in serving the residents in the proposed service area. </P>
                <P>• The proposed strategy, program design, process, method, projects, and/or statement of work with schedule or timeline that will expedite the reintegration of homeless veterans into the workforce. </P>
                <P>• Describe the measures of success for the plan. A summary of anticipated outcomes, goals, number of participants served, number hired, increase in wages, educational degrees, cost effectiveness, results-oriented model, benefits, and value added by the project. </P>
                <P>
                    B. 
                    <E T="03">Section 2—Technical Proposal</E>
                     that is not to exceed 15 single-sided pages of double-spaced 12-pitch font and one inch left, right, top, and bottom margins and does count towards the 75 page maximum. The technical proposal consists of a narrative proposal that demonstrates the need for this particular grant program, the services and activities proposed to obtain successful outcomes for the homeless veterans to be served; and the applicant's ability to accomplish the expected outcomes of the proposed project design. All applications must respond to the requirements for the program concept, required activities, and results oriented model set forth in Section I of the SGA. 
                </P>
                <P>
                    <E T="03">Required Content:</E>
                     There are program activities that all applications must contain to be found technically acceptable under this SGA. Programs must be “employment-focused” and must be responsive to the rating criteria in Section V (1). 
                    <E T="03">The required program activities are:</E>
                     Participant outreach and project awareness activities, pre-enrollment assessments, individual employment plans for each participant, case management, job placement, job retention follow-up (at 90, 180, and 270 days) after individual enters employment, utilization and coordination of employment services through the One-Stop Career Center System, including the DVOP and LVER staff, and with community linkages with other programs that provide support to homeless veterans. All applicants must respond to the requirements for the program concept, required activities and results-oriented model described in Section I. of the SGA. 
                </P>
                <P>
                    <E T="03">The following format for the technical proposal is recommended:</E>
                </P>
                <P>
                    <E T="03">Need for the program:</E>
                     The applicant must identify the geographical area to be served and provide an estimate of the number of homeless veterans in the designated geographical area. Include poverty and unemployment rates in the area and identify the disparities in the local community infrastructure that exacerbate the employment barriers faced by the targeted veterans. Include labor market information and job opportunities in the employment fields and industries that are in demand in the geographical area to be served. Applicants are to clearly describe the proposed program awareness and participant outreach strategies. 
                </P>
                <P>
                    <E T="03">Approach or strategy to increase employment and job retention:</E>
                     Applicants must be responsive to the Rating Criteria contained in Section V (1) and address all of the rating factors as thoroughly as possible in the narrative. The applicant must: 
                </P>
                <P>• Describe the specific employment and training services to be provided under this grant; the applicant's local employer network that will be used to place homeless veterans into employment; and the sequence or flow of such services; </P>
                <P>
                    • Indicate the type(s) of training that will be provided under the grant and how it relates to the jobs that are in demand, length of training, training 
                    <PRTPAGE P="18684"/>
                    curriculum, and how the training will improve the eligible veterans' employment opportunities within that geographical area; 
                </P>
                <P>• Provide a follow-up plan that addresses employment retention after 90-, 180-, and 270-days for participants who have entered employment; </P>
                <P>• Include the completed Recommended Format for Common Measures Planned Quarterly Technical Performance Goals (and planned expenditures) form listed in Appendix D. If the Common Measures Planned Quarterly Technical Performance Goals form listed in Appendix D is not submitted, the grant application package will be considered as non-responsive and not evaluated. </P>
                <P>
                    <E T="03">Linkages with facilities that serve homeless veterans:</E>
                     Describe program and resource linkages with other facilities that will be involved in identifying potential clients for this program. Applicants are encouraged to submit a list of their local area network of service providers that offer and provide services to benefit HVRP participants. Describe any networks with other related resources and/or other programs that serve homeless veterans. Indicate how the program will be coordinated with any efforts that are conducted by public and private agencies in the community. Indicate how the applicant will coordinate with any local continuum of care efforts for the homeless among agencies in the community. If a Memorandum of Understanding (MOU) or other service agreement with service providers exists, copies should be provided. 
                </P>
                <P>
                    <E T="03">Linkages with other providers of employment and training services to homeless veterans:</E>
                     Describe the linkages, networks, and relationships the proposed program will have with employers, educational providers, and other providers of services to homeless veterans; include a description of the relationship with other employment and training programs in the One-Stop Career Centers such as Disabled Veterans' Outreach Program (DVOP), the Local Veterans' Employment Representative (LVER) program, and programs under the Workforce Investment Act such as the Veterans' Workforce Investment Program (VWIP); list the type of services that will be provided by each. Note the type of agreement in place, if applicable. Linkages with the workforce investment system and educational providers are required. Describe any networks with any other resources and/or other programs for homeless veterans. If an MOU or other service agreement with other service providers exists, copies should be provided. 
                </P>
                <P>
                    <E T="03">Linkages with other Federal agencies:</E>
                     Describe program and resource linkages with the Department of Housing and Urban Development (HUD), Department of Health and Human Services (HHS), and Department of Veterans Affairs (DVA), to include the Compensated Work Therapy (CWT) and Grant and Per Diem programs. If an MOU or other service agreement with other service providers exists, copies should be provided. 
                </P>
                <P>
                    <E T="03">Proposed supportive service strategy for veterans:</E>
                     Describe how supportive service resources for veterans will be obtained and used. If resources are provided by other sources or linkages, such as Federal, State, local, or faith-based and community programs, the applicant must fully explain the use of these resources and how they will be applied. If a MOU or other service agreement with other service providers exists, copies should be provided. 
                </P>
                <P>
                    <E T="03">Organizational capability to provide required program activities:</E>
                     The applicant must describe key staff skills, experience, biographies, history, knowledge, qualifications, capabilities, office locations, and/or organizational chart. It is preferred that the grantee and sub-awardee(s) be a well established service provider and not in the initial start-up phase or process. 
                </P>
                <P>The applicant's relevant current and prior experience (within the last three year period) in operating employment and training programs is to be clearly described, if applicable. A summary narrative of program experience and employment and training performance outcomes is required. The applicant must provide information showing outcomes of employment and training programs that it has had in the past three (3) years in terms of enrollments and participants who have entered into employment. An applicant that has operated a HVRP, other homeless employment and training program, or Veterans' Workforce Investment Program must also include the final or most recent cumulative quarterly technical performance report. </P>
                <P>
                    Please note that the Department of Labor grant review panel members, who will be reviewing all grant applications submitted as a result of this SGA, do 
                    <E T="03">not</E>
                     have access to any reporting information systems during the review process, therefore, if final or most recent cumulative quarterly technical performance reports are not submitted, the grant application may be considered non-responsive. 
                </P>
                <P>
                    <E T="03">Measures of Success</E>
                    —Applicants are to describe the measures of success for the proposed plan. Applicants are to describe the proposed outcomes, goals, number served, number hired, increased wages, educational degrees, cost effectiveness, result-oriented model, feedback mechanism, performance accountability, evaluation and improvement, and/or the proposed system to monitor the implementation of program activities and achievement of stated project objectives. Applicants must indicate their planned level of performance utilizing the Common Measures reporting methodology as described in Appendix H. If the Common Measures reporting methodology is not utilized by the applicant, the application will be considered non-responsive and not evaluated. 
                </P>
                <P>
                    <E T="03">Sustainability</E>
                    —Applicants are to describe how the proposed program can or will outlast the federal funding. 
                </P>
                <P>
                    <E T="03">Proposed housing strategy for homeless veterans:</E>
                     Describe how local housing resources for eligible homeless veterans will be obtained or accessed. These resources must be from linkages or sources other than the HVRP grant such as HUD, HHS, community housing resources, DVA Grant and Per Diem Program, or other local housing programs. 
                </P>
                <P>
                    C. 
                    <E T="03">Section 3—The Cost Proposal must contain the following:</E>
                     Applicants can expect that the cost proposal will be reviewed for allocability, allowability, and reasonableness. 
                </P>
                <P>(1) Standard Form SF-424, “Application for Federal Assistance” (with the original signed in blue-ink) (Appendix A) must be completed; </P>
                <P>The Catalog of Federal Domestic Assistance number for this program is 17.805 and it must be entered on the SF-424, in Block 11. </P>
                <P>
                    The organizational unit section of Block 8 of the SF-424 must contain the Dun and Bradstreet Number (DUNS) of the applicant. Beginning October 1, 2003, all applicants for Federal grant funding opportunities are required to include a DUNS number with their application. 
                    <E T="03">See</E>
                     OMB Notice of Final Policy Issuance, 68 FR 38402 (June 27, 2003). Applicants' DUNS number is to be entered into Block 8 of SF-424. The DUNS number is a nine-digit identification number that uniquely identifies business entities. There is no charge for obtaining a DUNS number. To obtain a DUNS number call 1-866-705-5711 or access the following web site: 
                    <E T="03">http://www.dunandbradstreet.com/.</E>
                </P>
                <P>
                    Requests for exemption from the DUNS number requirement must be made to the Office of Management and Budget. If no DUNS number is provided 
                    <PRTPAGE P="18685"/>
                    then the grant application will be considered non-responsive. 
                </P>
                <P>(2) Standard Form SF-424A “Budget Information Sheet” (Appendix B) must be included; </P>
                <P>(3) As an attachment to SF-424A, the applicant must provide a detailed cost breakout of each line item on the Budget Information Sheet. Please label this page or pages the “Budget Narrative” and ensure that costs reported on the SF-424A correspond accurately with the Budget Narrative; </P>
                <P>
                    <E T="03">The Budget Narrative must include, at a minimum:</E>
                </P>
                <P>
                    • 
                    <E T="03">Personnel Costs</E>
                    —Applicants must provide a breakout of all personnel costs by position, title, annual salary rates, and percent of time of each position to be devoted to the proposed project (including sub-grantees) by completing the “Direct Cost Descriptions for Applicants and Sub-Applicants” form (Appendix E); 
                </P>
                <P>
                    • 
                    <E T="03">Fringe Benefits</E>
                    —Applicants must provide an explanation and breakout of extraordinary fringe benefit rates and associated charges (i.e., rates exceeding 35% of salaries and wages); 
                </P>
                <P>
                    • 
                    <E T="03">Explanation of Costs and Methodologies</E>
                    —Applicants must provide an explanation of the purpose and composition of, and methodology used to derive the costs of each of the following: Personnel, fringe, travel, equipment, supplies, sub-awards/contracts, and any other costs. The applicant must include costs of any required travel described in this Solicitation. Planned travel expenditures may not exceed 5% of the total HVRP funds requested. Mileage charges may not exceed 44.5 cents per mile or the current Federal rate; 
                </P>
                <P>
                    • 
                    <E T="03">Follow-Up Services</E>
                    —Applicants must describe all associated costs for obtaining and retaining participant information pertinent to the follow-up services at 90-, 180-, and 270-days after the program performance period ends. In addition, if State Unemployment Insurance data will be used to substantiate applicants follow-up results, it is suggested that the applicant include any official Memorandums of Understanding (MOUs) or other formalized agreements that enable the applicant to obtain such information. 
                </P>
                <P>
                    • 
                    <E T="03">Equipment Purchases</E>
                    —Applicants must provide a description/specification of, and justification for, equipment purchases, if any. Tangible, non-expendable, personal property having a useful life of more than one year and a unit acquisition cost of $5,000 or more per unit must be specifically identified. 
                </P>
                <P>
                    • 
                    <E T="03">Other Funds</E>
                    —Applicants are to describe other funding sources to include matching funds, leveraged funds, and in-kind services. Matching funds are not required for HVRP grants, however are encouraged. When resources such as matching funds, leveraged funds, and/or the value of in-kind contributions are made available, please describe in Section B of the Budget Information Sheet. 
                </P>
                <P>(4) A completed Assurance and Certification signature page (Appendix C) (signed in blue ink) must be submitted; </P>
                <P>(5) All applicants must submit evidence of satisfactory financial management capability, which must include recent (within the last 18 months) grant specific financial and/or audit statements (does not count towards the 75 page limitation). All successful grantees and sub-awardee(s) are required to utilize Generally Accepted Accounting Practices (GAAP), maintain a separate accounting for these grant funds, and have a checking account; </P>
                <P>(6) All applicants must include, as a separate appendix, a list of all employment and training government grants and contracts that they have had in the past three (3) years, including grant/contract officer contact information (this is included in the 75 page limitation). VETS reserves the right to have a DOL representative review and verify this data; </P>
                <P>(7) A completed Survey on Ensuring Equal Opportunity for Applicants (Appendix F) must be provided. </P>
                <HD SOURCE="HD2">3. Submission Dates and Times (Acceptable Methods of Submission) </HD>
                <P>The grant application package must be received at the designated place by the date and time specified or it will not be considered. Any application received at the Office of Procurement Services after 5 p.m. ET, May 14, 2007, will not be considered unless it is received before the award is made and: </P>
                <P>• It is determined by the Government that the late receipt was due solely to mishandling by the Government after receipt at the U.S. Department of Labor at the address indicated; or </P>
                <P>• It was sent by registered or certified mail not later than the fifth calendar day before May 14, 2007; or </P>
                <P>• It was sent by U.S. Postal Service Express Mail Next Day Service-Post Office to Addressee, not later than 5:00 p.m. at the place of mailing two (2) working days, excluding weekends and Federal holidays, prior to May 14, 2007. </P>
                <P>
                    The only acceptable evidence to establish the date of mailing of a late application sent by registered or certified mail is the U.S. Postal Service postmark on the envelope or wrapper and on the original receipt from the U.S. Postal Service. If the postmark is not legible, an application received after the above closing time and date will be processed as if mailed late. “Postmark” means a printed, stamped or otherwise placed impression (
                    <E T="03">not</E>
                     a postage meter machine impression) that is readily identifiable without further action as having been applied and affixed by an employee of the U.S. Postal Service on the date of mailing. Therefore applicants should request that the postal clerk place a legible hand cancellation “bull's-eye” postmark on both the receipt and the envelope or wrapper. Applications cannot be accepted by e-mail or facsimile machine. 
                </P>
                <P>The only acceptable evidence to establish the date of mailing of a late application sent by U.S. Postal Service Express Mail Next Day Service-Post Office to Addressee is the date entered by the Post Office clerk on the “Express Mail Next Day Service-Post Office to Addressee” label and the postmark on the envelope or wrapper and on the original receipt from the U.S. Postal Service. “Postmark” has the same meaning as defined above. Therefore, applicants should request that the postal clerk place a legible hand cancellation “bull's-eye” postmark on both the receipt and the envelope or wrapper. </P>
                <P>The only acceptable evidence to establish the time of receipt at the U.S. Department of Labor is the date/time stamp of the Procurement Services Center on the application wrapper or other documentary evidence or receipt maintained by that office. Applications sent by other delivery services, such as Federal Express, UPS, etc., will also be accepted. </P>
                <P>All applicants are advised that U.S. mail delivery in the Washington, DC area has been erratic due to security concerns. All applicants must take this into consideration when preparing to meet the application deadline, as you assume the risk for ensuring a timely submission, that is, if, because of these mail problems, the Department does not receive an application or receives it too late to give proper consideration, even if it was timely mailed, the Department is not required to consider the application. </P>
                <HD SOURCE="HD2">4. Intergovernmental Review </HD>
                <P>Not Applicable. </P>
                <HD SOURCE="HD2">5. Funding Restrictions </HD>
                <P>A. Proposals exceeding $200,000 that serve Non-Urban areas and $300,000 that serve Urban areas will be considered non-responsive and will not be evaluated. </P>
                <P>
                    B. There is a limit of one (1) application per submitting organization 
                    <PRTPAGE P="18686"/>
                    and physical location serving the same HVRP participant population. If two (2) original applications from the same organization for the same physical location serving the same HVRP participant population are submitted, the application with the later date will be considered as non-responsive. Please do not submit duplicate original grant applications as only one (1) grant application will be considered for funding purposes.
                </P>
                <P>C. Due to the limited availability of funding, if an organization was awarded Fiscal Year 2005 or Fiscal Year 2006 HVRP funds for a specific physical location serving the same HVRP participant population and will be applying for second and possible third year funding in PY 2007, then that organization at that specific physical location serving the same HVRP participant population will be considered ineligible to compete for a new grant using PY 2007 HVRP funds. Therefore, due to the limited funding availability, we are unable to award more than one (1) HVRP grant per organization at a specific physical location serving the same HVRP participant population. A separate Director's Memorandum will be issued for grantees that are eligible to apply for second and third optional year funding that includes detailed instructions on how to apply for these funds. </P>
                <P>D. There will not be reimbursement of pre-award costs unless specifically agreed upon in writing by the Department of Labor. </P>
                <P>E. Entities described in Section 501(c)(4) of the Internal Revenue Code that engage in lobbying activities are not eligible to receive funds under this announcement because Section 18 of the Lobbying Disclosure Act of 1995, Public Law No. 104-65, 109 Stat. 691, prohibits the award of Federal funds to these entities. </P>
                <P>
                    <E T="03">F. Limitations on Administrative and Indirect Costs.</E>
                </P>
                <P>Administrative costs, which consist of all direct and indirect costs associated with the supervision and management of the program, are limited to and may not exceed 20% of the total grant award. </P>
                <P>Indirect costs claimed by the applicant must be based on a federally approved rate. A copy of the current negotiated approved and signed indirect cost negotiation agreement must be submitted with the application. Furthermore, indirect costs are considered a part of administrative costs for HVRP purposes and, therefore, may not exceed 20% of the total grant award. </P>
                <P>
                    • If the applicant does not presently have an approved indirect cost rate, a proposed rate with justification may be submitted. Successful applicants will be required to negotiate an acceptable and allowable rate within 90 days of grant award with the appropriate DOL Regional Office of Cost Determination or with the applicant's cognizant agency for indirect cost rates (
                    <E T="03">See</E>
                     Office of Management and Budget Web site at: 
                    <E T="03">http://www.whitehouse.gov/omb/grants/attach.html.</E>
                </P>
                <P>• Indirect cost rates traceable and trackable through the State Workforce Agency's Cost Accounting System represent an acceptable means of allocating costs to DOL and, therefore, can be approved for use in grants to State Workforce Agencies. </P>
                <HD SOURCE="HD1">V. Application Review Information:</HD>
                <HD SOURCE="HD2">1. Application Evaluation Criteria </HD>
                <P>Applications may receive up to 110 total points based on the following criteria: </P>
                <HD SOURCE="HD3">A. Need for the Project: 10 Points </HD>
                <P>The applicant will document the need for this project, as demonstrated by: </P>
                <P>(1) The potential number or concentration of homeless individuals and homeless veterans in the proposed project area relative to other similar areas; (2) the rates of poverty and unemployment in the proposed project area as determined by the census or other surveys; and (3) the extent of the gaps in the local infrastructure to effectively address the employment barriers that characterize the target population. </P>
                <HD SOURCE="HD3">B. Overall Strategy To Increase Employment and Retention in Employment: 35 Points [and up to 10 additional points (for a total of 45 points) if overall strategy includes an approach for addressing barriers to employment faced by chronically homeless veterans as described below.] </HD>
                <P>The application must include a description of the approach to providing comprehensive employment and training services, including outreach, pre-enrollment assessment, job training, job development, obtaining employer commitments to hire, placement, and post-placement follow-up services. Applicants must address how they will target occupations that are locally in demand with career growth potential and that will provide wages to ensure self-sufficiency for the participant. Supportive services provided as part of the strategy of promoting job readiness and job retention must be indicated. The applicant must identify the local services and sources of training to be used for participants. At least 80% of participants must participate in training activities. A description of the relationship with other employment and training programs delivered through the One-Stop Career Center System must be specified. Applicants must indicate how the activities will be tailored or responsive to the needs of homeless veterans. A participant flow chart may be used to show the sequence and mix of services (does not count towards the 75 page limitation). In addition, if State Unemployment Insurance data will be used to substantiate the applicant's follow-up results, it is suggested that the applicant include any official MOUs or other formalized agreement that enables the applicant to obtain such information (does not count towards the 75 page limitation).</P>
                <P>
                    <E T="03">Additional Points (referenced in the Heading to Section B):</E>
                     Up to an additional 10 points under this section will be awarded to grant proposals that focus some of their effort on addressing the barriers to employment faced by chronically homeless veterans. A veteran who is “chronically homeless” is an unaccompanied homeless individual with a “disabling condition” who has either been continuously homeless for a year or more, OR who has had at least four (4) episodes of homelessness in the past three (3) years. A disabling condition is defined as a diagnosable substance use disorder, serious mental illness, developmental disability, or chronic physical illness or disability including the co-occurrence of two or more of these conditions. A “disabling condition” limits an individual's ability to work or perform one or more activities of daily living. 
                </P>
                <NOTE>
                    <HD SOURCE="HED">Note:</HD>
                    <P>The applicant must complete the Recommended Format for Common Measures Planned Quarterly Technical Performance Goals (Appendix D), with proposed programmatic outcomes, including participants served, placement/entered employments and job retention or a similar document containing the same information and if not, the grant application will be considered non-responsive and will not be evaluated. </P>
                </NOTE>
                <HD SOURCE="HD3">C. Quality and Extent of Linkages With Other Providers of Services to the Homeless and to Veterans: 20 Points </HD>
                <P>
                    The application must provide information on the quality and extent of the linkages this program will have with employers, educational providers, and other providers of services to homeless veterans in the local community including faith-based and community organizations. For each service, the applicant must specify who the provider is, the source of funding (if known), and the type of linkages/referral system established or proposed. Describe, to the 
                    <PRTPAGE P="18687"/>
                    extent possible, how the project would be incorporated into the local community's continuum of care approach and the local community's ten (10) year plan to end homelessness, if applicable (see Interagency Council on Homelessness Web page at 
                    <E T="03">www.ich.gov</E>
                     for additional information). Describe how the proposed project links to the appropriate State Workforce Agency and One-Stop Career Center(s) including coordination and collaboration with DVOP/LVER and other One-Stop Career Center staff, HUD, HHS, DVA, educational institutions, and other local community-based programs and the services that will be provided as necessary on behalf of the homeless veteran participants to be served. 
                </P>
                <HD SOURCE="HD3">D. Demonstrated Capability in Providing Required Program Services, Including Programmatic Reporting and Participant Tracking: 25 Points </HD>
                <P>The applicant must describe its relevant prior experience in operating employment and training programs and providing services to participants similar to those that are proposed under this solicitation. Specific outcomes previously achieved by the applicant must be described, such as number of enrollments, number of participants that entered employment, cost per placement into employment, benefits secured, network coalitions, etc. The applicant must also address its capacity for timely startup of the program, programmatic reporting, and participant tracking. The applicant should describe its staff experience and ability to manage the administrative, programmatic, and financial aspects of a grant program. Include a recent (within the last 18 months) grant specific financial statement and/or audit (does not count towards the 75 page limitation). Final or most recent financial and technical performance reports for other relevant programs must be submitted, if applicable. Because prior HVRP experience is not a requirement for this grant, applicants may have other similar type programmatic performance reports to submit as evidence of experience in operating other employment and training type programs. </P>
                <HD SOURCE="HD3">E. Quality of Overall Housing Strategy: 10 Points </HD>
                <P>
                    The application must demonstrate how the applicant proposes to obtain or access resources for participants in the program and participants entering into the labor force. This discussion should specify the provisions made to access temporary, transitional, and permanent housing for participants through various community resources such as HUD, DVA Grant and Per Diem Program, and other locally funded housing programs. HVRP funds may 
                    <E T="03">not</E>
                     be used for emergency, transitional, or permanent housing purposes or purchasing or leasing of vehicles. 
                </P>
                <HD SOURCE="HD2">2. Review and Selection Process </HD>
                <P>Grant applications will be reviewed by a Department of Labor grant review panel using the point scoring system specified above in Section V(1). Urban and Non-Urban applications will be evaluated against the same criteria. The grant review panel will assign a score after objectively and carefully evaluating each responsive grant application and all responsive grant applications will be ranked based on this score. The ranking will be the primary basis to identify applicants as potential grantees. The grant review panel will establish a competitive range, based upon the proposal evaluation, for the purpose of selecting qualified applicants. For this solicitation, the minimum acceptable score for consideration is 70, but the competitive range may be set higher. </P>
                <P>The grant review panel will have the authority and expertise to compare the goals of applications in the competitive range, to consider any information that comes to their attention, to form an opinion on what is most advantageous to the government and to judge allowed costs, cost-per-placement, and other goals. The Assistant Secretary for Veterans' Employment and Training and Grant Officer will make a final selection based on the grant review panel findings, grant application scores, geographical presence of the applicants, existing grants, and the areas to be served. We reserve the right to select a lower scoring application from one category (urban or non-urban) over a higher rated application from the other category if the Grant Officer or Assistant Secretary determines it is necessary to achieve an appropriate mix of urban and non-urban projects. The grant review panel's conclusions are advisory in nature and not binding on the Grant Officer. </P>
                <P>The grant review panel and Grant Officer will screen all applicant cost proposals to ensure expenses are allocable, allowable, and reasonable. Determinations of allowable costs will be made in accordance with the applicable Federal cost principles, e.g. Non-Profit Organizations—OMB Circular A-122. Unallowable costs are those charges to a grant that a grantor agency or its representatives determined not to be allowed in accordance with the applicable Federal Cost Principles or other conditions contained in the grant. If the grant review panel and Grant Officer conclude that the cost proposal contains an expense(s) that is not allocable, allowable, and/or reasonable, the Grant Officer may request a revision of the application for funding. Further, the grant review panel will consider applicant information concerning the proposed cost per placement, percentage of participants who enter unsubsidized employment, average wage at placement, and 90-, 180-, and 270-day retention in employment percentages. The national average cost per placement for HVRP for last year was $2,200. </P>
                <P>The Government reserves the right to ask the applicant for clarification on any aspect of a grant application. The Grant Officer may consult with the Department of Labor staff on any potential grantee and/or sub-awardee(s) concerns. The Grant Officer's determination for award under SGA #07-07 is the final agency action. The submission of the same proposal from any prior year HVRP competition does not guarantee an award under this Solicitation. </P>
                <HD SOURCE="HD2">3. Anticipated Announcement and Award Dates </HD>
                <P>Announcement of this award is expected to occur by June 20, 2007. The grant agreement will be awarded by no later than July 1, 2007. </P>
                <HD SOURCE="HD1">VI. Award Administration Information </HD>
                <HD SOURCE="HD2">1. Award Notices </HD>
                <P>A. The Notice of Award signed by the Grant Officer is the authorizing document and will be provided through postal mail and/or by electronic means to the authorized representative listed on the SF-424 Grant Application. Notice that an organization has been selected as a grant recipient does not constitute final approval of the grant application as submitted. Before the actual grant award, the Grant Officer and/or the Grant Officer's Technical Representative may enter into negotiations concerning such items as program components, funding levels, and administrative systems. If the negotiations do not result in an acceptable submittal, the Grant Officer reserves the right to terminate the negotiation and decline to fund the proposal. Please note: Grant award occurs only after the prospective grantee and the Grant Officer signs the Grant award document. </P>
                <P>
                    B. A post-award conference will be held for those grantees awarded PY 2007 HVRP funds through this competition. The post-award conference 
                    <PRTPAGE P="18688"/>
                    is expected to be held in August 2007 and up to two (2) grant recipient representatives must be present. The site of the post-award conference has not yet been determined, however, for planning and budgeting purposes, applicants should allot four (4) days and use Denver, CO as the conference site. The post-award conference will focus on providing information and assistance on reporting, recordkeeping, grant requirements, and also include networking opportunities to learn of best practices from more experienced and successful grantees and sub-awardee(s). Costs associated with attending this conference for up to two (2) grantee representatives will be allowed as long as they are incurred in accordance with Federal travel regulations. Such costs must be charged as administrative costs and reflected in the proposed budget. 
                </P>
                <HD SOURCE="HD2">2. Administrative and National Policy Requirements </HD>
                <P>All grantees and sub-awardees must comply with the provisions of Title 38 U.S.C. and its regulations, as applicable. </P>
                <HD SOURCE="HD3">A. Administrative Program Requirements </HD>
                <P>All grantees and sub-awardees, including faith-based and community organizations, will be subject to applicable Federal laws (including provisions of appropriations law), regulations, and the applicable Office of Management and Budget (OMB) Circulars. The grant(s) awarded under this SGA will be subject to the following administrative standards and provisions, if applicable: </P>
                <P>• 29 CFR part 2—General Participation in Department of Labor Programs by Faith-Based and Community Organizations; Equal Treatment of All Department of Labor Program Participants and Beneficiaries. </P>
                <P>• 29 CFR part 30—Equal Employment Opportunity in Apprenticeship and Training. </P>
                <P>• 29 CFR part 31—Nondiscrimination in Federally Assisted Programs of the Department of Labor—Effectuation of Title VI of the Civil Rights Act of 1964. </P>
                <P>• 29 CFR part 32—Nondiscrimination on the Basis of Handicap in Programs or Activities Receiving Federal Financial Assistance. </P>
                <P>• 29 CFR part 33—Enforcement of Nondiscrimination on the Basis of Handicap in Programs or Activities Conducted by the Department of Labor. </P>
                <P>• 29 CFR part 35—Nondiscrimination on the Basis of Age in Programs and Activities Receiving Federal Financial Assistance from the Department of Labor. </P>
                <P>• 29 CFR part 36—Nondiscrimination on the Basis of Sex in Education Programs or Activities Receiving Federal Assistance. </P>
                <P>• 29 CFR part 37—Implementation of the Nondiscrimination and Equal Opportunity Provisions of the Workforce Investment Act of 1998. </P>
                <P>• 29 CFR part 93—New Restrictions on Lobbying. </P>
                <P>• 29 CFR part 94—Government-wide Requirements for Drug-Free Workplace (Financial Assistance). </P>
                <P>• 29 CFR part 95—Grants and Agreements with Institutions of Higher Education, Hospitals, and other Non-Profit Organizations, and with Commercial Organizations. </P>
                <P>• 29 CFR part 96—Audit Requirements for Grants, Contracts and Other Agreements. </P>
                <P>• 29 CFR part 97—Uniform Administrative Requirements for Grants and Cooperative Agreements to State and Local Governments. </P>
                <P>• 29 CFR part 98—Government-wide Debarment and Suspension (Non procurement). </P>
                <P>• 29 CFR part 99—Audit of States, Local Governments, and Non-Profit Organizations. </P>
                <P>• Applicable cost principles and audit requirements under OMB Circulars A-21, A-87, A-110, A-122, A-133, and 48 CFR part 31. </P>
                <P>• In accordance with Section 18 of the Lobbying Disclosure Act of 1995, Public Law 104-65 (2 U.S.C. 1611), non-profit entities incorporated under 501(c)(4) that engage in lobbying activities are not eligible to received Federal funds and grants. </P>
                <P>• 38 U.S.C. Section 4215—Requirements for priority of service for veterans in all Department of Labor training programs. </P>
                <HD SOURCE="HD2">3. Electronic Reporting </HD>
                <P>All HVRP grantees will enter data and electronically attach their quarterly technical performance, success stories, etc. into the U.S. Department of Labor, Veterans' Employment and Training Service, Outcomes and Performance Accountability Reporting (VOPAR) System and SF-269 Financial Status Report data into the DOL E-Grants System according to the reporting requirements and timetables described below. Note: VETS has requested that the two separate reporting systems for grantee programmatic and financial performance (VOPAR and E-Grants) be linked for seamless grantee reporting and it is expected to be completed during PY 2007. </P>
                <HD SOURCE="HD3">A. Quarterly Financial Reports </HD>
                <P>No later than 30 days after the end of each Federal fiscal quarter, the grantee must report outlays, program income, and other financial information on a Federal fiscal quarterly basis using SF-269, Financial Status Report and submit a copy of the HHS/PMS 272 draw down report. These financial reports must be data entered into the E-Grants system and must cite the assigned grant number. </P>
                <HD SOURCE="HD3">B. Quarterly Program Reports </HD>
                <P>No later than 30 days after the end of each Federal fiscal quarter, grantees must submit a Quarterly Technical Narrative Performance Report into VOPAR that contains the following: </P>
                <P>(1) A comparison of actual accomplishments to planned goals for the reporting period and any findings related to monitoring efforts; </P>
                <P>(2) An explanation for variances of plus or minus 15% of planned program and/or expenditure goals, to include: Identification of corrective action that will be taken to meet the planned goals, if required; and a timetable for accomplishment of the corrective action. </P>
                <HD SOURCE="HD3">C. 90-Day Final Performance Report </HD>
                <P>No later than 120 days after the grant performance expiration date, the grantee must electronically submit to the VOPAR and E-Grants Reporting Systems a final report showing results and performance as of the 90th day after the grant period, and containing the following: </P>
                <P>(1) Final Financial Status Report SF-269 (that zeros out all unliquidated obligations); and </P>
                <P>(2) Final Technical Performance Report comparing goals vs. actual performance levels. </P>
                <HD SOURCE="HD3">D. 180-Day Follow-Up Report </HD>
                <P>No later than 210 days after the grant performance expiration date, the grantee must electronically submit to the VOPAR and E-Grants Reporting Systems a Follow-Up Report showing results and performance as of the 180th day after the grant expiration date, and containing the following: </P>
                <P>(1) Final Financial Status Report SF-269 Long Form (if not previously submitted); and </P>
                <P>(2) 180-Day Follow-Up Report identifying: </P>
                <P>(a) The total number of veterans who entered employment during the entire grant period; </P>
                <P>(b) The number of veterans who retained employment as defined under Common Measures at the 90 and 180 day follow-up periods; </P>
                <P>
                    (c) If the veterans are still employed at the same or similar job, and if not, what are the reason(s); 
                    <PRTPAGE P="18689"/>
                </P>
                <P>(d) Whether training received was applicable to jobs held; </P>
                <P>(e) Participant average hourly and weekly wages at the 90- and 180-day follow-up periods; </P>
                <P>(f) An explanation of why those veterans entered employment during the grant, but not employed at the end of the follow-up period, are not so employed; and </P>
                <P>(g) Any recommendations to improve the program. </P>
                <HD SOURCE="HD3">E. 270-Day Follow-Up Performance Report </HD>
                <P>No later than 300 days after the grant performance expiration date, the grantee must electronically submit to the VOPAR and E-Grants Reporting Systems a Follow-up Report showing results and performance as of the 270th day after the grant period, and containing the following: </P>
                <P>(a) The total number of veterans who entered employment during the entire grant period; </P>
                <P>(b) The number of veterans who retained employment as defined under Common Measures at the 90-, 180- and 270-day follow-up periods; </P>
                <P>(c) If the veterans are still employed at the same or similar job, and if not, what are the reason(s); </P>
                <P>(d) Whether training received was applicable to jobs held; </P>
                <P>(e) Participant average hourly and weekly wages at the 90-, 180-, and 270-day follow-up periods; </P>
                <P>(f) An explanation of why those veterans entered employment during the grant, but not employed at the end of the follow-up period, are not so employed; and </P>
                <P>(g) Any recommendations to improve the program. </P>
                <P>
                    <E T="03">Agency Contact:</E>
                     All questions regarding this SGA should be directed to Cassandra Mitchell, e-mail address: 
                    <E T="03">mitchell.cassandra@dol.gov,</E>
                     at tel: (202) 693-4570 (note this is not a toll-free number). To obtain further information on the Homeless Veterans' Reintegration Program of the U.S. Department of Labor, visit the USDOL website of the Veterans' Employment and Training Service at 
                    <E T="03">www.dol.gov/vets.</E>
                     Individuals with hearing impairments may call (800) 670-7008 (TTY/TDD). 
                </P>
                <HD SOURCE="HD1">VII. Other Information </HD>
                <HD SOURCE="HD2">A. Acknowledgement of USDOL Funding </HD>
                <P>
                    1. 
                    <E T="03">Printed Materials:</E>
                     In all circumstances, the following must be displayed on printed materials prepared by the grantee while in receipt of DOL grant funding: “Preparation of this item was funded by the United States Department of Labor under Grant No. [insert the appropriate grant number].” 
                </P>
                <P>• All printed materials must also include the following notice: “This document does not necessarily reflect the views or policies of the U.S. Department of Labor, nor does mention of trade names, commercial products, or organizations imply endorsement by the U.S. Government.” </P>
                <P>2. Public references to grant: When issuing statements, press releases, requests for proposals, bid solicitations, and other documents describing projects or programs funded in whole or in part with Federal money, all grantees receiving Federal funds must clearly state: </P>
                <P>• The percentage of the total costs of the program or project, which will be financed with Federal money; </P>
                <P>• The dollar amount of Federal financial assistance for the project or program; and </P>
                <P>• The percentage and dollar amount of the total costs of the project or program that will be financed by non-governmental sources. </P>
                <HD SOURCE="HD2">B. Use of USDOL Logo </HD>
                <P>Prior to the use of the USDOL Logo, the Grant Officer must approve such use. </P>
                <P>In addition, once approval is given the following guidance is provided: </P>
                <P>• The USDOL logo may be applied to USDOL-funded material prepared for distribution, including posters, videos, pamphlets, research documents, national survey results, impact evaluations, best practice reports, and other publications of global interest. The grantee(s) must consult with USDOL on whether the logo may be used on any such items prior to final draft or final preparation for distribution. In no event will the USDOL logo be placed on any item until USDOL has given the Grantee permission to use the logo on the item. </P>
                <P>• All documents must include the following notice: “This documentation does not necessarily reflect the views or policies of the U.S. Department of Labor, nor does mention of trade names, commercial products, or organizations imply endorsement by the U.S. Government.” </P>
                <P>C. OMB Information Collection No 1205-0458, Expires September 30, 2009. According to the Paperwork Reduction Act of 1995, no persons are required to respond to a collection of information unless such collection displays a valid OMB control number. Public reporting burden for this collection of information is estimated to average 20 hours per response, including time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding the burden estimated or any other aspect of this collection of information, including suggestions for reducing this burden, to the U.S. Department of Labor, to the attention of Cassandra Mitchell, 200 Constitution Avenue, NW., Room S-4307, Washington, DC 20210. </P>
                <P>This information is being collected for the purpose of awarding a grant. The information collected through this “Solicitation for Grant Applications” will be used by the Department of Labor to ensure that grants are awarded to the applicant best suited to perform the functions of the grant. Submission of this information is required in order for the applicant to be considered for award of this grant. Unless otherwise specifically noted in this announcement, information submitted in the respondent's application is not considered to be confidential. </P>
                <P>
                    <E T="03">Resources for the Applicant:</E>
                     The Department of Labor maintains a number of web-based resources that may be of assistance to applicants. The webpage for the USDOL VETS at 
                    <E T="03">www.dol.gov/vets/programs/main.htm</E>
                     is a valuable source of information including the program highlights and brochures, glossary of terms, frequently used acronyms, general and special grant provisions, power point presentations on how to apply for HVRP funding, On-Site Monitoring Visits, etc. The Interagency Council on Homeless at webpage 
                    <E T="03">www.ich.gov</E>
                     has information from various departments that assist homeless persons including updated information on local community ten (10) year plans to end homelessness and continuum of care plans. America's Service Locator webpage at 
                    <E T="03">www.servicelocator.org</E>
                     provides a directory of our nation's One-Stop Career Centers and 
                    <E T="03">www.workforce3one.org</E>
                     is another Department of Labor resource site. The National Association of Workforce Boards maintains a webpage at 
                    <E T="03">www.nawb.org/asp/wibdir.asp</E>
                     that contains contact information for the State and local Workforce Investment Boards. Applicants may also review “VETS' Guide to Competitive and Discretionary Grants” located at webpage 
                    <E T="03">http://www.dol.gov/vets/grants/Final_VETS_Guide-linked.pdf.</E>
                     For a basic understanding of the grants process and basic responsibilities of receiving Federal grant support, please see “Guidance for Faith-Based and Community Organizations on Partnering with the Federal Government” at webpages 
                    <E T="03">www.whitehouse.gov/government/fbci</E>
                     and 
                    <E T="03">www.dol.gov/cfbci,</E>
                      
                    <PRTPAGE P="18690"/>
                    Also, the National Coalition for Homeless Veterans webpage at 
                    <E T="03">www.nchv.org.</E>
                </P>
                <P>
                    <E T="03">Appendices:</E>
                     (Located on U.S. Department of Labor, Veterans' Employment and Training Service webpage 
                    <E T="03">www.dol.gov/vets</E>
                     follow link for the applicable SGA listed under announcements.) 
                </P>
                <FP SOURCE="FP-2">Appendix A: Application for Federal Assistance SF-424 </FP>
                <FP SOURCE="FP-2">Appendix B: Budget Information Sheet SF-424A </FP>
                <FP SOURCE="FP-2">Appendix C: Assurances and Certifications Signature Page </FP>
                <FP SOURCE="FP-2">Appendix D: Recommended Format for Planned Common Measures Quarterly Technical Performance Goals </FP>
                <FP SOURCE="FP-2">Appendix E: Direct Cost Descriptions for Applicants and Sub-Applicants </FP>
                <FP SOURCE="FP-2">Appendix F: Survey on Ensuring Equal Opportunity for Applicants </FP>
                <FP SOURCE="FP-2">Appendix G: List of 75 Largest Cities Nationwide </FP>
                <FP SOURCE="FP-2">Appendix H: Common Measures Technical Assistance Guide (TAG) for Competitive Grantees </FP>
                <SIG>
                    <NAME>Lisa Harvey, </NAME>
                    <TITLE>Grant Officer. </TITLE>
                </SIG>
            </PREAMB>
            <FRDOC> [FR Doc. E7-7024 Filed 4-12-07; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4510-79-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">LEGAL SERVICES CORPORATION </AGENCY>
                <SUBJECT>Notice of Availability of Calendar Year 2008 Competitive Grant Funds </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Legal Services Corporation. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Solicitation for proposals for the provision of civil legal services. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Legal Services Corporation (LSC) is the national organization charged with administering Federal funds provided for civil legal services to low-income people. </P>
                    <P>LSC hereby announces the availability of competitive grant funds and is soliciting grant proposals from interested parties who are qualified to provide effective, efficient, and high quality civil legal services to eligible clients in the service area(s) of the states and territories identified below. The exact amount of congressionally appropriated funds and the date, terms, and conditions of their availability for calendar year 2008 have not been determined. </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        See 
                        <E T="02">Supplementary Information</E>
                         section for grants competition dates. 
                    </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Legal Services Corporation—Competitive Grants, 3333 K Street, NW., Third Floor, Washington, DC 20007-3522. </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Office of Program Performance by e-mail at 
                        <E T="03">competition@lsc.gov,</E>
                         or visit the grants competition Web site at 
                        <E T="03">www.ain.lsc.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The Request for Proposals (RFP) will be available the week of April 16, 2007. Applicants must file a Notice of Intent to Compete (NIC; RFP Form-H) to participate in the competitive grants process. </P>
                <P>Applicants competing for the service areas listed below, except for VA-20, must file the NIC by May 21, 2007, 5 p.m. E.D.T. The due date for filing grant proposals for these service areas is June 14, 2007, 5 p.m. E.D.T. </P>
                <P>Applicants competing for service area VA-20 in Virginia must file the NIC by July 2, 2007, 5 p.m. E.D.T. The due date for filing grant proposals for service area VA-20 in Virginia is September 3, 2007, 5 p.m. E.D.T. </P>
                <P>LSC is seeking proposals from: (1) Non-profit organizations that have as a purpose the provision of legal assistance to eligible clients; (2) private attorneys; (3) groups of private attorneys or law firms; (4) state or local governments; and (5) sub-state regional planning and coordination agencies that are composed of sub-state areas and whose governing boards are controlled by locally elected officials. </P>
                <P>
                    The RFP, containing the NIC (Form-H) and grant application, guidelines, proposal content requirements, service area descriptions, and specific selection criteria, will be available from 
                    <E T="03">www.ain.lsc.gov</E>
                     the week of April 16, 2007. LSC will not fax the RFP to interested parties. 
                </P>
                <P>
                    Below are the service areas for which LSC is requesting grant proposals. Service area descriptions will be available from Appendix A of the RFP. Interested parties are asked to visit 
                    <E T="03">www.ain.lsc.gov</E>
                     regularly for updates on the LSC competitive grants process. 
                </P>
                <GPOTABLE COLS="2" OPTS="L2,tp0,i1" CDEF="s50,r50">
                    <TTITLE>  </TTITLE>
                    <BOXHD>
                        <CHED H="1">State </CHED>
                        <CHED H="1">Service area </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Alabama </ENT>
                        <ENT>AL-4. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">American Samoa </ENT>
                        <ENT>AS-1. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Arizona </ENT>
                        <ENT>AZ-2, AZ-3, AZ-5, MAZ, NAZ-5, NAZ-6. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Arkansas </ENT>
                        <ENT>AR-6, AR-7. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">California </ENT>
                        <ENT>CA-1, CA-27, CA-28, CA-31, MCA, NCA-1. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">District of Columbia </ENT>
                        <ENT>DC-1. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Florida </ENT>
                        <ENT>FL-18. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Hawaii </ENT>
                        <ENT>MHI. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Illinois </ENT>
                        <ENT>IL-3, IL-7. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Kentucky </ENT>
                        <ENT>KY-2, KY-5, KY-9, KY-10. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Louisiana </ENT>
                        <ENT>LA-1, LA-12. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Massachusetts </ENT>
                        <ENT>MA-4, MA-10, MA-11. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Michigan </ENT>
                        <ENT>MI-9, MI-12, MI-13, MI-14, MI-15, MMI, NMI-1. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Minnesota </ENT>
                        <ENT>MN-1, MN-4, MN-5, MN-6, MMN, NMN-1. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Missouri </ENT>
                        <ENT>MO-3, MO-4, MO-5, MO-7, MMO. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">New Mexico </ENT>
                        <ENT>NM-1, NM-5, MNM, NNM-2, NNM-4. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">New York </ENT>
                        <ENT>NY-9. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">North Dakota </ENT>
                        <ENT>ND-3, MND, NND-3. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Ohio </ENT>
                        <ENT>OH-5, OH-17, OH-18, OH-20, OH-21, OH-23, MOH. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Oklahoma </ENT>
                        <ENT>NOK-1. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Pennsylvania </ENT>
                        <ENT>PA-1, PA-24, MPA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Puerto Rico </ENT>
                        <ENT>PR-1, PR-2, MPR. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">South Carolina </ENT>
                        <ENT>MSC. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">South Dakota </ENT>
                        <ENT>SD-2, SD-4, MSD, NSD-1. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Tennessee </ENT>
                        <ENT>TN-4, TN-7, TN-9, TN-10. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Texas </ENT>
                        <ENT>TX-13, TX-14, TX-15, NTX-1. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Virginia </ENT>
                        <ENT>VA-17, VA-18, VA-19, VA-20, MVA. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">West Virginia </ENT>
                        <ENT>WV-5, MWV. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Wisconsin </ENT>
                        <ENT>WI-5, MWI. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Wyoming </ENT>
                        <ENT>WY-4, MWY, NWY-1. </ENT>
                    </ROW>
                </GPOTABLE>
                <SIG>
                    <DATED>Dated: April 9, 2007. </DATED>
                    <NAME>Michael A. Genz, </NAME>
                    <TITLE>Director, Office of Program Performance, Legal Services Corporation.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC> [FR Doc. E7-7012 Filed 4-12-07; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 7050-01-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">NATIONAL SCIENCE FOUNDATION </AGENCY>
                <SUBJECT>Advisory Committee of International Science and Engineering; Notice of Meeting </SUBJECT>
                <P>In accordance with Federal Advisory Committee Act (Pub. L. 92-463, as amended), the National Science Foundation announces the following meeting: </P>
                <P>
                    <E T="03">Name:</E>
                     Advisory Committee for International Science and Engineering (#25104). 
                </P>
                <P>
                    <E T="03">Date/Time:</E>
                     May 4, 2007; 3 p.m. to 5 p.m. 
                </P>
                <P>
                    <E T="03">Place:</E>
                     National Science Foundation, 4201 Wilson Boulevard, Room 950, Arlington, Virginia. 
                </P>
                <P>
                    <E T="03">Type of Meeting:</E>
                     Open (Teleconference). 
                </P>
                <P>
                    <E T="03">Contact Person:</E>
                     Eduardo Feller, National Science Foundation, 4201 Wilson Boulevard, Arlington, VA 22230, (703) 292-8710. 
                </P>
                <P>
                    If you are attending the meeting and need access to the NSF, please contact the individual listed above so your name may be added to the building access list. 
                    <PRTPAGE P="18691"/>
                </P>
                <P>
                    <E T="03">Purpose of Meeting:</E>
                     To provide advice concerning the NSF programs in international science and engineering. 
                </P>
                <P>
                    <E T="03">Agenda:</E>
                     Discussion of current programs, initiatives and future budget cycle. 
                </P>
                <SIG>
                    <DATED>Dated: April 10, 2007. </DATED>
                    <NAME>Susanne Bolton, </NAME>
                    <TITLE>Committee Management Officer. </TITLE>
                </SIG>
            </PREAMB>
            <FRDOC> [FR Doc. E7-7011 Filed 4-12-07; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 7555-01-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">NUCLEAR REGULATORY COMMISSION </AGENCY>
                <DEPDOC>[Docket No. 50-133] </DEPDOC>
                <SUBJECT>Environmental Assessment and Finding of No Significant Impact Related to Issuance of License Amendment for the Humboldt Bay Power Plant Unit 3 License DPR-007, Humboldt, CA</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>U.S. Nuclear Regulatory Commission. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Environmental assessment and finding of no significant impact. </P>
                </ACT>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        John Hickman, Division of Waste Management and Environmental Protection, Office of Federal and State Materials and Environmental Management Programs, U.S. Nuclear Regulatory Commission, Mail Stop: T7E18, Washington, DC 20555-00001. Telephone: (301) 415-3017; e-mail: 
                        <E T="03">jbh@nrc.gov</E>
                        . 
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Introduction </HD>
                <P>The U.S. Nuclear Regulatory Commission (NRC) is considering a request, dated December 20, 2006, by the Pacific Gas and Electric Company (PGE or the Licensee), to approve an amendment to Facility Operating License No. DPR-7 that would revise License Condition 2.B.3 to allow the receipt, possession, and use of byproduct, source, or special nuclear material without restriction to amount or atomic number, for sample analysis or instrument calibration or associated with radioactive apparatus or components. </P>
                <HD SOURCE="HD1">II. Environmental Assessment </HD>
                <HD SOURCE="HD2">Background </HD>
                <P>Humboldt Bay Power Plant (HBPP) was permanently shut down in July 1976, and until recently was in safe storage condition (SAFSTOR). SAFSTOR is the decommissioning method in which a nuclear facility is placed and maintained in a condition that allows the safe storage of radioactive components of the nuclear plant and subsequent decontamination to levels that permit license termination. A Decommissioning Plan (DP) was approved in July 1988. Subsequent to the 1996 License Termination rule, the licensee converted its DP into its Defueled Safety Analysis Report which is updated every two years. A Post Shutdown Decommissioning Activities Report was issued by the licensee in February 1998. The licensee is now engaged in some incremental decommissioning activities. In December 2003, PG&amp;E formally submitted a license application to the U.S. Nuclear Regulatory Commission (NRC) for approval of a dry-cask Independent Spent Fuel Storage Installation (ISFSI) at the Humboldt Bay site. A license and safety evaluation report for the Humboldt Bay ISFSI were issued on November 17, 2005. PG&amp;E plans to begin active decommissioning of the facility in 2007. </P>
                <P>This Environmental Assessment (EA) has been developed in accordance with the requirements of 10 CFR Part 51.21. </P>
                <HD SOURCE="HD2">Proposed Action </HD>
                <P>The change proposed by this amendment will replace the current license condition 2.B.3© which addresses the receipt, possession, and use of byproduct materials with one which allows the receipt, possession, and use of byproduct, source, or special nuclear material without restriction to chemical or physical form or atomic number, for sample analysis or instrument calibration or associated with radioactive apparatus or components. The proposed action is contained in the licensee's application dated December 20, 2006. </P>
                <HD SOURCE="HD2">Need for Proposed Action </HD>
                <P>The current license condition was included in the license that was issued by the NRC when HBPP entered the possess-but-not-operate SAFSTOR phase. The license, including License Condition 2.B.3(c), was proposed by PG&amp;E on July 30, 1984, and approved and issued by the NRC on July 16, 1985, as Amendment No. 19 to the facility license. License Condition 2.B.3(c) was established based on the byproduct materials onsite at the time and not based on any safety issue. The licensee has now begun preparations for transfer of the spent fuel from the spent fuel pool to an onsite Independent Spent Fuel Storage Installation and for active decommissioning. Offsite equipment will need to be received to perform these activities. However, review of potential equipment has revealed that some would be unsuitable due to radiological composition which contains atomic numbers not allowed by the current license condition. </P>
                <HD SOURCE="HD2">Environmental Impacts of the Proposed Action </HD>
                <P>The NRC has completed its evaluation of the proposed amendments to the License and concludes the changes provide a minor revision of the existing provision for the receipt, possession, and use of special nuclear, source, and byproduct materials. The revised license condition is similar to the license condition currently in place for multiple decommissioning and operating nuclear power facilities. The NRC evaluated the safety impacts of the proposed changes and determined that the changes proposed by this license amendment request will provide reasonable assurance that the applicable radiation protection requirements of 10 CFR parts 20, 30, 40, and 70 will be met. </P>
                <P>The NRC has evaluated the change and determined that the revised license condition will not significantly change the types or quantities of special nuclear, source, and byproduct materials the license may receive, possess, or use and would therefore have no significant impacts to the environment. </P>
                <P>Due to the limited nature of the amendment which will not significantly change the licensed activities on site, the proposed action does not have a potential to affect any historic sites, would not increase the probability or consequences of accidents, would not change the types of effluents that may be released offsite, and would not increase occupation or public radiation exposure. </P>
                <HD SOURCE="HD2">Alternatives to the Proposed Action </HD>
                <P>The alternative to the proposed action would be to deny the request. Denial of this amendment request would have the same environmental impact as the proposed action. </P>
                <HD SOURCE="HD2">Agencies and Persons Consulted </HD>
                <P>
                    This EA was prepared by John B. Hickman, Project Manager, Decommissioning Directorate, Division of Waste Management and Environmental Protection (DWMEP). NRC staff determined that the proposed action is not a major decommissioning activity and will not affect listed or proposed endangered species, nor critical habitat. Therefore, no further consultation is required under Section 7 of the Endangered Species Act. Likewise, NRC staff determined that the proposed action is not the type of activity that has the potential to cause 
                    <PRTPAGE P="18692"/>
                    previously unconsidered effects on historic properties, as consultation for site decommissioning has been conducted previously. There are no additional impacts to historic properties associated with the disposal method and location for demolition debris. Therefore, no consultation is required under Section 106 of the National Historic Preservation Act. The NRC discussed the proposed action with the State of California Radiologic Health Branch. The state official had no comments. 
                </P>
                <HD SOURCE="HD1">III. Finding of No Significant Impact </HD>
                <P>On the basis of the environmental assessment, the NRC concludes that the proposed action will not have a significant effect on the quality of the human environment. Accordingly, preparation of an environmental impact statement for the proposed action is not warranted. </P>
                <HD SOURCE="HD1">IV. Further Information </HD>
                <P>
                    For further details with respect to the proposed action, see the licensee's letter dated December 20, 2006. (ADAMS Accession No. ML063560061) The NRC Public Documents Room is located at NRC Headquarters in Rockville, MD, and can be contacted at (800) 397-4209. Documents may be examined, and/or copied for a fee, at the NRC's Public Document Room (PDR), located at One White Flint North, 11555 Rockville Pike (first floor), Rockville, Maryland. Publicly available records will be accessible electronically from the Agencywide Documents Access and Management System's (ADAMS) Public Library component on the NRC Web site, 
                    <E T="03">http://www.nrc.gov</E>
                     (the Public Electronic Reading Room). Persons who do not have access to ADAMS or who encounter problems in accessing the documents located in ADAMS should contact the NRC PDR Reference staff by telephone at 1-800-397-4209, or 301-415-4737, or by e-mail at 
                    <E T="03">pdr@nrc.gov</E>
                    . 
                </P>
                <SIG>
                    <DATED>Dated at Rockville, Maryland, this 5th day of April, 2007. </DATED>
                    <P>For the Nuclear Regulatory Commission. </P>
                    <NAME>Keith I. McConnell, </NAME>
                    <TITLE>Deputy Director, Decommissioning and Uranium Recovery Licensing Directorate, Division of Waste Management and Environmental Protection, Office of Federal and State Materials and Environmental Management Programs.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. E7-7074 Filed 4-12-07; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 7590-01-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">PENSION BENEFIT GUARANTY CORPORATION </AGENCY>
                <SUBJECT>Proposed Submission of Information Collection for OMB Review; Comment Request; Procedures for Implementing Multiemployer Plan Elections </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Pension Benefit Guaranty Corporation. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of intention to request OMB approval. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Pension Benefit Guaranty Corporation (PBGC) intends to request that the Office of Management and Budget (OMB) approve, under the Paperwork Reduction Act, a collection of information under its procedures on multiemployer plan elections. This notice informs the public of the PBGC's intent and solicits public comment on the collection of information. </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments should be submitted by June 12, 2007. </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Comments may be submitted by any of the following methods: </P>
                    <P>
                        • 
                        <E T="03">Federal eRulemaking Portal: http://www.regulations.gov.</E>
                         Follow the Web site instructions for submitting comments. 
                    </P>
                    <P>
                        • 
                        <E T="03">E-mail: paperwork.comments@pbgc.gov.</E>
                    </P>
                    <P>
                        • 
                        <E T="03">Fax:</E>
                         202-326-4224. 
                    </P>
                    <P>
                        • 
                        <E T="03">Mail or Hand Delivery:</E>
                         Legislative and Regulatory Department, Pension Benefit Guaranty Corporation, 1200 K Street, NW., Washington, DC 20005-4026. Comments received will be posted to 
                        <E T="03">http://www.pbgc.gov.</E>
                    </P>
                    <P>Copies of the collection of information may be obtained without charge by writing to the Disclosure Division of the Office of the General Counsel of PBGC at the above address or by visiting the Disclosure Division or calling 202-326-4040 during normal business hours. (TTY and TDD users may call the Federal relay service toll-free at 1-800-877-8339 and ask to be connected to 202-326-4040.) </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Constance Markakis, Attorney, Legislative and Regulatory Department, Pension Benefit Guaranty Corporation, 1200 K Street, NW., Washington, DC 20005-4026, 202-326-4000, ext. 6779. (For TTY and TDD, call 800-877-8339 and request connection to 202-326-4000, ext. 6779.) </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>Section 1106 of the Pension Plan Protection Act of 2006 (“PPA 2006”) amends the definition of a “multiemployer plan” in Title I of ERISA and the Internal Revenue Code of 1986 to allow certain plans to elect to be multiemployer plans pursuant to procedures prescribed by PBGC. A plan is eligible for the election if it is (i) a plan revoking a previous election to remain a single-employer plan under section 3(37)(E) of ERISA, or (ii) a plan with respect to which substantially all employer contributions were made by tax-exempt employers. In either case, for the three plan years preceding the enactment of PPA 2006, the plan must have been a plan to which more than one employer was required to contribute that was maintained pursuant to one or more collective bargaining agreements. PPA 2006 also imposes other requirements for an election, and provides certain exemptions from the requirements. All elections must be made by August 17, 2007. </P>
                <P>PBGC's proposed procedures for implementing the multiemployer plan election requires a plan to submit specified information to PBGC to demonstrate that it meets the statutory eligibility requirements. The information collection includes names of contributing employers, copies of collective bargaining agreements that require contributions to the plan, numbers of participants and contributions to the plan under those collective bargaining agreements and the plan as a whole, information on common control among contributing employers to the plan, copies of the plan and trust documents, and evidence of the tax-exempt status of contributing employers and the percentage of total plan contributions attributable to these employers. For the limited purposes of the election under section 1106 of PPA 2006, the procedures provide a safe harbor provision for meeting the multiemployer criterion that a plan be “maintained pursuant to collective bargaining agreements.” </P>
                <P>The PBGC intends to request that OMB approve this collection of information for three years. (Although plans must make an election by August 17, 2007, PBGC may request additional information, after that date, that is needed to review the election.) An agency may not conduct or sponsor, and a person is not required to respond to, a collection of information unless it displays a currently valid OMB control number. </P>
                <P>The PBGC estimates that from 20 to 50 plans will respond to this collection of information. The PBGC further estimates that the average burden of this collection of information is 5 hours and $1,875 per plan, with an average total burden of 175 hours and $65,625. </P>
                <P>
                    The PBGC is soliciting public comments to—
                    <PRTPAGE P="18693"/>
                </P>
                <P>• 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>• Evaluate the accuracy of the agency's estimate of the burden of the 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>
                <SIG>
                    <DATED>Issued in Washington, DC, this 11th day of April 2007. </DATED>
                    <NAME>Marc A. Felton, </NAME>
                    <TITLE>Deputy Chief Information Officer, Pension Benefit Guaranty Corporation.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC> [FR Doc. E7-7126 Filed 4-12-07; 10:57 am] </FRDOC>
            <BILCOD>BILLING CODE 7709-01-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">PENSION BENEFIT GUARANTY CORPORATION </AGENCY>
                <SUBJECT>Required Interest Rate Assumption for Determining Variable-Rate Premium for Single-Employer Plans; Interest on Late Premium Payments; Interest on Underpayments and Overpayments of Single-Employer Plan Termination Liability and Multiemployer Withdrawal Liability; Interest Assumptions for Multiemployer Plan Valuations Following Mass Withdrawal </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Pension Benefit Guaranty Corporation. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of interest rates and assumptions. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        This notice informs the public of the interest rates and assumptions to be used under certain Pension Benefit Guaranty Corporation regulations. These rates and assumptions are published elsewhere (or can be derived from rates published elsewhere), but are collected and published in this notice for the convenience of the public. Interest rates are also published on the PBGC's Web site (
                        <E T="03">http://www.pbgc.gov</E>
                        ). 
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The required interest rate for determining the variable-rate premium under part 4006 applies to premium payment years beginning in April 2007. The interest assumptions for performing multiemployer plan valuations following mass withdrawal under part 4281 apply to valuation dates occurring in May 2007. The interest rates for late premium payments under part 4007 and for underpayments and overpayments of single-employer plan termination liability under part 4062 and multiemployer withdrawal liability under part 4219 apply to interest accruing during the second quarter (April through June) of 2007. </P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Catherine B. Klion, Manager, Regulatory and Policy Division, Legislative and Regulatory Department, Pension Benefit Guaranty Corporation, 1200 K Street, NW., Washington, DC 20005, 202-326-4024. (TTY/TDD users may call the Federal relay service toll-free at 1-800-877-8339 and ask to be connected to 202-326-4024.) </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Variable-Rate Premiums </HD>
                <P>Section 4006(a)(3)(E)(iii)(II) of the Employee Retirement Income Security Act of 1974 (ERISA) and § 4006.4(b)(1) of the PBGC's regulation on Premium Rates (29 CFR part 4006) prescribe use of an assumed interest rate (the “required interest rate”) in determining a single-employer plan's variable-rate premium. Pursuant to the Pension Protection Act of 2006, for premium payment years beginning in 2006 or 2007, the required interest rate is the “applicable percentage” of the annual rate of interest determined by the Secretary of the Treasury on amounts invested conservatively in long-term investment grade corporate bonds for the month preceding the beginning of the plan year for which premiums are being paid (the “premium payment year”). </P>
                <P>On February 2, 2007 (at 72 FR 4955), the Internal Revenue Service (IRS) published final regulations containing updated mortality tables for determining current liability under section 412(l)(7) of the Code and section 302(d)(7) of ERISA for plan years beginning on or after January 1, 2007. As a result, in accordance with section 4006(a)(3)(E)(iii)(II) of ERISA, the “applicable percentage” to be used in determining the required interest rate for plan years beginning in 2007 is 100 percent. </P>
                <P>The required interest rate to be used in determining variable-rate premiums for premium payment years beginning in April 2007 is 5.84 percent (i.e., 100 percent of the 5.84 percent composite corporate bond rate for March 2007 as determined by the Treasury). </P>
                <P>The following table lists the required interest rates to be used in determining variable-rate premiums for premium payment years beginning between May 2006 and April 2007. </P>
                <GPOTABLE COLS="2" OPTS="L2,tp0,i1" CDEF="s50,10">
                    <TTITLE>  </TTITLE>
                    <BOXHD>
                        <CHED H="1">For premium payment years beginning in: </CHED>
                        <CHED H="1">The required interest rate is: </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">May 2006 </ENT>
                        <ENT>5.25 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">June 2006 </ENT>
                        <ENT>5.35 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">July 2006 </ENT>
                        <ENT>5.36 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">August 2006 </ENT>
                        <ENT>5.36 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">September 2006 </ENT>
                        <ENT>5.19 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">October 2006 </ENT>
                        <ENT>5.06 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">November 2006 </ENT>
                        <ENT>5.05 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">December 2006 </ENT>
                        <ENT>4.90 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">January 2007 </ENT>
                        <ENT>5.75 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">February 2007 </ENT>
                        <ENT>5.89 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">March 2007 </ENT>
                        <ENT>5.85 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">April 2007 </ENT>
                        <ENT>5.84 </ENT>
                    </ROW>
                </GPOTABLE>
                <HD SOURCE="HD1">Late Premium Payments; Underpayments and Overpayments of Single-Employer Plan Termination Liability </HD>
                <P>Section 4007(b) of ERISA and § 4007.7(a) of the PBGC's regulation on Payment of Premiums (29 CFR part 4007) require the payment of interest on late premium payments at the rate established under section 6601 of the Internal Revenue Code. Similarly, § 4062.7 of the PBGC's regulation on Liability for Termination of Single-Employer Plans (29 CFR part 4062) requires that interest be charged or credited at the section 6601 rate on underpayments and overpayments of employer liability under section 4062 of ERISA. The section 6601 rate is established periodically (currently quarterly) by the Internal Revenue Service. The rate applicable to the second quarter (April through June) of 2007, as announced by the IRS, is 8 percent. </P>
                <P>The following table lists the late payment interest rates for premiums and employer liability for the specified time periods: </P>
                <GPOTABLE COLS="3" OPTS="L2,tp0,i1" CDEF="s50,10,10">
                    <TTITLE>  </TTITLE>
                    <BOXHD>
                        <CHED H="1">From </CHED>
                        <CHED H="1">Through </CHED>
                        <CHED H="1">
                            Interest rate 
                            <LI>(percent) </LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">4/1/01 </ENT>
                        <ENT>6/30/01 </ENT>
                        <ENT>8 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">7/1/01 </ENT>
                        <ENT>12/31/01 </ENT>
                        <ENT>7 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">1/1/02 </ENT>
                        <ENT>12/31/02 </ENT>
                        <ENT>6 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">1/1/03 </ENT>
                        <ENT>9/30/03 </ENT>
                        <ENT>5 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">10/1/03 </ENT>
                        <ENT>3/31/04 </ENT>
                        <ENT>4 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">4/1/04 </ENT>
                        <ENT>6/30/04 </ENT>
                        <ENT>5 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">7/1/04 </ENT>
                        <ENT>9/30/04 </ENT>
                        <ENT>4 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">10/1/04 </ENT>
                        <ENT>3/31/05 </ENT>
                        <ENT>5 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">4/1/05 </ENT>
                        <ENT>9/30/05 </ENT>
                        <ENT>6 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">10/1/05 </ENT>
                        <ENT>6/30/06 </ENT>
                        <ENT>7 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">7/1/06 </ENT>
                        <ENT>6/30/07 </ENT>
                        <ENT>8 </ENT>
                    </ROW>
                </GPOTABLE>
                <HD SOURCE="HD1">Underpayments and Overpayments of Multiemployer Withdrawal Liability </HD>
                <P>
                    Section 4219.32(b) of the PBGC's regulation on Notice, Collection, and Redetermination of Withdrawal Liability (29 CFR part 4219) specifies the rate at which a multiemployer plan is to charge or credit interest on underpayments and overpayments of 
                    <PRTPAGE P="18694"/>
                    withdrawal liability under section 4219 of ERISA unless an applicable plan provision provides otherwise. For interest accruing during any calendar quarter, the specified rate is the average quoted prime rate on short-term commercial loans for the fifteenth day (or the next business day if the fifteenth day is not a business day) of the month preceding the beginning of the quarter, as reported by the Board of Governors of the Federal Reserve System in Statistical Release H.15 (“Selected Interest Rates”). The rate for the second quarter (April through June) of 2007 (
                    <E T="03">i.e.</E>
                    , the rate reported for March 15, 2007) is 8.25 percent.
                </P>
                <P>The following table lists the withdrawal liability underpayment and overpayment interest rates for the specified time periods:</P>
                <GPOTABLE COLS="3" OPTS="L2,tp0,i1" CDEF="s50,10,10">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">From</CHED>
                        <CHED H="1">Through</CHED>
                        <CHED H="1">
                            Interest rate 
                            <LI>(percent)</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">4/1/01 </ENT>
                        <ENT>6/30/01 </ENT>
                        <ENT>8.50</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">7/1/01 </ENT>
                        <ENT>9/30/01 </ENT>
                        <ENT>7.00</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">10/1/01 </ENT>
                        <ENT>12/31/01 </ENT>
                        <ENT>6.50</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">1/1/02 </ENT>
                        <ENT>12/31/02 </ENT>
                        <ENT>4.75</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">1/1/03 </ENT>
                        <ENT>9/30/03 </ENT>
                        <ENT>4.25</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">10/1/03 </ENT>
                        <ENT>9/30/04 </ENT>
                        <ENT>4.00</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">10/1/04 </ENT>
                        <ENT>12/31/04 </ENT>
                        <ENT>4.50</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">1/1/05 </ENT>
                        <ENT>3/31/05 </ENT>
                        <ENT>5.25</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">4/1/05 </ENT>
                        <ENT>6/30/05 </ENT>
                        <ENT>5.50</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">7/1/05 </ENT>
                        <ENT>9/30/05 </ENT>
                        <ENT>6.00</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">10/1/05 </ENT>
                        <ENT>12/31/05 </ENT>
                        <ENT>6.50</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">1/1/06 </ENT>
                        <ENT>3/31/06 </ENT>
                        <ENT>7.25</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">4/1/06 </ENT>
                        <ENT>6/30/06 </ENT>
                        <ENT>7.50</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">7/1/06 </ENT>
                        <ENT>9/30/06 </ENT>
                        <ENT>8.00</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">10/1/06 </ENT>
                        <ENT>6/30/07 </ENT>
                        <ENT>8.25</ENT>
                    </ROW>
                </GPOTABLE>
                <HD SOURCE="HD1">Multiemployer Plan Valuations Following Mass Withdrawal</HD>
                <P>
                    The PBGC's regulation on Duties of Plan Sponsor Following Mass Withdrawal (29 CFR part 4281) prescribes the use of interest assumptions under the PBGC's regulation on Allocation of Assets in Single-Employer Plans (29 CFR part 4044). The interest assumptions applicable to valuation dates in May 2007 under part 4044 are contained in an amendment to part 4044 published elsewhere in today's 
                    <E T="04">Federal Register</E>
                    . Tables showing the assumptions applicable to prior periods are codified in appendix B to 29 CFR part 4044.
                </P>
                <SIG>
                    <DATED>Issued in Washington, DC, on this 10th day of April 2007.</DATED>
                    <NAME>Vincent K. Snowbarger,</NAME>
                    <TITLE>Interim Director, Pension Benefit Guaranty Corporation.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. E7-7097 Filed 4-12-07; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 7709-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">RAILROAD RETIREMENT BOARD </AGENCY>
                <SUBJECT>Agency Forms Submitted for OMB Review, Request for Comments </SUBJECT>
                <P>
                    <E T="03">Summary:</E>
                     In accordance with the Paperwork Reduction Act of 1995 (44 U.S.C. Chapter 35), the Railroad Retirement Board (RRB) is forwarding an Information Collection Request (ICR) to the Office of Information and Regulatory Affairs (OIRA), Office of Management and Budget (OMB) to request a revision to the following collection of information: 3220-0052, Application to Act as Representative Payee, consisting of RRB Form(s) AA-5, Application for Substitution of Payee, G-478, Statement Regarding Patient's Capability to Manage Payments and booklet RB-5, Your Duties as Representative Payee-Representative Payee Record. Our ICR describes the information we seek to collect from the public. Completion is required to obtain or retain benefits. One response is required of each respondent. Review and approval by OIRA ensures that we impose appropriate paperwork burdens. 
                </P>
                <P>The RRB invites comments on the proposed collection of information to determine (1) The practical utility of the collection; (2) the accuracy of the estimated burden of the collection; (3) ways to enhance the quality, utility and clarity of the information that is the subject of collection; and (4) ways to minimize the burden of collections on respondents, including the use of automated collection techniques or other forms of information technology. Comments to RRB or OIRA must contain the OMB control number of the ICR. For proper consideration of your comments, it is best if RRB and OIRA receive them within 30 days of publication date. </P>
                <P>
                    <E T="03">Previous Requests for Comments:</E>
                     The RRB has already published the initial 60-day notice (71 FR No. 227 on 68644 and 68645 on November 27, 2006) required by 44 U.S.C. 3506(c)(2). That request elicited no comments. 
                </P>
                <HD SOURCE="HD1">Information Collection Request (ICR) </HD>
                <P>
                    <E T="03">Title:</E>
                     Application to Act as Representative Payee. 
                </P>
                <P>
                    <E T="03">OMB Control Number:</E>
                     3220-0052. 
                </P>
                <P>
                    <E T="03">Form(s) submitted:</E>
                     AA-5, Application for Substitution of Payee; G-478, Statement Regarding Patient's Capability to Manage Payments; and RB-5, your duties as Representative Payee's Record. 
                </P>
                <P>
                    <E T="03">Type of request:</E>
                     Revision of a currently approved collection. 
                </P>
                <P>
                    <E T="03">Affected public:</E>
                     Individuals or households; Business or other for Profit. 
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     Under Section 12 of the Railroad Retirement Act, the Railroad Retirement Board (RRB) may pay benefits to a representative payee when an employee, spouse or survivor annuitant is incompetent or is a minor. The collection obtains information related to the representative payee application, supporting documentation, and the maintenance of records pertaining to the receipt and use of the benefits. 
                </P>
                <P>
                    <E T="03">Changes Proposed:</E>
                     The RRB proposes a revised title for the information collection (currently Railroad Retirement Act Continuing Entitlement), Application to Act as Representative Payee, to more accurately reflect the information collected. No changes are proposed to the forms in the collection. 
                </P>
                <P>
                    <E T="03">The burden estimate for the ICR is as follows:</E>
                </P>
                <P>
                    <E T="03">Estimated annual number of respondents:</E>
                     17,300. 
                </P>
                <P>
                    <E T="03">Total annual responses:</E>
                     20,300. 
                </P>
                <P>
                    <E T="03">Total annual reporting hours:</E>
                     16,350. 
                </P>
                <P>
                    <E T="03">Additional Information or Comments:</E>
                     Copies of the forms and supporting documents can be obtained from Charles Mierzwa, the agency clearance officer (312-751-3363) or 
                    <E T="03">Charles.Mierzwa@rrb.gov.</E>
                </P>
                <P>
                    Comments regarding the information collection should be addressed to Ronald J. Hodapp, Railroad Retirement Board, 844 North Rush Street, Chicago, Illinois, 60611-2092 or 
                    <E T="03">Ronald.Hodapp@rrb.gov</E>
                     and to the OMB Desk Officer for the RRB, at the Office of Management and Budget, Room 10230, New Executive Office Building, Washington, DC 20503. 
                </P>
                <SIG>
                    <NAME>Charles Mierzwa, </NAME>
                    <TITLE>Clearance Officer.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC> [FR Doc. E7-7001 Filed 4-12-07; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 7905-01-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">SECURITIES AND EXCHANGE COMMISSION </AGENCY>
                <SUBJECT>Proposed Collection; Comment Request </SUBJECT>
                <FP SOURCE="FP-1">Upon Written Request, Copies Available From: Securities and Exchange Commission, Office of Filings and Information Services, Washington, DC 20549</FP>
                <EXTRACT>
                    <FP SOURCE="FP-2">Extension: Rule 6a-3, SEC File No. 270-0015, OMB Control No. 3235-0021</FP>
                </EXTRACT>
                <P>
                    Notice is hereby given that pursuant to the Paperwork Reduction Act of 1995 (44 U.S.C. 3501 
                    <E T="03">et seq.</E>
                    ), the Securities and Exchange Commission (“Commission”) is soliciting comments on the collection of information summarized below. The Commission plans to submit this existing collection of information to the Office of 
                    <PRTPAGE P="18695"/>
                    Management and Budget for extension and approval. 
                </P>
                <P>
                    Section 6 of the Securities Exchange Act of 1934 (15 U.S.C. 78a 
                    <E T="03">et seq.</E>
                    ) sets out a framework for the registration and regulation of national securities exchanges. Under Commission Rule 6a-3 (17 CFR 240.6a-3), one of the rules that implements Section 6, a national securities exchange (or an exchange exempted from registration as a national securities exchange based on limited trading volume) must provide certain supplemental information to the Commission, including any material (including notices, circulars, bulletins, lists, and periodicals) issued or made generally available to members of, or participants or subscribers to, the exchange. Rule 6a-3 also requires the exchanges to file monthly reports that set forth the volume and aggregate dollar amount of securities sold on the exchange each month. 
                </P>
                <P>The information required to be filed with the Commission pursuant to Rule 6a-3 is designed to enable the Commission to carry out its statutorily mandated oversight functions and to ensure that registered and exempt exchanges continue to be in compliance with the Act. </P>
                <P>The respondents to the collection of information are national securities exchanges and exchanges that are exempt from registration based on limited trading volume. </P>
                <P>The Commission estimates that each respondent makes approximately 25 such filings on an annual basis at an average cost of approximately $21 per response. Currently, 12 respondents (ten national securities exchanges and two exempt exchanges) are subject to the collection of information requirements of Rule 6a-3. The Commission estimates that the total burden for all respondents is 150 hours (25 filings/respondent per year × 0.5 hours/filing × 12 respondents) and $6300 ($21/response × 25 responses/respondent per year × 12 respondents) per year. </P>
                <P>Written 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. Consideration will be given to comments and suggestions submitted in writing within 60 days of this publication. </P>
                <P>
                    Comments should be directed to: R. Corey Booth, Director/Chief Information Officer, Securities and Exchange Commission, c/o Shirley Martinson, 6432 General Green Way, Alexandria, Virginia 22312 or send an e-mail to: 
                    <E T="03">PRA_Mailbox@sec.gov.</E>
                     Comments must be submitted within 60 days of this notice. 
                </P>
                <SIG>
                    <DATED>Dated: April 5, 2007. </DATED>
                    <NAME>Florence E. Harmon, </NAME>
                    <TITLE>Deputy Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC> [FR Doc. E7-7006 Filed 4-12-07; 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-55583; File No. SR-Amex-2006-107] </DEPDOC>
                <SUBJECT>Self-Regulatory Organizations; American Stock Exchange LLC; Notice of Filing of Proposed Rule Change and Amendment No. 1 Thereto Relating to Amex Book Clerks </SUBJECT>
                <DATE>April 5, 2007. </DATE>
                <P>
                    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/>
                     notice is hereby given that on November 14, 2006, the American Stock Exchange LLC (“Amex” or “Exchange”) filed with the Securities and Exchange Commission (“Commission”) the proposed rule change as described in Items I, II, and III below, which Items have been substantially prepared by the Exchange. The Exchange filed Amendment No. 1 to the proposal on March 29, 2007. The Commission is publishing this notice to solicit comment on the proposed rule change, as amended, from interested persons. 
                </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>
                <HD SOURCE="HD1">I. Self-Regulatory Organization's Statement of the Terms of Substance of the Proposed Rule Change </HD>
                <P>
                    The Exchange proposes to eliminate the agency obligations of Exchange options specialists and establish Amex book clerks (“ABCs”). The text of the proposed rule change is available at Amex, the Commission's Public Reference Room, and 
                    <E T="03">http://www.amex.com</E>
                    . 
                </P>
                <HD SOURCE="HD1">II. Self-Regulatory Organization's Statement of the Purpose of, and Statutory Basis for, the Proposed Rule Change </HD>
                <P>In its filing with the Commission, Amex included statements concerning the purpose of and basis for the proposed rule change and discussed any comments it received on the proposed rule change. The text of these statements may be examined at the places specified in Item IV below. The Exchange has prepared summaries, set forth in Sections A, B, and C below, of the most significant aspects of such statements. </P>
                <HD SOURCE="HD2">A. Self-Regulatory Organization's Statement of the Purpose of, and Statutory Basis for, the Proposed Rule Change </HD>
                <HD SOURCE="HD3">1. Purpose </HD>
                <P>
                    The purpose of this proposed rule change is to eliminate the obligation and ability of an Exchange options specialist to act as an agent in connection with orders in his or her assigned options classes. This proposal would also permit the Exchange to designate Exchange employees or independent contractors to serve as ABCs, responsible for maintaining and operating the ANTE Central Book (
                    <E T="03">i.e.</E>
                    , the specialist's customer limit order book) and the ANTE Display Book.
                    <SU>3</SU>
                    <FTREF/>
                     The Exchange also seeks to amend certain Exchange rules relating to the operation of the Plan for the Purpose of Creating and Operating an Intermarket Option Linkage (“Linkage Plan”) to accommodate the implementation of pertinent ABC rules and other proposed rule changes described herein.
                    <SU>4</SU>
                    <FTREF/>
                     Finally, this proposed rule change also would implement several other amendments to conform other Exchange rules to the proposal. The Exchange notes that the proposal substantially mirrors changes recently adopted by the Chicago Board 
                    <PRTPAGE P="18696"/>
                    Options Exchange to eliminate DPM agency responsibilities and establish PAR Officials.
                    <SU>5</SU>
                    <FTREF/>
                     The following summarizes the effects this proposed rule change would have on existing Exchange rules. 
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         The Exchange submits that all incoming customer orders are represented in the ANTE Central Book, and if marketable, will be automatically executed subject to a number of limited exceptions. Orders that are otherwise eligible for automatic execution may not receive an automatic execution: (i) Whenever the Amex Best Bid or Offer (ABBO) crosses the National Best Bid or Offer (NBBO) and causes an inversion in the quote; or (ii) whenever a better bid or offer is being disseminated by another options exchange and the order is not eligible for automatic price matching. In addition, if quotes are deemed unreliable or the Exchange is experiencing communications or systems problems, non-firm markets or delays in the dissemination of quotes by the Options Price Reporting Authority, orders will not be automatically executed. In these limited cases, incoming customer orders will be routed to the ANTE Display Book for manual handling. 
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         Exchange rules governing the operation of the Linkage Plan are set forth under Amex Rules 940 through 945 and Amex Rule 941-ANTE. 
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 52798 (November 18, 2005), 70 FR 71344 (November 28, 2005). 
                    </P>
                </FTNT>
                <P>
                    a. 
                    <E T="03">Agency Responsibilities</E>
                </P>
                <P>
                    Generally, Amex Rule 170 (applicable to options transactions by Amex Rule 950-ANTE(l)) governs options specialists on the Exchange and describes the obligations imposed on an options specialist. These obligations include the general obligation, with respect to each of a specialist's assigned options classes, to fulfill market-making obligations and provide functions of a floor broker (to the extent that the options specialist acts as a floor broker). Rule 170(b), in particular, describes the floor broker and agency functions that an options specialist is required to perform. As a condition of being registered as a specialist by the Exchange, options specialists are required to execute options orders on an agency basis for those classes of options assigned to them.
                    <SU>6</SU>
                    <FTREF/>
                     Accordingly, all options specialists on the Amex presently act as both agent and principal for orders in their respective assigned options classes. The Exchange has now determined that it is in the best interest of the Exchange, its members, and investors to eliminate the agency obligation of options specialists. 
                </P>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         
                        <E T="03">See</E>
                         Amex Rule 950-ANTE(l), incorporating Amex Rule 170 to options transactions. 
                    </P>
                </FTNT>
                <P>
                    This rule change proposes to eliminate those provisions providing for the options specialist's broker and agency functions and would provide that an options specialist “shall not execute orders as an agent or floor broker.” 
                    <SU>7</SU>
                    <FTREF/>
                     Instead, the Exchange proposes to create a new category of market participant, the ABC, who will be responsible for maintaining and operating the customer limit order book. This responsibility would include handling and executing orders that are routed to the customer limit order book. The proposal would clarify that the specialists' accounts shall continue to be used by the ABC to execute P/A and Satisfaction Orders routed to the Exchange and that the specialists shall continue to be liable for any charges incurred in relation to executing such orders. This change would afford options specialists the ability to concentrate their efforts exclusively on their market-making functions and would eliminate the potential conflicts associated with options specialists acting as both principal and agent with respect to orders they handle and trades they make as options specialists. 
                </P>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         Proposed Amex Rule 950-ANTE(l), Commentary .01. 
                    </P>
                </FTNT>
                <P>The ABC would be an Exchange employee or independent contractor designated by the Exchange to be responsible for: (i) Maintaining and operating the customer limit order book for the assigned options classes; and (ii) effecting proper executions of orders placed in the customer order limit book. The ABC would be prohibited from having an affiliation with any member that is approved to act as a specialist, registered options trader (“ROT”), remote registered options trader (“RROT”) and supplemental registered options trader (“SROT”) on the Exchange. The Exchange believes that the responsibility for executing agency orders at trading posts should belong to the ABC, who has no interest that might conflict with the duties owed to the customer. Additionally, given that the increased reliance on electronic order execution has resulted in the virtual elimination of manual order handling, a vast majority of orders are currently never handled or seen by specialists. This trend effectively eliminates the need for specialists to act in an agency capacity and perform functions related thereto. </P>
                <P>
                    b. 
                    <E T="03">Other Affected Rules</E>
                </P>
                <P>The Exchange is proposing amendments to other Exchange rules to allow the Exchange to reassign agency responsibilities and obligations from the options specialist to the ABC, as detailed below. </P>
                <P>
                    <E T="03">Display Obligation</E>
                    . Currently, under Amex Rule 958A-ANTE, an options specialist is required to immediately display the full price and size of any eligible customer limit orders when such orders represent buying or selling interest that is at a better price or size than the best disseminated Amex quote.
                    <SU>8</SU>
                    <FTREF/>
                     Because the options specialist no longer would be operating the customer limit order book or executing orders as agent and since the vast majority of orders are currently either executed, displayed or booked immediately and without any input from a specialist, the Exchange proposes to shift the display obligation in its entirety from the options specialist to the ABC.
                    <SU>9</SU>
                    <FTREF/>
                     Accordingly, the ABC would be required to maintain and keep active the Exchange's automated customer limit order display facility in ANTE. 
                </P>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         
                        <E T="03">See</E>
                         Amex Rule 958A-ANTE(e). See also Securities Exchange Act Release No. 51062 (January 21, 2005), 70 FR 4163 (January 28, 2005) (File No. SR-Amex-00-27). 
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         The display obligation set forth in Amex Rule 958A-ANTE(e), along with the exceptions set forth therein, would be moved to proposed Amex Rule 995-ANTE. 
                    </P>
                </FTNT>
                <P>
                    <E T="03">Due Diligence Responsibility</E>
                    . Under the proposed rule, the ABC would be required to use due diligence to execute customer orders at the best prices available to him or her under the rules of the Exchange. 
                </P>
                <P>
                    <E T="03">Public Order Book Responsibilities</E>
                    . In addition to his or her responsibility for maintaining orders in the electronic customer order limit order book in ANTE, the ABC also would be prohibited from removing a booked public customer order unless the order is cancelled, expires, is transmitted in accordance with Intermarket Option Linkage (“Linkage”) obligations, or is executed. 
                </P>
                <P>
                    <E T="03">Linkage Obligations</E>
                    . As the options specialist would no longer be executing agency orders, this responsibility, and any associated Linkage obligations that previously were handled by the options specialist, would now fall upon the Exchange. As an employee (or independent contractor) of the Exchange, the ABC would be responsible for handling Linkage orders in the option classes appointed to him or her. Specifically, an ABC would have the means to: (1) Utilize an options specialist's account to route Principal Acting as Agent (“P/A”) Orders 
                    <SU>10</SU>
                    <FTREF/>
                     and Satisfaction Orders to away markets based on prior instructions that must be provided by the options specialist to the ABC, and (2) handle all Linkage orders or portions of Linkage orders received by the Exchange that are not automatically executed. The ABC also would have the means to utilize the options specialist's account to fill Satisfaction Orders that result from a Trade Through 
                    <SU>11</SU>
                    <FTREF/>
                     that the Exchange effects. Because the Linkage Plan requires that P/A Orders be submitted for the account of an eligible market maker,
                    <SU>12</SU>
                    <FTREF/>
                     the ABC must be able to utilize the options specialist's account to fulfill the Linkage obligations imposed by Amex rules. 
                </P>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         A “Principal Acting as Agent (“P/A”) Order” is an order for the principal account of a specialist (or equivalent entity on another Participant Exchange under the Linkage Plan that is authorized to represent public customer orders), reflecting the terms of a related unexecuted public customer order for which the specialist is acting as agent. 
                        <E T="03">See</E>
                         Linkage Plan Section 2(16)(a). 
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         
                        <E T="03">See</E>
                         Amex Rule 940(b)(19). 
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         
                        <E T="03">See</E>
                         Linkage Plan Section 2(16)(a); 
                        <E T="03">see also</E>
                         Amex Rule 940(10)(i). 
                    </P>
                </FTNT>
                <P>
                    Amex Linkage Rules would be amended to require an options specialist to make available its account to the ABC for the purpose of enabling the ABC to satisfy certain Linkage-related obligations. Amex Linkage Rules also would be amended to obligate the 
                    <PRTPAGE P="18697"/>
                    options specialist to provide the ABC with prior written instructions for routing P/A Orders, and Satisfaction Orders to other markets.
                    <SU>13</SU>
                    <FTREF/>
                     Since orders routed pursuant to the Linkage can be configured in numerous ways, these written instructions would, with some degree of specificity (
                    <E T="03">i.e.</E>
                    , state whether the order should be routed automatically, the means through which the order should be routed, etc.), direct how the ABC should handle responses to Linkage Orders, as provided under proposed Amex Rule 995-ANTE, as well as detail the procedures the ABCs would be required to follow when utilizing the options specialists' accounts. 
                </P>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         The Exchange intends to file with the Commission a request for an exemption from the requirements set forth in Rule 608(c) of Regulation NMS under the Act requiring the Exchange to comply with and enforce compliance by its members with certain provisions of the Linkage Plan that require eligible market makers (such as specialists and ROTs) through whom the P/A Order is routed to be functioning as the agent with respect to that order. This exemption would facilitate the establishment of ABCs and their handling of Linkage Orders. 
                    </P>
                </FTNT>
                <P>Finally, when handling outbound P/A Orders and Satisfaction Orders, the ABC shall use due diligence to execute the orders entrusted to him/her, act in accordance with the prior written instructions provided by the options specialist for P/A Orders and Satisfaction Orders that the ABC represents, and act in accordance with Amex rules regarding P/A and Satisfaction Orders received through the Linkage. </P>
                <P>
                    <E T="03">Compensation of ABCs</E>
                    . As an Exchange employee or independent contractor, the ABC's compensation would be determined and paid solely by the Amex. No options specialist, ROT, RROT or SROT would be permitted to directly or indirectly compensate or provide any other form of consideration to an ABC. 
                </P>
                <P>
                    <E T="03">Liability of the Exchange for Actions of ABCs</E>
                    . The Exchange's liability for the actions of ABCs would be limited in the same manner as currently provided under existing Exchange rules, including (but not limited to) Article IV, Section 1(e) of the Amex Constitution (Exchange Liability) and Amex Rule 61 (Exchange's Costs of Defending Legal Proceedings). 
                </P>
                <P>
                    <E T="03">Firm Disseminated Market Quotes</E>
                    . Amex Rule 958A-ANTE currently provides that, in the case of an order received by the options specialist, the options specialist's firm quote obligation attaches at the time the order is received by such specialist, regardless of whether the options specialist is actually aware of the order at that time. This provision is a direct consequence of the fact that the options specialists currently represent orders on the customer limit order book in an agency capacity from the moment such orders are received on the book. However, because the options specialist no longer would be operating the customer limit order book if the proposed rule change were approved, Amex Rule 958A-ANTE would be modified such that the firm quote obligation would attach, when an options specialist is the responsible broker or dealer, at the same time those obligations attach with respect to each other responsible broker or dealer—that is, when the order is announced to the trading crowd either via electronic display or by the ABC. 
                </P>
                <P>
                    <E T="03">Rules Relating to ANTE's Automatic Execution Feature</E>
                    . Under established procedures set forth in Amex Rule 933-ANTE (ANTE Automatic Matching and Execution of Options Orders), an order eligible for automatic matching and execution will not be automatically executed if the Amex disseminated quote is inferior to the NBBO by more than the price matching amount and instead is routed to the specialist for manual handling. On the assumption that the specialist would always be responsible for representing such orders as an agent, Commentary .01(b) provides for automatic price matching series that “[i]f the Exchange's best bid or offer is inferior to the NBBO displayed by another options exchange by more than the price matching amount, the order will be routed to the specialist and not automatically executed.” In addition, this Commentary also provides that if a customer order exceeds the established order size parameter, it will be routed to the specialist and not automatically executed. However, because the Exchange has set the order size parameter to 25,001 contracts, orders should rarely exceed the established order size parameter, and therefore, would not be routed to the specialist for manual handling. Similarly, for automatic price improvement series, Commentary .01(c) provides that a “customer order that exceeds the established order size parameter will be either automatically executed at the Exchange's best bid or offer if it is within the automatic matching and execution order size parameters * * *, or it will be routed to the specialist and not automatically executed.” 
                </P>
                <P>
                    Commentary .01(e) to Amex Rule 933-ANTE further provides instances in which an order is re-routed to the specialist and not automatically executed. These situations are as follows: (i) Where the current best bid or offer for a series is crossed (e.g., 4.20 bid, 4 asked) or locked (
                    <E T="03">e.g.</E>
                    , 4 bid, 4 asked); 
                    <SU>14</SU>
                    <FTREF/>
                     (ii) the specialist in conjunction with a Floor Governor or two Floor Officials determined quotes in such options or options exchange(s) are not reliable; or (iii) the Exchange is experiencing communications or systems problems, non-firm markets or delays in the dissemination of quotes by the Options Price Reporting Authority. 
                </P>
                <FTNT>
                    <P>
                        <SU>14</SU>
                         
                        <E T="03">See</E>
                         Amex Rule 951-ANTE, Commentary .01. 
                    </P>
                </FTNT>
                <P>In order to make Amex Rule 933-ANTE consistent with the proposal, Commentary .01(b), (c) and (e) to Amex Rule 933-ANTE would be revised to provide that an order that is not automatically executed will be routed to the ABC rather than the specialist. </P>
                <P>
                    <E T="03">Duty To Report Unusual Activity</E>
                    . Amex Rule 958A-ANTE also will require the ABC, as well as the specialist, to report to a Floor Official any unusual activity, transactions, or price changes or other unusual market conditions or circumstances with respect to the ABCs appointed option classes that may be detrimental to the maintenance of a fair and orderly market. 
                </P>
                <P>
                    <E T="03">General Options Specialist Rules</E>
                    . There are also other Exchange rules relating to options specialists that must be amended to reflect the fact that options specialists will not be operating the customer limit order book or executing orders as agent with respect to their allocated option classes. For example, Amex Rule 154 states, “[n]o member or member organization shall place with a specialist, acting as broker, any order to effect on the Exchange any transaction except at the market or at a limited price.” The proposal would amend Amex Rule 950-ANTE(f) (incorporating Amex Rule 154 to options transactions) to state that Exchange specialists are prohibited from acting as a floor broker or in an agency capacity in connection with orders in his or her assigned options classes. Therefore, the proposal will require members to use an independent floor broker or book orders with the ABC when warranted. Rule 950-ANTE(f) would also be amended to make clear that ABCs, not options specialists, would accept stop, stop limit, spread or straddle orders. Additionally, Amex Rule 155 discusses the precedence specialists are to assign to orders entrusted to them as agents. The proposal would amend Amex Rule 950-ANTE(a) (incorporating Amex Rule 155 to options transactions) to impose the precedence requirement on ABCs in the case of options transactions. Finally, Amex Rule 177 requires all specialists to report certain activities or 
                    <PRTPAGE P="18698"/>
                    information to a Floor Official. The proposal would amend Amex Rule 950-ANTE(a) (incorporating Rule 177 to options) obligating the ABC, as well as an options specialist, to report to a Floor Official those activities and such information as delineated in Amex Rule 177.
                </P>
                <P>
                    c. 
                    <E T="03">Implementation</E>
                </P>
                <P>Finally, to ensure a smooth and orderly transition of the responsibility for operating customer limit order book and executing agency orders from options specialists to ABCs, the Exchange proposes to implement this rule change to all applicable trading posts over a 180-day period from the effective date of this rule change. During this 180-day transition period, any options specialist who continues to operate the customer limit order book would continue to be subject to the same agency obligations as currently provided under Amex Rules 950-ANTE(l) and 958A-ANTE(e), except that, upon the approval of this proposal, these prior obligations instead would be reflected in a Regulatory Circular during the 180-day transition period. </P>
                <HD SOURCE="HD3">2. Statutory Basis </HD>
                <P>
                    Amex believes the proposed rule change is consistent with Section 6(b) of the Act 
                    <SU>15</SU>
                    <FTREF/>
                     in general and furthers the objectives of Section 6(b)(5) of the Act 
                    <SU>16</SU>
                    <FTREF/>
                     in particular in that it is designed to prevent fraudulent and manipulative acts and practices, to promote just and equitable principles of trade, to foster cooperation and coordination with persons engaged in regulating, clearing, settling, processing information with respect to, and facilitating transactions in securities, 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; and is not designed to permit unfair discrimination between customers, issuers, brokers, or dealers, or to regulate by virtue of any authority conferred by the Act matters not related to the purpose of the Act or the administration of the Exchange. 
                </P>
                <FTNT>
                    <P>
                        <SU>15</SU>
                         15 U.S.C. 78f(b). 
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>16</SU>
                         15 U.S.C. 78f(b)(5). 
                    </P>
                </FTNT>
                <HD SOURCE="HD2">B. Self-Regulatory Organization's Statement on Burden on Competition </HD>
                <P>The Exchange believes that this proposed rule change would not impose any burden on competition that is not necessary or appropriate in furtherance of the purposes of the Act. </P>
                <HD SOURCE="HD2">C. Self-Regulatory Organization's Statement on Comments on the Proposed Rule Change Received From Members, Participants or Others </HD>
                <P>No written comments were solicited or received with respect to the proposed rule change. </P>
                <HD SOURCE="HD1">III. Date of Effectiveness of the Proposed Rule Change and Timing for Commission Action </HD>
                <P>
                    Within 35 days of the date of publication of this notice in the 
                    <E T="04">Federal Register</E>
                     or within such longer period (i) As the Commission may designate up to 90 days of such date if it finds such longer period to be appropriate and publishes its reasons for so finding, or (ii) as to which the Exchange consents, the Commission will: 
                </P>
                <P>(A) By order approve the proposed rule change, or </P>
                <P>(B) Institute proceedings to determine whether the proposed rule change should be disapproved. </P>
                <HD SOURCE="HD1">IV. Solicitation of Comments </HD>
                <P>Interested persons are invited to submit written data, views, and arguments concerning the foregoing, including whether the proposed rule change is consistent with the Act. Comments may be submitted by any of the following methods: </P>
                <HD SOURCE="HD2">Electronic Comments </HD>
                <P>
                    • Use the Commission's Internet comment form (
                    <E T="03">http://www.sec.gov/rules/sro.shtml</E>
                    ); or 
                </P>
                <P>
                    • Send an e-mail to 
                    <E T="03">rule-comments@sec.gov.</E>
                     Please include File Number SR-Amex-2006-107 on the subject line. 
                </P>
                <HD SOURCE="HD2">Paper Comments </HD>
                <P>• Send paper comments in triplicate to Nancy M. Morris, Secretary, Securities and Exchange Commission, 100 F Street, NE., Washington, DC 20549-1090.</P>
                <FP>
                    All submissions should refer to File Number SR-Amex-2006-107. This file number should be included on the subject line if e-mail is used. To help the Commission process and review your comments more efficiently, please use only one method. The Commission will post all comments on the Commission's Internet Web site (
                    <E T="03">http://www.sec.gov/rules/sro.shtml</E>
                    ). 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 the filing also will be available for inspection and copying at the principal office of the Exchange. All comments received will be posted without change; the Commission does not edit personal identifying information from submissions. You should submit only information that you wish to make available publicly. All submissions should refer to File Number SR-Amex-2006-107 and should be submitted on or before May 4, 2007. 
                </FP>
                <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>Florence E. Harmon, </NAME>
                    <TITLE>Deputy Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. E7-6960 Filed 4-12-07; 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-55602; File No. SR-Amex-2007-33] </DEPDOC>
                <SUBJECT>Self-Regulatory Organizations; American Stock Exchange LLC; Notice of Filing and Immediate Effectiveness of Proposed Rule Change Relating to the Extension of the Allocation and Performance Evaluation Procedures for Securities Admitted to Dealings on an Unlisted Basis </SUBJECT>
                <DATE>April 9, 2007. </DATE>
                <P>
                    Pursuant to Section 19(b)(1) 
                    <SU>1</SU>
                    <FTREF/>
                     of the Securities Exchange Act of 1934 (the “Act”) 
                    <SU>2</SU>
                    <FTREF/>
                     and Rule 19b-4 thereunder,
                    <SU>3</SU>
                    <FTREF/>
                     notice is hereby given  that on April 3, 2007, the American Stock Exchange LLC (the “Amex” or “Exchange”), filed with the Securities and Exchange Commission (“Commission”) the proposed rule change as described in Items I and II below, which Items have been substantially prepared by Exchange. The Exchange has designated this proposal as non-controversial under Section 19(b)(3)(A)(iii) of the Act 
                    <SU>4</SU>
                    <FTREF/>
                     and Rule 19b-4(f)(6) thereunder,
                    <SU>5</SU>
                    <FTREF/>
                     which renders the proposed rule change effective upon filing with the Commission. The Commission is publishing this notice to solicit 
                    <PRTPAGE P="18699"/>
                    comments on the proposed rule change from interested persons. 
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         15 U.S.C.78s(b)(1).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         15 U.S.C. 78a.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         17 CFR 240.19b-4.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         15 U.S.C. 78s(b)(3)(A)(iii).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         17 CFR 240.19b-4(f)(6).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">I. Self-Regulatory Organization's Statement of the Terms of Substance of the Proposed Rule Change </HD>
                <P>Amex seeks a one year extension of its allocations and performance evaluation procedures for securities admitted to dealings on an unlisted trading privileges (“UTP”) basis to permit these programs to remain in effect while the Commission considers permanent approval of these procedures. </P>
                <P>
                    The text of the proposed rule change is available on the Amex's Web site at 
                    <E T="03">http://www.amex.com,</E>
                     the Exchange's Office of the Secretary, and at the Commission's Public Reference Room. 
                </P>
                <HD SOURCE="HD1">II. Self-Regulatory Organization's Statement of the Purpose of, and Statutory Basis for, the Proposed Rule Change </HD>
                <P>In its filing with the Commission, the Exchange included statements concerning the purpose of and basis for the proposed rule changes and discussed any comments it received regarding the proposal. The text of these statements may be examined at the places specified in Item IV below. The Exchange has prepared summaries, set forth in sections A, B, and C below, of the most significant aspects of such statements. </P>
                <HD SOURCE="HD2">A. Self-Regulatory Organization's Statement of the Purpose of, and the Statutory Basis for, the Proposed Rule Change </HD>
                <HD SOURCE="HD3">1. Purpose </HD>
                <P>
                    The Exchange is proposing to extend its allocations and performance evaluation procedures for securities admitted to dealings on an unlisted trading privileges basis (the “Pilot Program”) from April 6, 2007 through and including April 6, 2008. The text of the rules shall remain unchanged. The Commission previously approved, on a pilot basis, the Exchange's allocation and performance evaluation procedures for securities admitted to dealings on an unlisted trading privileges basis through two independent approval orders.
                    <SU>6</SU>
                    <FTREF/>
                     In 2003, the Pilot Program was extended through October 5, 2003 
                    <SU>7</SU>
                    <FTREF/>
                     and April 5, 2004.
                    <SU>8</SU>
                    <FTREF/>
                     In 2004, the Pilot Program was extended through April 6, 2005.
                    <SU>9</SU>
                    <FTREF/>
                     In 2005, the Pilot Program was extended through April 6, 2006.
                    <SU>10</SU>
                    <FTREF/>
                     In 2006, the Pilot Program was extended through April 6, 2007.
                    <SU>11</SU>
                    <FTREF/>
                     The instant proposed rule change makes no substantive change to the Pilot Program other than to extend it through and including April 6, 2008. 
                </P>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 45698 (April 5, 2002); 67 FR 18051 (April 12, 2002) (SR-Amex-2001-107) and 46750 (October 30, 2002), 67 FR 67880 (November 7, 2002) (SR-Amex-2002-19).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 47779 (May 1, 2003), 68 FR 24777 (May 8, 2003).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 48657 (October 17, 2003), 68 FR 61025 (October 24, 2003).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 49613 (April 26, 2004); 69 FR 24204 (May 3, 2004).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 52004 (July 8, 2005); 70 FR 41061 (July 15, 2005) (retroactively reinstating the Pilot Program to April 6, 2005, and extending it through and including April 6, 2006).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 53649 (April 13, 2006); 71 FR 20425 (April 20, 2006).
                    </P>
                </FTNT>
                <HD SOURCE="HD3">2. Statutory Basis </HD>
                <P>
                    The Exchange believes that the proposed rule change is consistent with Section 6 of the Act 
                    <SU>12</SU>
                    <FTREF/>
                     in general and furthers the objectives of Section 6(b)(5) 
                    <SU>13</SU>
                    <FTREF/>
                     in particular in that it is designed to prevent fraudulent and manipulative acts and practices, to promote just and equitable principles of trade, to foster cooperation and coordination with persons engaged in facilitating transactions in securities, and to remove impediments to and perfect the mechanism of a free and open market and a national market system. 
                </P>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         15 U.S.C. 78f.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         15 U.S.C. 78f(b)(5).
                    </P>
                </FTNT>
                <HD SOURCE="HD2">B. Self-Regulatory Organization's Statement on Burden on Competition </HD>
                <P>The proposed rule change will impose no burden on competition that is not necessary or appropriate in furtherance of the purposes of the Act. </P>
                <HD SOURCE="HD2">C. Self-Regulatory Organization's Statement on Comments on the Proposed Rule Change Received From Members, Participants or Others </HD>
                <P>Written comments on the proposed rule change were neither solicited nor received. </P>
                <HD SOURCE="HD1">III. Date of Effectiveness of the Proposed Rule Change and Timing for Commission Action </HD>
                <P>
                    Because the proposed rule change does not: (1) Significantly affect the protection of investors or the public interest; (2) impose any significant burden on competition; and (3) become operative for 30 days after the date of the filing, or such shorter time as the Commission may designate if consistent with the protection of investors and the public interest, the proposed rule change has become effective pursuant to Section 19(b)(3)(A) of the Act 
                    <SU>14</SU>
                    <FTREF/>
                     and Rule 19b-4(f)(6) thereunder.
                    <SU>15</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>14</SU>
                         15 U.S.C. 78s(b)(3)(A).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>15</SU>
                         17 CFR 240.19b-4(f)(6).
                    </P>
                </FTNT>
                <P>At any time within 60 days of the filing of the proposed rule change, the Commission may summarily abrogate such rule change if it appears to the Commission that such action is necessary or appropriate in the public interest, for the protection of investors, or otherwise in furtherance of the purposes of the Act. </P>
                <P>
                    A proposed rule change normally may not become operative prior to 30 days after the date of filing.
                    <SU>16</SU>
                    <FTREF/>
                     However, Rule 19b-4(f)(6)(iii) 
                    <SU>17</SU>
                    <FTREF/>
                     permits the Commission to designate a shorter time if such action is consistent with the protection of investors and the public interest. The Exchange has requested that the Commission waive the 30-day operative delay. The Commission believes that waiver of the 30 day operative delay is consistent with the protection of investors and the public interest because the proposed rule change would merely permit the continuation of the Pilot Program in its current form on an uninterrupted basis through and including April 6, 2008.
                    <SU>18</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>16</SU>
                         17 CFR 240.19b-4(f)(6)(iii). Rule 19b-4(f)(6)(iii) requires that a self-regulatory organization submit to the Commission written notice of its intent to file the proposed rule change, along with a brief description and text of the proposed rule change, at least five business days prior to the date of filing of the proposed rule change, or such shorter time as designated by the Commission. On March 26, 2007, the Exchange provided such notice to the Commission in the form of a draft version of the proposed rule change. Despite providing such notice to the Commission, the Exchange subsequently requested that the Commission waive the five-day prefiling requirement. The Exchange's request to waive the five-day prefiling requirement is moot given that the Exchange has satisfied it by submitting the draft version of the proposed rule change.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>17</SU>
                         17 CFR 240.19b-4(f)(6)(iii).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>18</SU>
                         For purposes only of waiving the 30-day operative delay, the Commission has considered the proposed rule's on efficiency, competition, and capital formation. 
                        <E T="03">See</E>
                         15 U.S.C. 78c(f).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">IV. Solicitation of Comments </HD>
                <P>Interested persons are invited to submit written data, views and arguments concerning the foregoing, including whether the proposed rule change is consistent with the Act. Comments may be submitted by any of the following methods: </P>
                <HD SOURCE="HD2">Electronic Comments</HD>
                <P>
                    • Use the Commission's Internet comment form (
                    <E T="03">http://www.sec.gov/rules/sro.shtml</E>
                    ); or 
                </P>
                <P>
                    • Send e-mail to 
                    <E T="03">rule-comments@sec.gov.</E>
                     Please include File Number SR-Amex-2007-33 on the subject line. 
                    <PRTPAGE P="18700"/>
                </P>
                <HD SOURCE="HD2">Paper Comments</HD>
                <P>• Send paper comments in triplicate to Nancy M. Morris, Secretary, Securities and Exchange Commission, 100 F Street, NE., Washington, DC 20549-1090. </P>
                <FP>
                    All submissions should refer to File Number SR-Amex-2007-33. This file number should be included on the subject line if e-mail is used. To help the Commission process and review your comments more efficiently, please use only one method. The Commission will post all comments on the Commission's Internet Web site (
                    <E T="03">http://www.sec.gov/rules/sro.shtml</E>
                    ). 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 filing also will be available for inspection and copying at the principal office of the Amex. All comments received will be posted without change; the Commission does not edit personal identifying information from submissions. You should submit only information that you wish to make available publicly. All submissions should refer to File Number SR-Amex-2007-33 and should be submitted by May 4, 2007. 
                </FP>
                <SIG>
                    <P>
                        For the Commission by the Division of Market Regulation, pursuant to delegated authority.
                        <SU>19</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>19</SU>
                             17 CFR 200.30-3(a)(12).
                        </P>
                    </FTNT>
                    <NAME>Florence E. Harmon, </NAME>
                    <TITLE>Deputy Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC> [FR Doc. E7-7054 Filed 4-12-07; 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-55595; File No. SR-CHX-2007-14] </DEPDOC>
                <SUBJECT>Self-Regulatory Organizations; Chicago Stock Exchange, Inc.; Notice of Filing and Immediate Effectiveness of Proposed Rule Change Relating to Participant Fees and Credits </SUBJECT>
                <DATE>April 6, 2007. </DATE>
                <P>
                    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/>
                     notice is hereby given that on March 23, 2007, the Chicago Stock Exchange, Inc. (“CHX” or “Exchange”) filed with the Securities and Exchange Commission (“Commission”) the proposed rule change as described in Items I, II, and III below, which Items have been substantially prepared by the Exchange. CHX has filed the proposal pursuant to Section 19(b)(3)(A) of the Act 
                    <SU>3</SU>
                    <FTREF/>
                     and Rule 19b-4(f)(2) thereunder,
                    <SU>4</SU>
                    <FTREF/>
                     which renders the proposal effective upon filing with the Commission. The Commission is publishing this notice to solicit comments on the proposed rule change from interested persons. 
                </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. 78s(b)(3)(A). 
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         17 CFR 240.19b-4(f)(2). 
                    </P>
                </FTNT>
                <HD SOURCE="HD1">I. Self-Regulatory Organization's Statement of the Terms of Substance of the Proposed Rule Change </HD>
                <P>
                    CHX proposes to amend its Fee Schedule to confirm that it will not charge a fee or pay a credit in connection with the execution, in the Matching System, of a single-sided order for 100 or more shares at a price less than $1.00 per share. The text of the proposed rule change is available at CHX, the Commission's Public Reference Room, and 
                    <E T="03">http://www.chx.com/rules/proposed_rules.htm</E>
                    . 
                </P>
                <HD SOURCE="HD1">II. Self-Regulatory Organization's Statement of the Purpose of, and Statutory Basis for, the Proposed Rule Change </HD>
                <P>In its filing with the Commission, CHX included statements concerning the purpose of and basis for the proposed rule change and discussed any comments it received on the proposed rule change. The text of these statements may be examined at the places specified in Item IV below. CHX has prepared summaries, set forth in Sections A, B, and C below, of the most significant aspects of such statements. </P>
                <HD SOURCE="HD2">A. Self-Regulatory Organization's Statement of the Purpose of, and Statutory Basis for, the Proposed Rule Change </HD>
                <HD SOURCE="HD3">1. Purpose </HD>
                <P>
                    The Exchange proposes to amend its Fee Schedule to confirm that it will not charge a fee or pay a credit in connection with the execution, in the Matching System, of a single-sided order for 100 or more shares at a price less than $1.00 per share. This provision is designed, in part, to confirm that the Exchange will not charge a fee that is greater than the maximum access fee set out in Rule 610(c)(2) of Regulation NMS.
                    <SU>5</SU>
                    <FTREF/>
                     It also confirms that the Exchange has determined that it would not be appropriate to provide a credit in connection with these no-cost executions. 
                </P>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         
                        <E T="03">See</E>
                         17 CFR 242.610(c)(2). 
                    </P>
                </FTNT>
                <HD SOURCE="HD3">2. Statutory Basis </HD>
                <P>
                    CHX believes that the proposed rule change is consistent with the provisions of Section 6 of the Act,
                    <SU>6</SU>
                    <FTREF/>
                     in general, and with Section 6(b)(4) of the Act,
                    <SU>7</SU>
                    <FTREF/>
                     in particular, in that the proposal provides for the equitable allocation of reasonable dues, fees, and other charges among its members. 
                </P>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         15 U.S.C. 78f. 
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         15 U.S.C. 78f(b)(4). 
                    </P>
                </FTNT>
                <HD SOURCE="HD2">B. Self-Regulatory Organization's Statement on Burden on Competition </HD>
                <P>The Exchange does not believe that the proposed rule change will result in any burden on competition that is not necessary or appropriate in furtherance of the purposes of the Act. </P>
                <HD SOURCE="HD2">C. Self-Regulatory Organization's Statement on Comments on the Proposed Rule Change Received From Members, Participants or Others </HD>
                <P>No written comments were either solicited or received. </P>
                <HD SOURCE="HD1">III. Date of Effectiveness of the Proposed Rule Change and Timing for Commission Action </HD>
                <P>
                    The foregoing rule change has become effective pursuant to Section 19(b)(3)(A)(ii) of the Act 
                    <SU>8</SU>
                    <FTREF/>
                     and subparagraph (f)(2) of Rule 19b-4 thereunder 
                    <SU>9</SU>
                    <FTREF/>
                     because it establishes or changes a due, fee, or other charge applicable only to a member imposed by the self-regulatory organization. Accordingly, the proposal is effective upon Commission receipt of the filing. At any time within 60 days of the filing of the proposed rule change, the Commission may summarily abrogate such rule change if it appears to the Commission that such action is necessary or appropriate in the public interest, for the protection of investors, or otherwise in furtherance of the purposes of the Act. 
                </P>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         15 U.S.C. 78s(b)(3)(A)(ii). 
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         17 CFR 240.19b-4(f)(2). 
                    </P>
                </FTNT>
                <HD SOURCE="HD1">IV. Solicitation of Comments </HD>
                <P>
                    Interested persons are invited to submit written data, views, and arguments concerning the foregoing, including whether the proposed rule change is consistent with the Act. Comments may be submitted by any of the following methods: 
                    <PRTPAGE P="18701"/>
                </P>
                <HD SOURCE="HD2">Electronic Comments </HD>
                <P>
                    • Use the Commission's Internet comment form (
                    <E T="03">http://www.sec.gov/rules/sro.shtml</E>
                    ); or 
                </P>
                <P>
                    • Send an e-mail to 
                    <E T="03">rule-comments@sec.gov</E>
                    . Please include File Number SR-CHX-2007-14 on the subject line. 
                </P>
                <HD SOURCE="HD2">Paper Comments </HD>
                <P>• Send paper comments in triplicate to Nancy M. Morris, Secretary, Securities and Exchange Commission, 100 F Street, NE, Washington, DC 20549-1090. </P>
                <FP>
                    All submissions should refer to File Number SR-CHX-2007-14. This file number should be included on the subject line if e-mail is used. To help the Commission process and review your comments more efficiently, please use only one method. The Commission will post all comments on the Commission's Internet Web site (
                    <E T="03">http://www.sec.gov/rules/sro.shtml</E>
                    ). 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 the filing also will be available for inspection and copying at the principal office of CHX. All comments received will be posted without change; the Commission does not edit personal identifying information from submissions. You should submit only information that you wish to make available publicly. All submissions should refer to File Number SR-CHX-2007-14 and should be submitted on or before May 4, 2007.
                    <FTREF/>
                </FP>
                <SIG>
                    <P>
                        For the Commission, by the Division of Market Regulation, pursuant to delegated authority.
                        <SU>10</SU>
                    </P>
                    <FTNT>
                        <P>
                            <SU>10</SU>
                             17 CFR 200.30-3(a)(12). 
                        </P>
                    </FTNT>
                    <NAME>Florence E. Harmon, </NAME>
                    <TITLE>Deputy Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. E7-6963 Filed 4-12-07; 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-55586; File No. SR-ISE-2007-19] </DEPDOC>
                <SUBJECT>Self-Regulatory Organizations; International Securities Exchange, LLC; Notice of Filing and Immediate Effectiveness of Proposed Rule Change Relating to Access to the Exchange by Sponsored Customers </SUBJECT>
                <DATE>April 5, 2007. </DATE>
                <P>
                    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/>
                     notice is hereby given that on March 13, 2007, the International Securities Exchange, LLC (“ISE” or “Exchange”) filed with the Securities and Exchange Commission (“Commission”) the proposed rule change as described in Items I and II below, which Items have been substantially prepared by ISE. The Exchange has filed the proposal as a “non-controversial” rule change pursuant to Section 19(b)(3)(A) of the Act 
                    <SU>3</SU>
                    <FTREF/>
                     and Rule 19b-4(f)(6) thereunder,
                    <SU>4</SU>
                    <FTREF/>
                     which renders it effective upon filing with the Commission. The Commission is publishing this notice to solicit comments on the proposed rule change from interested persons. 
                </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. 78s(b)(3)(A). 
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         17 CFR 240.19b-4(f)(6). 
                    </P>
                </FTNT>
                <HD SOURCE="HD1">I. Self-Regulatory Organization's Statement of the Terms of Substance of the Proposed Rule Change </HD>
                <P>
                    ISE proposes to amend ISE Rule 706 to permit Sponsored Customers of a Member to access the Exchange. The text of the proposed rule change is available at ISE, the Commission's Public Reference Room, and 
                    <E T="03">www.iseoptions.com</E>
                    . 
                </P>
                <HD SOURCE="HD1">II. Self-Regulatory Organization's Statement of the Purpose of, and Statutory Basis for, the Proposed Rule Change </HD>
                <P>In its filing with the Commission, ISE included statements concerning the purpose of and basis for the proposed rule change and discussed any comments it received on the proposed rule change. The text of these statements may be examined at the places specified in Item IV below. ISE has prepared summaries, set forth in Sections A, B, and C below, of the most significant aspects of such statements. </P>
                <HD SOURCE="HD2">A. Self-Regulatory Organization's Statement of the Purpose of, and Statutory Basis for, the Proposed Rule Change </HD>
                <HD SOURCE="HD3">1. Purpose </HD>
                <P>
                    This proposed rule change seeks to permit Sponsored Customers of Members to access the Exchange provided that a Sponsored Customer Agreement has been entered into with the Exchange by the Sponsored Customer, and provided certain other conditions are satisfied. The proposed revisions to Rule 706 outlines the requirements that Sponsoring Members and Sponsored Customers would be required to meet prior to engaging in a Sponsoring Member/Sponsored Customer relationship.
                    <SU>5</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         ISE notes that this proposed rule change will enable Sponsored Customers of Members to access both its Options Exchange, as per Rule 706, and its Stock Exchange, as per Rule 2100, which incorporates Rule 706 by cross-reference. 
                    </P>
                </FTNT>
                <P>A “Sponsored Customer” is a non-Member of the Exchange, such as an institutional investor, that trades under a Sponsoring Member's execution and clearing identity pursuant to a sponsorship arrangement between such non-Member and a Member. The Sponsoring Member must have documentation acknowledging it has full and complete responsibility for all trading activity conducted by its Sponsored Customer. A Sponsoring Member that provides access to a Sponsored Customer also has a continuing obligation to comply with all ISE rules and procedures and the federal securities laws and regulations. A Sponsoring Member must also continue to satisfy any agency obligations that may exist between itself and its Sponsored Customer. </P>
                <P>A Sponsored Customer's access to the Exchange is conditioned on the following requirements being met: Sponsored Customers would be required to enter into a sponsorship arrangement with a “Sponsoring Member,” which is defined as an ISE Member that has been designated by a Sponsored Customer to execute, clear and settle transactions on ISE. The sponsorship arrangement consists of three separate components. </P>
                <P>First, the Sponsored Customer would have to enter into and maintain a customer agreement with its Sponsoring Member, establishing a proper relationship and account through which the Sponsored Customer would be permitted to trade on ISE. </P>
                <P>
                    Second, the Sponsored Customer and its Sponsoring Member would have to enter into a written agreement that 
                    <PRTPAGE P="18702"/>
                    incorporates the following Sponsorship Provisions: 
                </P>
                <P>(1) The Sponsoring Member acknowledges and agrees that: (i) All orders entered by its Sponsored Customer and any person acting on behalf of or in the name of such Sponsored Customer and any executions occurring as a result of such orders are binding in all respects on the Sponsoring Member; and (ii) the Sponsoring Member is responsible for any and all actions taken by such Sponsored Customer and any person acting on behalf of or in the name of such Sponsored Customer. </P>
                <P>(2) The Sponsored Customer agrees that it would comply with the ISE Certificate of Formation, Constitution, Rules and procedures with regard to its activity on the Exchange as if the Sponsored Customer were an ISE Member. </P>
                <P>
                    (3) The Sponsored Customer agrees that it would maintain, keep current and provide to the Sponsoring Member a list of its Authorized Traders 
                    <SU>6</SU>
                    <FTREF/>
                     who would be permitted to obtain access to the Exchange on behalf of the Sponsored Customer(s). 
                </P>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         
                        <E T="03">See</E>
                         proposed ISE Rule 706, Supplementary Material .01(b)(2)(iv). 
                    </P>
                </FTNT>
                <P>(4) The Sponsored Customer agrees that it would familiarize its Authorized Traders with all of the Sponsored Customer's obligations under ISE Rules and would assure that they receive appropriate training prior to any use of or access to the Exchange. </P>
                <P>(5) The Sponsored Customer agrees that it would not permit anyone other than Authorized Traders to use or obtain access to the Exchange. </P>
                <P>(6) The Sponsored Customer agrees that it would take reasonable security precautions to prevent unauthorized use or access to the Exchange, including unauthorized entry of information into the System, or the information and data made available therein. The Sponsored Customer understands and agrees that it is responsible for any and all orders, trades and other messages and instructions entered, transmitted or received under identifiers, passwords and security codes of Authorized Traders, and for the trading and other consequences thereof. </P>
                <P>(7) The Sponsored Customer acknowledges its responsibility for establishing adequate procedures and controls that permit it to effectively monitor its employees, agents and customers' use of and access to the Exchange for compliance with the terms of the Sponsorship Provisions. </P>
                <P>(8) The Sponsored Customer agrees that it would pay when due all amounts, if any, payable to the Sponsoring Member, ISE or any other third parties that arise from the Sponsored Customer's access to and use of the Exchange. Such amounts would include, but would not be limited to, applicable exchange and regulatory fees. </P>
                <P>Third, the Sponsoring Member would have to provide ISE with an express acknowledgement of the Sponsoring Member's responsibility for the orders, executions and actions of its Sponsored Customer. </P>
                <P>
                    As a further condition to access to the Exchange, each Member would be required to maintain an up-to-date list of persons who could obtain access to the Exchange on behalf of the Sponsoring Member or the Sponsoring Member's Sponsored Customers, 
                    <E T="03">i.e.</E>
                    , Authorized Traders, and provide the list to ISE upon request. In addition, each Member would have to have reasonable procedures to ensure that all of its Authorized Traders maintain the physical security of ISE and otherwise comply with ISE Rules. If ISE determines that an Authorized Trader has caused a Member to violate ISE Rules, ISE could direct the Member to suspend or withdraw the person's status as an Authorized Trader. 
                </P>
                <P>
                    The Sponsoring Member/Sponsored Customer relationship would allow a Member to grant access to ISE to their customers while confirming that those customers who do have access to ISE have appropriate procedures in place to comply with ISE rules. Furthermore, the identity of all individuals with access (
                    <E T="03">i.e.</E>
                    , Authorized Traders) would have to be disclosed to the Exchange, giving the Exchange better information in the event that the Exchange determines to take action because its systems have been used inappropriately. 
                </P>
                <HD SOURCE="HD3">2. Statutory Basis </HD>
                <P>
                    ISE believes that the proposed rule change is consistent with the provisions of Section 6 of the Act,
                    <SU>7</SU>
                    <FTREF/>
                     in general, and with Section 6(b)(5) of the Act,
                    <SU>8</SU>
                    <FTREF/>
                     in particular, in that the proposal is designed 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. 
                </P>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         15 U.S.C. 78f. 
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         15 U.S.C. 78f(b)(5). 
                    </P>
                </FTNT>
                <HD SOURCE="HD2">B. Self-Regulatory Organization's Statement on Burden on Competition </HD>
                <P>ISE does not believe that the proposed rule change will result in any burden on competition that is not necessary or appropriate in furtherance of the purposes of the Act. </P>
                <HD SOURCE="HD2">C. Self-Regulatory Organization's Statement on Comments on the Proposed Rule Change Received From Members, Participants or Others </HD>
                <P>The Exchange has not solicited, and does not intend to solicit, comments on this proposed rule change. The Exchange has not received any unsolicited written comments from members or other interested parties. </P>
                <HD SOURCE="HD1">III. Date of Effectiveness of the Proposed Rule Change and Timing for Commission Action </HD>
                <P>
                    Because the forgoing rule change does not: (1) Significantly affect the protection of investors or the public interest; (2) impose any significant burden on competition; and (3) become operative for 30 days after the date of this filing, or such shorter time as the Commission may designate, it has become effective pursuant to Section 19(b)(3)(A) of the Act 
                    <SU>9</SU>
                    <FTREF/>
                     and Rule 19b-4(f)(6) thereunder.
                    <SU>10</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         15 U.S.C. 78s(b)(3)(A). 
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         17 CFR 240.19b-4(f)(6). 
                    </P>
                </FTNT>
                <P>
                    A proposed rule change filed under 19b-4(f)(6) normally may not become operative prior to 30 days after the date of filing.
                    <SU>11</SU>
                    <FTREF/>
                     However, Rule 19b-4(f)(6)(iii) 
                    <SU>12</SU>
                    <FTREF/>
                     permits the Commission to designate a shorter time if such action is consistent with the protection of investors and the public interest. The Exchange has requested that the Commission waive the 30-day operative delay. The Commission believes that waiving the 30-day operative delay is consistent with the protection of investors and the public interest because such waiver would permit ISE Members to immediately provide its Sponsored Customers access to ISE's markets.
                    <SU>13</SU>
                    <FTREF/>
                     For this reason, the Commission designates the proposed rule change to be operative upon filing with the Commission.
                    <SU>14</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         17 CFR 240.19b-4(f)(6)(iii). In addition, Rule 19b-4(f)(6)(iii) requires that a self-regulatory organization submit to the Commission written notice of its intent to file the proposed rule change, along with a brief description and text of the proposed rule change, at least five business days prior to the date of filing of the proposed rule change, or such shorter time as designated by the Commission. The Commission has decided to waive the five-day pre-filing notice requirement. 
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         The Commission notes that proposed ISE Rule 706, Supplementary Material .01 is substantially similar to NYSE Arca, Inc. Rule 7.29. 
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>14</SU>
                         For the purposes only of waiving the 30-day operative delay, the Commission has considered the proposed rule's impact on efficiency, competition, and capital formation. 
                        <E T="03">See</E>
                         15 U.S.C. 78c(f). 
                    </P>
                </FTNT>
                <P>
                    At any time within 60 days of the filing of such proposed rule change the Commission may summarily abrogate such rule change if it appears to the Commission that such action is 
                    <PRTPAGE P="18703"/>
                    necessary or appropriate in the public interest, for the protection of investors or otherwise in furtherance of the purposes of the Act. 
                </P>
                <HD SOURCE="HD1">IV. Solicitation of Comments </HD>
                <P>Interested persons are invited to submit written data, views, and arguments concerning the foregoing, including whether the proposed rule change is consistent with the Act. Comments may be submitted by any of the following methods: </P>
                <HD SOURCE="HD2">Electronic Comments </HD>
                <P>
                    • Use the Commission's Internet comment form (
                    <E T="03">http://www.sec.gov/rules/sro.shtml</E>
                    ); or 
                </P>
                <P>
                    • Send an e-mail to 
                    <E T="03">rule-comments@sec.gov.</E>
                     Please include File Number SR-ISE-2007-19 on the subject line. 
                </P>
                <HD SOURCE="HD2">Paper Comments </HD>
                <P>• Send paper comments in triplicate to Nancy M. Morris, Secretary, Securities and Exchange Commission, 100 F Street, NE, Washington, DC 20549-1090. </P>
                <FP>
                    All submissions should refer to File Number SR-ISE-2007-19. This file number should be included on the subject line if e-mail is used. To help the Commission process and review your comments more efficiently, please use only one method. The Commission will post all comments on the Commission's Internet Web site (
                    <E T="03">http://www.sec.gov/rules/sro.shtml</E>
                    ). 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 the filing also will be available for inspection and copying at the principal office of ISE. All comments received will be posted without change; the Commission does not edit personal identifying information from submissions. You should submit only information that you wish to make available publicly. All submissions should refer to File Number SR-ISE-2007-19 and should be submitted on or before May 4, 2007. 
                </FP>
                <SIG>
                    <P>
                        For the Commission, by the Division of Market Regulation, pursuant to delegated authority.
                        <SU>15</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>15</SU>
                             17 CFR 200.30-3(a)(12). 
                        </P>
                    </FTNT>
                    <NAME>Florence E. Harmon, </NAME>
                    <TITLE>Deputy Secretary. </TITLE>
                </SIG>
            </PREAMB>
            <FRDOC> [FR Doc. E7-6961 Filed 4-12-07; 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-55604; File No. SR-NASD-2006-109] </DEPDOC>
                <SUBJECT>Self-Regulatory Organizations; National Association of Securities Dealers, Inc.; Notice of Filing of Proposed Rule Change and Amendment Nos. 1 and 2 Thereto Relating to Representation of Parties in Arbitration and Mediation </SUBJECT>
                <DATE> April 9, 2007. </DATE>
                <P>
                    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/>
                     notice is hereby given that the National Association of Securities Dealers, Inc. (“NASD”), through its wholly owned subsidiary, NASD Dispute Resolution, Inc. (“NASD Dispute Resolution”) filed with the Securities and Exchange Commission (“SEC” or “Commission”) on September 14, 2006, and amended on November 9, 2006 (Amendment No. 1) 
                    <SU>3</SU>
                    <FTREF/>
                     and February 23, 2007 (Amendment No. 2),
                    <SU>4</SU>
                    <FTREF/>
                     the proposed rule change as described in Items I, II, and III below, which Items have been prepared by NASD Dispute Resolution. The Commission is publishing this notice to solicit comments on the proposed rule change, as amended, from interested persons. 
                </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>
                         Amendment No. 1 makes clarifying changes to the rule text emphasizing that attorneys may represent parties in NASD's forum, unless state law prohibits such representation. Amendment No. 1 also makes several clarifying and technical changes to the proposed rule filing. 
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         Amendment No. 2 makes clarifying changes to the rule text concerning restrictions on non-attorney representation. Amendment No. 2 also includes minor organizational changes to a paragraph and footnotes describing the American Bar Association Model Rule of Professional Conduct 5.5. 
                    </P>
                </FTNT>
                <HD SOURCE="HD1">I. Self-Regulatory Organization's Statement of the Terms of Substance of the Proposed Rule Change </HD>
                <P>
                    NASD Dispute Resolution is proposing to amend the Code of Arbitration Procedure for Customer Disputes (“Customer Code”), the Code of Arbitration Procedure for Industry Disputes (“Industry Code”), and the NASD Code of Arbitration Procedure (“Code”) to address representation of parties in arbitration and mediation.
                    <SU>5</SU>
                    <FTREF/>
                     Below is the text of the proposed rule change. Proposed new language is in italics; proposed deletions are in brackets. 
                </P>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         The proposed rule change contemplates changes to Rules 12208 and 13208 of the Customer and Industry Codes, which restate old Rule 10316. 
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 55158 (Jan. 24, 2007); 72 FR 4574 (Jan. 31, 2007) (File Nos. SR-NASD-2003-158 and SR-NASD-2004-011) (Order Approving Proposed Rule Change and Amendments 1, 2, 3, and 4 to Amend NASD Arbitration Rules for Customer Disputes and Notice of Filing and Order Granting Accelerated Approval of Amendments 5, 6, and 7 Thereto; Order Approving Proposed Rule Change and Amendments 1, 2, 3, and 4 to Amend NASD Arbitration Rules for Industry Disputes and Notice of Filing and Order Granting Accelerated Approval of Amendments 5, 6, and 7 Thereto). The changes to Proposed Rule 10407 reflect changes to the new NASD Code of Mediation Procedure. 
                        <E T="03">See</E>
                         Securities Exchange Act Rel. No. 52705 (Oct. 31, 2005); 70 FR 67525 (Nov. 7, 2005) (SR-NASD-2004-013). The new NASD Code of Mediation Procedure is currently included in the Code, but will be removed and renumbered as a separate Code now that the Customer and Industry Codes have been approved. 
                    </P>
                </FTNT>
                <STARS/>
                <HD SOURCE="HD1">Customer Code </HD>
                <FP>12208. Representation of Parties </FP>
                <HD SOURCE="HD2">(a) Representation by a Party </HD>
                <P>
                    <E T="03">Parties may represent themselves in an arbitration held in a United States hearing location. A member of a partnership may represent the partnership; and a bona fide officer of a corporation, trust, or association may represent the corporation, trust, or association.</E>
                </P>
                <HD SOURCE="HD2">(b) Representation by an Attorney </HD>
                <P>
                    At 
                    <E T="03">any stage of an arbitration proceeding held in a United States hearing location,</E>
                     [All] 
                    <E T="03">all</E>
                     parties 
                    <E T="03">shall</E>
                     have the right to be represented by [counsel during any stage of an arbitration] 
                    <E T="03">an attorney at law in good standing and admitted to practice before the Supreme Court of the United States or the highest court of any state of the United States, the District of Columbia, or any commonwealth, territory, or possession of the United States, unless state law prohibits such representation.</E>
                </P>
                <HD SOURCE="HD2">(c) Representation by Others </HD>
                <P>
                    <E T="03">Parties may be represented in an arbitration by a person who is not an attorney, unless:</E>
                </P>
                <P>
                    • 
                    <E T="03">state law prohibits such representation, or</E>
                </P>
                <P>
                    • 
                    <E T="03">the person is currently suspended or barred from the securities industry in any capacity, or</E>
                </P>
                <P>
                    • 
                    <E T="03">the person is currently suspended from the practice of law or disbarred.</E>
                    <PRTPAGE P="18704"/>
                </P>
                <HD SOURCE="HD2">(d) Qualifications of Representative </HD>
                <P>
                    <E T="03">Issues regarding the qualifications of a person to represent a party in arbitration are governed by applicable law and may be determined by an appropriate court or other regulatory agency. In the absence of a court order, the arbitration proceeding shall not be stayed or otherwise delayed pending resolution of such issues.</E>
                </P>
                <STARS/>
                <HD SOURCE="HD1">Industry Code </HD>
                <FP>13208. Representation of Parties </FP>
                <HD SOURCE="HD2">(a) Representation by a Party </HD>
                <P>
                    <E T="03">Parties may represent themselves in an arbitration held in a United States hearing location. A member of a partnership may represent the partnership; and a bona fide officer of a corporation, trust, or association may represent the corporation, trust, or association.</E>
                </P>
                <HD SOURCE="HD2">(b) Representation by an Attorney </HD>
                <P>
                    <E T="03">At any stage of an arbitration proceeding held in a United States hearing location,</E>
                     [All] 
                    <E T="03">all</E>
                     parties 
                    <E T="03">shall</E>
                     have the right to be represented by [counsel during any stage of an arbitration] 
                    <E T="03">an attorney at law in good standing and admitted to practice before the Supreme Court of the United States or the highest court of any state of the United States, the District of Columbia, or any commonwealth, territory, or possession of the United States, unless state law prohibits such representation.</E>
                </P>
                <HD SOURCE="HD2">(c) Representation by Others </HD>
                <P>
                    <E T="03">Parties may be represented in an arbitration by a person who is not an attorney, unless:</E>
                </P>
                <P>
                    • 
                    <E T="03">state law prohibits such representation, or</E>
                </P>
                <P>
                    • 
                    <E T="03">the person is currently suspended or barred from the securities industry in any capacity, or</E>
                </P>
                <P>
                    • 
                    <E T="03">the person is currently suspended from the practice of law or disbarred.</E>
                </P>
                <HD SOURCE="HD2">(d) Qualifications of Representative </HD>
                <P>
                    <E T="03">Issues regarding the qualifications of a person to represent a party in arbitration are governed by applicable law and may be determined by an appropriate court or other regulatory agency. In the absence of a court order, the arbitration proceeding shall not be stayed or otherwise delayed pending resolution of such issues.</E>
                </P>
                <STARS/>
                <HD SOURCE="HD1">Code of Arbitration Procedure </HD>
                <FP>
                    10407. 
                    <E T="03">Representation of Parties</E>
                </FP>
                <HD SOURCE="HD2">(a) Representation by Party </HD>
                <P>
                    <E T="03">Parties may represent themselves in mediation held in a United States hearing location. A member of a partnership may represent the partnership; and a bona fide officer of a corporation, trust, or association may represent the corporation, trust, or association.</E>
                </P>
                <HD SOURCE="HD2">(b) Representation by an Attorney </HD>
                <P>
                    <E T="03">At any stage of a mediation proceeding held in a United States hearing location, all parties shall have the right to be represented by an attorney at law in good standing and admitted to practice before the Supreme Court of the United States or the highest court of any state of the United States, the District of Columbia, or any commonwealth, territory, or possession of the United States, unless state law prohibits such representation.</E>
                </P>
                <HD SOURCE="HD2">(c) Representation by Others </HD>
                <P>
                    <E T="03">Parties may be represented in mediation by a person who is not an attorney, unless:</E>
                </P>
                <P>
                    • 
                    <E T="03">state law prohibits such representation, or</E>
                </P>
                <P>
                    • 
                    <E T="03">the person is currently suspended or barred from the securities industry in any capacity, or</E>
                </P>
                <P>
                    • 
                    <E T="03">the person is currently suspended from the practice of law or disbarred.</E>
                </P>
                <HD SOURCE="HD2">(d) Qualifications of Representatives </HD>
                <P>
                    <E T="03">Issues regarding the qualifications of a person to represent a party in mediation are governed by applicable law and may be determined by an appropriate court or other regulatory agency. In the absence of a court order, the mediation proceeding shall not be delayed pending resolution of such issues.</E>
                </P>
                <FP>
                    [10407] 
                    <E T="03">10408.</E>
                     Mediator Selection 
                </FP>
                <P>(a)-(d) No change.</P>
                <FP>
                    [10408] 
                    <E T="03">10409.</E>
                     Limitation on Liability 
                </FP>
                <P>No change. </P>
                <FP>
                    [10409] 
                    <E T="03">10410.</E>
                     Mediation Ground Rules 
                </FP>
                <P>(a)-(g) No change. </P>
                <FP>
                    [10410] 
                    <E T="03">10411.</E>
                     Mediation Fees 
                </FP>
                <P>(a)-(c) No change. </P>
                <STARS/>
                <HD SOURCE="HD1">II. Self-Regulatory Organization's Statement of the Purpose of, and Statutory Basis for, the Proposed Rule Change </HD>
                <P>In its filing with the Commission, NASD included statements concerning the purpose of and basis for the proposed rule change and discussed any comments it received on the proposed rule change. The text of these statements may be examined at the places specified in Item IV below. NASD has prepared summaries, set forth in Sections A, B, and C below, of the most significant aspects of such statements. </P>
                <HD SOURCE="HD2">A. Self-Regulatory Organization's Statement of the Purpose of, and Statutory Basis for, the Proposed Rule Change </HD>
                <HD SOURCE="HD3"> 1. Purpose </HD>
                <HD SOURCE="HD3">Background </HD>
                <P>NASD Dispute Resolution believes a rule is needed to clarify the issue of representation of parties in dispute resolution. NASD Rule 10316 states that all parties shall have the right to representation by counsel at any stage of the proceedings. The rule provides no guidance on the kind of representatives who are permitted to practice in the NASD dispute resolution forum, or on the qualifications those representatives must have to participate in the forum. Moreover, Rule 10316 does not address a growing trend in American jurisprudence, the multi-jurisdictional practice of law. </P>
                <P>
                    The multi-jurisdictional practice of law occurs when attorneys, licensed in one United States (U.S.) jurisdiction, practice law in a jurisdiction in which they are not licensed. In the area of dispute resolution, for example, it is common for an attorney licensed to practice law in one state to represent a client in a dispute resolution proceeding in another state in which the attorney is not licensed. Although this practice is permitted in many jurisdictions, it may be a violation of certain other states' unauthorized practice of law provisions. Until recent years, most states had taken no action against this practice. However, two state courts have found that out-of-state attorneys must meet certain conditions in order to participate in a dispute resolution proceeding in their jurisdictions.
                    <SU>6</SU>
                    <FTREF/>
                     In light of these developments, the American Bar Association (ABA) amended its Model Rule of Professional Conduct 5.5 (ABA Model Rule 5.5) to promote the multi-jurisdictional practice of law.
                    <SU>7</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         
                        <E T="03">See Birbrower, Montalbano, Condo &amp; Frank</E>
                         v. 
                        <E T="03">Superior Court,</E>
                         949 P.2d 1 (Cal. 1998); 
                        <E T="03">see also Florida Bar</E>
                         v. 
                        <E T="03">Rapoport</E>
                        , 845 So. 2d 874, 2003 Fla. LEXIS 250 (Fla. 2003). 
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         ABA Model Rule 5.5, as amended, would allow a United States lawyer, admitted in one United States jurisdiction, to engage in certain types of legal activity in another United States jurisdiction where he is not licensed to practice, without being deemed to be engaging in the unauthorized practice of law. For purposes of the dispute resolution forum, ABA Model Rule 5.5, as amended, states, in relevant part, that a lawyer may provide legal services on a temporary basis in an out-of-state jurisdiction that are in or reasonably related to a pending or potential arbitration, mediation, or other alternative dispute resolution proceeding in the jurisdiction or another jurisdiction, if the services 
                        <PRTPAGE/>
                        arise out of or are reasonably related to the lawyer's practice in a jurisdiction in which the lawyer is admitted to practice and are not services for which the forum requires pro hac vice admission. This rule is sometimes referred to as the temporary practice rule. Twenty-seven states have either adopted ABA Model Rule 5.5 or a similar version of the rule or currently have a temporary practice rule in effect. American Bar Association, Charts on State Adoption of MJP Proposals (visited Aug. 23, 2006) 
                        <E T="03">http://www.abanet.org/cpr/mjp/state_adoption.html</E>
                        . Other states have adopted a temporary practice rule that, like ABA Model Rule 5.5, allows an attorney not licensed in a state to provide certain types of legal services in the state on a limited basis. The laws of Michigan and Virginia specifically authorize occasional or incidental practice by out-of-state lawyers. 
                        <E T="03">See</E>
                         Mich. Comp. Law Ann. sec. 600.916 and Va. State Bar Rule, Pt. 6, sec. 1(C). 
                    </P>
                </FTNT>
                <PRTPAGE P="18705"/>
                <P>Accordingly, NASD proposes to codify its current practice of permitting the multi-jurisdictional practice of law in NASD's dispute resolution forum to the extent permitted under applicable state law. NASD also proposes to codify its current practice which allows non-attorney representatives to represent parties in arbitration or mediation. </P>
                <HD SOURCE="HD2">Previous Proposal Relating to Representation in Arbitration and Mediation </HD>
                <P>
                    On February 9, 2005, NASD filed a proposed rule change with the Commission to address attorney representation in arbitration and mediation.
                    <SU>8</SU>
                    <FTREF/>
                     The proposed rule change would have: 
                </P>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         
                        <E T="03">See</E>
                         File No. SR-NASD-2005-023. 
                    </P>
                </FTNT>
                <P>• Allowed parties to represent themselves in an arbitration or mediation; </P>
                <P>• Allowed parties to be represented by an attorney at law admitted to practice before a U.S. jurisdiction at any stage of the proceeding; and </P>
                <P>• Deferred to the states any issues regarding qualifications of a person to represent a party. </P>
                <P>
                    NASD amended this proposal on July 8, 2005 to clarify that it was intended to address the issue of multi-jurisdictional practice of law by attorneys, and was not intended to address the issue of representation by non-attorneys in arbitration or mediation proceedings.
                    <SU>9</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         
                        <E T="03">Id.</E>
                         at Amendment No. 1. 
                    </P>
                </FTNT>
                <P>
                    As amended, the attorney representation proposal was published in the 
                    <E T="04">Federal Register</E>
                     on July 21, 2005.
                    <SU>10</SU>
                    <FTREF/>
                     The SEC received fifteen comments, which primarily focused on two issues: Whether the rule should preempt state law regarding attorney licensing, and whether the rule should prohibit non-attorneys from practicing in NASD's forum. The comments and NASD's response are discussed in subsection C below. 
                </P>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         
                        <E T="03">See</E>
                         Securities Exchange Act Rel. No. 34-52045 (July 15, 2005); 70 FR 42123 (July 21, 2005) (File No. SR-NASD-2005-023). 
                    </P>
                </FTNT>
                <P>Based on the comments received on the attorney representation proposal, as amended, NASD recognized that the proposal may have been ambiguous. NASD did not intend to change current practice in the forum regarding representation of parties by non-attorneys, or to preempt state law on the issue of attorney licensing. Because the comments indicated that these positions were unclear, NASD withdrew its proposal. The current proposed rule change addresses representation of parties by themselves, by attorneys and by non-attorneys in arbitration and mediation. </P>
                <HD SOURCE="HD2">Representation of Parties by Themselves, Attorneys and Non-Attorneys in Arbitration and Mediation </HD>
                <P>NASD is proposing to amend Rules 12208 and 13208 of the Customer and Industry Codes, respectively, and Rule 10407 of the Code to clarify that in both arbitration and mediation: (1) Parties may represent themselves; (2) parties may be represented by an attorney, provided certain criteria are met; (3) parties may be represented by a person who is not an attorney, unless state law prohibits such representation or the person is currently suspended or barred from the securities industry in any capacity or is an attorney who is currently suspended from the practice of law or disbarred; and (4) issues regarding qualifications of a representative are governed by applicable law. </P>
                <P>First, the proposed rule change codifies current practice by explicitly stating that parties may represent themselves in arbitration. </P>
                <P>
                    Second, the proposed rule change codifies current practice permitting the multi-jurisdictional practice of law by attorneys in the NASD dispute resolution forum to the extent permitted by state law. In addition, the proposed rule change states that if a party chooses to be represented by an attorney, the attorney must be licensed to practice in a U.S. jurisdiction and be in good standing in that jurisdiction.
                    <SU>11</SU>
                    <FTREF/>
                     NASD believes that requiring an attorney to be licensed in a U.S. jurisdiction and to be in good standing in that jurisdiction will protect investors by prohibiting individuals who have been suspended from the practice of law or disbarred from representing parties in the NASD forum. Further, the requirement that an attorney must be licensed to practice in a U.S. jurisdiction sets a standard of practice for the arbitration forum that is consistent with the other rules and proceedings of NASD. In particular, Rule 9141(b) of the NASD Code of Procedure states, in relevant part, that a person may be represented in any disciplinary proceeding by an attorney at law admitted to practice before the highest court of any state of the United States, the District of Columbia, or any commonwealth, territory, or possession of the United States.
                    <SU>12</SU>
                    <FTREF/>
                     The proposed rule change also is consistent with Rule 102(b) of the SEC Rules of Practice, which states that, “[i]n any proceeding, a person may be represented by an attorney at law admitted to practice before the Supreme Court of the United States or the highest court of any State * * *” 
                    <SU>13</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         The requirement to be licensed to practice in a U.S. jurisdiction and be in good standing in that jurisdiction is in addition to and not in lieu of the requirement that an attorney must comply with applicable laws of the relevant jurisdiction. As previously noted, while the multi-jurisdictional practice of law may be permitted in many jurisdictions, it may constitute a violation of certain states' unauthorized practice of law provisions. 
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         This rule has been enforced in NASD Enforcement proceedings. In two similar cases, a respondent's answer was stricken from the record because the respondent's representative had not indicated that he was a licensed attorney. 
                        <E T="03">See</E>
                         NASDR Office of the Hearing Officers, OHO Order 97-15 (C01970032) (visited Aug. 24, 2006), available at: 
                        <E T="03">http://www.nasd.com/web/groups/enforcement/documents/oho_disciplinary_orders/nasdw_007839.pdf</E>
                        ; 
                        <E T="03">see also</E>
                         OHO Order 98-10 (C10970176) (visited Aug. 24, 2006), available at: 
                        <E T="03">http://www.nasd.com/web/groups/enforcement/documents/oho_disciplinary_orders/nasdw_007695.pdf</E>
                        . 
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         
                        <E T="03">See</E>
                         SEC Rules of Practice, 17 CFR § 201.102(b) (2004). 
                    </P>
                </FTNT>
                <P>Third, the proposed rule change addresses the representation of parties by non-attorneys in the NASD forum. Under the proposed rule change, parties may be represented in an arbitration or mediation by a person who is not an attorney, unless state law prohibits such representation or the person is currently suspended or barred from the securities industry in any capacity or is an attorney who is currently suspended from the practice of law or disbarred. </P>
                <P>
                    This provision would be applicable to all arbitration claims. NASD understands, however, that it may be difficult for investors with claims of less than $100,000 to retain an attorney on a contingency-fee basis because the attorney may believe that the attorney's share of the award might be too small to justify the effort. In these circumstances, NASD believes that investors should be able to seek other assistance to resolve their arbitration or mediation claims for a more affordable fee.
                    <SU>14</SU>
                    <FTREF/>
                     At the same time, NASD believes 
                    <PRTPAGE P="18706"/>
                    that such non-attorney representatives should not be persons who have been found by a regulatory body in essence to be unfit to represent clients or to conduct securities business with the public. Thus, to protect investors, the rule would prohibit non-attorney representatives who are currently suspended or barred from the securities industry, or attorneys who are currently suspended from the practice of law or disbarred, from representing parties in the NASD dispute resolution forum. While NASD remains concerned about some aspects of non-attorney representation, NASD does not wish to prohibit investors from retaining a non-attorney representative if that person is the only affordable representation available, and the requirements of the proposed rule are met. 
                </P>
                <FTNT>
                    <P>
                        <SU>14</SU>
                         Consistent with current practice, the proposed rule would allow a relative, friend or associate to 
                        <PRTPAGE/>
                        represent or assist a person (
                        <E T="03">e.g.</E>
                        , an elderly or disabled person) with his or her arbitration or mediation. In addition, law school securities arbitration clinics can provide investors with affordable legal representation. NASD notes that a securities arbitration clinic also can help an investor who has a smaller claim but is unable to hire an attorney, provided the investor qualifies for assistance. 
                        <E T="03">See</E>
                         How to Find an Attorney (for more information on clinic locations and eligibility requirements) (visited Sept. 13, 2006), available at: 
                        <E T="03">&lt;http://www.nasd.com/ArbitrationMediation/StartanArbitrationorMediation/HowtoFindanAttorney/index.htm</E>
                        &gt;.
                    </P>
                </FTNT>
                <P>Last, the proposed rule change would allow an attorney to represent a client in an NASD arbitration or mediation held in any U.S. hearing location, regardless of the jurisdiction in which the attorney is licensed. An attorney's ability to represent clients in a jurisdiction in which he or she is not licensed, however, would be subject to the applicable law of that jurisdiction. The proposed rule change is not intended to preempt state law; it is intended to reflect current practice in the forum which, based on experience, indicates that the outcome of a dispute resolution proceeding depends more on the level of knowledge, training and skill of the attorneys, rather than the jurisdiction from which the attorneys received their license to practice. </P>
                <HD SOURCE="HD3">2. Statutory Basis </HD>
                <P>
                    NASD believes that the proposed rule change is consistent with the provisions of Section 15A(b)(6) of the Act,
                    <SU>15</SU>
                    <FTREF/>
                     which requires, among other things, that NASD's rules must be designed to prevent fraudulent and manipulative acts and practices, to promote just and equitable principles of trade, and, in general, to protect investors and the public interest. NASD believes that the proposed rule change balances the needs of investors to have access to representation, particularly in small cases, with NASD's responsibility to protect investors, the integrity of its forum, and the public interest. 
                </P>
                <FTNT>
                    <P>
                        <SU>15</SU>
                         15 U.S.C. 78o-3(b)(6).
                    </P>
                </FTNT>
                <HD SOURCE="HD2">B. Self-Regulatory Organization's Statement on Burden on Competition </HD>
                <P>NASD does not believe that the proposed rule change will result in any burden on competition that is not necessary or appropriate in furtherance of the purposes of the Act, as amended. </P>
                <HD SOURCE="HD2">C. Self-Regulatory Organization's Statement on Comments on the Proposed Rule Change Received From Members, Participants, or Others </HD>
                <P>
                    Written comments were neither solicited nor received by NASD. The SEC received fifteen comments on the attorney representation proposal that it published for comment on July 21, 2005.
                    <SU>16</SU>
                    <FTREF/>
                     Commenters primarily focused on two issues: Whether the rule should preempt state law regarding attorney licensing, and whether the rule should prohibit non-attorneys from practicing in NASD's forum. 
                </P>
                <FTNT>
                    <P>
                        <SU>16</SU>
                         Comments were submitted by Timothy A. Canning, Esq., Law Offices of Timothy A. Canning, dated February 11, 2005 (“Canning I Letter”); Albert A. Rapoport, Esq., dated June 20, 2005 (“Rapoport Letter”); Joseph C. Korsak, Esq., Law Office of Joseph C. Korsak, dated July 22, 2005 (“Korsak Letter”); Michael Firestein, Esq. and Navid Yadegar, Esq., Proskauer Rose LLP, dated August 1, 2005 (“Firestein Letter”); Rodney J. Heggy, Esq., Heggy &amp; Associates, LLC, dated August 4, 2005 (“Heggy Letter”); Richard L. Sacks, Securities Arbitration Consultant, dated August 9, 2005 (“Sacks Letter”); Rosemary Shockman, President, Public Investors Arbitration Bar Association, dated August 9, 2005 (“PIABA Letter”); Joseph O'Donnell, dated August 10, 2005 (“O'Donnell Letter”); Irwin G. Stein, dated August 10, 2005 (“Stein Letter”); Montgomery G. Griffin, Esq., Securities Arbitration Offices of Montgomery G. Griffin, dated August 10, 2005 (“Griffin Letter”); Timothy A. Canning, Esq., Law Offices of Timothy A. Canning, dated August 10, 2005 (“Canning II Letter”); Kevin P. Takacs, CCO, Dominion Investor Services, Inc., dated August 11, 2005 (“Takacs Letter”); Jill I. Gross, Director of Advocacy and Barbara Black, Director of Research, Pace Investor Rights Project, dated August 11, 2005 (“Pace Letter”); and Stephen C. Krosschell, Esq., Goodman &amp; Nekvasil, P.A., dated August 11, 2005 (“Krosschell Letter”). The letter received from Marie W. Hayes, dated March 25, 2005, does not comment on the proposed rule change.
                    </P>
                </FTNT>
                <P>
                    With respect to the state preemption issue, several commenters agreed that state law should control whether attorneys may participate in arbitrations in a state in which they are not licensed.
                    <SU>17</SU>
                    <FTREF/>
                     These commenters stated that representatives should be licensed legal practitioners who are regulated and have demonstrated a minimum level of competence required to represent clients. Several other commenters opposed the provision of the proposal that would allow state law to control attorney-licensure issues, stating that the provision could result in delays in arbitration proceedings as representatives make the qualifications of an out-of-state representative the focus of the proceedings.
                    <SU>18</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>17</SU>
                         
                        <E T="03">See</E>
                         Firestein Letter, Heggy Letter, Pace Letter, PIABA Letter and Rapoport Letter.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>18</SU>
                         
                        <E T="03">See</E>
                         Canning I &amp; II Letters, Korsak Letter, Krosschell Letter, Sacks Letter and Stein Letter. 
                    </P>
                </FTNT>
                <P>
                    Other commenters addressed whether the proposal would prohibit, in effect, non-attorneys from practicing in NASD's forum. Several commenters contended that the proposal should address non-attorney representation and should allow non-attorneys to practice in the forum.
                    <SU>19</SU>
                    <FTREF/>
                     These commenters argued that the proposal attempted to deny investors access to qualified non-attorney representatives who have securities industry experience and are willing to accept cases that are too small to enable investors to retain a securities attorney. Other commenters contended that the proposal should prohibit compensated non-attorney representation in securities arbitration, stating that the lack of legal training makes non-attorneys less knowledgeable or competent to deal fully with the laws and issues that arise in an arbitration proceeding.
                    <SU>20</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>19</SU>
                         
                        <E T="03">See</E>
                        , Griffin Letter, O'Donnell Letter, Rapoport Letter, Sacks Letter, Stein Letter and Takacs Letter.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>20</SU>
                         
                        <E T="03">See</E>
                         Firestein Letter, Heggy Letter, Korsak Letter, Pace Letter and PIABA Letter.
                    </P>
                </FTNT>
                <P>As noted above, based on the disparate comments received on the proposal, NASD recognized that the proposal may not have been clear. NASD did not intend to change current practice in the forum regarding representation of parties by non-attorneys; nor did it intend to preempt state law on the issue of attorney licensing. Because the comments indicated that these positions were unclear, NASD has withdrawn the attorney representation proposal and is filing this new proposal to replace it. </P>
                <HD SOURCE="HD1">III. Date of Effectiveness of the Proposed Rule Change and Timing for Commission Action</HD>
                <P>
                    Within 35 days of the date of publication of this notice in the 
                    <E T="04">Federal Register</E>
                     or within such longer period (i) as the Commission may designate up to 90 days of such date if it finds such longer period to be appropriate and publishes its reasons for so finding or (ii) as to which the self-regulatory organization consents, the Commission will: 
                </P>
                <P>A. By order approve such proposed rule change, or </P>
                <P>
                    B. Institute proceedings to determine whether the proposed rule change should be disapproved. 
                    <PRTPAGE P="18707"/>
                </P>
                <HD SOURCE="HD1">IV. Solicitation of Comments </HD>
                <P>Interested persons are invited to submit written data, views, and arguments concerning the foregoing, including whether the proposed rule change, as amended, is consistent with the Act. Comments may be submitted by any of the following methods: </P>
                <HD SOURCE="HD2">Electronic Comments </HD>
                <P>
                    • Use the Commission's Internet comment form (
                    <E T="03">http://www.sec.gov/rules/sro.shtml</E>
                    ); or 
                </P>
                <P>
                    • Send an e-mail to 
                    <E T="03">rule-comments@sec.gov.</E>
                     Please include File Number SR-NASD-2006-109 on the subject line. 
                </P>
                <HD SOURCE="HD2">Paper Comments</HD>
                <P>• Send paper comments in triplicate to Nancy M. Morris, Secretary, Securities and Exchange Commission, 100 F Street, NE., Washington, DC 20549-1090. </P>
                <FP>
                    All submissions should refer to File Number SR-NASD-2006-109. This file number should be included on the subject line if e-mail is used. To help the Commission process and review your comments more efficiently, please use only one method. The Commission will post all comments on the Commission's Internet Web site (
                    <E T="03">http://www.sec.gov/rules/sro.shtml</E>
                    ). 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 filing will also be available for inspection and copying at the principal office of NASD. All comments received will be posted without change; the Commission does not edit personal identifying information from submissions. You should submit only information that you wish to make available publicly. All submissions should refer to the File Number SR-NASD-2006-109 and should be submitted on or before May 4, 2007. 
                    <FTREF/>
                </FP>
                <SIG>
                    <P>
                        For the Commission, by the Division of Market Regulation, pursuant to delegated authority.
                        <SU>21</SU>
                    </P>
                    <FTNT>
                        <P>
                            <SU>21</SU>
                             17 CFR 200.30-3(a)(12). 
                        </P>
                    </FTNT>
                    <NAME>Florence E. Harmon, </NAME>
                    <TITLE>Deputy Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC> [FR Doc. E7-7008 Filed 4-12-07; 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-55590; File No. SR-NYSE-2007-29] </DEPDOC>
                <SUBJECT>Self-Regulatory Organizations; New York Stock Exchange LLC; Notice of Filing and Immediate Effectiveness of Proposed Rule Change and Amendment No. 1 Thereto Relating to Rules 13 (“Definitions of Orders”) and 17 (“Use of Exchange Facilities”) </SUBJECT>
                <DATE>April 5, 2007. </DATE>
                <P>
                    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/>
                     notice is hereby given that on March 16, 2007, the New York Stock Exchange LLC (“NYSE” or “Exchange”) filed with the Securities and Exchange Commission (“Commission”) the proposed rule change as described in Items I and II below, which Items have been substantially prepared by the Exchange. On April 5, 2007, NYSE filed Amendment No. 1 to the proposed rule change. The Exchange has filed the proposal as a “non-controversial” rule change pursuant to Section 19(b)(3)(A) of the Act 
                    <SU>3</SU>
                    <FTREF/>
                     and Rule 19b-4(f)(6) thereunder,
                    <SU>4</SU>
                    <FTREF/>
                     which renders it effective upon filing with the Commission. The Commission is publishing this notice to solicit comments on the proposed rule change, as amended, from interested persons. 
                </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. 78s(b)(3)(A). 
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         17 CFR 240.19b-4(f)(6). 
                    </P>
                </FTNT>
                <HD SOURCE="HD1">I. Self-Regulatory Organization's Statement of the Terms of Substance of the Proposed Rule Change </HD>
                <P>
                    The Exchange is proposing to amend Exchange Rules 13 (“Definitions of Orders”) and 17 (“Use of Exchange Facilities”) in order to establish a mechanism to route orders to away market centers when that market center is displaying the national best bid and offer in accordance with Exchange Rules and Regulation NMS under the Act 
                    <SU>5</SU>
                    <FTREF/>
                     (“Reg. NMS”). The Exchange further proposes to have its order router facilitate the acceptance of executions that result in an odd-lot or a sub-penny execution. The text of the proposed rule change is available at NYSE, the Commission's Public Reference Room, and 
                    <E T="03">www.nyse.com.</E>
                </P>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         17 CFR 242.600 
                        <E T="03">et seq.</E>
                    </P>
                </FTNT>
                <HD SOURCE="HD1">II. Self-Regulatory Organization's Statement of the Purpose of, and Statutory Basis for, the Proposed Rule Change</HD>
                <P>In its filing with the Commission, NYSE included statements concerning the purpose of and basis for the proposed rule change and discussed any comments it received on the proposed rule change. The text of these statements may be examined at the places specified in Item IV below. NYSE has prepared summaries, set forth in Sections, A, B, and C below, of the most significant aspects of such statements.</P>
                <HD SOURCE="HD2">A. Self-Regulatory Organization's Statement of the Purpose of, and Statutory Basis for, the Proposed Rule Change </HD>
                <HD SOURCE="HD3">1. Purpose</HD>
                <P>
                    The Exchange is proposing to amend Exchange Rules 13 and 17 to establish a mechanism to route orders to away market centers (“Routing Broker”) when that market center is displaying the national best bid and offer in accordance with Exchange Rules and Reg. NMS. Through this filing the Exchange further proposes to have its Routing Broker facilitate the acceptance of executions that result in an odd-lot 
                    <SU>6</SU>
                    <FTREF/>
                     or a sub-penny 
                    <SU>7</SU>
                    <FTREF/>
                     execution after the Routing Broker routed an Exchange order to an away market center. 
                </P>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         Odd-lot orders are orders for a size less than the standard unit (round lot) of trading, which is 100 shares for most stocks, although some stocks trade in 10 share units. 
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         The Exchange notes that trading centers that provide sub-penny executions are currently developing order types that allow market participants to request a non-sub-penny execution. The Exchange states that the Routing Broker will perform this function only until such time as needed for the creation of these new order types and the completion of any systems modifications associated with the handling of the new order types. 
                    </P>
                </FTNT>
                <P>
                    The Exchange intends to use its broker-dealer affiliate,
                    <SU>8</SU>
                    <FTREF/>
                     Archipelago Securities LLC (“ArcaSec”), as its 
                    <PRTPAGE P="18708"/>
                    Routing Broker 
                    <SU>9</SU>
                    <FTREF/>
                     to route orders,
                    <SU>10</SU>
                    <FTREF/>
                     subject to Exchange rules and Reg. NMS, to away market centers displaying protected bids and protected offers, as defined in Rule 600(b)(57) of Reg. NMS. The Exchange believes that the Routing Broker will offer an efficient mechanism for the Exchange to route orders to away market centers for execution in compliance with Exchange Rules and Reg. NMS. 
                </P>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         On February 27, 2006, the Commission approved the Exchange's business combination with Archipelago Holdings, Inc. (“Merger”). 
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 53382 (February 27, 2006), 71 FR 11251 (March 6, 2006) (SR-NYSE-2005-77). Pursuant to the Merger, NYSE Group, Inc. became the overall parent company of the Exchange and Archipelago Holdings, Inc. NYSE Group, Inc. operates two securities exchanges: The Exchange and NYSE Arca, Inc. (formerly known as the Archipelago Exchange, or ArcaEx®, and the Pacific Exchange). ArcaSec remains a wholly owned subsidiary of Archipelago Holdings, Inc. and is therefore an affiliate of the Exchange. 
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         In the event the Exchange seeks to use another entity as its Routing Broker, the Exchange understands that it would be required to obtain Commission approval. 
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         Currently ArcaSec performs two functions for NYSE Arca, Inc. ArcaSec acts as the outbound order routing facility of NYSE Arca, Inc. 
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 52497 (September 22, 2005), 70 FR 56949 (September 29, 2005) (SR-PCX-2005-90); 
                        <E T="03">see also</E>
                         Securities Exchange Act Release No. 44983 (October 25, 2001), 66 FR 55225 (November 1, 2001) (SR-PCX-00-25). The Exchange states that, currently, the NASD is responsible for carrying out the oversight and enforcement responsibilities for ArcaSec as the designated examining authority designated by the Commission pursuant to Rule 17d-1 of the Act with the responsibility for examining the Routing Broker for compliance with the applicable financial responsibility rules. The Exchange states that it intends to enter into a 17d-2 agreement with a regulator other than the Exchange or any of its affiliates to regulate its outbound router. 
                    </P>
                    <P>
                        In addition, on March 12, 2007, the Commission authorized ArcaSec to act as a marketing agent on behalf of NYSE Arca Tech 100 Index and NYSE Arca Tech 100 ETF. This business activity has no connection to ArcaSec's facility functions as described above. 
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 55442 (March 12, 2007), 72 FR 12654 (March 16, 2007) (SR-NYSEArca-2007-09). 
                    </P>
                </FTNT>
                <P>Pursuant to the proposed rule, Exchange systems will provide the Routing Broker with routing instructions to route orders to other market centers and report such executions back to the Exchange. The Exchange states that the Routing Broker cannot change the terms of an order or the routing instructions, nor does the Routing Broker have any discretion about where to route an order. </P>
                <P>
                    The Exchange states that the Routing Broker will operate as a “facility” 
                    <SU>11</SU>
                    <FTREF/>
                     of the Exchange in that it will serve as a “system of communication to or from” 
                    <SU>12</SU>
                    <FTREF/>
                     the Exchange. When an order must be routed to an away market center for execution, Exchange systems will affix all order handling information to the order. Exchange systems will automatically transmit the order and the relevant order handling information to the Routing Broker. In turn, the Routing Broker will facilitate the delivery of the received order to the destination away market. The Routing Broker will obtain receipts of executions and deliver those receipts of executions back to Exchange systems. 
                </P>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         The term “facility” as defined in Section 3(a)(2) of the Act, as amended, provides, * * * when used with respect to an exchange includes its premises, tangible or intangible property whether on the premises or not, any right to the use of such premises or property or any service thereof for the purpose of effecting or reporting a transaction on an exchange (including, among other things, any system of communication to or from the exchange, by ticker or otherwise, maintained by or with the consent of the exchange), and any right of the exchange to the use of any property or service. 
                        <E T="03">See</E>
                         15 U.S.C. 78c(a)(2). 
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <P>In particular, and without limitation, under the Act, the Exchange will be responsible for filing with the Commission rule changes and fees relating to the functions performed by the Routing Broker for the Exchange and will be subject to exchange non-discrimination requirements. </P>
                <P>Furthermore, the books, records, premises, officers, agents, directors, and employees of the Routing Broker, as a facility of the Exchange, shall be deemed to be the books, records, premises, officers, agents, directors, and employees of the Exchange for purposes of, and subject to oversight pursuant to, the Act. The books and records of the Routing Broker as a facility of the Exchange shall be subject at all times to inspection and copying by the Exchange and the Commission. </P>
                <P>In addition to routing orders to away market centers, the Routing Broker will facilitate the acceptance of executions that results in an odd-lot or a sub-penny execution as Exchange systems are unable to accept such executions after the Routing Broker routes an Exchange order to an away market center. Currently, odd-lot orders on the Exchange are executed in a trading system that is separate from the Exchange system responsible for the execution of round-lot orders (“odd-lot trading platform”). The Exchange odd-lot trading platform executes all odd-lots orders against the specialist as the contra party separate from the trading system that is responsible for the execution of round lot orders. Since odd-lot orders are handled in a separate trading system, the Exchange systems that are responsible for the execution of round lot orders are unable to accept receipts of execution in odd-lots at the present time. </P>
                <P>Similarly, the Exchange has chosen not to quote and trade in sub-penny increments when permitted under Reg. NMS. </P>
                <P>
                    In order to process receipts of odd-lot and sub-penny executions from an away market, the Exchange proposes to have the Routing Broker facilitate the handling of such odd-lot and sub-penny execution. Specifically, if the Routing Broker is in receipt of an odd-lot execution in response to the Exchange's routing of a round lot order, it will assume the odd-lot position. The Routing Broker will then sell/buy the requested number of round lot shares to the Exchange member. The Routing Broker will perform this adjustment to each odd-lot execution in order to transmit a round lot execution to the Exchange. The Routing Broker will afford the Exchange order (
                    <E T="03">i.e.</E>
                     for the Exchange member) the most favorable execution price based on the odd-lot execution(s) received by the Routing Broker from the away market. 
                </P>
                <P>With regard to a sub-penny execution, the Routing Broker will perform an adjustment to each sub-penny execution. Specifically, the Routing Broker will round down for each buy order and up for each sell order and transmit a round penny execution to the Exchange order. Again, the Routing Broker will afford the Exchange order the most favorable execution price based on the sub-penny execution received by the Routing Broker from the away market. </P>
                <P>
                    The Routing Broker will liquidate positions assumed as a result of the services provided to the Exchange. This service provided by the Routing Broker with regard to odd-lot and sub-penny executions is not intended to operate as a means to generate revenue. Rather, the Routing Broker is providing an additional service to the Exchange in order to facilitate the receipt of odd-lot and sub-penny executions from away market centers. To that end, it is the intent of the Routing Broker to be flat in all positions at the end of each trading day.
                    <SU>13</SU>
                    <FTREF/>
                     The Routing Broker will incorporate an automated system to immediately assist in the liquidation (acquisition) for any residual long (short) positions. To mitigate financial risk 
                    <SU>14</SU>
                    <FTREF/>
                     to the Routing Broker, registered trading personnel of the Routing Broker may be required to manually assist, as soon as practicable, in the liquidation (acquisition) of such positions when, due to the nature of the security (
                    <E T="03">e.g.</E>
                     high-priced securities that trade with a wide spread) and its trading pattern or volatile market conditions, liquidation (acquisition) is not immediately possible. 
                </P>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         Absent any unusual market conditions or the timing of such trades (for example, the execution of the order at 15:59:59) it is intended that the Routing Broker will be flat in all positions at the end of each trading day. 
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>14</SU>
                         Any and all loses incurred during the facilitation of odd-lot and sub-penny executions will be assumed by the Routing Broker as part of the routing service provided. 
                    </P>
                </FTNT>
                <P>Below are examples of how the Routing Broker is intended to operate. </P>
                <HD SOURCE="HD2">ODD-LOT Executions </HD>
                <EXAMPLE>
                    <HD SOURCE="HED">Example 1:</HD>
                    <P>
                        Exchange member Firm X enters an order on the Exchange to buy 100 
                        <PRTPAGE P="18709"/>
                        shares of ABC at $20.00. Exchange systems transmit the order with order handling instructions to the Routing Broker. The Routing Broker then transmits the order with the order handling instructions received from the Exchange systems to market center A. The Routing Broker receives reports of two odd-lot executions from market center A. The first report of execution is for 30 shares executed at a price of $20.00. The second report of execution completes the original order with an execution of the remaining 70 shares at a price of $20.00. The Routing Broker will sell 100 shares to Exchange member Firm X at $20.00 and use the odd-lots received from market center A to offset the position. The Routing Broker's position is flat. 
                    </P>
                </EXAMPLE>
                <EXAMPLE>
                    <HD SOURCE="HED">Example 2:</HD>
                    <P>Exchange member Firm X enters an order on the Exchange to buy 100 shares of ABC at $20.00. The Exchange systems transmit the order with order handling instructions to the Routing Broker. The Routing Broker then transmits the order with the order handling instructions received from the Exchange systems to market center A. The Routing Broker receives two odd-lot fills from market center A. The first report is for 30 shares executed at a price of $19.99. The second report of execution completes the original with an execution of the remaining 70 shares at a price of $20.00. The Routing Broker sells 100 shares to Firm X at $19.99 and uses the odd-lots to offset the position. The Routing Broker's position is flat, with a loss of $0.70. </P>
                </EXAMPLE>
                <EXAMPLE>
                    <HD SOURCE="HED">Example 3:</HD>
                    <P>Exchange member Firm X enters an order on the Exchange to buy 100 shares of ABC at $20.00. The Exchange systems transmit the order with order handling instructions to the Routing Broker. The Routing Broker then transmits the order with the order handling instructions received from the Exchange systems to market center A. The Routing Broker receives an odd-lot fill of only 30 shares at $20.00 and a report of cancellation for the remaining 70 shares of the original order. The Routing Broker will sell 100 shares to Firm X at $20.00. In turn, the Routing Broker will then go into the market to buy 70 shares of ABC. The Routing Broker receives a fill of 70 at $20.05. The Routing Broker will then use both odd-lots positions to offset the position taken as a result of handling the order of Firm X. The Routing Broker's position is flat, with a loss of $3.50. </P>
                </EXAMPLE>
                <EXAMPLE>
                    <HD SOURCE="HED">Example 4:</HD>
                    <P>Exchange member Firm X enters an order on the Exchange to buy 100 shares of ABC at $20.00. The Exchange systems transmit the order with order handling instructions to the Routing Broker. The Routing Broker then transmits the order with the order handling instructions received from the Exchange systems to market center A. The Routing Broker receives an odd-lot fill of only 30 shares at $20.00 and a report of cancellation for the remaining 70 shares of the original order. The Routing Broker will sell 100 shares to Firm X at $20.00. In turn, the Routing Broker will then go into the market to buy 70 shares of ABC. The Routing Broker receives a fill of 70 at $19.99. The Routing Broker will then use both odd-lots positions to offset the position taken as a result of handling the order of Firm X. The Routing Broker's position is flat, with a profit of $0.70. </P>
                </EXAMPLE>
                <HD SOURCE="HD2">SUB-PENNY Executions </HD>
                <EXAMPLE>
                    <HD SOURCE="HED">Example 1:</HD>
                    <P>Exchange member Firm X enters an order on the Exchange to buy 100 shares of ABC at $20.00. The Exchange's best offer is $19.98. Market Center A is displaying a best offer at $19.97. Market Center A also offers a mid-point match execution process that may result in a trade price that includes sub-pennies. The Exchange systems transmit the order with order handling instructions to the Routing Broker. The Routing Broker then transmits the order with the order handling instructions received from Exchange systems to market center A. The Routing Broker receives a fill of 100 shares at $19.975 due to a mid-point cross occurring at market center A. The Routing Broker will sell 100 shares to member Firm X at $19.97 and uses the fill of 100 shares at $19.975 to offset the position. The Routing Broker will be flat, with a loss of $0.50. </P>
                    <P>The use of the Routing Broker to route orders to another market center will be optional. In the event a member organization does not want to use the Routing Broker it must enter an immediate-or-cancel order or any such other order type available on the Exchange that is not eligible for routing. All bids and offers entered on the Exchange that are routed to other market centers via the Routing Broker which result in an execution shall be binding on the member organization that entered such bid and offer. </P>
                    <P>The Routing Broker will not engage in any business for the Exchange other than its outbound router and facilitation functions as described above. In the event the Exchange seeks to have the Routing Broker engage in any other activities, it understands that the ability of the Routing Broker to engage in such new business activity would require Commission approval. </P>
                    <P>The Exchange believes that the above-described operation of the Routing Broker will serve as the most economically efficient execution of securities transactions. Furthermore, the Routing Broker is necessary for the Exchange to comply with its obligations pursuant to Reg. NMS. </P>
                </EXAMPLE>
                <HD SOURCE="HD3">2. Statutory Basis </HD>
                <P>
                    The Exchange believes that the proposed rule change is consistent with the requirement under Section 6(b)(5) of the Act 
                    <SU>15</SU>
                    <FTREF/>
                     that an exchange have rules that are 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. The proposed rule change is also designed to support the principles of Section 11A(a)(1) 
                    <SU>16</SU>
                    <FTREF/>
                     in that it seeks to assure economically efficient execution of securities transactions. 
                </P>
                <FTNT>
                    <P>
                        <SU>15</SU>
                         15 U.S.C. 78f(b)(5). 
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>16</SU>
                         15 U.S.C. 78k-1(a)(1). 
                    </P>
                </FTNT>
                <HD SOURCE="HD2">B. Self-Regulatory Organization's Statement on Burden on Competition </HD>
                <P>The Exchange does not believe that the proposed rule change will result in any burden on competition that is not necessary or appropriate in furtherance of the purposes of the Act. </P>
                <HD SOURCE="HD2">C. Self-Regulatory Organization's Statement on Comments on the Proposed Rule Change Received From Members, Participants or Others </HD>
                <P>The Exchange has neither solicited nor received written comments on the proposed rule change. </P>
                <HD SOURCE="HD1">III. Date of Effectiveness of the Proposed Rule Change and Timing for Commission Action </HD>
                <P>
                    Because the forgoing rule change does not: (1) Significantly affect the protection of investors or the public interest; (2) impose any significant burden on competition; and (3) become operative for 30 days after the date of this filing, or such shorter time as the Commission may designate, it has become effective pursuant to Section 19(b)(3)(A) of the Act 
                    <SU>17</SU>
                    <FTREF/>
                     and Rule 19b-4(f)(6) thereunder.
                    <SU>18</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>17</SU>
                         15 U.S.C. 78s(b)(3)(A). 
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>18</SU>
                         17 CFR 240.19b-4(f)(6).
                    </P>
                </FTNT>
                <P>
                    A proposed rule change filed under 19b-4(f)(6) normally may not become operative prior to 30 days after the date of filing.
                    <SU>19</SU>
                    <FTREF/>
                     However, Rule 19b-4(f)(6)(iii) 
                    <SU>20</SU>
                    <FTREF/>
                     permits the Commission to designate a shorter time if such action is consistent with the protection of investors and the public interest. The Exchange has requested that the Commission waive the 30-day operative delay. The Commission believes that waiving the 30-day operative delay is consistent with the protection of investors and the public interest because such waiver would permit NYSE to immediately use the Routing Broker to route orders to other trading centers to prevent trade-troughs of protected quotations in NMS stocks.
                    <SU>21</SU>
                    <FTREF/>
                     For this reason, the Commission designates the proposed rule change to 
                    <PRTPAGE P="18710"/>
                    be operative upon filing with the Commission.
                    <SU>22</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>19</SU>
                         17 CFR 240.19b-4(f)(6)(iii). In addition, Rule 19b-4(f)(6)(iii) requires that a self-regulatory organization submit to the Commission written notice of its intent to file the proposed rule change, along with a brief description and text of the proposed rule change, at least five business days prior to the date of filing of the proposed rule change, or such shorter time as designated by the Commission. NYSE has satisfied the five-day pre-filing notice requirement. 
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>20</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>21</SU>
                         The Commission notes that NYSE's proposed Rule 17(b) is substantially similar to Rule 2.11 of the National Stock Exchange, Inc.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>22</SU>
                         For the purposes only of waiving the 30-day operative delay, the Commission has considered the proposed rule's impact on efficiency, competition, and capital formation. 
                        <E T="03">See</E>
                         15 U.S.C. 78c(f). 
                    </P>
                </FTNT>
                <P>
                    At any time within 60 days of the filing of such proposed rule change the Commission may summarily abrogate such rule change if it appears to the Commission that such action is necessary or appropriate in the public interest, for the protection of investors or otherwise in furtherance of the purposes of the Act.
                    <SU>23</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>23</SU>
                        15 U.S.C. 78s(b)(3)(C). For purposes of calculating the 60-day period within which the Commission may summarily abrogate the proposal, the Commission considers the period to commence on April 5, 2007, the date on which the Exchange submitted Amendment No. 1. 
                    </P>
                </FTNT>
                <HD SOURCE="HD1">IV. Solicitation of Comments </HD>
                <P>Interested persons are invited to submit written data, views, and arguments concerning the foregoing, including whether the proposed rule change is consistent with the Act. Comments may be submitted by any of the following methods: </P>
                <HD SOURCE="HD2">Electronic Comments</HD>
                <P>
                    • Use the Commission's Internet comment form (
                    <E T="03">http://www.sec.gov/rules/sro.shtml</E>
                    ); or 
                </P>
                <P>
                    • Send an e-mail to 
                    <E T="03">rule-comments@sec.gov.</E>
                     Please include File Number SR-NYSE-2007-29 on the subject line. 
                </P>
                <HD SOURCE="HD2">Paper Comments </HD>
                <P>• Send paper comments in triplicate to Nancy M. Morris, Secretary, Securities and Exchange Commission, 100 F Street, NE, Washington, DC 20549-1090. </P>
                <P>
                    All submissions should refer to File Number SR-NYSE-2007-29. This file number should be included on the subject line if e-mail is used. To help the Commission process and review your comments more efficiently, please use only one method. The Commission will post all comments on the Commission's Internet Web site (
                    <E T="03">http://www.sec.gov/rules/sro.shtml</E>
                    ). 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 the filing also will be available for inspection and copying at the principal office of NYSE. All comments received will be posted without change; the Commission does not edit personal identifying information from submissions. You should submit only information that you wish to make available publicly. All submissions should refer to File Number SR-NYSE-2007-29 and should be submitted on or before May 4, 2007. 
                </P>
                <SIG>
                    <P>
                        For the Commission, by the Division of Market Regulation, pursuant to delegated authority.
                        <SU>24</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>24</SU>
                            17 CFR 200.30-3(a)(12). 
                        </P>
                    </FTNT>
                    <NAME>Florence E. Harmon, </NAME>
                    <TITLE>Deputy Secretary. </TITLE>
                </SIG>
            </PREAMB>
            <FRDOC> [FR Doc. E7-6962 Filed 4-12-07; 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-55594; File No. SR-NYSE-2005-48] </DEPDOC>
                <SUBJECT>Self-Regulatory Organizations; New York Stock Exchange LLC; Notice of Filing of Amendments No. 1, 2, 3, and 4 Thereto to Proposed Rule Change to Amend Rule 619 Pertaining to Subpoenas for the Production of Documents and Appearances of Witnesses </SUBJECT>
                <DATE>April 6, 2007. </DATE>
                <P>
                    On July 13, 2005, 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/>
                     the New York Stock Exchange LLC (“NYSE” or “Exchange”) filed with the Securities and Exchange Commission (“SEC” or “Commission”) a proposed rule change to amend NYSE Rule 619, pertaining to subpoenas for the production of documents and appearance of witnesses. The proposed rule change was published for comment in the 
                    <E T="04">Federal Register</E>
                     on September 26, 2005,
                    <SU>3</SU>
                    <FTREF/>
                     and the Commission received no comments on the proposal. On April 18, 2006, November 2, 2006, December 22, 2006, and February 8, 2007, the NYSE filed Amendments No. 1, 2, 3, and 4, respectively, to revise the rule change as described in Items I, II, and III below, which Items have been prepared by the NYSE.
                    <SU>4</SU>
                    <FTREF/>
                     The Commission is publishing this notice to solicit comments on the proposed rule change, as amended, from interested persons. 
                </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>
                         Securities Exchange Act Release No. 52468 (Sept. 19, 2005), 70 FR 56201 (Sept. 26, 2005). 
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         Amendment No. 1 clarified that only the arbitrator(s) may issue subpoenas and delineated the manner in which a party may request the issuance of a subpoena. Amendment No. 2 established a time frame for the parties to make and respond to objections to the requested subpoena and clarified that the arbitrator(s) may not rule on such a request until this time period has elapsed. Amendment No. 3 made technical changes to the rule and clarified that the arbitrator(s) must receive copies of any objections to the issuance of a subpoena. Amendment No. 4 clarified that a party requesting a subpoena may not serve the request or the draft subpoena on a non-party. 
                    </P>
                </FTNT>
                <HD SOURCE="HD1">I. Self-Regulatory Organization's Statement of the Terms of Substance of the Proposed Rule Change </HD>
                <P>NYSE is proposing to revise Rule 619, which pertains to subpoenas for the production of documents and the appearance of witnesses. Below is the text of the proposed rule change. Proposed new language is italicized and proposed deletions are in brackets. </P>
                <STARS/>
                <P>(a) to (e) No change. </P>
                <P>(f) Subpoenas. </P>
                <P>
                    (
                    <E T="03">1</E>
                    ) The arbitrator(s) [and any counsel of record to the proceedings] 
                    <E T="03">may issue subpoenas for the production of documents or the appearance of witnesses</E>
                     [shall have the power of the subpoena process as provided by law. All parties shall be given a copy of the subpoena upon its issuance. The parties shall produce witnesses and present proofs to the fullest extent possible without resort to the subpoena process.] 
                    <E T="03">The party who requests a subpoena must make a written request asking the arbitrator(s) to issue a subpoena. The request, along with the requested draft subpoena must be served directly on each other party in a manner that is reasonably expected to cause the request and the requested subpoena to be delivered to all parties on the same day. The requesting party may not serve the request or the requested draft subpoena on a non-party. The request and the requested subpoena must also be filed with the Director of Arbitration, with additional copies for each arbitrator, at the same time and in the same manner in which they are served on the parties. The parties shall produce witnesses and present proof at the hearing whenever possible without using subpoenas. </E>
                </P>
                <P>
                    (
                    <E T="03">2</E>
                    ) 
                    <E T="03">
                        In the event a party receiving such a request objects to the scope or propriety of the subpoena, that party shall, within 10 days of service of the request, file with the Director of Arbitration, with copies to all other parties, written objections, including additional copies for each arbitrator. The party seeking the subpoena may respond thereto within five days of receipt of the objection. The arbitrator(s) appointed shall rule promptly on the 
                        <PRTPAGE P="18711"/>
                        issuance and scope of the subpoena after the time period for objections and replies thereto has elapsed. 
                    </E>
                </P>
                <P>
                    (
                    <E T="03">3</E>
                    ) 
                    <E T="03">If the arbitrator(s) issue a subpoena, the party that requested the subpoena must serve the subpoena at the same time and in the same manner on all parties, and, if applicable, on any non-party receiving the subpoena. </E>
                </P>
                <P>
                    (
                    <E T="03">4</E>
                    ) 
                    <E T="03">Any party that receives documents in response to a subpoena served upon a non-party shall provide notice to all other parties within five days of receipt of the documents. Thereafter, any party may request copies of such documents and, if such a request is made, the documents must be provided within 10 days following receipt of the request. The party requesting the documents shall be responsible for the reasonable costs associated with the production of the copies, unless the panel determines otherwise.</E>
                </P>
                <P>(g) No change. </P>
                <STARS/>
                <HD SOURCE="HD1">II. Self-Regulatory Organization's Statement of the Purpose of, and Statutory Basis for, the Proposed Rule Change </HD>
                <P>In its filing with the Commission, the NYSE included statements concerning the purpose of and basis for the proposed rule change. The text of these statements may be examined at the places specified in Item IV below. The NYSE has prepared summaries, set forth in Sections A, B, and C below, of the most significant aspects of such statements. </P>
                <HD SOURCE="HD2">A. Self-Regulatory Organization's Statement of the Purpose of, and Statutory Basis for, the Proposed Rule Change </HD>
                <HD SOURCE="HD3">1. Purpose </HD>
                <HD SOURCE="HD3">Proposal </HD>
                <P>In the initial rule filing, the Exchange proposed to revise NYSE Rule 619 to provide for a 10-day notice period requirement before a party issues a subpoena to a non-party for pre-hearing discovery. Under the proposed rule change only the arbitrator(s) may issue subpoenas for the production of documents and the appearance of witnesses. In addition, the arbitrator(s), and not the courts, would rule on discovery disputes concerning the issuance of subpoenas. The party who requests a subpoena would make a written request asking the arbitrator(s) to issue a subpoena and would send a copy of the request and the requested draft subpoena to the Director of Arbitration, each arbitrator, and all parties to the arbitration in a manner reasonably expected to result in delivery to everyone on the same day. The requesting party may not serve the request or the requested draft subpoena on any non-party. </P>
                <P>If a party has an objection to the propriety or scope of the subpoena, that party would be required to file objections in writing with the Director of Arbitration and send copies to all other parties, including each arbitrator, within 10 days of service of the request and draft subpoena. The party requesting the subpoena could file a reply to the objection within five days of receipt of the objection. The arbitrator(s) would determine the propriety and scope of the requested subpoena after the time period for filing objections or replies had elapsed. If a subpoena is issued by the arbitrator(s), the party that requested the subpoena would be required to serve the subpoena at the same time and in the same manner on all parties, and, if applicable, on any non-party receiving the subpoena. </P>
                <P>Additionally, the proposed rule change provides that any party that receives documents in response to a subpoena served upon a non-party must provide notice to all other parties within five days of receipt of the documents. Thereafter, any party may request copies of those documents and, if such a request is made, the documents must be provided within 10 days following receipt of the request. The party requesting the documents is responsible for the reasonable costs associated with the production of the copies, unless the panel determines otherwise. </P>
                <HD SOURCE="HD3">2. Statutory Basis </HD>
                <P>
                    NYSE believes that the proposed rule change is consistent with Section 6(b)(5) 
                    <SU>5</SU>
                    <FTREF/>
                     of the Act in that the rule change promotes just and equitable principles of trade by ensuring that members, member organizations and the public have a fair and impartial forum for the resolution of their disputes. 
                </P>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         15 U.S.C. 78f(b)(5). 
                    </P>
                </FTNT>
                <HD SOURCE="HD2">B. Self-Regulatory Organization's Statement on Burden on Competition </HD>
                <P>The Exchange does not believe that the proposed rule change will impose any burden on competition that is not necessary or appropriate in furtherance of the purposes of the Act. </P>
                <HD SOURCE="HD2">C. Self-Regulatory Organization's Statement on Comments on the Proposed Rule Change Received From Members, Participants or Others </HD>
                <P>
                    The Commission published the proposed amendments to Rule 619 (SR-NYSE-2005-48) in the 
                    <E T="04">Federal Register</E>
                     on September 26, 2005. The Commission received no comments in response to the proposal. 
                </P>
                <HD SOURCE="HD1">III. Date of Effectiveness of the Proposed Rule Change and Timing for Commission Action </HD>
                <P>
                    Within 35 days of the date of publication of this notice in the 
                    <E T="04">Federal Register</E>
                     or within such longer period (i) as the Commission may designate up to 90 days of such date if it finds such longer period to be appropriate and publishes its reasons for so finding or (ii) as to which the self-regulatory organization consents, the Commission will: 
                </P>
                <P>(A) By order approve the proposed rule change, or </P>
                <P>(B) Institute proceedings to determine whether the proposed rule change should be disapproved. </P>
                <HD SOURCE="HD1">IV. Solicitation of Comments </HD>
                <P>Interested persons are invited to submit written data, views and arguments concerning the foregoing, including whether the proposed rule change is consistent with the Act. Comments may be submitted by any of the following methods: </P>
                <HD SOURCE="HD2">Electronic Comments</HD>
                <P>
                    • Use the Commission's Internet comment form (
                    <E T="03">http://www.sec.gov/rules/sro.shtml</E>
                    ); or 
                </P>
                <P>
                    • Send e-mail to 
                    <E T="03">rule-comments@sec.gov.</E>
                     Please include File Number SR-NYSE-2006-48 on the subject line. 
                </P>
                <HD SOURCE="HD2">Paper Comments</HD>
                <P>• Send paper comments in triplicate to Nancy M. Morris, Secretary, Securities and Exchange Commission, 100 F Street, NE., Washington, DC 20549-1090. </P>
                <FP>
                    All submissions should refer to File Number SR-NYSE-2005-48. This file number should be included on the subject line if e-mail is used. To help the Commission process and review your comments more efficiently, please use only one method. The Commission will post all comments on the Commission's Internet Web site (
                    <E T="03">http://www.sec.gov/rules/sro/shtml</E>
                    ). 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 
                    <PRTPAGE P="18712"/>
                    the Commission's Public Reference Room. Copies of such filing also will be available for inspection and copying at the principal office of the NYSE. All comments received will be posted without change; the Commission does not edit personal identifying information from submissions. You should submit only information that you wish to make available publicly. All submissions should refer to File number SR-NYSE-2005-48 and should be submitted on or before May 4, 2007. 
                </FP>
                <SIG>
                    <P>
                        For the Commission, by the Division of Market Regulation, pursuant to delegated authority.
                        <SU>6</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>6</SU>
                             17 CFR 200.30-3(a)(12).
                        </P>
                    </FTNT>
                    <NAME>Florence E. Harmon, </NAME>
                    <TITLE>Deputy Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC> [FR Doc. E7-7055 Filed 4-12-07; 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-55600; File No. SR-NYSE-2007-27]</DEPDOC>
                <SUBJECT>Self-Regulatory Organizations; New York Stock Exchange LLC; Notice of Filing of Proposed Rule Change and Amendment Nos. 1 and 2 Thereto To Adopt Generic Listing Standards for Index-Linked Securities</SUBJECT>
                <DATE>April 9, 2007.</DATE>
                <P>
                    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/>
                     notice is hereby given that on March 9, 2007, the New York Stock Exchange LLC (“NYSE” or “Exchange”) filed with the Securities and Exchange Commission (“Commission”) the proposed rule change as described in Items I, II, and III below, which Items have been substantially prepared by the Exchange. On April 4, 2007, the Exchange filed Amendment No. 1 to the proposed rule change. On April 5, 2007, the Exchange filed Amendment No. 2 to the proposed rule change. The Commission is publishing this notice to solicit comments on the proposed rule change, as amended, from interested persons.
                </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>
                <HD SOURCE="HD1">I. Self-Regulatory Organization's Statement of the Terms of Substance of the Proposed Rule Change</HD>
                <P>
                    The Exchange proposes to adopt generic listing standards for equity index-linked securities (“Equity Index-Linked Securities”), commodity-linked securities (“Commodity-Linked Securities”), and currency-linked securities (“Currency-Linked Securities” and, together with Equity Index-Linked Securities and Commodity-Linked Securities, “Index-Linked Securities”). The text of the proposed rule change is available at NYSE, the Commission's Public Reference Room, and 
                    <E T="03">www.nyse.com</E>
                    .
                </P>
                <HD SOURCE="HD1">II. Self-Regulatory Organization's Statement of the Purpose of, and Statutory Basis for, the Proposed Rule Change</HD>
                <P>In its filing with the Commission, the Exchange included statements concerning the purpose of, and basis for, the proposed rule change and discussed any comments it received on the proposed rule change. The text of these statements may be examined at the places specified in Item IV below. The Exchange has prepared summaries, set forth in Sections A, B, and C below, of the most significant aspects of such statements.</P>
                <HD SOURCE="HD2">A. Self-Regulatory Organization's Statement of the Purpose of, and Statutory Basis for, the Proposed Rule Change</HD>
                <HD SOURCE="HD3">1. Purpose</HD>
                <P>
                    The Exchange proposes to add new Section 703.22 to its Listed Company Manual (the “Manual”) to provide generic listing standards to permit the listing and trading of Index-Linked Securities pursuant to Rule 19b-4(e) 
                    <SU>3</SU>
                    <FTREF/>
                     under the Act. The Exchange represents that any securities it lists and/or trades pursuant to proposed Section 703.22 of the Manual will satisfy the standards set forth therein. The Exchange states that within five business days after commencement of trading of an Index-Linked Security pursuant to proposed Section 703.22 of the Manual, the Exchange will file a Form 19b-4(e).
                    <SU>4</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         Rule 19b-4(e) provides that the listing and trading of a new derivative securities product by a self-regulatory organization (“SRO”) shall not be deemed a proposed rule change if the Commission has approved the SRO's trading rules, procedures, and listing standards for the product class that would include the new derivatives securities product, and the SRO has a surveillance program for the product class. 
                        <E T="03">See</E>
                         17 CFR 240.19b-4(e)(1).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         
                        <E T="03">See</E>
                         17 CFR 240.19b-4(e)(2)(ii).
                    </P>
                </FTNT>
                <HD SOURCE="HD2">Index-Linked Securities</HD>
                <P>
                    Index-Linked Securities are designed for investors who desire to participate in a specific market segment by providing exposure to one or more identifiable underlying securities, commodities, currencies, derivative instruments, or market indexes of the foregoing (the “Underlying Index” or “Underlying Indexes”).
                    <SU>5</SU>
                    <FTREF/>
                     Index-Linked Securities are the non-convertible debt of an issuer that have a term of at least one year, but not greater than thirty years, and are tied to the performance of the Underlying Index. Index-Linked Securities may or may not make interest payments based on dividends or other cash distributions paid on the securities comprising the Underlying Index or Indexes to the holder during their term. Despite the fact that Index-Linked Securities are linked to an Underlying Index, each will trade as a single, exchange-listed security.
                </P>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         The Exchange states that the holder of an Index-Linked Security may or may not be fully exposed to the appreciation and/or depreciation of the underlying component assets. For example, an Index-Linked Security may be subject to a “cap” on the maximum principal amount to be repaid to holders or a “floor” on the minimum principal amount to be repaid to holders at maturity.
                    </P>
                </FTNT>
                <P>
                    The Exchange represents that the proposed generic listing standards will not be applicable to Index-Linked Securities with respect to which the payment at maturity is based on a multiple of the negative performance of an Underlying Index or Indexes. An Index-Linked Security may or may not provide “principal protection,” 
                    <E T="03">i.e.</E>
                    , a minimum guaranteed amount to be repaid.
                    <SU>6</SU>
                    <FTREF/>
                     The Exchange believes that the flexibility to list a variety of Index-Linked Securities will offer investors the opportunity to more precisely focus their specific investment strategies.
                </P>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         Some Index-Linked Securities may provide for “contingent” protection of the principal amount, whereby the principal protection may disappear if the Underlying Index at any point in time during the life of such security reaches a certain predetermined level.
                    </P>
                </FTNT>
                <P>Index-Linked Securities do not give the holder any right to receive a portfolio component, dividend payments, or any other ownership right or interest in the portfolio or underlying components comprising the Underlying Index. Pursuant to proposed Section 703.22 of the Manual, the current or composite value of the Underlying Index will be widely disseminated at least every 15 seconds during the trading day.</P>
                <HD SOURCE="HD2">Proposed Listing Criteria for Index-Linked Securities</HD>
                <P>The Exchange will apply the following requirements to all issuers of Index-Linked Securities:</P>
                <P>
                    • If the issuer is a NYSE-listed company, the entity must be a company in good standing (
                    <E T="03">i.e.</E>
                    , meets NYSE's applicable continued listing criteria); if the issuer is an affiliate of a NYSE-listed company, the NYSE-listed company must be a company in good standing; if not listed, the issuer must meet the size and earnings requirements of Sections 102.01-102.03 or Sections 103.01-103.05 of the Manual. Sovereign issuers 
                    <PRTPAGE P="18713"/>
                    will be evaluated on a case-by-case basis.
                </P>
                <P>
                    • The issuer will be expected to have a minimum tangible net worth
                    <SU>7</SU>
                    <FTREF/>
                     of $250,000,000. In the alternative, the issuer will be expected: (i) To have a minimum tangible net worth of $150,000,000 and (ii) not to issue Index-Linked Securities, the original issue price of which, combined with all the issuer's other Index-Linked Securities listed on a national securities exchange, exceeds 25% of the issuer's tangible net worth at the time of issuance. If the Index-Linked Securities are fully and unconditionally guaranteed by an affiliate of the issuer, the Exchange will rely on such affiliate's tangible net worth for purposes of these requirements and will include in its calculation all Index-Linked Securities that are fully and unconditionally guaranteed by such affiliate.
                </P>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         “Tangible net worth” is defined as total assets, 
                        <E T="03">less</E>
                         intangible assets and total liabilities. Intangibles include non-material benefits such as goodwill, patents, copyrights, and trademarks.
                    </P>
                </FTNT>
                <P>
                    • The issuer must be in compliance with Rule 10A-3 under the Act.
                    <SU>8</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         
                        <E T="03">See</E>
                         17 CFR 240.10A-3 (setting forth the listing standards relating to audit committees).
                    </P>
                </FTNT>
                <P>The Exchange will apply the following requirements to each issue of Index-Linked Securities:</P>
                <P>
                    • The issue must have a minimum public distribution of at least 1 million units and a minimum of 400 holders, except if traded on the NYSE Bonds system and the applicable NYSE Bonds listing and trading standards are satisfied; 
                    <SU>9</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         
                        <E T="03">See</E>
                         NYSE Rule 86 (establishing rules and standards with respect to the Exchange's electronic system, known as “NYSE Bonds,” for receiving, processing, executing, and reporting bids, offers, and executions in bonds).
                    </P>
                </FTNT>
                <P>• The issue must have a principal amount/aggregate market value of not less than $4 million;</P>
                <P>• The issue must have a term of at least one year, but not greater than thirty years;</P>
                <P>• The issue must be the non-convertible debt of the issuer; and</P>
                <P>• The issue must not base its payment at maturity on a multiple of the negative performance of an Underlying Index or Indexes, although the payment at maturity may or may not provide for a multiple of the positive performance of an Underlying Index or Indexes.</P>
                <P>Index-Linked Securities must have at least 400 holders at the time of listing. This requirement will not be applicable if the issue provides for the redemption of Index-Linked Securities at the option of the holders on at least a weekly basis. The Exchange believes that a weekly redemption right will ensure a strong correlation between the market price of the Index-Linked Securities and the performance of the Underlying Index, as holders will be unlikely to sell their Index-Linked Securities for less than their redemption value if they have a weekly right to be redeemed for their full value. In addition, in the case of those Index-Linked Securities with a weekly redemption feature that are currently listed, as well as all of those that are currently proposed to be listed, the issuer has the ability to issue new Index-Linked Securities from time to time at the indicative value at the time of such sale. This provides a ready supply of new Index-Linked Securities thereby lessening the possibility that the market price of such securities will be affected by a scarcity of available Index-Linked Securities for sale. It also assists in maintaining a strong correlation between the market price and the indicative value, as investors will be unlikely to pay more than the indicative value in the open market if they can acquire Index-Linked Securities from the issuer at that price. </P>
                <P>The ability to list Index-Linked Securities with these characteristics without any specific requirements as to the number of holders is important to the successful listing of such securities. Issuers issuing these types of Index-Linked Securities generally do not intend to do so by way of an underwritten offering. Rather, the distribution arrangement is analogous to that of an exchange traded fund issuance, in that the issue is launched without any significant distribution event, and the float increases over time as investors purchase additional securities from the issuer at the then indicative value. Investors will generally seek to purchase the securities at a point when the Underlying Index is at a level that they perceive as providing an attractive growth opportunity. In the context of such a distribution arrangement, it is difficult for an issuer to guarantee its ability to sell to sufficient investors on the listing date to meet a specific number-of-holders requirement. However, the Exchange believes that this difficulty in ensuring 400 holders on the listing date is not indicative of a likely long-term lack of liquidity in Index-Linked Securities or, for the reasons set forth in the prior paragraph, of a difficulty in establishing a pricing equilibrium in the Index-Linked Securities or a successful two-sided market. </P>
                <HD SOURCE="HD2">Equity Index-Linked Securities Listing Standards </HD>
                <P>
                    Equity Index-Linked Securities will be subject to the criteria in proposed Section 703.22(B)(I) of the Manual for initial and continued listing. For an Underlying Index to be appropriate for the initial listing of an Equity Index-Linked Security, such Underlying Index must comprise at least ten component securities of different issuers. The Underlying Index must also either: (i) Be approved for the trading of options or other derivative securities by the Commission under Section 19(b)(2) of the Act 
                    <SU>10</SU>
                    <FTREF/>
                     and rules thereunder, and the conditions set forth in the Commission's approval order, including comprehensive surveillance sharing agreements for non-U.S. stocks, continue to be satisfied, or (ii) meet the following requirements:
                </P>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         15 U.S.C. 78s(b)(2).
                    </P>
                </FTNT>
                <P>• Each component security must have a minimum market value of at least $75 million, except that for each of the lowest dollar weighted component securities in the Underlying Index that in the aggregate account for no more than 10% of the dollar weight of such Underlying Index, the market value can be at least $50 million; </P>
                <P>• Each component security must have a trading volume in each of the last six months of not less than 1,000,000 shares, except that for each of the lowest dollar weighted component securities in the Underlying Index that in the aggregate account for no more than 10% of the dollar weight of such Underlying Index, the trading volume must be at least 500,000 shares in each of the last six months; </P>
                <P>• Underlying Indexes based upon the equal-dollar or modified equal-dollar weighting methodology must be rebalanced at least quarterly; </P>
                <P>• In the case of a capitalization weighted or modified capitalization weighted Underlying Index, the lesser of the five highest dollar weighted component securities in the Underlying Index or the highest dollar weighted component securities in the Underlying Index that in the aggregate represent at least 30% of the total number of component securities in the Underlying Index, each have an average monthly trading volume of at least 2,000,000 shares over the previous six months; </P>
                <P>• No component security will represent more than 25% of the dollar weight of the Underlying Index, and the five highest dollar weighted component securities in the Underlying Index will not in the aggregate account for more than 50% of the weight of the Underlying Index (60% for an Underlying Index consisting of fewer than 25 component securities); </P>
                <P>
                    • 90% of the Underlying Index's dollar weight and at least 80% of the total number of component securities 
                    <PRTPAGE P="18714"/>
                    must meet the then current criteria for standardized options trading on a national securities exchange; and 
                </P>
                <P>
                    • All component securities must either: (i) Be issued by a reporting company under the Act that is listed on a national securities exchange and be an “NMS stock,” as defined in Rule 600 of Regulation NMS,
                    <SU>11</SU>
                    <FTREF/>
                     or (ii) be foreign country securities or American Depository Receipts (“ADRs”), provided that the foreign country securities or foreign country securities underlying ADRs having their primary trading market outside the United States on foreign trading markets that are not parties to comprehensive surveillance agreements with the Exchange will not, in the aggregate, represent more than 20% of the dollar weight of the Underlying Index. 
                </P>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         
                        <E T="03">See</E>
                         17 CFR 242.600(b)(47).
                    </P>
                </FTNT>
                <P>The Exchange will commence delisting or removal proceedings of an Equity Index-Linked Security if any of the standards set forth in the initial eligibility criteria are not continuously maintained, except that: </P>
                <P>• The criteria that no single component represent more than 25% of the dollar weight of the Underlying Index and the five highest dollar weighted components in the Underlying Index cannot represent more than 50% (or 60% for Underlying Indexes with less than 25 components) of the dollar weight of the Underlying Index, need only be satisfied for capitalization weighted, modified capitalization weighted, and price weighted Underlying Indexes as of the first day of January and July in each year; </P>
                <P>
                    • The total number of components in the Underlying Index may not increase or decrease by more than 33
                    <FR>1/3</FR>
                    % from the number of components in the Underlying Index at the time of its initial listing, and in no event may be less than ten components; 
                </P>
                <P>• The trading volume of each component security in the Underlying Index must be at least 500,000 shares for each of the last six months, except that for each of the lowest dollar weighted components in the Underlying Index that in the aggregate account for no more than 10% of the dollar weight of the Underlying Index, trading volume must be at least 400,000 shares for each of the last six months; and </P>
                <P>• For a capitalization weighted or modified capitalization weighted Underlying Index, the lesser of the five highest dollar weighted component securities in the Underlying Index or the highest dollar weighted component securities in the Underlying Index that in the aggregate represent at least 30% of the total number of stocks in the Underlying Index have an average monthly trading volume of at least 1,000,000 shares over the previous six months. </P>
                <P>
                    In connection with an Equity Index-Linked Security, the Exchange will commence delisting or removal proceedings if an Underlying Index or Indexes fails to satisfy the maintenance standards or conditions for such Underlying Index or Indexes as set forth by the Commission in its order under Section 19(b)(2) of the Act 
                    <SU>12</SU>
                    <FTREF/>
                     approving the Underlying Index or Indexes for the trading of options or other derivatives. The Exchange will also commence delisting or removal proceedings of an Equity Index-Linked Security under any of the following circumstances:
                </P>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         15 U.S.C. 78s(b)(2).
                    </P>
                </FTNT>
                <P>• If the aggregate market value or the principal amount of the Equity Index-Linked Securities publicly held is less than $400,000; </P>
                <P>• If the value of the Underlying Index or composite value of the Underlying Indexes is no longer calculated and widely disseminated on at least a 15-second basis during the time the Equity Index-Linked Securities trade on the Exchange; or </P>
                <P>• If such other event occurs or condition exists which, in the opinion of the Exchange, makes further dealings on the Exchange inadvisable. </P>
                <HD SOURCE="HD2">Commodity-Linked Securities Listing Standards </HD>
                <P>Commodity-Linked Securities will be subject to the criteria in proposed Section 703.22(B)(II) of the Manual for initial and continued listing. An issue of Commodity-Linked Securities must meet initial listing standards set forth in either the first or second bullet point below: </P>
                <P>
                    • One or more physical commodities or commodity futures, options, or other commodity derivatives or Commodity Trust Shares (as defined in Exchange Rule 1300B) or basket or index of any of the foregoing (the “Commodity Reference Asset”) to which the security is linked shall have been reviewed and approved for the trading of Commodity Trust Shares, options, or other derivatives by the Commission under Section 19(b)(2) of the Act 
                    <SU>13</SU>
                    <FTREF/>
                     and rules thereunder, and the conditions set forth in the Commission's approval order, including with respect to comprehensive surveillance sharing agreements, continue to be satisfied; or 
                </P>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <P>• The pricing information for each component of a Commodity Reference Asset must be derived from a market which is an Intermarket Surveillance Group (“ISG”) member or affiliate or with which the Exchange has a comprehensive surveillance sharing agreement. Notwithstanding the previous sentence, pricing information for gold and silver may be derived from the London Bullion Market Association. </P>
                <P>In addition, the issue must meet both of the following initial listing criteria: </P>
                <P>• The value of the Commodity Reference Asset must be calculated and widely disseminated on at least a 15-second basis during the time the Commodity-Linked Securities trade on the Exchange; and </P>
                <P>• In the case of Commodity-Linked Securities that are periodically redeemable, the indicative value of the subject Commodity-Linked Securities must be calculated and widely disseminated by one or more major market data vendors on at least a 15-second basis during the time the Commodity-Linked Securities trade on the Exchange. </P>
                <P>The Exchange will commence delisting or removal proceedings if any of the initial listing criteria described above is not continuously maintained. Notwithstanding the foregoing sentence, an issue of Commodity-Linked Securities will not be delisted for a failure to have in place comprehensive surveillance sharing agreements if the Commodity Reference Asset has at least 10 components, and the Exchange has comprehensive surveillance sharing agreements with respect to at least 90% of the dollar weight of the Commodity Reference Asset. The Exchange will also commence delisting or removal proceedings: </P>
                <P>• If the aggregate market value or the principal amount of the Commodity-Linked Securities publicly held is less than $400,000; </P>
                <P>• If the value of the Commodity Reference Asset is no longer calculated or available and a new Commodity Reference Asset is substituted, unless the new Commodity Reference Asset meets the requirements of proposed Section 703.22; or </P>
                <P>• If such other event occurs or condition exists which, in the opinion of the Exchange, makes further dealings on the Exchange inadvisable. </P>
                <HD SOURCE="HD2">Currency-Linked Securities Listing Standards </HD>
                <P>
                    Currency-Linked Securities will be subject to the criteria in proposed Section 703.22(B)(III) of the Manual for initial and continued listing. An issue of Currency-Linked Securities must meet initial listing standards set forth in either the first or second bullet point below: 
                    <PRTPAGE P="18715"/>
                </P>
                <P>
                    • One or more currencies, or options, currency futures, or other currency derivatives, or Currency Trust Shares (as defined in Exchange Rule 1300A), or a basket or index of any of the foregoing (the “Currency Reference Asset”) to which the Currency-Linked Security is linked shall have been reviewed and approved for the trading of Currency Trust Shares, options, or other derivatives by the Commission under Section 19(b)(2) of the Act 
                    <SU>14</SU>
                    <FTREF/>
                     and rules thereunder, and the conditions set forth in the Commission's approval order, including with respect to comprehensive surveillance sharing agreements, continue to be satisfied; or 
                </P>
                <FTNT>
                    <P>
                        <SU>14</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <P>• The pricing information for each component of a Currency Reference Asset must be (a) the generally accepted spot price for the currency exchange rate in question or (b) derived from a market which (i) is an ISG member or affiliate of an ISG member or with which the Exchange has in place a comprehensive surveillance sharing agreement and (ii) is the pricing source for components of a Currency Reference Asset that has previously been approved by the Commission. </P>
                <P>In addition, the issue must meet both of the following initial listing criteria: </P>
                <P>• The value of the Currency Reference Asset must be calculated and widely disseminated on at least a 15-second basis during the time the Currency-Linked Securities trade on the Exchange; and </P>
                <P>• In the case of Currency-Linked Securities that are periodically redeemable, the indicative value of the subject Currency-Linked Securities must be calculated and widely disseminated by one or more major market data vendors on at least a 15-second basis during the time the Currency-Linked Securities trade on the Exchange. </P>
                <P>The Exchange will commence delisting or removal proceedings if any of the initial listing criteria described above is not continuously maintained. Notwithstanding the foregoing sentence, an issue of Currency-Linked Securities will not be delisted for a failure to have in place comprehensive surveillance sharing agreements if the Currency Reference Asset has at least 10 components, and the Exchange has comprehensive surveillance sharing agreements with respect to at least 90% of the dollar weight of the Currency Reference Asset. The Exchange will also commence delisting or removal proceedings under any of the following circumstances: </P>
                <P>• If the aggregate market value or the principal amount of the Currency-Linked Securities publicly held is less than $400,000; </P>
                <P>• If the value of the Currency Reference Asset is no longer calculated or available and a new Currency Reference Asset is substituted, unless the new Currency Reference Asset meets the requirements of proposed Section 703.22; or </P>
                <P>• If such other event occurs or condition exists which, in the opinion of the Exchange, makes further dealings on the Exchange inadvisable.</P>
                <HD SOURCE="HD2">Exchange Rules Applicable to Index-Linked Securities </HD>
                <P>Index-Linked Securities traded on the Exchange's equity trading floor will be subject to all Exchange rules governing the trading of equity securities. The Exchange's equity margin rules and the Exchange's regular trading hours (9:30 a.m. to 4 p.m. Eastern Time) will apply to transactions in Index-Linked Securities. Index-Linked Securities traded on the NYSE Bonds system will be subject to the rules applicable to securities traded on that system. </P>
                <HD SOURCE="HD2">Information Memorandum </HD>
                <P>Upon evaluating the nature and complexity of each Index-Linked Security, the Exchange represents that it will prepare and distribute, if appropriate, an Information Memorandum to member organizations describing the product. Accordingly, the particular structure and corresponding risks of an Index-Linked Security will be highlighted and disclosed. In particular, the Memorandum will set forth the Exchange's suitability rule that requires a member organization recommending a transaction in Index-Linked Securities: (1) To determine that such transaction is suitable for the customer (NYSE Rule 723) and (2) to have a reasonable basis for believing that the customer can evaluate the special characteristics, and is able to bear the financial risks, of such transaction. In addition, the Information Memorandum will reference the requirement that NYSE member organizations must deliver a prospectus to investors purchasing newly issued Index-Linked Securities prior to or concurrently with the confirmation of a transaction. </P>
                <HD SOURCE="HD2">Surveillance </HD>
                <P>The Exchange will closely monitor activity in Index-Linked Securities to identify and deter any potential improper trading activity in such securities. Additionally, the Exchange represents that its surveillance procedures are adequate to properly monitor the trading of Index-Linked Securities. Specifically, the Exchange will rely on its existing surveillance procedures governing equities, options, and exchange-traded funds. The Exchange has developed procedures to closely monitor activity in Index-Linked Securities and the Underlying Indexes and their components to identify and deter potential improper trading activity. To the extent applicable, the Exchange will be able to obtain trading and beneficial holder information from the primary trading markets for the components of the Underlying Indexes in relation to Index-Linked Securities, either pursuant to bilateral information sharing agreements with those markets or because those markets are full members or affiliate members of the ISG. </P>
                <HD SOURCE="HD2">Firewall Procedures </HD>
                <P>If the Underlying Index is maintained by a broker-dealer, the broker-dealer shall erect a “firewall” around the personnel responsible for the maintenance of the Underlying Index or who have access to information concerning changes and adjustments to the Underlying Index, and the Underlying Index shall be calculated by a third party who is not a broker-dealer. Any advisory committee, supervisory board, or similar entity that advises an Index Licensor or Administrator (each as defined in NYSE Rule 1100, Supplementary Material .10) or that makes decisions regarding the Underlying Index or portfolio composition, methodology, and related matters must implement and maintain, or be subject to, procedures designed to prevent the use and dissemination of material, non-public information regarding the applicable Underlying Index or portfolio. </P>
                <P>
                    NYSE Rules 1300B(b) and Rule 1301B restrict the ability of the specialist firm for any issue of Commodity-Linked Securities or its affiliates to make markets in and trade the Commodity Reference Asset components, the commodities underlying the Commodity Reference Asset components, or options, futures, or options on futures on the Commodity Reference Asset, or any other derivatives based on the Commodity Reference Asset, any Commodity Reference Asset component, or any physical commodity or commodities underlying a Commodity Reference Asset component. Similarly, a proposed rule change to NYSE Rules 1300A and 1301A 
                    <SU>15</SU>
                    <FTREF/>
                     seeks to impose similar restrictions on the ability of the 
                    <PRTPAGE P="18716"/>
                    specialist firm for any issue of Currency-Linked Securities or its affiliates to make markets in and trade the Currency Reference Asset components, the currencies underlying the Currency Reference Asset components, or options, futures, or options on futures on the Currency Reference Asset, or any other derivatives based on the Currency Reference Asset, any Currency Reference Asset component, or any currency underlying a Currency Reference Asset component. 
                </P>
                <FTNT>
                    <P>
                        <SU>15</SU>
                         
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 55222 (February 1, 2007), 72 FR 6021 (February 8, 2007) (SR-NYSE-2006-68).
                    </P>
                </FTNT>
                <HD SOURCE="HD2">Trading Halts </HD>
                <P>In the case of Commodity-or Currency-Linked Securities, if the indicative value or the Commodity Reference Asset value or Currency Reference Asset value, as the case may be, applicable to a series of such securities is not being disseminated as required, or, in the case of Equity Index-Linked Securities, if the value of the Underlying Index is not being disseminated as required, the Exchange may halt trading during the day on which such interruption first occurs. If such interruption persists past the trading day in which it occurred, the Exchange will halt trading no later than the beginning of the trading day following the interruption. </P>
                <HD SOURCE="HD3">2. Statutory Basis </HD>
                <P>
                    The proposed rule change is consistent with Section 6(b) of the Act,
                    <SU>16</SU>
                    <FTREF/>
                     in general, and furthers the objectives of Section 6(b)(5) of the Act,
                    <SU>17</SU>
                    <FTREF/>
                     in particular, in that it is designed to promote just and equitable principles of trade, to foster cooperation and coordination with persons engaged in regulating, clearing, settling, processing information with respect to, and facilitating transactions in securities, 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. 
                </P>
                <FTNT>
                    <P>
                        <SU>16</SU>
                         15 U.S.C. 78f(b).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>17</SU>
                         15 U.S.C. 78f(b)(5).
                    </P>
                </FTNT>
                <HD SOURCE="HD2">B. Self-Regulatory Organization's Statement on Burden on Competition </HD>
                <P>The Exchange does not believe that the proposed rule change will impose any burden on competition that is not necessary or appropriate in furtherance of the purposes of the Act. </P>
                <HD SOURCE="HD2">C. Self-Regulatory Organization's Statement on Comments on the Proposed Rule Change Received From Members, Participants or Others </HD>
                <P>The Exchange has neither solicited nor received written comments on the proposed rule change. </P>
                <HD SOURCE="HD1">III. Date of Effectiveness of the Proposed Rule Change and Timing for Commission Action </HD>
                <P>
                    Within 35 days of the date of publication of this notice in the 
                    <E T="04">Federal Register</E>
                     or within such longer period (i) as the Commission may designate up to 90 days of such date if it finds such longer period to be appropriate and publishes its reasons for so finding or (ii) as to which the Exchange consents, the Commission will: 
                </P>
                <P>(A) By order approve such proposed rule change, or </P>
                <P>(B) Institute proceedings to determine whether the proposed rule change should be disapproved.</P>
                <FP>The Exchange has requested accelerated approval of this proposed rule change prior to the 30th day after the date of publication of the notice of the filing thereof. The Commission has determined that a 15-day comment period is appropriate in this case. </FP>
                <HD SOURCE="HD1">IV. Solicitation of Comments </HD>
                <P>Interested persons are invited to submit written data, views, and arguments concerning the foregoing, including whether the proposed rule change is consistent with the Act. Comments may be submitted by any of the following methods: </P>
                <HD SOURCE="HD2">Electronic Comments </HD>
                <P>
                    • Use the Commission's Internet comment form (
                    <E T="03">http://www.sec.gov/rules/sro.shtml</E>
                    ); or 
                </P>
                <P>
                    • Send an e-mail to 
                    <E T="03">rule-comments@sec.gov.</E>
                     Please include File Number SR-NYSE-2007-27 on the subject line. 
                </P>
                <HD SOURCE="HD2">Paper Comments </HD>
                <P>• Send paper comments in triplicate to Nancy M. Morris, Secretary, Securities and Exchange Commission, Station Place, 100 F Street, NE., Washington, DC 20549-1090.</P>
                <FP>
                    All submissions should refer to File Number SR-NYSE-2007-27. This file number should be included on the subject line if e-mail is used. To help the Commission process and review your comments more efficiently, please use only one method. The Commission will post all comments on the Commission's Internet Web site (
                    <E T="03">http://www.sec.gov/rules/sro.shtml</E>
                    ). 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 the filing also will be available for inspection and copying at the principal office of the Exchange. All comments received will be posted without change; the Commission does not edit personal identifying information from submissions. You should submit only information that you wish to make available publicly. All submissions should refer to File Number SR-NYSE-2007-27 and should be submitted on or before April 30, 2007. 
                </FP>
                <SIG>
                    <P>
                        For the Commission, by the Division of Market Regulation, pursuant to delegated authority.
                        <SU>18</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>18</SU>
                             17 CFR 200.30-3(a)(12).
                        </P>
                    </FTNT>
                    <NAME>Florence E. Harmon, </NAME>
                    <TITLE>Deputy Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC> [FR Doc. E7-7056 Filed 4-12-07; 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-55596; File No. SR-NYSEArca-2007-30] </DEPDOC>
                <SUBJECT>Self-Regulatory Organizations; NYSE Arca, Inc.; Notice of Filing and Immediate Effectiveness of Proposed Rule Change Amending Fees for Transactions in Listed and Nasdaq Securities Priced Less Than One Dollar </SUBJECT>
                <DATE>April 6, 2007. </DATE>
                <P>
                    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/>
                     notice is hereby given that on March 22, 2007, NYSE Arca, Inc. (“NYSE Arca” or “Exchange”), through its wholly owned subsidiary NYSE Arca Equities, Inc. (“NYSE Arca Equities”), filed with the Securities and Exchange Commission (“Commission”) the proposed rule change as described in Items I, II, and III below, which Items have been substantially prepared by the Exchange. NYSE Arca has filed the proposal pursuant to Section 19(b)(3)(A) of the Act 
                    <SU>3</SU>
                    <FTREF/>
                     and Rule 19b-4(f)(2) thereunder,
                    <SU>4</SU>
                    <FTREF/>
                      
                    <PRTPAGE P="18717"/>
                    which renders the proposal effective upon filing with the Commission. The Commission is publishing this notice to solicit comments on the proposed rule change from interested persons. 
                </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. 78s(b)(3)(A). 
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         17 CFR 240.19b-4(f)(2). 
                    </P>
                </FTNT>
                <HD SOURCE="HD1">I. Self-Regulatory Organization's Statement of the Terms of Substance of the Proposed Rule Change </HD>
                <P>
                    The Exchange proposes to amend the section of its Schedule of Fees and Charges for Exchange Services (“Fee Schedule”) that applies to transactions by ETP Holders 
                    <SU>5</SU>
                    <FTREF/>
                     to add a pricing structure for listed and Nasdaq securities priced less than one dollar. The text of the proposed rule change is available at NYSE Arca, the Commission's Public Reference Room, and 
                    <E T="03">www.nysearca.com.</E>
                </P>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         
                        <E T="03">See</E>
                         NYSE Arca Equities Rule 1.1(n). 
                    </P>
                </FTNT>
                <HD SOURCE="HD1">II. Self-Regulatory Organization's Statement of the Purpose of, and Statutory Basis for, the Proposed Rule Change </HD>
                <P>In its filing with the Commission, NYSE Arca included statements concerning the purpose of and basis for the proposed rule change and discussed any comments it received on the proposed rule change. The text of these statements may be examined at the places specified in Item IV below. NYSE Arca has prepared summaries, set forth in Sections A, B, and C below, of the most significant aspects of such statements. </P>
                <HD SOURCE="HD2">A. Self-Regulatory Organization's Statement of the Purpose of, and Statutory Basis for, the Proposed Rule Change </HD>
                <HD SOURCE="HD3">1. Purpose </HD>
                <P>
                    The Exchange proposes to amend the section of its Fee Schedule that applies to transactions by ETP Holders to add a separate pricing structure for listed and Nasdaq securities priced less than one dollar ($1.00) consistent with Rule 610(c) of Regulation NMS.
                    <SU> 6</SU>
                    <FTREF/>
                     The Exchange intends to implement these changes to the Fee Schedule pursuant to this proposal immediately upon filing. 
                </P>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         17 CFR 242.610(c). 
                    </P>
                </FTNT>
                <P>The Fee Schedule currently provides that ETP Holders are charged between $0.001 per share and $0.003 per share for round-lot transactions in NYSE-listed and Nasdaq securities that execute against orders residing on the NYSE Arca Book. ETP Holders are charged $0.03 per share for listed securities and $0.004 per share for Nasdaq securities for odd-lot orders that execute against orders residing on the NYSE Arca Book. Similarly, ETP Holder orders that route to any away market center or participant and are executed are charged between $0.001 per share and $0.03 per share, dependent upon the away market center or participant, the type of security, and whether the transaction was for a round or odd-lot. </P>
                <P>
                    The Exchange proposes to amend the Fee Schedule to (i) clarify that these fees will remain unchanged for listed and Nasdaq securities priced greater than or equal to $1.00, and (ii) add a separate, distinct pricing structure for listed and Nasdaq securities priced less than $1.00, pursuant to Rule 610(c) of Regulation NMS, and consistent with the recent fee announcement 
                    <SU>7</SU>
                    <FTREF/>
                     by The NASDAQ Stock Market LLC. Specifically, the Exchange proposes to implement a fee of 0.1% of the total dollar value for all round and odd-lot transactions of ETP Holders that execute against orders residing on the NYSE Arca Book for listed or Nasdaq securities priced less than $1.00, and shall impose a fee of 0.3% of the total dollar value for orders of listed and Nasdaq securities priced less than $1.00 that route and are executed with any away market center or participant. The Exchange will not provide a rebate (credit) to ETP Holders for any transactions in securities priced less than $1.00. 
                </P>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 55576 (April 3, 2007) (SR-NASDAQ-2007-026); 
                        <E T="03">see also</E>
                         NASDAQ Head Trader Alert #2007-065: NASDAQ Announces Pricing Change for Non-NASDAQ Listed Executions Under $1 (March 21, 2007) (announcing an execution fee of 0.1%, or 10 basis points, for non-NASDAQ securities with a share price below $1.00). 
                    </P>
                </FTNT>
                <HD SOURCE="HD3">2. Statutory Basis </HD>
                <P>
                    The Exchange believes that the proposed rule change is consistent with Section 6(b) of the Act,
                    <SU>8</SU>
                    <FTREF/>
                     in general, and furthers the objectives of Section 6(b)(4) of the Act,
                    <SU>9</SU>
                    <FTREF/>
                     in particular, in that it is intended to provide for the equitable allocation of reasonable dues, fees, and other charges among its members and other persons using its facilities. 
                </P>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         15 U.S.C. 78f(b). 
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         15 U.S.C. 78f(b)(4). 
                    </P>
                </FTNT>
                <HD SOURCE="HD2">B. Self-Regulatory Organization's Statement on Burden on Competition </HD>
                <P>The Exchange does not believe that the proposed rule change will result in any burden on competition that is not necessary or appropriate in furtherance of the purposes of the Act. </P>
                <HD SOURCE="HD2">C. Self-Regulatory Organization's Statement on Comments on the Proposed Rule Change Received From Members, Participants or Others </HD>
                <P>No written comments were either solicited or received. </P>
                <HD SOURCE="HD1">III. Date of Effectiveness of the Proposed Rule Change and Timing for Commission Action </HD>
                <P>
                    The foregoing rule change has become effective pursuant to Section 19(b)(3)(A)(ii) of the Act 
                    <SU>10</SU>
                    <FTREF/>
                     and subparagraph (f)(2) of Rule 19b-4 thereunder 
                    <SU>11</SU>
                    <FTREF/>
                     because it establishes or changes a due, fee, or other charge applicable only to a member imposed by the self-regulatory organization. Accordingly, the proposal is effective upon Commission receipt of the filing. At any time within 60 days of the filing of the proposed rule change, the Commission may summarily abrogate such rule change if it appears to the Commission that such action is necessary or appropriate in the public interest, for the protection of investors, or otherwise in furtherance of the purposes of the Act. 
                </P>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         15 U.S.C. 78s(b)(3)(A)(ii). 
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         17 CFR 240.19b-4(f)(2). 
                    </P>
                </FTNT>
                <HD SOURCE="HD1">IV. Solicitation of Comments </HD>
                <P>Interested persons are invited to submit written data, views, and arguments concerning the foregoing, including whether the proposed rule change is consistent with the Act. Comments may be submitted by any of the following methods: </P>
                <HD SOURCE="HD2">Electronic Comments </HD>
                <P>
                    • Use the Commission's Internet comment form (
                    <E T="03">http://www.sec.gov/rules/sro.shtml</E>
                    ); or 
                </P>
                <P>
                    • Send an e-mail to 
                    <E T="03">rule-comments@sec.gov.</E>
                     Please include File Number SR-NYSEArca-2007-30 on the subject line. 
                </P>
                <HD SOURCE="HD2">Paper Comments </HD>
                <P>• Send paper comments in triplicate to Nancy M. Morris, Secretary, Securities and Exchange Commission, 100 F Street, NE., Washington, DC 20549-1090. </P>
                <FP>
                    All submissions should refer to File Number SR-NYSEArca-2007-30. This file number should be included on the subject line if e-mail is used. To help the Commission process and review your comments more efficiently, please use only one method. The Commission will post all comments on the Commission's Internet Web site (
                    <E T="03">http://www.sec.gov/rules/sro.shtml</E>
                    ). 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 
                    <PRTPAGE P="18718"/>
                    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 the filing also will be available for inspection and copying at the principal office of NYSE Arca. All comments received will be posted without change; the Commission does not edit personal identifying information from submissions. You should submit only information that you wish to make available publicly. All submissions should refer to File Number SR-NYSEArca-2007-30 and should be submitted on or before May 4, 2007. 
                </FP>
                <SIG>
                    <P>
                        For the Commission, by the Division of Market Regulation, pursuant to delegated authority.
                        <SU>12</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>12</SU>
                             17 CFR 200.30-3(a)(12). 
                        </P>
                    </FTNT>
                    <NAME>Florence E. Harmon, </NAME>
                    <TITLE>Deputy Secretary. </TITLE>
                </SIG>
            </PREAMB>
            <FRDOC> [FR Doc. E7-6959 Filed 4-12-07; 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-55599; File No. SR-Phlx-2007-32] </DEPDOC>
                <SUBJECT>Self-Regulatory Organizations; Philadelphia Stock Exchange, Inc.; Notice of Filing and Immediate Effectiveness of Proposed Rule Change Relating to the Equity Option and Index Option Floor Brokerage Assessment </SUBJECT>
                <DATE>April 6, 2007. </DATE>
                <P>
                    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/>
                     notice is hereby given that on March 30, 2007, the Philadelphia Stock Exchange, Inc. (“Phlx” or “Exchange”) filed with the Securities and Exchange Commission (“Commission”) the proposed rule change as described in Items I, II, and III below, which Items have been substantially prepared by Phlx. Phlx filed the proposal pursuant to Section 19(b)(3)(A)(ii) of the Act 
                    <SU>3</SU>
                    <FTREF/>
                     and Rule 19b-4(f)(2) thereunder,
                    <SU>4</SU>
                    <FTREF/>
                     which renders the proposal effective upon filing with the Commission. The Commission is publishing this notice to solicit comments on the proposed rule change from interested persons. 
                </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. 78s(b)(3)(A)(ii).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         17 CFR 240.19b-4(f)(2).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">I. Self-Regulatory Organization's Statement of the Terms of Substance of the Proposed Rule Change </HD>
                <P>Phlx proposes to amend the equity option and index option Floor Brokerage Assessment to change the levels of the monthly net floor brokerage income and corresponding assessment and to effectively reduce the fee cap from $100,000 per month to $10,000 per month. The proposed equity option and index option Floor Brokerage Assessment is set forth below: </P>
                <GPOTABLE COLS="2" OPTS="L2,tp0,i1" CDEF="s50,r75">
                    <TTITLE>  </TTITLE>
                    <BOXHD>
                        <CHED H="1">Monthly net floor brokerage income </CHED>
                        <CHED H="1">Assessment </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">$0-$200,000 </ENT>
                        <ENT>5% for all amounts up to and including $200,000. </ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01">Any amount over $200,000 </ENT>
                        <ENT>No additional charge. </ENT>
                    </ROW>
                    <ROW EXPSTB="01">
                        <ENT I="21">Monthly Cap: $10,000. </ENT>
                    </ROW>
                </GPOTABLE>
                <FP>The proposed amendments to the Floor Brokerage Assessment, as set forth above, are scheduled to become effective for trades settling on or after April 2, 2007. </FP>
                <P>
                    The Exchange also proposes to make a minor technical change to clarify that the title “Summary of Equity Option and RUT and RMN Charges” should appear on each page of that section of the fee schedule rather than merely on the first page. The text of the proposed rule change is available at Phlx, the Commission's Public Reference Room, and 
                    <E T="03">http://www.phlx.com</E>
                    . 
                </P>
                <HD SOURCE="HD1">II. Self-Regulatory Organization's Statement of the Purpose of, and Statutory Basis for, the Proposed Rule Change </HD>
                <P>In its filing with the Commission, Phlx included statements concerning the purpose of, and basis for, the proposed rule change and discussed any comments it received on the proposed rule change. The text of these statements may be examined at the places specified in Item IV below. Phlx has prepared summaries, set forth in Sections A, B, and C below, of the most significant aspects of such statements. </P>
                <HD SOURCE="HD2">A. Self-Regulatory Organization's Statement of the Purpose of, and Statutory Basis for, the Proposed Rule Change </HD>
                <HD SOURCE="HD3">1. Purpose </HD>
                <P>
                    The purpose of amending the Floor Brokerage Assessment, including effectively lowering the monthly fee cap to $10,000,
                    <SU>5</SU>
                    <FTREF/>
                     is to create a financial incentive for floor brokers to send additional order flow to the Exchange, which should, in turn, allow the Exchange to remain competitive. 
                </P>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         Although the fee schedule will reflect a cap of $10,000, in actuality listing the cap is just for clarity; mathematically, the cap would exist anyway because the 5% assessment would be applied to the monthly net floor brokerage income for all amounts up to and including $200,000. For example, if the net floor brokerage income is $300,000 for a particular month, then the first $200,000 would be assessed a rate of 5%, (which is $10,000) and the remainder ($100,000) would not be charged any additional Floor Brokerage Assessment.
                    </P>
                </FTNT>
                <P>
                    The purpose of setting forth the title “Summary of Equity Option and RUT and RMN Charges” on each applicable page of the fee schedule is to codify a change that was recently made to the Exchange's fee schedule. The Exchange recently filed a proposed rule change to assess equity option charges (including payment for order flow charges), as opposed to index option charges, on (1) options on the Russell 2000® Index 
                    <SU>6</SU>
                    <FTREF/>
                     traded under the symbol RUT (the “Full Value Russell Index”), and (2) options on the one-tenth value Russell 2000® Index traded under the symbol RMN (the “Reduced Value Russell Index”).
                    <SU>7</SU>
                    <FTREF/>
                     The Exchange changed the title of the first page of the equity option fee schedule from “Summary of Equity Option Charges” to “Summary of Equity Option and RUT and RMN Charges,” but inadvertently did not make corresponding changes to the title on each subsequent page of the equity option fee schedule. Thus, placing the title “Summary of Equity Option and RUT and RMN Charges” on each page will more accurately reflect the changes that were recently made to the Exchange's fee schedule, as described above. 
                </P>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         Russell 2000® is a trademark and service mark of the Frank Russell Company, used under license. Neither Frank Russell Company's publication of the Russell Indexes nor its licensing of its trademarks for use in connection with securities or other financial products derived from a Russell Index in any way suggests or implies a representation or opinion by Frank Russell Company as to the attractiveness of investment in any securities or other financial products based upon or derived from any Russell Index. Frank Russell Company is not the issuer of any such securities or other financial products and makes no express or implied warranties of merchantability or fitness for any particular purpose with respect to any Russell Index or any data included or reflected therein, nor as to results to be obtained by any person or any entity from the use of the Russell Index or any data included or reflected therein. 
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 55473 (March 14, 2007), 72 FR 13338 (March 21, 2007) (SR-Phlx-2007-12).
                    </P>
                </FTNT>
                <HD SOURCE="HD3">2. Statutory Basis </HD>
                <P>
                    The Exchange believes that its proposal to amend its schedule of fees is consistent with Section 6(b) of the Act,
                    <SU>8</SU>
                    <FTREF/>
                     in general, and furthers the objectives of Section 6(b)(4) of the Act,
                    <SU>9</SU>
                    <FTREF/>
                     in particular, in that it is an equitable 
                    <PRTPAGE P="18719"/>
                    allocation of reasonable fees and other charges among Exchange members. 
                </P>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         15 U.S.C. 78f(b). 
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         15 U.S.C. 78f(b)(4). 
                    </P>
                </FTNT>
                <HD SOURCE="HD2">B. Self-Regulatory Organization's Statement on Burden on Competition </HD>
                <P>The Exchange does not believe that the proposed rule change will impose any burden on competition that is not necessary or appropriate in furtherance of the purposes of the Act. </P>
                <HD SOURCE="HD2">C. Self-Regulatory Organization's Statement on Comments on the Proposed Rule Change Received From Members, Participants, or Others </HD>
                <P>The Exchange has neither solicited nor received written comments on the proposed rule change. </P>
                <HD SOURCE="HD1">III. Date of Effectiveness of the Proposed Rule Change and Timing for Commission Action </HD>
                <P>
                    The foregoing proposed rule change has been designated as a fee change pursuant to Section 19(b)(3)(A)(ii) of the Act 
                    <SU>10</SU>
                    <FTREF/>
                     and Rule 19b-4(f)(2) 
                    <SU>11</SU>
                    <FTREF/>
                     thereunder. Accordingly, the proposed rule change is effective upon filing with the Commission. At any time within 60 days of the filing of the proposed rule change, the Commission may summarily abrogate such rule change if it appears to the Commission that such action is necessary or appropriate in the public interest, for the protection of investors, or otherwise in furtherance of the purposes of the Act. 
                </P>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         15 U.S.C. 78s(b)(3)(A)(ii). 
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         17 CFR 240.19b-4(f)(2). 
                    </P>
                </FTNT>
                <HD SOURCE="HD1">IV. Solicitation of Comments </HD>
                <P>Interested persons are invited to submit written data, views, and arguments concerning the foregoing, including whether the proposed rule change is consistent with the Act. Comments may be submitted by any of the following methods: </P>
                <HD SOURCE="HD2">Electronic Comments </HD>
                <P>
                    • Use the Commission's Internet comment form (
                    <E T="03">http://www.sec.gov/rules/sro.shtml</E>
                    ); or 
                </P>
                <P>
                    • Send an e-mail to 
                    <E T="03">rule-comments@sec.gov</E>
                    . Please include File No. SR-Phlx-2007-32 on the subject line. 
                </P>
                <HD SOURCE="HD2">Paper Comments </HD>
                <P>• Send paper comments in triplicate to Nancy M. Morris, Secretary, Securities and Exchange Commission, Station Place, 100 F Street, NE., Washington, DC 20549-1090. </P>
                <FP>
                    All submissions should refer to File No. SR-Phlx-2007-32. This file number should be included on the subject line if e-mail is used. To help the Commission process and review your comments more efficiently, please use only one method. The Commission will post all comments on the Commission's Internet Web site (
                    <E T="03">http://www.sec.gov/rules/sro.shtml</E>
                    ). 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 filing will also be available for inspection and copying at the principal office of the Exchange. All comments received will be posted without change; the Commission does not edit personal identifying information from submissions. You should submit only information that you wish to make available publicly. All submissions should refer to File No. SR-Phlx-2007-32 and should be submitted on or before May 4, 2007. 
                </FP>
                <SIG>
                    <P>
                        For the Commission, by the Division of Market Regulation, pursuant to delegated authority.
                        <SU>12</SU>
                        <FTREF/>
                    </P>
                    <NAME>Florence E. Harmon, </NAME>
                    <TITLE>Deputy Secretary. </TITLE>
                </SIG>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         17 CFR 200.30-3(a)(12). 
                    </P>
                </FTNT>
            </PREAMB>
            <FRDOC> [FR Doc. E7-7007 Filed 4-12-07; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 8010-01-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">SMALL BUSINESS ADMINISTRATION </AGENCY>
                <DEPDOC>[Disaster Declaration #10849] </DEPDOC>
                <SUBJECT>Washington Disaster # WA-00012 Declaration of Economic Injury </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Small Business Administration. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This is a notice of an Economic Injury Disaster Loan (EIDL) declaration for the State of Washington, dated 04/09/2007. </P>
                    <P>
                        <E T="03">Incident:</E>
                         Windstorm. 
                    </P>
                    <P>
                        <E T="03">Incident Period:</E>
                         12/14/2006 through 12/15/2006. 
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">Effective Date:</HD>
                    <P>04/09/2007. </P>
                    <P>
                        <E T="03">EIDL Loan Application Deadline Date:</E>
                         01/09/2008. 
                    </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Submit completed loan applications to: U.S. Small Business Administration, Processing and Disbursement Center, 14925 Kingsport Road, Fort Worth, TX 76155. </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>A. Escobar, Office of Disaster Assistance, U.S. Small Business Administration, 409 3rd Street, SW, Suite 6050, Washington, DC 20416. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>Notice is hereby given that as a result of the Administrator's EIDL declaration, applications for economic injury disaster loans may be filed at the address listed above or other locally announced locations. </P>
                <P>The following areas have been determined to be adversely affected by the disaster: </P>
                <FP SOURCE="FP-1">
                    <E T="03">Primary Counties:</E>
                     King, Lewis, San Juan 
                </FP>
                <FP SOURCE="FP-2">
                    <E T="03">Contiguous Counties:</E>
                </FP>
                <FP SOURCE="FP1-2">Washington: Chelan, Cowlitz, Grays Harbor, Kitsap, Kittitas, Pacific, Pierce, Skamania, Snohomish, Thurston, Wahkiakum, Yakima </FP>
                <P>The Interest Rate is: 4.000. </P>
                <P>The number assigned to this disaster for economic injury is 108490. </P>
                <P>The States which received an EIDL Declaration # is Washington. </P>
                <EXTRACT>
                    <FP>(Catalog of Federal Domestic Assistance Number 59002)</FP>
                </EXTRACT>
                <SIG>
                    <DATED>Dated: April 9, 2007. </DATED>
                    <NAME>Steven C. Preston, </NAME>
                    <TITLE>Administrator.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. E7-7029 Filed 4-12-07; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 8025-01-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">SMALL BUSINESS ADMINISTRATION </AGENCY>
                <SUBJECT>Audit and Financial Management Advisory (AFMAC) Committee Notice of Cancellation of Public Meeting </SUBJECT>
                <P>
                    The U.S. Small Business Administration, Audit and Financial Management Advisory Committee (AFMAC) federal meeting originally scheduled for Wednesday, April 18, 2007 has been cancelled. A new date and time for this meeting will be announced soon. If you have any questions, please contact Jennifer Main, Chief Financial Officer, 409 3rd Street, SW., 6th Floor, Washington, DC 20416, phone: (202) 205-6449, e-mail: 
                    <E T="03">Jennifer.Main@sba.gov</E>
                    . 
                </P>
                <SIG>
                    <NAME>Matthew Teague, </NAME>
                    <TITLE>Committee Management Officer.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. E7-7030 Filed 4-12-07; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 8025-01-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="18720"/>
                <AGENCY TYPE="N">DEPARTMENT OF STATE </AGENCY>
                <DEPDOC>[Public Notice: 5771] </DEPDOC>
                <SUBJECT> 60-Day Notice of Proposed Information Collection: DS-230, Application for Immigrant Visa and Alien Registration, OMB Number 1405-0015 </SUBJECT>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of request for public comments. </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. We are conducting this process in accordance with the Paperwork Reduction Act of 1995. 
                    </P>
                    <P>
                        • 
                        <E T="03">Title of Information Collection:</E>
                         Application for Immigrant Visa and Alien Registration. 
                    </P>
                    <P>
                        • 
                        <E T="03">OMB Control Number:</E>
                         1405-0015. 
                    </P>
                    <P>
                        • 
                        <E T="03">Type of Request:</E>
                         Extension of a Currently Approved Collection. 
                    </P>
                    <P>
                        • 
                        <E T="03">Originating Office:</E>
                         Bureau of Consular Affairs, Department of State (CA/VO). 
                    </P>
                    <P>
                        • 
                        <E T="03">Form Number:</E>
                         DS-230. 
                    </P>
                    <P>
                        • 
                        <E T="03">Respondents:</E>
                         Immigrant visa applicants. 
                    </P>
                    <P>
                        • 
                        <E T="03">Estimated Number of Respondents:</E>
                         475,000 per year. 
                    </P>
                    <P>
                        • 
                        <E T="03">Estimated Number of Responses:</E>
                         475,000 per year. 
                    </P>
                    <P>
                        • 
                        <E T="03">Average Hours per Response:</E>
                         2 hours. 
                    </P>
                    <P>
                        • 
                        <E T="03">Total Estimated Burden:</E>
                         950,000 hours per year. 
                    </P>
                    <P>
                        • 
                        <E T="03">Frequency:</E>
                         Once per respondent. 
                    </P>
                    <P>
                        • 
                        <E T="03">Obligation to Respond:</E>
                         Required to Obtain or Retain a Benefit. 
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATE(S):</HD>
                    <P>The Department will accept comments from the public up to 60 days from April 13, 2007. </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may submit comments by any of the following methods: </P>
                    <P>
                        • E-mail: 
                        <E T="03">VisaRegs@state.gov</E>
                         (Subject line must read DS-230 Reauthorization). 
                    </P>
                    <P>• Mail (paper, disk, or CD-ROM submissions): Chief, Legislation and Regulation Division, Visa Services—DS-1884 Reauthorization, 2401 E. Street, NW., Washington DC 20520-30106. </P>
                    <P>• Fax: (202) 663-3898. </P>
                    <P>You must include the DS form number (if applicable), information collection title, and OMB control number in any correspondence. </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Direct requests for additional information regarding the collection listed in this notice, including requests for copies of the proposed information collection and supporting documents, to Lauren Prosnik of the Office of Visa Services, U.S. Department of State, 2401 E. Street, NW., L-603, Washington, DC 20522, who may be reached at (202) 663-2951 or 
                        <E T="03">prosnikla@state.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>We are soliciting public comments to permit the Department to: </P>
                <P>• Evaluate whether the proposed information collection is necessary for the proper performance of our functions. </P>
                <P>• Evaluate the accuracy of our 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 the use of automated collection techniques or other forms of technology. </P>
                <P>
                    <E T="03">Abstract of proposed collection:</E>
                </P>
                <P>Form DS-230 is used to elicit information to determine the eligibility of aliens applying for immigrant visas. </P>
                <P>
                    <E T="03">Methodology:</E>
                </P>
                <P>The information will be collected in person at posts. </P>
                <SIG>
                    <DATED>Dated: March 30, 2007. </DATED>
                    <NAME>Stephen A. Edson, </NAME>
                    <TITLE> Deputy Assistant Secretary for Bureau of Consular Affairs, Department of State.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. E7-7043 Filed 4-12-07; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4710-06-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF STATE </AGENCY>
                <DEPDOC>[Public Notice: 5770] </DEPDOC>
                <SUBJECT>30-Day Notice of Proposed Information Collection: DS-4100, Iran Program Vetting, OMB 1405-0176 </SUBJECT>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of request for public comment and submission to OMB of proposed collection of information. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Department of State has submitted the following information collection request to the Office of Management and Budget (OMB) for approval in accordance with the Paperwork Reduction Act of 1995. </P>
                    <P>
                        • 
                        <E T="03">Title of Information Collection:</E>
                         Iran program vetting. 
                    </P>
                    <P>
                        • 
                        <E T="03">OMB Control Number:</E>
                         OMB 1405-0176. 
                    </P>
                    <P>
                        • 
                        <E T="03">Type of Request:</E>
                         Extension of currently approved collection. 
                    </P>
                    <P>
                        • 
                        <E T="03">Originating Offices:</E>
                         Bureau of Near Eastern Affairs, Bureau of Democracy Human Rights and Labor, Bureau of Educational and Cultural Affairs. 
                    </P>
                    <P>
                        • 
                        <E T="03">Form Number:</E>
                         DS 4100. 
                    </P>
                    <P>
                        • 
                        <E T="03">Respondents:</E>
                         Program applicants. 
                    </P>
                    <P>
                        • 
                        <E T="03">Estimated Number of Respondents:</E>
                         200. 
                    </P>
                    <P>
                        • 
                        <E T="03">Estimated Number of Responses:</E>
                         200. 
                    </P>
                    <P>
                        • 
                        <E T="03">Average Hours per Response:</E>
                         1 hour. 
                    </P>
                    <P>
                        • 
                        <E T="03">Total Estimated Burden:</E>
                         200 hours. 
                    </P>
                    <P>
                        • 
                        <E T="03">Frequency:</E>
                         On occasion. 
                    </P>
                    <P>
                        • 
                        <E T="03">Obligation to Respond:</E>
                         Required to Obtain or Retain Benefit. 
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATE(S):</HD>
                    <P>Submit comments to the Office of Management and Budget (OMB) for up to 30 days from April 13, 2007. </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Direct comments and questions to Katherine Astrich, the Department of State Desk Officer in the Office of Information and Regulatory Affairs at the Office of Management and Budget (OMB), who may be reached at 202-395-4718. You may submit comments by any of the following methods: </P>
                    <P>
                        • E-mail: 
                        <E T="03">kastrich@omb.eop.gov</E>
                        . You must include the DS form number, information collection title, and OMB control number in the subject line of your message. 
                    </P>
                    <P>• Mail (paper, disk, or CD-ROM submissions): Office of Information and Regulatory Affairs, Office of Management and Budget, 725 17th Street, NW., Washington, DC 20503. </P>
                    <P>• Fax: 202-395-6974 </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        You may obtain copies of the proposed information collection and supporting documents from Thomas Hill, who may be reached at 202-647-2942 or at 
                        <E T="03">HillTM2@state.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>We are soliciting public comments to permit the Department to: </P>
                <P>• Evaluate whether the proposed information collection is necessary to properly perform our functions. </P>
                <P>• Evaluate the accuracy of our 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, </P>
                <P>
                    <E T="03">Abstract of proposed collection:</E>
                </P>
                <P>
                    A critical component of the Administration's Iran policy is the support for indigenous Iranian voices calling for freedom. President Bush himself has pledged this support and the State Department has made the awarding of grants for this purpose a key component of its Iran policy. As a condition of licensing these activities, the Office of Foreign Assets Control (OFAC) has requested the Department of State to follow certain procedures to effectuate the goals of Sections 481(b), 531(a), 571, 582, and 635(b) of the Foreign Assistance Act of 1961 (as 
                    <PRTPAGE P="18721"/>
                    amended); 18 U.S.C. 2339A and 2339B; Executive Order 13224; and Homeland Security Presidential Directive 6. These licensing conditions mandate that the Department conduct a vetting of potential Iran democracy grantees and sub-grantees for counter-terrorism purposes. To conduct this vetting the Department will collect information from grantees and sub-grantees regarding the identity and background of their key employees and Boards of Directors. 
                </P>
                <P>
                    <E T="03">Methodology:</E>
                </P>
                <P>DS 4100 information collection device will be forwarded to potential grantee electronically; respondents will be requested to return form to appropriate Department of State Bureau via fax, post-mail, or electronically.</P>
                <SIG>
                    <DATED>Dated: March 16, 2007.</DATED>
                    <NAME>David M. Denehy,</NAME>
                    <TITLE>Senior Advisor, Bureau of Near Eastern Affairs, Department of State.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. E7-7045 Filed 4-12-07; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4710-31-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF STATE </AGENCY>
                <DEPDOC>[Public Notice: 5769] </DEPDOC>
                <SUBJECT>60-Day Notice of Proposed Information Collection: Form DS-156K, Nonimmigrant Fiance(e) Visa Application, OMB Control Number 1405-0096 </SUBJECT>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of request for public comments. </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. We are conducting this process in accordance with the Paperwork Reduction Act of 1995. 
                    </P>
                    <P>
                        • 
                        <E T="03">Title of Information Collection:</E>
                         Nonimmigrant Fiance(e) Visa Application. 
                    </P>
                    <P>
                        • 
                        <E T="03">OMB Control Number:</E>
                         1405-0096. 
                    </P>
                    <P>
                        • 
                        <E T="03">Type of Request:</E>
                         Extension of a Currently Approved Collection. 
                    </P>
                    <P>
                        • 
                        <E T="03">Originating Office:</E>
                         Bureau of Consular Affairs, Department of State (CA/VO). 
                    </P>
                    <P>
                        • 
                        <E T="03">Form Number:</E>
                         DS-156K. 
                    </P>
                    <P>
                        • 
                        <E T="03">Respondents:</E>
                         Aliens applying for a nonimmigrant visa to enter the U.S. as the fiancé(e) of a U.S. citizen. 
                    </P>
                    <P>
                        • 
                        <E T="03">Estimated Number of Respondents:</E>
                         35,000. 
                    </P>
                    <P>
                        • 
                        <E T="03">Estimated Number of Responses:</E>
                         35,000. 
                    </P>
                    <P>
                        • 
                        <E T="03">Average Hours per Response:</E>
                         1 hour. 
                    </P>
                    <P>
                        • 
                        <E T="03">Total Estimated Burden:</E>
                         35,000 hours per year. 
                    </P>
                    <P>
                        • 
                        <E T="03">Frequency:</E>
                         Once per respondent. 
                    </P>
                    <P>
                        • 
                        <E T="03">Obligation to Respond:</E>
                         Required to Obtain or Retain a Benefit. 
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATE(S):</HD>
                    <P>The Department will accept comments from the public up to 60 days from April 13, 2007. </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may submit comments by any of the following methods: </P>
                    <P>
                        • E-mail: 
                        <E T="03">VisaRegs@state.gov</E>
                         (Subject line must read DS-156K Reauthorization). 
                    </P>
                    <P>• Mail (paper, disk, or CD-ROM submissions): Chief, Legislation and Regulation Division, Visa Services—DS-1884 Reauthorization, 2401 E. Street, NW., Washington, DC 20520-30106. </P>
                    <P>• Fax: (202) 663-3898 </P>
                    <P>You must include the DS form number (if applicable), information collection title, and OMB control number in any correspondence. </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Direct requests for additional information regarding the collection listed in this notice, including requests for copies of the proposed information collection and supporting documents, to Lauren Prosnik of the Office of Visa Services, U.S. Department of State, 2401 E. Street, NW., L-603, Washington, DC 20522, who may be reached at (202) 663-2951 or 
                        <E T="03">prosnikla@state.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>We are soliciting public comments to permit the Department to: </P>
                <P>• Evaluate whether the proposed information collection is necessary for the proper performance of our functions. </P>
                <P>• Evaluate the accuracy of our 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 the use of automated collection techniques or other forms of technology. </P>
                <P>
                    <E T="03">Abstract of proposed collection:</E>
                </P>
                <P>Form DS-156K is used by consular officers to determine the eligibility of an alien applicant for a non-immigrant fiancé(e) visa. </P>
                <P>
                    <E T="03">Methodology:</E>
                </P>
                <P>The DS-156K is submitted to consular posts abroad. </P>
                <SIG>
                    <DATED>Dated: March 30, 2007. </DATED>
                    <NAME>Stephen A. Edson, </NAME>
                    <TITLE>Deputy Assistant Secretary for Bureau of Consular Affairs, Department of State.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. E7-7046 Filed 4-12-07; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4710-06-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF STATE </AGENCY>
                <DEPDOC>[Public Notice: 5768] </DEPDOC>
                <SUBJECT> 60-Day Notice of Proposed Information Collection: DS-156E, Nonimmigrant Treaty Trader/Investor Application, OMB Control Number 1405-0101 </SUBJECT>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of request for public comments. </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. We are conducting this process in accordance with the Paperwork Reduction Act of 1995. 
                    </P>
                    <P>
                        • 
                        <E T="03">Title of Information Collection:</E>
                         Nonimmigrant Treaty Trader/Investor Application. 
                    </P>
                    <P>
                        • 
                        <E T="03">OMB Control Number:</E>
                         1405-0101. 
                    </P>
                    <P>
                        • 
                        <E T="03">Type of Request:</E>
                         Extension of a Currently Approved Collection. 
                    </P>
                    <P>
                        • 
                        <E T="03">Originating Office:</E>
                         Bureau of Consular Affairs, Department of State (CA/VO). 
                    </P>
                    <P>
                        • 
                        <E T="03">Form Number:</E>
                         DS-156E. 
                    </P>
                    <P>
                        • 
                        <E T="03">Respondents:</E>
                         Nonimmigrant treaty trader/investor visa applicants. 
                    </P>
                    <P>
                        • 
                        <E T="03">Estimated Number of Respondents:</E>
                         17,000. 
                    </P>
                    <P>
                        • 
                        <E T="03">Estimated Number of Responses:</E>
                         17,000. 
                    </P>
                    <P>
                        • 
                        <E T="03">Average Hours per Response:</E>
                         4 hours. 
                    </P>
                    <P>
                        • 
                        <E T="03">Total Estimated Burden:</E>
                         68,000 hours per year. 
                    </P>
                    <P>
                        • 
                        <E T="03">Frequency:</E>
                         Once per respondent. 
                    </P>
                    <P>
                        • 
                        <E T="03">Obligation to Respond:</E>
                         Required to Obtain or Retain a Benefit. 
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATE(S):</HD>
                    <P>The Department will accept comments from the public up to 60 days from April 13, 2007. </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may submit comments by any of the following methods: </P>
                    <P>
                        • E-mail: 
                        <E T="03">VisaRegs@state.gov</E>
                         (Subject line must read DS-156E Reauthorization). 
                    </P>
                    <P>• Mail (paper, disk, or CD-ROM submissions): Chief, Legislation and Regulation Division, Visa Services—DS-1884 Reauthorization, 2401 E Street, NW., Washington, DC 20520-30106. </P>
                    <P>• Fax: (202) 663-3898. </P>
                    <P>You must include the DS form number (if applicable), information collection title, and OMB control number in any correspondence. </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Direct requests for additional information regarding the collection listed in this notice, including requests for copies of the proposed information collection and supporting documents, to 
                        <PRTPAGE P="18722"/>
                        Lauren Prosnik of the Office of Visa Services, U.S. Department of State, 2401 E Street, NW., L-603, Washington, DC 20522, who may be reached at (202) 663-2951 or 
                        <E T="03">prosnikla@state.gov</E>
                        . 
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>We are soliciting public comments to permit the Department to: </P>
                <P>• Evaluate whether the proposed information collection is necessary for the proper performance of our functions. </P>
                <P>• Evaluate the accuracy of our 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 the use of automated collection techniques or other forms of technology. </P>
                <P>
                    <E T="03">Abstract of proposed collection:</E>
                </P>
                <P>Form DS-156E is completed by aliens seeking nonimmigrant treaty trader/investor visas to the U.S. The Department will use the DS-156E to elicit information necessary to determine an applicant's visa eligibility. </P>
                <P>
                    <E T="03">Methodology:</E>
                </P>
                <P>The DS-156E is submitted to consular posts abroad. </P>
                <SIG>
                    <DATED>Dated: March 30, 2007. </DATED>
                    <NAME>Stephen A. Edson, </NAME>
                    <TITLE> Deputy Assistant Secretary for Bureau of Consular Affairs, Department of State.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. E7-7047 Filed 4-12-07; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4710-06-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF STATE </AGENCY>
                <DEPDOC>[Public Notice 5773] </DEPDOC>
                <SUBJECT>Culturally Significant Objects Imported for Exhibition Determinations: “The Herculaneum Women and the Origins of Archaeology” </SUBJECT>
                <P>
                    <E T="03">Summary:</E>
                     Notice is hereby given of the following determinations: Pursuant to the authority vested in me by the Act of October 19, 1965 (79 Stat. 985; 22 U.S.C. 2459), Executive Order 12047 of March 27, 1978, the Foreign Affairs Reform and Restructuring Act of 1998 (112 Stat. 2681, 
                    <E T="03">et seq.</E>
                    ; 22 U.S.C. 6501 note, 
                    <E T="03">et seq.</E>
                    ), Delegation of Authority No. 234 of October 1, 1999, Delegation of Authority No. 236 of October 19, 1999, as amended, and Delegation of Authority No. 257 of April 15, 2003 [68 FR 19875], I hereby determine that the objects to be included in the exhibition “The Herculaneum Women and the Origins of Archaeology”, imported from abroad for temporary exhibition within the United States, are of cultural significance. The objects are imported pursuant to a loan agreement with a foreign owner. I also determine that the exhibition or display of all of these objects at the Getty Villa, Los Angeles, California, beginning on or about July 12, 2007, until on or about November 5, 2007, and the continued temporary display of two of the objects until on or about April 14, 2008, is in the national interest. Public Notice of these Determinations is ordered to be published in the 
                    <E T="04">Federal Register</E>
                    . 
                </P>
                <P>
                    <E T="03">For Further Information Contact:</E>
                     For further information, including a list of the exhibit objects, contact Julie Simpson, Attorney-Adviser, Office of the Legal Adviser, U.S. Department of State (telephone: (202) 453-8050). The address is U.S. Department of State, SA-44, 301 4th Street, SW., Room 700, Washington, DC 20547-0001. 
                </P>
                <SIG>
                    <DATED>Dated: April 6, 2007. </DATED>
                    <NAME>C. Miller Crouch, </NAME>
                    <TITLE>Principal Deputy Assistant Secretary for Educational and Cultural Affairs, Department of State.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC> [FR Doc. E7-7037 Filed 4-12-07; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4710-05-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF STATE </AGENCY>
                <DEPDOC>[Public Notice 5772] </DEPDOC>
                <SUBJECT>Culturally Significant Objects Imported for Exhibition Determinations: “Treasures From the Hermitage and Guggenheim Collections” </SUBJECT>
                <P>
                    <E T="03">Summary:</E>
                     Notice is hereby given of the following determinations: Pursuant to the authority vested in me by the Act of October 19, 1965 (79 Stat. 985; 22 U.S.C. 2459), Executive Order 12047 of March 27, 1978, the Foreign Affairs Reform and Restructuring Act of 1998 (112 Stat. 2681, 
                    <E T="03">et seq.</E>
                    ; 22 U.S.C. 6501 note, 
                    <E T="03">et seq.</E>
                    ), Delegation of Authority No. 234 of October 1, 1999, Delegation of Authority No. 236 of October 19, 1999, as amended, and Delegation of Authority No. 257 of April 15, 2003 [68 FR 19875], I hereby determine that the objects to be included in the exhibition “Treasures from the Hermitage and Guggenheim Collections”, imported from abroad for temporary exhibition within the United States, are of cultural significance. The objects are imported pursuant to loan agreements with the foreign owners or custodians. I also determine that the exhibition or display of the exhibit objects at the Guggenheim-Hermitage Museum, Las Vegas, Nevada, from on or about May 25, 2007, until on or about February 29, 2008, and at possible additional venues yet to be determined, is in the national interest. Public Notice of these Determinations is ordered to be published in the 
                    <E T="04">Federal Register</E>
                    . 
                </P>
                <P>
                    <E T="03">For Further Information Contact:</E>
                     For further information, including a list of the exhibit objects, contact Wolodymyr Sulzynsky, Attorney-Adviser, Office of the Legal Adviser, U.S. Department of State (telephone: (202) 453-8050). The address is U.S. Department of State, SA-44, 301 4th Street, SW., Room 700, Washington, DC 20547-0001. 
                </P>
                <SIG>
                    <DATED>Dated: April 5, 2007. </DATED>
                    <NAME>C. Miller Crouch, </NAME>
                    <TITLE>Principal Deputy Assistant Secretary for Educational and Cultural Affairs, Department of State.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. E7-7040 Filed 4-12-07; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4710-05-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF STATE </AGENCY>
                <DEPDOC>[Public Notice 5774] </DEPDOC>
                <SUBJECT>Announcement of Meetings of the International Telecommunication Advisory Committee </SUBJECT>
                <P>
                    <E T="03">Summary:</E>
                     This notice announces meetings of the International Telecommunication Advisory Committee (ITAC) to prepare advice on U.S. positions for responses to: ITU letter of March 14, 2007 to Members of the Council regarding organizational changes within the General Secretariat and the Bureaux of the Sectors of the Union, ITU DM-07/1008 to the entire ITU membership regarding ITU's role on international public policy issues pertaining to the Internet and the management of Internet resources, and ITU DM-07/1003 to the entire ITU membership regarding the planning schedule for the fourth World Telecommunications Policy Forum on convergence and emerging policy issues. 
                </P>
                <P>The ITAC will meet on April 26, 2007 from 10-noon EDT at the offices of AT&amp;T, 1120 20th Street, Washington, DC to start preparations for advice on three letters from the International Telecommunication Union. </P>
                <P>
                    This meeting is open to the public. Further information may be obtained from the Secretariat at 
                    <E T="03">minardje@state.gov</E>
                    , telephone 202 647-3234. 
                </P>
                <SIG>
                    <DATED>Dated: April 9, 2007. </DATED>
                    <NAME>Anne D. Jillson, </NAME>
                    <TITLE>Foreign Affairs Officer, International Communications and Information Policy, Department of State.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC> [FR Doc. E7-7036 Filed 4-12-07; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4710-07-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="18723"/>
                <AGENCY TYPE="N">TENNESSEE VALLEY AUTHORITY </AGENCY>
                <SUBJECT>Paperwork Reduction Act of 1995, as amended by Public Law 104-13; Proposed Collection, Comment Request </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Tennessee Valley Authority. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Proposed collection; comment request. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The proposed information collection described below will be submitted to the Office of Management and Budget (OMB) for review, as required by the Paperwork Reduction Act of 1995 (44 U.S.C. Chapter 35, as amended). The Tennessee Valley Authority is soliciting public comments on this proposed collection as provided by 5 CFR 1320.8(d)(1). Requests for information, including copies of the information collection proposed and supporting documentation, should be directed to the Agency Clearance Officer: Alice D. Witt, Tennessee Valley Authority, 1101 Market Street (EB 5B), Chattanooga, Tennessee 37402-2801; (423) 751-6832. (SC: 0008QG1) Comments should be sent to the Agency Clearance Officer no later than June 12, 2007. </P>
                </SUM>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P SOURCE="NPAR">
                    <E T="03">Type of Request:</E>
                     Regular submission; proposal for a new collection. (OMB Control number: 3316-0000). 
                </P>
                <P>
                    <E T="03">Title of Information Collection:</E>
                     Safety Harbors and Safety Landings Assessment, Tennessee River. 
                </P>
                <P>
                    <E T="03">Frequency of Use:</E>
                     Approximately every 10 years. 
                </P>
                <P>
                    <E T="03">Type of Affected Public:</E>
                     Business, Federal Government. 
                </P>
                <P>
                    <E T="03">Small Businesses or Organizations Affected:</E>
                     No. 
                </P>
                <P>
                    <E T="03">Estimated Number of Annual Responses:</E>
                     80. 
                </P>
                <P>
                    <E T="03">Estimated Total Annual Burden Hours:</E>
                     40. 
                </P>
                <P>
                    <E T="03">Estimated Average Burden Hours Per Response:</E>
                     0.5. 
                </P>
                <P>
                    <E T="03">Need for and Use of Information:</E>
                     The Tennessee Valley Authority, in conjunction with the U.S. Army Corps of Engineers, is assessing the status of the safety harbors and safety landings located along the Tennessee River and its tributaries. This type of assessment was performed approximately ten years ago. However, due to the changing river conditions and uses over the past several years, along with the growing demand for lake access, it is important to identify and preserve the most essential and useful safety harbors and safety landings that are currently designated. Only those safety harbors and safety landings that are considered nonessential and unusable by the towing industry would be discontinued. The information provided through this assessment will be used to support the justification of preserving stretches of shoreline for commercial navigation uses. Respondents are not required to answer all of the questions, but are requested to focus their review on the portion of the river that their tows transit. 
                </P>
                <SIG>
                    <NAME>Steve A. Anderson, </NAME>
                    <TITLE>Manager, IS Business Services, Information Services. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. E7-6980 Filed 4-12-07; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 8120-08-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <SUBJECT>Noise Compatibility Program Notice, Alexandria, LA</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The Federal Aviation Administration (FAA) announces that it is reviewing a proposed noise compatibility program that was submitted for Alexandria International Airport under the provisions of 49 U.S.C. 74501 
                        <E T="03">et seq.</E>
                         (the Aviation Safety and Noise Abatement Act, hereinafter referred to as “the Act”) and 14 CFR part 150 by the England Economic and Industrial Development District. This program was submitted subsequent to a determination by FAA that associated noise exposure maps submitted under 14 CFR Part 150 for Alexandria International Airport were in compliance with applicable requirements, effective January 26, 2006, and published in the 
                        <E T="04">Federal Register</E>
                         February 3, 2006 (Volume 71 Number 23). The proposed noise compatibility program will be approved or disapproved on or before October 6, 2007.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The effective date of the start of FAA's review of the noise compatibility program is April 9, 2007. The public comment period ends June 8, 2007.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Mr. Tim Tandy, Federal Aviation Administration, ASW-640, Fort Worth, TX 76193-0640 at (817) 222-5644. Comments on the proposed noise compatibility program should also be submitted to the above office.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>This notice announces that the FAA is reviewing a proposed noise compatibility program for Alexandria International Airport that will be approved or disapproved on  or before October 6, 2007. This notice also announces the availability of this program for public review and comment.</P>
                <P>An airport operator who has submitted noise exposure maps that are found by the FAA to be in compliance with the requirements of Federal Aviation Regulations (FAR) Part 150, promulgated pursuant to the Act, may submit a noise compatibility program for FAA approval which sets forth the measures the operator has taken or proposes to reduce existing non-compatible uses and prevent the introduction of additional non-compatible uses.</P>
                <P>The FAA has formally received the noise compatibility program for Alexandria International Airport, effective on April 9, 2007. The airport operator has requested that the FAA review this material and that the noise mitigation measures, to be implemented jointly by the airport and surrounding communities, be approved as a noise compatibility program under section 47504 of the Act. Preliminary review of the submitted material indicates that it conforms to FAR part 150 requirements for the submittal of noise compatibility programs, but that further review will be necessary prior to approval or disapproval of the program. The formal review period, limited by law to a maximum of 180 days, will be completed on or before October 6, 2007.</P>
                <P>The FAA's detailed evaluation will be conducted under the provisions of 14 CFR part 150, section 150.33. The primary considerations in the evaluation process are whether the proposed measures may reduce the level of aviation safety or create an undue burden on interstate or foreign commerce, and whether they are reasonably consistent with obtaining the goal of reducing existing non-compatible land uses and preventing the introduction of additional non-compatible land uses.</P>
                <P>Interested persons are invited to comment on the proposed program with specific reference to these factors. All comments relating to these factors, other than those properly addressed to local land use authorities, will be considered by the FAA to the extent practicable. Copies of the noise exposure maps and the proposed noise compatiblity program are available for examination at the following locations:</P>
                <FP SOURCE="FP-1">Federal Aviation Administration, 2601 Meacham Boulevard, Fort Worth, Texas;</FP>
                <FP SOURCE="FP-1">England Economic and Industrial Development District, 1611 Arnold Drive, Alexandria, Louisiana. </FP>
                <PRTPAGE P="18724"/>
                <P>
                    Questions may be directed to the individual named above under the heading, 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                    .
                </P>
                <SIG>
                    <DATED>Issued in Fort Worth, Texas, April 9, 2007.</DATED>
                    <NAME>Kelvin L. Solco, </NAME>
                    <TITLE>Manager, Airports Division,</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 07-1837 Filed 4-12-07; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-13-M </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <SUBJECT>Notice of Extension of Public Comment Period on Draft Environmental Impact Statement (Draft EIS) for the Development of Extension of Runway 9R/27L and Other Associated Airport Projects at Fort Lauderdale-Hollywood International (FLL)</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>The lead Federal agency is the Federal Aviation Administration (FAA), Department of Transportation (DOT).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of extension of public comment period on Draft EIS.  </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The FAA is issuing this notice to advise the public that the comment period for the Draft EIS has been extended to May 21, 2007. The originally published date for the close of the public comment period was May 14, 2007.</P>
                    <P>The comment period is being extended by one week because information has been provided to all interested parties that replaces some of the information previously issued in the Draft EIS. Specifically, Appendix G.1.B Hazardous Air Pollutant Evaluation has been replaced with a more current version then was inadvertently included in the Draft EIS issued on March 30, 2007.</P>
                    <P>
                        <E T="03">Public Comment and Information Workshop/Public Hearing.</E>
                         The public comment period on the Draft EIS starts March 30, 2007 and will now end on May 21, 2007. There is no change in the date for the Public Information Workshop and Public Hearing that will be held on May 1, 2007 at the Greater Fort Lauderdale/Broward County Convention Center, 1950 Eisenhower Boulevard, Fort Lauderdale, FL 33316; Telephone: (954) 765-5900.
                    </P>
                    <P>
                        Comments can only be accepted with the full name and address of the individual commenting. Mail and fax comments are to be submitted to Ms. Virginia Lane of the FAA, at the address shown in 
                        <E T="02">FOR FURTHER INFORMATION CONTACT.</E>
                         E-mail comments should be sent to 
                        <E T="03">FLL-EIScomments@landrum-brown.com</E>
                        ). All comments must be postmarked, faxed or e-mailed no later than midnight, Monday, May 21, 2007. The Draft EIS may be reviewed for comment during regular business hours at the following location:
                    </P>
                    <P>1. Broward County Government Center, 115 S. Andrews Avenue, Fort Lauderdale, FL 33301 (Telephone: 954-357-7000).</P>
                    <P>2. Broward County Library—Main Branch, 100 S. Andrews Avenue, Fort Lauderdale, FL 33301 (Telephone: 954-354-7444).</P>
                    <P>3. Broward County Library—Fort Lauderdale Branch, 1300 E. Sunrise Boulevard, Fort Lauderdale, FL 3304 (Telephone: 954-765-4263).</P>
                    <P>4. Broward County Library—Hollywood Branch, 2600 Hollywood Boulevard, Hollywood, FL 33020 (Telephone: 954-926-2430).</P>
                    <P>5. Broward County Library—Dania Breach Paul DeMaio Branch, 255 E. Dania Beach Boulevard, Dania Beach, FL 33004 (Telephone: 954-926-2420).</P>
                    <P>6. Broward County Library—Davie/Cooper City Branch, 4600 SW 82nd Avenue, Davie, FL 33328 (Telephone: 954-680-0050).</P>
                    <P>8. Broward County Library—Stirling Road Branch, 3151 Stirling Road, Hollywood, FL 33021 (Telephone: 954-985-2689).</P>
                    <P>9. Broward County Library—Pembroke Pines/Walter C. Young Branch, 955 NW. 129th Avenue, Pembroke Pines, FL 33025 (Telephone: 954-437-2635).</P>
                    <P>10. Broward County Library—West Regional Branch, 8601 W. Broward Boulevard, Plantation, FL 33324 (Telephone: 954-831-3300).</P>
                    <P>11. Broward County Library—Sunrise Dan Pearl Branch, 10500 W. Oakland Park Boulevard, Sunrise, FL 33351 (Telephone: 954-749-2521).</P>
                    <P>12. Fort Lauderdale-Hollywood International Airport, Public Outreach Trailer, Broward County Aviation Department, 550 Northwest 10th Street, Dania Beach, FL 33315 (Telephone: 954-359-6977).</P>
                    <P>13. Broward County Administration Office, Broward County Governmental Center, 115 S. Andrews Avenue, Room 409, Fort Lauderdale, FL 33301 (Telephone: 954-357-7000).</P>
                    <P>14. Broward County Aviation Department, 320 Terminal Drive, Fort Lauderdale, FL 33315 (Telephone: 954-359-6118).</P>
                    <P>
                        Broward County will be providing an electronic copy of the Draft EIS on the Broward County web site at 
                        <E T="03">http://www.broward.org/airport/.</E>
                         A CD version of the Draft EIS document will also be available during regular business hours at the following public locations:
                    </P>
                    <P>15. City of Lauderhill, Lauderhill City Hall, 2000 City Hall Drive, Lauderhill, FL 33313 (Telephone: 954-739-0100).</P>
                    <P>16. City of Pembroke Pines, Pembroke Pines City Hall, 10100 Pines Boulevard, Pembroke Pines, FL 33025 (Telephone: 954-431-4500).</P>
                    <P>17. City of Cooper City, Cooper City Hall, 9090 SW. 50th Place, Cooper City, FL 33328 (Telephone: 954-434-4300).</P>
                    <P>18. City of Sunrise, 10770 W. Oakland Park Blvd., Sunrise, FL 33351 (Telephone: 954-741-2580).</P>
                    <P>19. City of Fort Lauderdale, 100 N. Andrews Avenue, Fort Lauderdale, FL 33301 (Telephone: 954-761-5000).</P>
                    <P>20. City of Plantation, Plantation City Hall, 400 NW. 73rd Avenue, Plantation, FL 33317 (Telephone: 954-797-2221).</P>
                    <P>21. City of Hollywood, Hollywood City Hall, 2600 Hollywood Boulevard, Hollywood, FL 33020 (Telephone: 954-921-3473).</P>
                    <P>22. City of Dania Beach, Dania Beach City Hall, 100 W. Dania Beach Boulevard, Dania Beach, FL 33004 (Telephone: 954-924-3600).</P>
                    <P>23. Town of Davie, Davie Town Hall, 6591 SW 45th Street, Davie, FL 33314 (Telephone: 954-797-1000).</P>
                </SUM>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The FAA encourages all interested parties to provide comments concerning the scope and content of the Draft EIS. Comments should be as specific as possible. Comments should address the contents of the Draft EIS, such as the analysis of potential environmental impacts, the adequacy of the proposed action to meet the stated need, or the merits of the various alternatives. Reviewers should organize their participation to make it meaningful and effective in making the FAA aware of the reviewer's interests and concerns. Reviewers should use quotations, page references, and other specific citations to the text of the Draft EIS and related documents. This commenting procedure is intended to ensure that substantive comments and concerns are made available to the FAA in a timely and effective manner, so that the FAA has an opportunity to address them.</P>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Ms. Virginia Lane, FAA Orlando Airports District Office, 5950 Hazeltine National Drive, Orlando, Florida 32822-5024. Telephone: (407) 812-6331, Fax: (407) 812-6978. </P>
                    <SIG>
                        <DATED>Issued in Orlando, Florida, on April 6, 2007.</DATED>
                        <NAME>W. Dean Stringer, </NAME>
                        <TITLE> Manager, FAA Orlando Airports District Office.</TITLE>
                    </SIG>
                </FURINF>
            </SUPLINF>
            <FRDOC>[FR Doc. 07-1836 Filed 4-12-07; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-13-M</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="18725"/>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION </AGENCY>
                <SUBAGY>Federal Highway Administration </SUBAGY>
                <SUBJECT>Environmental Impact Statement; Cidra-Cayey Connector, Puerto Rico </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Highway Administration (FHWA), DOT. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of intent. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The FHWA is issuing this notice to advise the public that an environmental impact statement (EIS) will be prepared for the Cidra-Cayey Connector in the east center area of Puerto Rico. The purpose of the EIS is to provide information and analyses for decisions on the project in accordance with the policies and purposes of the National Environmental Policy Act. </P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Félix Rodríguez, P.E., Federal Highway Administration, Puerto Rico Division, 350 Carlos Chardon Street, Suite 210, San Juan, Puerto Rico 00918, Telephone (787) 766-5600 Ext. 230; or Ms. Irma García, P.E., Programming and Special Studies Area, Puerto Rico Highway and Transportation Authority, PO Box 42007, San Juan, Puerto Rico, 00940-2007, Telephone (787) 729-1580. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The FHWA, in cooperation with the Commonwealth of Puerto Rico Department of Transportation and Public Works (PRDTPW), through its Highway and Transportation Authority (HTA), will prepare a joint environmental impact statement (EIS) on a proposal to construct a new roadway in the municipality of Cidra. The proposed action consists of the construction of a new roadway which will provide the municipality of Cidra and bordering districts with an access from Cidra to PR-52. The new highway will begin in existing PR-7733 and end in PR-52 or PR-184, depending on the alternative that will be selected during the environmental process. The route will have partial access control. </P>
                <P>A State, non-Federal, Draft Environmental Impact Statement (DEIS) was prepared for the proposed project in the year 2000 and public hearings were held in the same year. Since the 2000, technical studies identified environmental and socio-economic factors which warranted the consideration of additional alternatives beyond the ones studied for the original preferred alternative presented in the DEIS. As a result, the FHWA in cooperation with the PRHTA will prepare an EIS. </P>
                <P>Alternatives under consideration include: No-Build; Transportation System Management (TSM) activities; upgrade existing roadways; Mass Transit; and five alignment alternatives to construct a new roadway on a new location. The new alignment of the road is necessary to relieve traffic congestion along existing PR-172 and in areas which have experienced a traffic increase such as the PR-7733 and PR-787. </P>
                <P>As part of the scoping process, Federal, State, and local agencies, private organizations, citizens and interest groups will have an opportunity to identify issues of concern and provide input on the purpose and need for the project, range of alternatives, methodology, and the development of the EIS. A public coordination plan will be developed. This plan will utilize the following outreach efforts to provide information and request input: newsletters, an internet Web site, e-mail and direct mail, informational meetings and briefings, public hearings, and other efforts, as necessary and appropriate. A public hearing will be held upon completion of the DEIS. The DEIS will be available for public and agency review and comments prior to the public hearings. </P>
                <P>To ensure that the full range of issues and alternatives related to this proposed action is addressed and all significant issues identified, comments and suggestions are invited from interested parties. Comments or questions concerning this proposed action, the EIS and Section 106 consultation should be directed to FHWA at the address provided above.</P>
                <EXTRACT>
                    <FP>(Catalogue of Federal Domestic Assistance Program Number 20.205, Highway Planning and Construction. The regulations implementing Executive Order 12372 regarding intergovernmental consultation on Federal programs and activities apply to this program.) </FP>
                </EXTRACT>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P>23 U.S.C. 315; 49 CFR 1.48. </P>
                </AUTH>
                <SIG>
                    <DATED>Issued on: April 5, 2007. </DATED>
                    <NAME>Félix Rodríguez-Soto, </NAME>
                    <TITLE>Puerto Rico Assistant Division Administrador.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC> [FR Doc. E7-7014 Filed 4-12-07; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4910-22-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION </AGENCY>
                <SUBAGY>Federal Motor Carrier Safety Administration </SUBAGY>
                <DEPDOC>[Docket Nos. FMCSA-02-12423, FMCSA-02-12844, FMCSA-04-19477, 04-17984] </DEPDOC>
                <SUBJECT>Qualification of Drivers; Exemption Renewals; Vision </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Motor Carrier Safety Administration (FMCSA), DOT. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of final disposition. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>FMCSA previously announced its decision to renew the exemptions from the vision requirement in the Federal Motor Carrier Safety Regulations for 11 individuals. FMCSA has statutory authority to exempt individuals from the vision requirement if the exemptions granted will not compromise safety. The Agency has reviewed the comments submitted in response to the previous announcement and concluded that granting these exemptions will provide a level of safety that will be equivalent to, or greater than, the level of safety maintained without the exemptions for these commercial motor vehicle (CMV) drivers. </P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Dr. Mary D. Gunnels, Chief, Physical Qualifications Division, (202) 366-4001, 
                        <E T="03">fmcsamedical@dot.gov</E>
                        , FMCSA, Department of Transportation, 400 Seventh Street, SW., Room 8301, Washington, DC 20590-0001. Office hours are from 8:30 a.m. to 5 p.m., Monday through Friday, except Federal holidays. 
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <HD SOURCE="HD1">Electronic Access </HD>
                <P>
                    You may see all the comments online through the Document Management System (DMS) at 
                    <E T="03">http://dmses.dot.gov.</E>
                </P>
                <HD SOURCE="HD1">Background </HD>
                <P>Under 49 U.S.C. 31136(e) and 31315, FMCSA may grant an exemption for a 2-year period if it finds “such exemption would likely achieve a level of safety that is equivalent to, or greater than, the level that would be achieved absent such exemption.” The statute also allows the Agency to renew exemptions at the end of the 2-year period. The comment period ended on March 8, 2007. </P>
                <HD SOURCE="HD1">Discussion of Comments </HD>
                <P>FMCSA received three comments in these proceedings. The comments were considered and discussed below. </P>
                <P>Ms. Sachau believes that the approval or renewal of vision exemptions make the roads much more dangerous. </P>
                <P>
                    A review of each record for safety while driving with the respective vision deficiencies over the past two years indicates each applicant continues to meet the vision exemption standards. To evaluate the effect of these exemptions on safety, FMCSA considered not only the medical reports about the applicants' vision, but also their driving records and experience with the vision deficiency. To qualify for an exemption from the vision 
                    <PRTPAGE P="18726"/>
                    standard, FMCSA requires a person to present verifiable evidence that he or she has driven a commercial vehicle safely with the vision deficiency for 3 years. Recent driving performance is especially important in evaluating future safety, according to several research studies designed to correlate past and future driving performance. Results of these studies support the principle that the best predictor of future performance by a driver is his/her past record of crashes and traffic violations. Copies of the studies may be found at docket number FMCSA-98-3637. 
                </P>
                <P>Advocates for Highway and Auto Safety (Advocates) expressed opposition to FMCSA's policy to grant exemptions from the FMCSR, including the driver qualification standards. Specifically, Advocates: (1) Objects to the manner in which FMCSA presents driver information to the public and makes safety determinations; (2) objects to the Agency's reliance on conclusions drawn from the vision waiver program; (3) claims the Agency has misinterpreted statutory language on the granting of exemptions (49 U.S.C. 31136(e) and 31315); and finally (4) suggests that a 1999 Supreme Court decision affects the legal validity of vision exemptions. </P>
                <P>The issues raised by Advocates were addressed at length in 64 FR 51568 (September 23, 1999), 64 FR 66962 (November 30, 1999), 64 FR 69586 (December 13, 1999), 65 FR 159 (January 3, 2000), 65 FR 57230 (September 21, 2000), and 66 FR 13825 (March 7, 2001). We will not address these points again here, but refer interested parties to those earlier discussions. </P>
                <P>Ms. Valerie L. Kaune is in support of the Federal vision exemption program. She believes that it does not pose a danger to our roads and is the livelihood of many drivers. </P>
                <HD SOURCE="HD1">Conclusion </HD>
                <P>The Agency has not received any adverse evidence on any of these drivers that indicates that safety is being compromised. Based upon its evaluation of the 11 renewal applications, FMCSA renews the Federal vision exemptions for Roger C. Carson, Charles R. O'Connell, William T. Cummins, Dennis R. O'Dell, Jr., Scott D. Goalder, Harold D. Jones, Lester G. Kelly, III, Jerry W. Parker, Virgil A. Potts, Henry A. Shelton and Ronald A. Stevens. </P>
                <P>In accordance with 49 U.S.C. 31136(e) and 31315, each renewal exemption will be valid for 2 years unless revoked earlier by FMCSA. The exemption will be revoked if: (1) The person fails to comply with the terms and conditions of the exemption; (2) the exemption has resulted in a lower level of safety than was maintained before it was granted; or (3) continuation of the exemption would not be consistent with the goals and objectives of 49 U.S.C. 31136 and 31315. </P>
                <SIG>
                    <DATED>Issued on: April 6, 2007. </DATED>
                    <NAME>Larry W. Minor, </NAME>
                    <TITLE>Acting, Associate Administrator, Policy and Program Development.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC> [FR Doc. E7-6997 Filed 4-12-07; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4910-EX-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION </AGENCY>
                <SUBAGY>Federal Motor Carrier Safety Administration </SUBAGY>
                <DEPDOC>[Docket No. FMCSA-98-3637, FMCSA-98-4334, FMCSA-00-7918, FMCSA-00-8203, FMCSA-02-13411, FMCSA-03-14223, FMCSA-05-20027] </DEPDOC>
                <SUBJECT>Qualification of Drivers; Exemption Applications; Vision </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Motor Carrier Safety Administration (FMCSA), DOT. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of renewal of exemptions; request for comments. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>FMCSA announces its decision to renew the exemptions from the vision requirement in the Federal Motor Carrier Safety Regulations for 16 individuals. FMCSA has statutory authority to exempt individuals from the vision requirement if the exemptions granted will not compromise safety. The Agency has concluded that granting these exemptions will provide a level of safety that will be equivalent to, or greater than, the level of safety maintained without the exemptions for these commercial motor vehicle (CMV) drivers. </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>This decision is effective April 21, 2007. Comments must be received on or before May 14, 2007. </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may submit comments identified by DOT Docket Management System (DMS) Docket Numbers FMCSA-98-3637, FMCSA-98-4334, FMCSA-00-7918, FMCSA-00-8203, FMCSA-02-13411, FMCSA-03-14223, FMCSA-05-20027, using any of the following methods. </P>
                    <P>
                        • 
                        <E T="03">Web site:</E>
                          
                        <E T="03">http://dmses.dot.gov.</E>
                         Follow the instructions for submitting comments on the DOT electronic docket site. 
                    </P>
                    <P>
                        • 
                        <E T="03">Fax:</E>
                         1-202-493-2251. 
                    </P>
                    <P>
                        • 
                        <E T="03">Mail:</E>
                         Docket Management Facility; U.S. Department of Transportation, 400 Seventh Street, SW., Nassif Building, Room PL-401, Washington, DC 20590-0001. 
                    </P>
                    <P>
                        • 
                        <E T="03">Hand Delivery:</E>
                         Room PL-401 on the plaza level of the Nassif Building, 400 Seventh Street, SW., Washington, DC, between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays. 
                    </P>
                    <P>
                        • 
                        <E T="03">Federal eRulemaking Portal:</E>
                         Go to 
                        <E T="03">http://www.regulations.gov.</E>
                         Follow the online instructions for submitting comments. 
                    </P>
                    <P>
                        <E T="03">Instructions:</E>
                         All submissions must include the Agency name and docket numbers for this Notice. Note that all comments received will be posted without change to 
                        <E T="03">http://dms.dot.gov</E>
                        , including any personal information provided. Please see the Privacy Act heading for further information. 
                    </P>
                    <P>
                        <E T="03">Docket:</E>
                         For access to the docket to read background documents or comments received, go to 
                        <E T="03">http://dms.dot.gov</E>
                         at any time or Room PL-401 on the plaza level of the Nassif Building, 400 Seventh Street, SW., Washington, DC, between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays. The DMS is available 24 hours each day, 365 days each year. If you want us to notify you that we received your comments, please include a self-addressed, stamped envelope or postcard or print the acknowledgement page that appears after submitting comments on-line. 
                    </P>
                    <P>
                        <E T="03">Privacy Act:</E>
                         Anyone may search the electronic form of all comments received into any of our dockets by the name of the individual submitting the comment (or of the person signing the comment, if submitted on behalf of an association, business, labor union, etc.). You may review the Department of Transportation's complete Privacy Act Statement in the 
                        <E T="04">Federal Register</E>
                         published on April 11, 2000 (65 FR 19477; Apr. 11, 2000). This information is also available at 
                        <E T="03">http://dms.dot.gov.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Dr. Mary D. Gunnels, Chief, Physical Qualifications Division, (202) 366-4001, 
                        <E T="03">fmcsamedical@dot.gov</E>
                         FMCSA, Department of Transportation, 400 Seventh Street, SW., Room 8301, Washington, DC 20590-0001. Office hours are from 8:30 a.m. to 5 p.m., E.T., Monday through Friday, except Federal holidays. 
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <HD SOURCE="HD1">Exemption Decision </HD>
                <P>
                    Under 49 U.S.C. 31136(e) and 31315, FMCSA may renew an exemption from the vision requirements in 49 CFR 391.41(b)(10), which applies to drivers of CMVs in interstate commerce, for a two-year period if it finds “such exemption would likely achieve a level of safety that is equivalent to, or greater than, the level that would be achieved 
                    <PRTPAGE P="18727"/>
                    absent such exemption.” The procedures for requesting an exemption (including renewals) are set out in 49 CFR part 381. This notice addresses 16 individuals who have requested renewal of their exemptions in accordance with FMCSA procedures. FMCSA has evaluated these 16 applications for renewal on their merits and decided to extend each exemption for a renewable two-year period. They are:   
                </P>
                <GPOTABLE COLS="3" OPTS="L2,tp0,p1,8/9,i1" CDEF="s50,r50,r50">
                    <TTITLE>   </TTITLE>
                    <BOXHD>
                          
                        <CHED H="1">   </CHED>
                        <CHED H="1">   </CHED>
                        <CHED H="1"> </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Rodger B. Anders </ENT>
                        <ENT>David R. Gross </ENT>
                        <ENT>William E. Reveal </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">John D. Bolding, Jr </ENT>
                        <ENT>James K. Holmes </ENT>
                        <ENT>Duane L. Riendeau </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Michael P. Curtin </ENT>
                        <ENT>Christopher J. Kane </ENT>
                        <ENT>Daniel J. Schaap </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Richard L. Elyard </ENT>
                        <ENT>Michael L. Manning </ENT>
                        <ENT>Janusz Tyrpien </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Michael R. Forschino </ENT>
                        <ENT>Kirby G. Oathout </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">William H. Goss </ENT>
                        <ENT>James R. Petre </ENT>
                    </ROW>
                </GPOTABLE>
                <P>These exemptions are extended subject to the following conditions: (1) That each individual have a physical examination every year (a) By an ophthalmologist or optometrist who attests that the vision in the better eye continues to meet the standard in 49 CFR 391.41(b)(10), and (b) by a medical examiner who attests that the individual is otherwise physically qualified under 49 CFR 391.41; (2) that each individual provide a copy of the ophthalmologist's or optometrist's report to the medical examiner at the time of the annual medical examination; and (3) that each individual provide a copy of the annual medical certification to the employer for retention in the driver's qualification file and retain a copy of the certification on his/her person while driving for presentation to a duly authorized Federal, State, or local enforcement official. Each exemption will be valid for two years unless rescinded earlier by FMCSA. The exemption will be rescinded if: (1) The person fails to comply with the terms and conditions of the exemption; (2) the exemption has resulted in a lower level of safety than was maintained before it was granted; or (3) continuation of the exemption would not be consistent with the goals and objectives of 49 U.S.C. 31136(e) and 31315. </P>
                <HD SOURCE="HD1">Basis for Renewing Exemptions </HD>
                <P>Under 49 U.S.C. 31315(b)(1), an exemption may be granted for no longer than two years from its approval date and may be renewed upon application for additional two year periods. In accordance with 49 U.S.C. 31136(e) and 31315, each of the 16 applicants has satisfied the entry conditions for obtaining an exemption from the vision requirements (63 FR 30285; 63 FR 54519; 65 FR 66293; 67 FR 71610; 69 FR 71098; 63 FR 66226; 64 FR 16517; 66 FR 17994; 68 FR 15037; 70 FR 16886; 65 FR 66286; 66 FR 13825; 68 FR 13360; 70 FR 14747; 67 FR 76439; 68 FR 10298; 70 FR 7543; 67 FR 68719; 68 FR 2629; 68 FR 10301; 68 FR 19596; 70 FR 2701; 70 FR 16887). Each of these 16 applicants has requested timely renewal of the exemption and has submitted evidence showing that the vision in the better eye continues to meet the standard specified at 49 CFR 391.41(b)(10) and that the vision impairment is stable. In addition, a review of each record of safety while driving with the respective vision deficiencies over the past two years indicates each applicant continues to meet the vision exemption standards. These factors provide an adequate basis for predicting each driver's ability to continue to drive safely in interstate commerce. Therefore, FMCSA concludes that extending the exemption for each renewal applicant for a period of two years is likely to achieve a level of safety equal to that existing without the exemption. </P>
                <HD SOURCE="HD1">Request for Comments </HD>
                <P>FMCSA will review comments received at any time concerning a particular driver's safety record and determine if the continuation of the exemption is consistent with the requirements at 49 U.S.C. 31136(e) and 31315. However, FMCSA requests that interested parties with specific data concerning the safety records of these drivers submit comments by May 14, 2007. </P>
                <P>
                    FMCSA believes that the requirements for a renewal of an exemption under 49 U.S.C. 31136(e) and 31315 can be satisfied by initially granting the renewal and then requesting and evaluating, if needed, subsequent comments submitted by interested parties. As indicated above, the Agency previously published notices of final disposition announcing its decision to exempt these 16 individuals from the vision requirement in 49 CFR 391.41(b)(10). The final decision to grant an exemption to each of these individuals was based on the merits of each case and only after careful consideration of the comments received to its notices of applications. The notices of applications stated in detail the qualifications, experience, and medical condition of each applicant for an exemption from the vision requirements. That information is available by consulting the above cited 
                    <E T="04">Federal Register</E>
                     publications. 
                </P>
                <P>Interested parties or organizations possessing information that would otherwise show that any, or all of these drivers, are not currently achieving the statutory level of safety should immediately notify FMCSA. The Agency will evaluate any adverse evidence submitted and, if safety is being compromised or if continuation of the exemption would not be consistent with the goals and objectives of 49 U.S.C. 31136(e) and 31315, FMCSA will take immediate steps to revoke the exemption of a driver. </P>
                <SIG>
                    <DATED>Issued on: April 9, 2007. </DATED>
                    <NAME>Larry W. Minor, </NAME>
                    <TITLE>Acting, Associate Administrator.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC> [FR Doc. E7-6998 Filed 4-12-07; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4910-EX-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION </AGENCY>
                <SUBAGY>Federal Motor Carrier Safety Administration </SUBAGY>
                <DEPDOC>[Docket Nos. FMCSA-98-4334, FMCSA-00-7363, FMCSA-00-7918, FMCSA-02-13411] </DEPDOC>
                <SUBJECT>Qualification of Drivers; Exemption Renewals; Vision </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Motor Carrier Safety Administration (FMCSA), DOT. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of final disposition. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>FMCSA previously announced its decision to renew the exemptions from the vision requirement in the Federal Motor Carrier Safety Regulations for 28 individuals. FMCSA has statutory authority to exempt individuals from the vision requirement if the exemptions granted will not compromise safety. The Agency has reviewed the comments submitted in response to the previous announcement and concluded that granting these exemptions will provide a level of safety that will be equivalent to, or greater than, the level of safety maintained without the exemptions for these commercial motor vehicle (CMV) drivers. </P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Dr. Mary D. Gunnels, Chief, Physical 
                        <PRTPAGE P="18728"/>
                        Qualifications Division, (202) 366-4001, 
                        <E T="03">fmcsamedical@dot.gov</E>
                        , FMCSA, Department of Transportation, 400 Seventh Street, SW., Room 8301, Washington, DC 20590-0001. Office hours are from 8:30 a.m. to 5 p.m., Monday through Friday, except Federal holidays. 
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <HD SOURCE="HD1">Electronic Access </HD>
                <P>
                    You may see all the comments online through the Document Management System (DMS) at 
                    <E T="03">http://dmses.dot.gov.</E>
                </P>
                <HD SOURCE="HD1">Background </HD>
                <P>Under 49 U.S.C. 31136(e) and 31315, FMCSA may grant an exemption for a 2-year period if it finds “such exemption would likely achieve a level of safety that is equivalent to, or greater than, the level that would be achieved absent such exemption.” The statute also allows the Agency to renew exemptions at the end of the 2-year period. The comment periods ended on March 16, and March 22, 2007. </P>
                <HD SOURCE="HD1">Discussion of Comments </HD>
                <P>FMCSA received two comments in these proceedings. The comments were considered and discussed below. </P>
                <P>Ms. Sachau believes that the approval or renewal of vision exemptions does not take into account the issue of safety on the road and granting exemptions only makes the roads much more dangerous. </P>
                <P>A review of each record for safety while driving with the respective vision deficiencies over the past two years indicates each applicant continues to meet the vision exemption standards. To evaluate the effect of these exemptions on safety, FMCSA considered not only the medical reports about the applicants' vision, but also their driving records and experience with the vision deficiency. To qualify for an exemption from the vision standard, FMCSA requires a person to present verifiable evidence that he or she has driven a commercial vehicle safely with the vision deficiency for 3 years. Recent driving performance is especially important in evaluating future safety, according to several research studies designed to correlate past and future driving performance. Results of these studies support the principle that the best predictor of future performance by a driver is his/her past record of crashes and traffic violations. Copies of the studies may be found at docket number FMCSA-98-3637. </P>
                <P>Advocates for Highway and Auto Safety (Advocates) expressed opposition to FMCSA's policy to grant exemptions from the FMCSR, including the driver qualification standards. Specifically, Advocates: (1) Objects to the manner in which FMCSA presents driver information to the public and makes safety determinations; (2) objects to the Agency's reliance on conclusions drawn from the vision waiver program; (3) claims the Agency has misinterpreted statutory language on the granting of exemptions (49 U.S.C. 31136(e) and 31315); and finally (4) suggests that a 1999 Supreme Court decision affects the legal validity of vision exemptions. </P>
                <P>The issues raised by Advocates were addressed at length in 64 FR 51568 (September 23, 1999), 64 FR 66962 (November 30, 1999), 64 FR 69586 (December 13, 1999), 65 FR 159 (January 3, 2000), 65 FR 57230 (September 21, 2000), and 66 FR 13825 (March 7, 2001). We will not address these points again here, but refer interested parties to those earlier discussions. </P>
                <HD SOURCE="HD1">Conclusion </HD>
                <P>The Agency has not received any adverse evidence on any of these drivers that indicates that safety is being compromised. Based upon its evaluation of the 28 renewal applications, FMCSA renews the Federal vision exemptions for Henry Ammons, Jr., Michael D. Archibald, Robert D. Bonner, Howard K. Bradley, Kirk G. Braegger, Ambroiso E. Calles, David S. Carman, Jose G. Cruz, Everett A. Doty, Cedric E. Foster, Glen T. Garrabrant, Donald J. Goretski, Harry P. Henning, Christopher L. Humphries, Alan L. Johnston, Ralph J. Miles, Dennis I. Nelson, William R. New, Rance A. Powell, Shannon E. Rasmussen, James R. Rieck, Thomas C. Rylee, Stanley B. Salkowski, III., Garfield A. Smith, Michael G. Thomas, William H. Twardus, Henry L. Walker, and Ronald Watt. </P>
                <P>In accordance with 49 U.S.C. 31136(e) and 31315, each renewal exemption will be valid for 2 years unless revoked earlier by FMCSA. The exemption will be revoked if: (1) The person fails to comply with the terms and conditions of the exemption; (2) the exemption has resulted in a lower level of safety than was maintained before it was granted; or (3) continuation of the exemption would not be consistent with the goals and objectives of 49 U.S.C. 31136 and 31315. </P>
                <SIG>
                    <DATED>Issued on: April 6, 2007. </DATED>
                    <NAME>Larry W. Minor, </NAME>
                    <TITLE>Acting, Associate Administrator, Policy and Program Development.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC> [FR Doc. E7-6999 Filed 4-12-07; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4910-EX-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION </AGENCY>
                <SUBAGY>Federal Railroad Administration </SUBAGY>
                <SUBJECT>Notice of Petitions for Approval; Railroad Safety Program Plans </SUBJECT>
                <P>Although not required, the Federal Railroad Administration (FRA) is providing notice that it has received petitions for approval of two Railroad Safety Program Plans (RSPP) submitted pursuant to 49 Code of Federal Regulations (CFR) part 236, subpart H. The individual petitions are described below, including the party seeking approval and the requisite docket numbers where the petitions and any related information may be found. These documents are available for public inspection; however, FRA is not accepting public comment on the documents as this notice is provided for information only. </P>
                <HD SOURCE="HD1">Alaska Railroad Corporation (ARRC) </HD>
                <DEPDOC>[Waiver Docket Number FRA-2007-27600] </DEPDOC>
                <P>ARRC submitted a petition for approval of an RSPP. The petition, the RSPP, and any related documents have been placed in the requisite docket and are available for public inspection. </P>
                <HD SOURCE="HD1">Norfolk Southern Corporation (NS) </HD>
                <DEPDOC>[Waiver Docket Number FRA-2006-26260] </DEPDOC>
                <P>NS submitted a petition for approval of an RSPP. The petition, the RSPP, and any related documents have been placed in the requisite docket and are available for public inspection. </P>
                <P>
                    All documents in the public docket are also available for inspection and copying on the Internet at the docket facility's Web site at 
                    <E T="03">http://dms.dot.gov</E>
                    . 
                </P>
                <P>
                    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-78). The Statement may also be found at 
                    <E T="03">http://dms.dot.gov</E>
                    . 
                </P>
                <SIG>
                    <DATED>Issued in Washington, DC on April 9, 2007. </DATED>
                    <NAME>Grady C. Cothen Jr., </NAME>
                    <TITLE>Deputy Associate Administrator for Safety Standards and Program Development.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC> [FR Doc. E7-7069 Filed 4-12-07; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4910-06-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION </AGENCY>
                <SUBAGY>Federal Railroad Administration </SUBAGY>
                <SUBJECT>Petition for Waiver of Compliance </SUBJECT>
                <P>
                    In accordance with Part 211 of Title 49 Code of Federal Regulations (CFR), notice is hereby given that the Federal Railroad Administration (FRA) received a request for a waiver of compliance with certain requirements of its safety 
                    <PRTPAGE P="18729"/>
                    standards. The individual petition is described below, including the party seeking relief, the regulatory provisions involved, the nature of the relief being requested, and the petitioner's arguments in favor of relief. 
                </P>
                <HD SOURCE="HD1">Canadian National Railway Company </HD>
                <DEPDOC>[Waiver Petition Docket Number FRA-2007-27410] </DEPDOC>
                <P>The Canadian National Railway Company (CN), on behalf of its wholly owned subsidiaries, Illinois Central Railroad Company, Wisconsin Central, Grand Trunk and Western Railroad Company, Chicago Central &amp; Pacific Railroad Company, Duluth, Winnipeg &amp; Pacific Railroad Company, Bessemer &amp; Lake Erie Railroad Company, and the Duluth Missabe &amp; Iron Range Railroad Company, seeks a waiver of compliance with the Locomotive Safety Standards, 49 CFR 229.25(b), as it pertains to the 92-day periodic requirement to inspect electrical devices and visible insulation. CN requests to remove DC traction motor covers and inspect the interior of the motor during the second and fourth periodic inspection. According to the petitioner, CN requires all traction motor brushes be replaced during the locomotive's annual inspection. </P>
                <P>Interested parties are invited to participate in these proceedings by submitting written views, data, or comments. FRA does not anticipate scheduling a public hearing in connection with these proceedings since the facts do not appear to warrant a hearing. If any interested party desires an opportunity for oral comment, they should notify FRA, in writing, before the end of the comment period and specify the basis for their request. </P>
                <P>
                    All communications concerning these proceedings should identify the appropriate docket number (FRA-2007-27410) and must be submitted to the Docket Clerk, DOT Docket Management Facility, Room PL-401 (Plaza Level), 400 7th Street, SW., Washington, DC 20590. Communications received within 45 days of the date of this notice will be considered by FRA before final action is taken. Comments received after that date will be considered as far as practicable. All written communications concerning these proceedings are available for examination during regular business hours (9 a.m.-5 p.m.) at the above facility. All documents in the public docket are also available for inspection and copying on the Internet at the docket facility's Web site at 
                    <E T="03">http://dms.dot.gov</E>
                    . 
                </P>
                <P>
                    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 comment (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-78). The Statement may also be found at 
                    <E T="03">http://dms.dot.gov</E>
                    . 
                </P>
                <SIG>
                    <DATED>Issued in Washington, DC on April 9, 2007. </DATED>
                    <NAME>Grady C. Cothen, Jr., </NAME>
                    <TITLE>Deputy Associate Administrator for Safety Standards and Program Development.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC> [FR Doc. E7-7068 Filed 4-12-07; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4910-06-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION </AGENCY>
                <SUBAGY>Federal Railroad Administration </SUBAGY>
                <DEPDOC>[Docket Number FRA-2007-27556] </DEPDOC>
                <SUBJECT>Petition for Waiver of Compliance </SUBJECT>
                <P>In accordance with Part 211 of Title 49 Code of Federal Regulations (CFR), notice is hereby given that the Federal Railroad Administration (FRA) received a request for a waiver of compliance with certain requirements of its safety standards. The individual petition is described below, including the party seeking relief, the regulatory provisions involved, the nature of the relief being requested, and the petitioner's arguments in favour of relief. </P>
                <HD SOURCE="HD1">SMS Lines </HD>
                <DEPDOC>[Docket Number FRA-2007-27556] </DEPDOC>
                <P>The SMS Lines, a Class III railroad, seeks a waiver of compliance from the requirements of Title 49 CFR 223.11. SMS has operated within the Pureland Industrial Park in Bridgeport, Gloucester County, New Jersey since June, 1994. The petitioner proposes to use Locomotive Number 412, on a limited basis only at this location for yard and local switching service. </P>
                <P>Locomotive Number 412, model VO-1000, was built by the Baldwin Locomotive Works (BLW) in 1945, and is owned by the United Railroad Historical Society (URHS), a non-profit organization. SMS is assisting the URHS in the restoration of this locomotive and upon completion, would operate it over approximately 5 miles of track with three grade crossings within the industrial park. The current operations average 1 train per day, 6 days per week, year-round throughout the park at restricted speed. All track is FRA Class I (10 mph). </P>
                <P>The petitioner believes that this locomotive can be safely operated throughout the industrial park with the current non-compliant safety-type glazing. The cost to the URHS for installation of all new window frames and compliant FRA Types I &amp; II glazing is significant with only a marginal increase in safety due to the low speed. Historically, there has been no vandalism of railroad glazing within the Pureland Industrial Park, and there are no overhead bridges nor tunnels. </P>
                <P>Interested parties are invited to participate in these proceedings by submitting written views, data, or comments. FRA does not anticipate scheduling a public hearing in connection with these proceedings since the facts do not appear to warrant a hearing. If any interested party desires an opportunity for oral comment, they should notify FRA, in writing, before the end of the comment period and specify the basis for their request. </P>
                <P>All communications concerning these proceedings should identify the appropriate docket number (e.g., Waiver Petition Docket Number FRA-2007-27556) and must be submitted in triplicate to the Docket Clerk, DOT Central Docket Management Facility, Room Pl-401, Washington, DC 20590-0001. Communications received within 45 days of the date of this notice will be considered by FRA before final action is taken. Comments received after that date will be considered as far as practicable. </P>
                <P>
                    All written communications concerning these proceedings are available for examination during regular business hours (9 a.m.-5 p.m.) at DOT Central Docket Management Facility, Room Pl-401 (Plaza Level), 400 Seventh Street, SW., Washington, DC. All documents in the public docket are also available for inspection and copying on the Internet at the docket facility's Web site at 
                    <E T="03">http://dms.dot.gov.</E>
                </P>
                <P>
                    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 comment (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 19377-78). The statement may also be found at 
                    <E T="03">http://dms.dot.gov.</E>
                </P>
                <SIG>
                    <DATED>Issued in Washington, DC, on April 9, 2007. </DATED>
                    <NAME>Grady C. Cothen, Jr., </NAME>
                    <TITLE>Deputy Associate Administrator for Safety Standards and Program Development.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC> [FR Doc. E7-7079 Filed 4-12-07; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4910-06-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="18730"/>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION </AGENCY>
                <SUBAGY>Federal Railroad Administration </SUBAGY>
                <DEPDOC>[Docket No. FRA-2005-23281, Notice No. 5] </DEPDOC>
                <SUBJECT>Safety of Private Highway-Rail Grade Crossings; Notice of Safety Inquiry </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Railroad Administration (FRA), Department of Transportation (DOT). </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of open meeting date change. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>On July 27, 2006, FRA published a notice announcing its intent to conduct a series of open meetings throughout the United States, in cooperation with appropriate State agencies, to consider issues related to the safety of private highway-rail grade crossings. FRA has conducted four meetings to date and on March 17, 2007, FRA published a notice announcing the scheduling of an additional meeting to be held April 26, 2007, in Syracuse, New York. Due to recently developed scheduling conflicts, however, it is necessary to postpone this April 26 meeting. This Notice No. 5 is an announcement that the Syracuse, New York, meeting has been rescheduled for July 26, 2007. FRA regrets any inconvenience this date change may have caused. </P>
                    <P>At the meeting, FRA intends to solicit oral statements from private crossing owners, railroads, and other interested parties on issues related to the safety of private highway-rail grade crossings, which will include, but not be limited to, current practices concerning the responsibility for safety at private grade crossings, the adequacy of warning devices at private crossings, and the relative merits of a more uniform approach to improving safety at private crossings. FRA has also opened a public docket on these issues so that interested parties may submit written comments for public review and consideration. </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The fifth public meeting will be held in Syracuse, New York on July 26, 2007, at the Renaissance Syracuse Hotel, 701 East Genesee Street, Syracuse, New York 13210, beginning at 9:30 a.m. </P>
                    <P>Persons wishing to participate are requested to provide their names, organizational affiliation, and contact information to Michelle Silva, FRA Docket Clerk, 1120 Vermont Avenue NW., Washington, DC 20590 (telephone: 202-493-6030). Persons needing sign language interpretation or other reasonable accommodation for disability are also encouraged to contact Ms. Silva using the aforementioned information. </P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Ron Ries, FRA Office of Safety, 1120 Vermont Avenue NW., Washington, DC 20590 (telephone: 202-493-6299); Miriam Kloeppel, FRA Office of Safety, 1120 Vermont Avenue NW., Washington, DC 20590 (telephone: 202-493-6299); or Kathryn Shelton, FRA Office of Chief Counsel, 1120 Vermont Avenue NW, Washington, DC 20590 (telephone: 202-493-6038). </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    For additional information, please see the initial notice published July 27, 2006, in the 
                    <E T="04">Federal Register</E>
                     (71 FR 42713) and available at 
                    <E T="03">http://a257.g.akamaitech.net/7/257/2422/01jan20061800/edocket.access.gpo.gov/2006/pdf/06-6501.pdf</E>
                </P>
                <HD SOURCE="HD1">Request for Comments </HD>
                <P>While FRA solicits discussion and comments on all areas of safety at private highway-rail grade crossings, we particularly encourage comments on the following topics: </P>
                <P>• At-grade highway-rail crossings present inherent risks to users, including the railroad and its employees, and to other persons in the vicinity should a train derail into an occupied area or release hazardous materials. When passenger trains are involved, the risks are heightened. From the standpoint of public policy, how do we determine whether the creation or continuation of a private crossing is justified? </P>
                <P>• Is the current assignment of responsibility for safety at private crossings effective? To what extent do risk management practices associated with insurance arrangements result in the “regulation” of safety at private crossings? </P>
                <P>• How should improvement and/or maintenance costs associated with private crossings be allocated? </P>
                <P>• Is there a need for alternative dispute resolution mechanisms to handle disputes that may arise between private crossing owners and the railroads? </P>
                <P>• Should the State or Federal Government assume greater responsibility for safety at private crossings? </P>
                <P>• Should there be nationwide standards for warning devices at private crossings, or for intersection design of new private grade crossings? </P>
                <P>• How do we determine when a private crossing has a “public purpose” and is subject to public use? </P>
                <P>• Should some crossings be categorized as “commercial crossings,” rather than as “private crossings?” </P>
                <P>• Are there innovative traffic control treatments that could improve safety at private crossings on major rail corridors, including those on which passenger service is provided? </P>
                <P>• Should DOT request enactment of legislation to address private crossings? If so, what should it include? </P>
                <SIG>
                    <DATED>Issued in Washington, DC, on April 9, 2007. </DATED>
                    <NAME>Jo Strang, </NAME>
                    <TITLE>Associate Administrator for Safety.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC> [FR Doc. E7-7064 Filed 4-12-07; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4910-06-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION </AGENCY>
                <SUBAGY>Federal Railroad Administration </SUBAGY>
                <SUBJECT>Notice of Application for Approval of Discontinuance or Modification of a Railroad Signal System or Relief From the Requirements of Title 49 Code of Federal Regulations Part 236 </SUBJECT>
                <P>Pursuant to Title 49 Code of Federal Regulations (CFR) part 235 and 49 U.S.C. 20502(a), the following railroad has petitioned the Federal Railroad Administration (FRA) seeking approval for the discontinuance or modification of the signal system or relief from the requirements of 49 CFR part 236 as detailed below. </P>
                <DEPDOC>[Docket Number FRA-2007-27287] </DEPDOC>
                <FP SOURCE="FP-1">
                    <E T="03">Applicant:</E>
                     BNSF Railway Company, Mr. Gregory C. Fox,  Vice President Engineering,  P.O. Box 961034,  Fort Worth, Texas 76161-0034. 
                </FP>
                <P>BNSF Railway Company (BNSF) seeks relief from the requirements of the Rules, Standards and Instructions, Title 49 CFR part 236, Section 236.377 Approach Locking, 236.378 Time locking, 236.379 Route Locking, 236.380 Indication Locking, and 236.381 Traffic Locking, on processor-based systems to the extent that only the following be required every four years after initial testing or program change: </P>
                <P>• Verification of the CRC/Check Sum/UCN of the existing location specific application logic to the previously tested version. </P>
                <P>• Tests on equipment outside the processor (switch indication, track indication, searchlight signal indication, approach locking (if external)) are verified to the processor's inputs and switch locking is tested from the processor's output to the switch machine. </P>
                <P>• Testing of the duration of any timers with variable settings. </P>
                <P>
                    <E T="03">Applicant's justification for relief:</E>
                     Many of BNSF's interlockings and control points are controlled by solid-state processor-based systems. The 2-year signal locking tests for solid-state 
                    <PRTPAGE P="18731"/>
                    interlockings required by the FRA place an undue burden on the railroad. Due to train traffic, some large control points can take a month or more to complete the 2-year locking tests. Once a processor-based system has been tested and locking tests documented on installation, re-testing should not be required since the logic continues to operate in the same manor as it did when installed and the operation does not change. 
                </P>
                <P>Any interested party desiring to protest the granting of an application shall set forth specifically the grounds upon which the protest is made, and include a concise statement of the interest of the party in the proceeding. Additionally, one copy of the protest shall be furnished to the applicant at the address listed above. </P>
                <P>All communications concerning this proceeding should be identified by docket number FRA-2007-27287 and may be submitted by one of the following methods: </P>
                <P>
                    • 
                    <E T="03">Web site: http://dms.dot.gov.</E>
                     Follow the instructions for submitting comments on the DOT electronic site; 
                </P>
                <P>
                    • 
                    <E T="03">Fax:</E>
                     202-493-2251; 
                </P>
                <P>
                    • 
                    <E T="03">Mail:</E>
                     Docket Management Facility, U.S. Department of Transportation, 400 Seventh Street, SW., Nassif Building, Room PL-401, Washington, DC 20590-0001; or 
                </P>
                <P>
                    • 
                    <E T="03">Hand Delivery:</E>
                     Room PL-401 on the Plaza Level of the Nassif Building, 400 Seventh Street, SW., Washington, DC, between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays. 
                </P>
                <P>
                    Communications received within 45 days of the date of this notice will be considered by the FRA before final action is taken. Comments received after that date will be considered as far as practicable. All written communications concerning these proceedings are available for examination during regular business hours (9 a.m.-5 p.m.) at the above facility. All documents in the public docket are also available for inspection and copying on the Internet at the docket facility's Web site at 
                    <E T="03">http://dms.dot.gov.</E>
                </P>
                <P>
                    FRA wishes to inform all potential commenters that 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 comment (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-78) or you may visit 
                    <E T="03">http://dms.dot.gov.</E>
                </P>
                <P>FRA expects to be able to determine these matters without an oral hearing. However, if a specific request for an oral hearing is accompanied by a showing that the party is unable to adequately present his or her position by written statements, an application may be set for public hearing. </P>
                <SIG>
                    <DATED>Issued in Washington, DC on April 9, 2007. </DATED>
                    <NAME>Grady C. Cothen, Jr., </NAME>
                    <TITLE>Deputy Associate Administrator for Safety Standards and Program Development.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC> [FR Doc. E7-7070 Filed 4-12-07; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4910-06-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION </AGENCY>
                <SUBAGY>Federal Railroad Administration </SUBAGY>
                <DEPDOC>[Docket Number FRA-2006-23687] </DEPDOC>
                <SUBJECT>Notice of Informational Filing </SUBJECT>
                <P>For informational purposes only, the Federal Railroad Administration (FRA) is providing notice that it has received an informational filing from BNSF Railway Company (BNSF) to test the next version of the railroad's Electronic Train Management System (ETMS) submitted pursuant to Title 49 Code of Federal Regulations (CFR) part 236.913. The informational filing is described below, including the submitting party and the requisite docket number where the informational filing and any related information may be found. The document is also available for public inspection; however, FRA is not accepting public comment on the document. </P>
                <HD SOURCE="HD1">BNSF Railway Company (BNSF) </HD>
                <DEPDOC>[Docket Number FRA-2006-23687] </DEPDOC>
                <P>BNSF has submitted an informational filing to FRA to continue operational testing of the next version of the railroad's ETMS. This continued testing will allow BNSF to obtain the necessary information required to amend its current Product Safety Plan (PSP) for a future submittal to the FRA. The informational filing has been placed in the Docket Number FRA-2006-23687, and is available for public inspection. </P>
                <P>
                    All documents in the public docket are available for examination during regular business hours (9 a.m.-5 p.m.) at the DOT Central Docket Management Facility, Room Pl-401 (Plaza Level), 400 Seventh Street, SW., Washington, DC. All documents in the public docket are also available for inspection and copying on the Internet at the docket facility's Web site at 
                    <E T="03">http://dms.dot.gov.</E>
                </P>
                <P>
                    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-78). The Statement may also be found at 
                    <E T="03">http://dms.dot.gov</E>
                    . 
                </P>
                <SIG>
                    <DATED>Issued in Washington, DC, on April 9, 2007. </DATED>
                    <NAME>Grady C. Cothen, Jr., </NAME>
                    <TITLE>Deputy Associate Administrator for Safety Standards and Program Development.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC> [FR Doc. E7-7077 Filed 4-12-07; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4910-06-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION </AGENCY>
                <SUBAGY> Federal Railroad Administration </SUBAGY>
                <DEPDOC> [Docket Number FRA-2007-27599] </DEPDOC>
                <SUBJECT>Notice of Application for Approval of Discontinuance or Modification of a Railroad Signal System or Relief From the Requirements of Title 49 Code of Federal Regulations Part 236 </SUBJECT>
                <P>Pursuant to Title 49 Code of Federal Regulations (CFR) Part 235 and 49 U.S.C. 20502(a), the following railroad has petitioned the Federal Railroad Administration (FRA) seeking approval for the discontinuance or modification of the signal system or relief from the requirements of 49 CFR Part 236 as detailed below. </P>
                <FP SOURCE="FP-1">
                    <E T="03">Applicant:</E>
                     CSX Transportation, Incorporated, Mr. C. M. King, Chief Engineer, Communications and Signals, 500 Water Street , SC J-350, Jacksonville, Florida 32202. 
                </FP>
                <P>CSX Transportation, Incorporated (CSXT) seeks approval of the proposed modification of the traffic control system, on the main track and yard tracks, at CP-Bowl, milepost 000-384.3, on the Atlanta Division, Boyles Terminal Subdivision, near Birmingham, Alabama. The proposed changes consist of a reduction to the limits of the traffic control system, including the following: discontinuance of all controlled signals at CP-Bowl, conversion of all remaining power-operated switches to hydraulic type switches under the jurisdiction and control of the local yardmaster, and designation of the trackage to Yard Limits, CSXT Operating Rule 193, for train movement authority. </P>
                <P>The reason given for the proposed changes is that present day operation, along with the proposal to modify the track configuration, including installation of an additional main track between Black Creek and Mary Lee, does not warrant retention of the power-operated switches and signals. </P>
                <P>
                    Any interested party desiring to protest the granting of an application shall set forth specifically the grounds upon which the protest is made, and include a concise statement of the interest of the party in the proceeding. Additionally, one copy of the protest 
                    <PRTPAGE P="18732"/>
                    shall be furnished to the applicant at the address listed above. 
                </P>
                <P>All communications concerning this proceeding should be identified by docket number FRA-2007-27599 and may be submitted by one of the following methods: </P>
                <P>
                    • 
                    <E T="03">Web site: http://dms.dot.gov.</E>
                </P>
                <P>Follow the instructions for submitting comments on the DOT electronic site; </P>
                <P>
                    • 
                    <E T="03">Fax:</E>
                     202-493-2251; 
                </P>
                <P>
                    • 
                    <E T="03">Mail:</E>
                     Docket Management Facility, U.S. Department of Transportation, 400 Seventh Street, SW., Nassif Building, Room PL-401, Washington, DC 20590-0001; or 
                </P>
                <P>
                    • 
                    <E T="03">Hand Delivery:</E>
                     Room PL-401 on the plaza level of the Nassif Building, 400 Seventh Street, SW., Washington, DC, between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays. 
                </P>
                <P>
                    Communications received within 45 days of the date of this notice will be considered by the FRA before final action is taken. Comments received after that date will be considered as far as practicable. All written communications concerning these proceedings are available for examination during regular business hours (9 a.m.-5 p.m.) at the above facility. All documents in the public docket are also available for inspection and copying on the Internet at the docket facility's Web site at 
                    <E T="03">http://dms.dot.gov</E>
                    . 
                </P>
                <P>
                    FRA wishes to inform all potential commenters that 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 comment (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-78) or you may visit 
                    <E T="03">http://dms.dot.gov</E>
                    . 
                </P>
                <P>FRA expects to be able to determine these matters without an oral hearing. However, if a specific request for an oral hearing is accompanied by a showing that the party is unable to adequately present his or her position by written statements, an application may be set for public hearing. </P>
                <SIG>
                    <DATED>Issued in Washington, DC on April 9, 2007. </DATED>
                    <NAME>Grady C. Cothen, Jr., </NAME>
                    <TITLE>Deputy Associate Administrator for Safety Standards and Program Development.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. E7-7059 Filed 4-12-07; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4910-06-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION </AGENCY>
                <SUBAGY>Federal Railroad Administration </SUBAGY>
                <DEPDOC>[Docket Number FRA-2007-27418] </DEPDOC>
                <SUBJECT>Notice of Application for Approval of Discontinuance or Modification of a Railroad Signal System or Relief From the Requirements of Title 49 Code of Federal Regulations Part 236 </SUBJECT>
                <P>Pursuant to Title 49 Code of Federal Regulations (CFR) Part 235 and 49 U.S.C. 20502(a), the following railroad has petitioned the Federal Railroad Administration (FRA) seeking approval for the discontinuance or modification of the signal system or relief from the requirements of 49 CFR part 236 as detailed below. </P>
                <HD SOURCE="HD1">Docket Number FRA-2007-27418 </HD>
                <FP SOURCE="FP-1">
                    <E T="03">Applicants:</E>
                     CSX Transportation, Incorporated, Mr. C.M. King, Chief Engineer, Communications and Signals, 500 Water Street , SC J-350, Jacksonville, Florida 32202.
                </FP>
                <FP SOURCE="FP-1">Four Rivers Transportation, Mr. A.V. Reck, President, 1500 Kentucky Avenue, Paducah, Kentucky 42003.</FP>
                <P>CSX Transportation, Incorporated (CSXT) and Four Rivers Transportation jointly seeks approval of the proposed modification of the signal system, on the single main track and siding, between Berkeley Run Jct., milepost BUC 0.0, near Grafton, West Virginia, and Hampton Jct., milepost BUC 41.9, near Adrian, West Virginia, on CSXT's Huntington Division East, Cowen Subdivision. The proposed changes consist of the conversion of the existing traffic control system to an automatic block signal (ABS) system; conversion of all power-operated switches to hand operation; and conversion of the method of operation to TWC-DCS authority, supplemented by signal indications of the ABS system. </P>
                <P>The reason given for the proposed changes is that the current traffic density does not warrant retention of this type of signal system. </P>
                <P>Any interested party desiring to protest the granting of an application shall set forth specifically the grounds upon which the protest is made, and include a concise statement of the interest of the party in the proceeding. Additionally, one copy of the protest shall be furnished to the applicant at the address listed above. </P>
                <P>All communications concerning this proceeding should be identified by docket number FRA-2007-27418 and may be submitted by one of the following methods: </P>
                <P>
                    • 
                    <E T="03">Web site:</E>
                      
                    <E T="03">http://dms.dot.gov.</E>
                </P>
                <P>Follow the instructions for submitting comments on the DOT electronic site; </P>
                <P>
                    • 
                    <E T="03">Fax:</E>
                     202-493-2251; 
                </P>
                <P>
                    • 
                    <E T="03">Mail:</E>
                     Docket Management Facility, U.S. Department of Transportation, 400 Seventh Street, SW., Nassif Building, Room PL-401, Washington, DC 20590-0001; or 
                </P>
                <P>
                    • 
                    <E T="03">Hand Delivery:</E>
                     Room PL-401 on the plaza level of the Nassif Building, 400 Seventh Street, SW., Washington, DC, between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays. 
                </P>
                <P>
                    Communications received within 45 days of the date of this notice will be considered by the FRA before final action is taken. Comments received after that date will be considered as far as practicable. All written communications concerning these proceedings are available for examination during regular business hours (9 a.m.-5 p.m.) at the above facility. All documents in the public docket are also available for inspection and copying on the Internet at the docket facility's Web site at 
                    <E T="03">http://dms.dot.gov</E>
                    . 
                </P>
                <P>
                    FRA wishes to inform all potential commenters that 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 comment (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-78) or you may visit 
                    <E T="03">http://dms.dot.gov</E>
                    . 
                </P>
                <P>FRA expects to be able to determine these matters without an oral hearing. However, if a specific request for an oral hearing is accompanied by a showing that the party is unable to adequately present his or her position by written statements, an application may be set for public hearing. </P>
                <SIG>
                    <DATED>Issued in Washington, DC on April 9, 2007. </DATED>
                    <NAME>Grady C. Cothen, Jr., </NAME>
                    <TITLE>Deputy Associate Administrator for Safety Standards and Program Development.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. E7-7060 Filed 4-12-07; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4910-06-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION </AGENCY>
                <SUBAGY>Federal Transit Administration </SUBAGY>
                <DEPDOC>[Docket Number: FTA-2005-23227] </DEPDOC>
                <SUBJECT>Notice of Final Title VI Circular </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Transit Administration (FTA), DOT. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>
                        Notice of Final Title VI and Title VI—Dependent Guidelines for 
                        <PRTPAGE P="18733"/>
                        Federal Transit Administration Recipients. 
                    </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Federal Transit Administration (FTA) has revised its Title VI Circular 4702.1 and is publishing a new Circular 4702.1A, “Title VI and Title VI—Dependent Guidelines for Federal Transit Administration Recipients.” The purpose of this circular is to provide recipients and subrecipients of Federal Transit Administration (FTA) financial assistance with guidance and instructions necessary to carry out the U.S. Department of Transportation's (“DOT” or the “Department”) Title VI regulations (49 CFR part 21) and to integrate into their programs and activities considerations expressed in the Department's Order on Environmental Justice (Order 5610.2), and Policy Guidance Concerning Recipients' Responsibilities to Limited English Proficient (“LEP”) Persons (70 FR 74087, December 14, 2005). Circular 4702.1A includes requirements and procedures which, if followed, will ensure that no person in the United States shall, on the basis of race, color, or national origin, be excluded from participation in, denied the benefits of, or be subjected to discrimination under any program or activity receiving financial assistance from FTA. </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>This guidance becomes effective May 14, 2007. This circular supersedes Title VI Circular 4702.1, “Title VI Program Guidelines for Urban Mass Transit Administration Recipients.” </P>
                </EFFDATE>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Availability of Final Circulars </HD>
                <P>
                    You may download the circular from the Department's Docket Management System (
                    <E T="03">http://dms.dot.gov</E>
                    ) by entering docket number 23227 in the search field, and then clicking on “reverse order.” The circular is the most recently posted document. You may also download an electronic copy of the circular from FTA's Web site, at 
                    <E T="03">http://www.fta.dot.gov.</E>
                     Paper copies of the circular may be obtained by calling FTA's Administrative Services Help Desk, at 202-366-4865. 
                </P>
                <HD SOURCE="HD1">I. Why Has FTA Revised This Circular? </HD>
                <P>Prior to this notice, FTA's Title VI Circular had not been revised since May 26, 1988. In the ensuing 18 years, much of the guidance in Circular 4702.1 has become outdated. Circular 4702.1A has been updated to incorporate developments in legislation, Executive Orders, DOT directives, and court cases that have transformed transportation policy and affected the rights and responsibilities of recipients and beneficiaries. These directives include the Intermodal Surface Transportation Equity Act (ISTEA), enacted in 1991; the Transportation Equity Act for the 21st Century (TEA-21), enacted in 1998; the Safe, Accountable, Flexible, Efficient Transportation Equity Act: A Legacy for Users (SAFETEA-LU), enacted in 2005; Executive Order 12898, “Federal Actions to Address Environmental Justice in Minority Populations and Low-Income Populations” (issued in 1994); the DOT Order on Environmental Justice 5610.2 (issued in 1997); Executive Order 13166, “Improving Access to Services for Persons with Limited English Proficiency” (issued in 2000); and DOT's “Policy Guidance Concerning Recipients” Responsibilities to Limited English Proficient Persons” (referred to as the “DOT LEP Guidance”) issued in 2001 and reissued in 2005. </P>
                <P>In addition, Circular 4702.1 needed to be updated to eliminate outdated nomenclature, such as references to FTA as the “Urban Mass Transit Administration” and to statutes such as the “Urban Mass Transit Act” and the “Federal Aid Urban System Program.” </P>
                <P>
                    In the process of revising this circular, FTA took the following factors into consideration: The requirements of the DOT Title VI regulations at 49 CFR part 21; external Title VI guidance, including the Department of Justice's (DOJ's) Title VI Legal Manual and the Council on Environmental Quality's “Environmental Justice Guidance Under the National Environmental Policy Act”; the outcomes of Title VI administrative complaints and lawsuits generated since the circular's last revision; the recommendations of the Government Accountability Office (GAO) in its November 2005 report on limited English proficiency (see GAO report, “Transportation Services: Better Dissemination and Oversight of DOT's Guidance Could Lead to Improved Access for Limited English-Proficient Populations,” GAO-06-52); changes in industry practices since the circular's last revision; and results of FTA Title VI oversight reviews. The 
                    <E T="04">Federal Register</E>
                     Notice accompanying FTA's draft Title VI Circular 
                    <E T="04">Federal Register</E>
                    , Vol. 71, No. 135, July 14, 2006) contains a detailed description of how these factors were taken into account during the circular's revision process. 
                </P>
                <P>
                    This document does not include the final circular; electronic versions of the circulars may be found on the docket, at 
                    <E T="03">http://dms.dot.gov,</E>
                     or on FTA's Web site, at 
                    <E T="03">http://www.fta.dot.gov.</E>
                     Paper copies of the circulars may be obtained by contacting FTA's Administrative Services Help Desk, at 202-366-4865. 
                </P>
                <HD SOURCE="HD1">II. How Does the Final Circular Differ From the Proposed Circular? </HD>
                <P>While much of the content of the final circular is identical to the proposed version, the final circular includes the following comprehensive changes made in response to comments received during FTA's July 14 to September 14, 2006, public comment period: </P>
                <P>• The title of the final circular has been changed from “Title VI Guidelines for FTA Recipients” to “Title VI and Title VI—Dependent Guidelines for Federal Transit Administration Recipients” and provisions of the final circular have been modified to clarify that the document outlines requirements pursuant to the DOT Title VI regulations; and guidance pursuant to the DOT Order 5610.2 on Environmental Justice and the DOT LEP Guidance located at 70 FR 74087 (December 14, 2005). The revised circular covers recipients' and subrecipients' responsibilities to ensure nondiscrimination on the basis of race, color, or national origin pursuant to the DOT Title VI regulations. Pursuant to Executive Order 12898 and the Department of Transportation Order on Environmental Justice, FTA has advised its grantees to ensure that the interests and well-being of low-income populations are considered and addressed during transportation decisionmaking. </P>
                <P>• The proposed circular included requirements that FTA recipients and subrecipients must abide by and recommended procedures that agencies can follow to meet the requirements. The final circular more clearly delineates what actions are required and what actions are merely encouraged or recommended. </P>
                <P>• The final circular provides recipients and subrecipients with greater flexibility to meet FTA requirements. While the proposed circular recommended a single strategy to comply with Title VI, the final circular in many cases allows recipients and subrecipients to choose from a menu of options in order to meet certain requirements and more clearly states that recipients and subrecipients can, in some cases, develop their own procedures for meeting the requirements in the DOT regulations and this circular. </P>
                <P>• The final circular references, on a more consistent basis, terminology that is already in use in existing FTA or DOT regulations and directives. Terms of art are used consistently throughout the document. </P>
                <P>
                    • The final circular includes updated appendices to assist recipients and subrecipients with compliance. 
                    <PRTPAGE P="18734"/>
                </P>
                <HD SOURCE="HD1">III. How Did FTA Involve the Public in the Circular Revision? </HD>
                <P>
                    FTA has responded to feedback received during two public comment periods. During the first comment period, which occurred between December 15, 2005 and January 17, 2006, FTA invited the public to comment on Circular 4702.1 and sought input from interested parties on any problems with compliance, best practices for compliance, and proposals for changes to this Circular (see 
                    <E T="04">Federal Register</E>
                    , Vol. 70, No. 240, December 15, 2005). FTA received comments from 23 individuals or organizations in response to this notice and request for comment. A summary of these comments as well as how they were incorporated into the proposed Title VI Circular is included in FTA's July 14, 2006, 
                    <E T="04">Federal Register</E>
                     Notice and Request for Comment. 
                </P>
                <P>
                    On July 14, 2006, FTA published a notice of its proposed circular in the 
                    <E T="04">Federal Register</E>
                    . The comment period lasted until September 14, 2006. During this period, FTA staff responded to questions from the public on the proposed circular and also invited stakeholder groups to submit comments to the docket. A summary of the outreach conducted and responses to questions received is included in the docket. 
                </P>
                <P>In response to the July 14, 2006, notice and request for comment, FTA received comments from 17 transit agencies, four non-profit organizations, three metropolitan planning organizations (MPOs), one State DOT, one individual, and one county government. A total of 27 entities submitted comments to the docket. We received diverse and even opposing comments. </P>
                <HD SOURCE="HD1">IV. How Has FTA Responded to Comments Received? </HD>
                <P>The remainder of this notice summarizes the specific comments received pursuant to FTA's July 14, 2006, notice and describes FTA's response. </P>
                <HD SOURCE="HD2">Positive Feedback </HD>
                <P>
                    <E T="03">Comments:</E>
                     Five organizations provided general positive feedback on the proposed circular, including that the circular seems reasonable in its approaches, that the proposed circular's elimination of outdated requirements is an improvement over the existing circular, that the guidance in general represents a great improvement over the 1988 Circular, that consolidation and consistency among the provisions will clarify FTA's compliance requirements, and that citizens will benefit from equal and fair access to Federally-funded transit systems. 
                </P>
                <HD SOURCE="HD2">The Relationship Between the Circular's Requirements and Recommendations </HD>
                <P>
                    <E T="03">Comments:</E>
                     Five organizations requested that the final circular clarify what actions recipients are required to take and what actions are merely encouraged or recommended. One commenter stated that FTA should avoid giving recommendations as opposed to issuing defined standards; another commenter suggested that FTA issue a summary matrix differentiating between requirements and recommendations. A third commenter requested that the circular clarify references to “shall” and “should” throughout the document. Another commenter stated that the proposed circular's mix of requirements and recommendations creates requirements without offering fixed standards for compliance. 
                </P>
                <P>
                    <E T="03">FTA Response:</E>
                     The final circular distinguishes between requirements, flowing from the DOT Title VI regulations, and guidance, based on the DOT Order on Environmental Justice and the DOT LEP Guidance. In several instances, the final circular also allows agencies to meet the requirements by adopting procedures that would not be overly burdensome and best fit with their existing business practices. The final circular in some instances allows recipients and subrecipients to choose from a menu of options or effective practices in order to comply with many of the requirements listed in Chapter IV and Chapter V. In some instances, recipients have the option of developing their own procedure to comply with a specific requirement. In cases where a recipient develops its own procedure for compliance, FTA will review the procedure, which should be included as part of the recipients' Title VI submission, to confirm that it meets the expectation of the relevant circular provision and the DOT Title VI regulations. The final circular's Chapter I, parts 1(c)(1) and 1(d)(1) clarify where the circular's requirements end and guidance begins. 
                </P>
                <HD SOURCE="HD2">The Circular's Administrative Burden on Grantees </HD>
                <P>
                    <E T="03">Comments:</E>
                     Four organizations commented that the proposed circular would impose administrative burdens on FTA grantees. One commenter stated that many of the proposed changes to the circular would have an adverse impact on the agency's ability to provide its required level and quality of service and would be unduly burdensome. A second commenter stated that the process of preparing and submitting Title VI reports detracts from their ability to provide public transportation and that the list of new and expanded recordkeeping and reporting requirements establish a substantial burden on FTA grantees. A third commenter suggested that agencies serving areas with under 200,000 people should only be required to file a Title VI report with FTA if there has been a complaint filed with the agency. A fourth commenter estimated that a threefold increase in resources over what the agency currently spends on Title VI administration would be needed in response to the proposed circular, but stated that the benefits of Title VI compliance outweigh the increased costs. This commenter also recommended that the final circular include a directive to appropriate sufficient resources to facilitate administration of the new circular. 
                </P>
                <P>
                    <E T="03">FTA Response:</E>
                     The final circular modifies the administrative and reporting requirements found in Circular 4702.1. In some instances FTA has added administrative and reporting requirements. In other instances FTA has removed administrative and reporting requirements. Under circular 4702.1A, all recipients and subrecipients, not just those transit agencies serving areas of 200,000 persons or more, are responsible for administering their public involvement activities in a non-discriminatory manner and submitting a summary of these activities to the FTA or to their direct recipient. Also under circular 4702.1A, all recipients and subrecipients must take responsible steps to ensure meaningful access to the benefits, services, information, and other important portions of their programs and activities for individuals who are Limited English Proficient (LEP). The final circular gives recipients and subrecipients great latitude to determine what specific actions are necessary to fulfill these requirements. 
                </P>
                <P>
                    Circular 4702.1A removes the old requirement that all recipients and subrecipients submit FTA and DOT Title VI assurances that are separate from FTA's annual list of certifications and assurances. The revised circular also eliminates the requirement under Circular 4702.1 that recipients report the grants that they receive from the FTA and that they re-submit in their Title VI compliance report copies of environmental analyses that had been previously submitted to FTA. Also removed in the final circular is the requirement that all recipients who provide transportations service conduct level and quality of service monitoring 
                    <PRTPAGE P="18735"/>
                    and report their results to FTA. This requirement is reserved for transit agencies serving areas with populations of 200,000 persons or greater. 
                </P>
                <P>Circular 4702.1A would further reduce administrative burdens by giving recipients and subrecipients greater flexibility to meet requirements through procedures that best match their resources, needs, and standard practices. For example, Chapter V, part 2 of the proposed circular required recipients providing transit service to geographic areas of 200,000 people or greater to monitor the service that they provide in order to ensure that the end result of policies and decisionmaking is equitable service. The proposed circular required that recipients fulfill this requirement by implementing level of service and quality of service monitoring procedures and analyzing the results of customer surveys. Chapter V, part 5 of the final circular continues to require that recipients monitor the service that they provide to ensure equitable service, but gives recipients the option of fulfilling this requirement by implementing either the level of service monitoring procedures, or the quality of service monitoring procedures, or the analysis of customer surveys, or developing their own monitoring procedures. Recipients may choose the option that would enable them to most efficiently meet these requirements. This approach, which is a departure from the format of Circular 4702.1 and the proposed Title VI Circular, should allow recipients and subrecipients to reduce the amount of time and resources that would be devoted to Title VI compliance while still ensuring that FTA funds are being administered without regard to race, color, or national origin.</P>
                <P>Finally, FTA will be conducting regional training in Calendar Year 2007 to inform recipients and subrecipients of the final circular's requirements and to discuss effective practices for compliance. FTA also has plans to develop an automated system where grantees can submit an electronic Title VI report. These training and electronic reporting activities should reduce the administrative burden associated with submitting Title VI reports. </P>
                <P>The final circular does not direct agencies to commit a certain level of resources towards Title VI compliance, because FTA does not generally dictate the internal resource allocation decisions of its grantees. </P>
                <HD SOURCE="HD2">The Relationship Between Title VI and Environmental Justice </HD>
                <P>Five organizations commented on the proposed circular's treatment of environmental justice principles and policies. One commenter stated that minority and low-income persons are an important category of individuals to which FTA should devote attention. Another commenter stated that the proposed circular fails to effectively differentiate between the requirements of Title VI and Executive Order 12898. A third commenter suggested that the proposed circular more consistently incorporate definitions and concepts from the DOT Order on Environmental Justice. Another commenter stated that by combining Title VI nondiscrimination law with the internal Federal agency policy for data collection and analysis required by the DOT Order on Environmental Justice, the proposed circular would create unfunded mandates, and a statutorily unrecognized protected class of low-income people. </P>
                <P>
                    <E T="03">FTA Response:</E>
                     The final circular fulfills the purpose of DOT Order 5610.2, which states that each operating administration in DOT integrates the considerations of Executive Order 12898 into the programs, policies, and activities that they administer or implement. Order 5610.2 is not solely internal to DOT and, in that FTA has integrated environmental justice considerations into its general grant program. The reformatted circular's guidance to recipients to identify and address, as appropriate, adverse and disproportionately high effects of their policies, programs, and activities on low-income populations as well as minority populations does not introduce low-income people as a protected class under Title VI. The final circular's reference to environmental justice principles and concepts reinforces considerations already embodied in Title VI and NEPA and does not create new mandates. 
                </P>
                <HD SOURCE="HD2">Subrecipient Compliance </HD>
                <P>
                    <E T="03">Comments:</E>
                     Two organizations commented on the proposed circular's requirements for subrecipient compliance with Title VI in Chapter IV. One commenter sought clarification as to whether Section 5316 and 5317 grantees and subrecipients would also be required to comply with the circular. The commenter also stated that FTA cannot reach around its grantees to force reports and documents from subrecipients and that passing on specific compliance requirements to subrecipients risks forcing subrecipients to prepare multiple, conflicting reports to comply with the multiple Federal agencies that extend financial assistance. Another commenter stated that the circular's new requirements for subrecipients equate to significant administrative expenses and recommended that subrecipients receiving under $150,000 be exempt from the public involvement and language access requirements in Chapter IV of the proposed circular. 
                </P>
                <P>
                    <E T="03">FTA Response:</E>
                     The final circular clarifies that Section 5316 and 5317 grantees are to follow the requirements for all recipients and subrecipients listed in Chapter IV. This notice clarifies that FTA can require recipients to pass forward Title VI requirements to their subrecipients, consistent with the final circular's guidance in Chapter IV. In addition, Chapter V of the final circular provides guidelines to designated recipients in large urbanized areas, so that these recipients can ensure that they are apportioning Job Access and Reverse Commute (JARC) and New Freedom funds to subrecipients without regard to race, color, or national origin. 
                </P>
                <P>In response to the commenter's concern that subrecipients will be subject to conflicting methodologies for civil rights compliance stemming from multiple Federal agencies, FTA notes that its circular is designed in part to clarify the DOT Title VI regulations. These regulations, as well as those issued by other Federal agencies, are modeled after Title VI regulations developed by DOJ. Because multiple Federal agencies have adopted nearly identical Title VI regulatory language, the risk that a transit provider receiving funds from many Federal sources will be subject to conflicting or diverging requirements is small. However, if a transit provider has reason to believe that one or more of the requirements in Chapter IV of the final Title VI Circular conflicts with a Title VI data collection or reporting requirement requested by another Federal agency, the provider should contact their direct recipient or FTA to discuss a strategy to resolve the conflict. </P>
                <P>
                    Chapter IV Section 3 of the final circular coffers guidance that subrecipients seek out and consider the viewpoints of minority, low-income, and LEP populations in the course of conducting public outreach and involvement activities; however, this section states that recipients and subrecipients have wide latitude to determine how, when, and how often specific public involvement measures should take place, and what specific measures are most appropriate. Subrecipients can take the resources available to their agency into account when determining the appropriate public involvement steps. Chapter IV Section 4 of the final circular requires that all subrecipients take reasonable 
                    <PRTPAGE P="18736"/>
                    steps to ensure meaningful access to their programs and activities by people with limited English proficiency; however, the final circular clarifies that certain FTA recipients or subrecipients, such as those serving very few LEP people or those with very limited resources may choose not to develop a written LEP plan as recommended in the DOT LEP Guidance. 
                </P>
                <HD SOURCE="HD2">Data Collection Methodology </HD>
                <P>
                    <E T="03">Comments:</E>
                     Three organizations commented on the data collection and analysis methodology in the proposed circular. One commenter requested that FTA restore the definition of “minority transit route” contained in Circular 4702.1. A second commenter requested that the proposed circular reinsert a modified definition of “minority transit route” as “a route that has at least 40 percent of its total route mileage in Census tracts or traffic analysis zones with a percentage of minority population greater than the percentage of the minority population in the transit service area,” and that agencies use this definition to assess the demographics of transit routes where no demographics on ridership based on customer survey data are available. A third commenter suggested that the circular define a “minority transit route” as a route where more than one-third of a route's passenger boardings are in minority areas or a route where more than one third of the stops are located in minority areas. 
                </P>
                <P>
                    <E T="03">FTA Response:</E>
                     The final circular does not include a definition of “minority route” in part because comments received during the December 15, 2005 to January 17, 2006, comment period questioned the usefulness of this definition and in part because FTA wants to ensure that recipients have the option of using methodology that best fits their needs. If recipients choose to develop their own procedures in order to evaluate the impacts of service reductions, as is an option in Chapter V, part 1b, or if recipients choose to develop their own procedures to monitor transit service for equity concerns, as is an option in Chapter V, part 1d, they have the option to incorporate the old circular's definition of “minority transit route” or their own definition of a “minority transit route” into their locally developed procedures. 
                </P>
                <HD SOURCE="HD2">Title VI Requirements for Paratransit Service </HD>
                <P>
                    <E T="03">Comments:</E>
                     Two organizations commented on the proposed circular's treatment of paratransit service. One commenter requested that agencies that provide only paratransit service not be required to submit a Title VI report. A second commenter asked that FTA clarify the reporting requirements of agencies that provide only paratransit services. 
                </P>
                <P>
                    <E T="03">FTA Response:</E>
                     The final circular does not provide guidance or requirements for agencies that provide Americans with Disabilities Act (ADA) complementary paratransit service. Title VI guidance for this mode of transportation was not included in part because of concerns that Title VI requirements might conflict with the detailed requirements for ADA complementary paratransit contained in the DOT regulations implementing Titles II and III of the ADA (49 CFR part 37). In addition, FTA has not, in recent years, received complaints that ADA complementary paratransit providers were discriminating on the basis of race, color, or national origin, nor have we received requests for guidance in this area. If FTA receives specific complaints that ADA complementary paratransit providers are engaging in disparate treatment or disparate impact discrimination, we will investigate such complaints and work with the transit provider to ensure that paratransit service is being administered consistent with Title VI. 
                </P>
                <P>The general requirements presented in Chapter IV of the circular, including the reporting requirements, would apply to agencies that provide demand-response transportation that is available to the general public or, in the case of services funded under FTA's Section 5310 program, is open to eligible older adults and individuals with disabilities. The requirements of this chapter also apply to providers of fixed-route transportation. </P>
                <HD SOURCE="HD2">Minority Representation on Decision Making Bodies </HD>
                <P>
                    <E T="03">Comments:</E>
                     One organization noted that the proposed circular eliminated a provision in Circular 4702.1 that recipients provide a racial breakdown of their nonelected boards, advisory councils, or committees and provide a description of the efforts made to encourage minorities to participate on such boards, councils, or committees. The organization recommended that FTA require transit agencies and MPOs to report on how affected communities of color are represented on decision making bodies. 
                </P>
                <P>
                    <E T="03">FTA Response:</E>
                     In the course of its Title VI oversight activities, FTA determined that most transit agencies could not meet the original circular's requirement to encourage minority participation on their decision-making bodies because transit boards of directors are generally appointed by the local political leadership and agency staff believed it would be inappropriate to interject themselves into this appointment process. FTA considered including in its final circular a provision that would instruct agencies to analyze whether jurisdictions with concentrations of minority and/or low-income people were adequately represented on transit agency or metropolitan planning boards. The final circular does not include such a provision because, regardless of the results of such analyses, agency staff would still not have the authority to influence the composition of their boards of directors. 
                </P>
                <HD SOURCE="HD2">Nondiscrimination in Emergency Preparedness </HD>
                <P>
                    <E T="03">Comments:</E>
                     One organization recommended that the final circular include language requiring FTA grantees to provide assistance to transit dependent populations in emergencies. 
                </P>
                <P>
                    <E T="03">FTA Response:</E>
                     FTA is working to ensure that its grantees consider civil rights issues in the course of developing and implementing emergency preparedness, disaster response, and disaster recovery plans so that race, color, and national origin, including LEP status, do not impede access to information, evacuation, and relief services that are provided by FTA grantees. Appendix D of the final circular includes a reference to FTA's Disaster Response and Recovery Resource for Transit Agencies which can be found at 
                    <E T="03">http://transit-safety.volpe.dot.gov/Publications/order/singledoc.asp?docid=437.</E>
                     This resource provides local transit agencies and transportation providers with useful information and best practices in emergency preparedness and disaster response and recovery, including information on how to respond to the unique needs of low-income people, limited English proficient people, people with disabilities, and older adults. 
                </P>
                <HD SOURCE="HD2">The Circular Revision Process </HD>
                <P>
                    <E T="03">Comments:</E>
                     Three organizations commented on the process FTA is using to revise its Title VI Circular. One commenter asked if FTA plans to allow for additional input on the document. Another commenter noted that with many open dockets for comments, it is hard to be able to comment while maintaining business functions, and the agency often does not have time to evaluate and respond to all issues. Two commenters stated that, to avoid inconsistencies, the proposed circular should reference and adopt language 
                    <PRTPAGE P="18737"/>
                    from the regulation on planning as well as the upcoming rulemaking to implement coordinated public transit-human services and the rulemaking for emergency preparedness for public transportation systems. 
                </P>
                <P>
                    <E T="03">FTA Response:</E>
                     As of the date of this publication, Circular 4702.1A is a final document: however, FTA will consider making changes to the circular if it receives comments from the public and determines that clarification to Circular 4702.1A is required. The provisions in this circular are consistent with the planning regulations at 23 CFR part 450 as well as FTA's proposed Elderly Individuals and Individuals with Disabilities, Job Access and Reverse Commute, and New Freedom programs Circulars. 
                </P>
                <HD SOURCE="HD1">V. Section-by-Section Discussion </HD>
                <P>FTA received comments from 27 entities on specific sections of the proposed circular. This section summarizes the provisions that were subject to comment, the nature of the comment, and FTA's response. </P>
                <HD SOURCE="HD2">Objectives of the Title VI Circular </HD>
                <P>Chapter II, part 1 of the proposed circular described the document's objectives, stating, in part, that the guidance and procedures will allow FTA recipients to “ensure that the level and quality of transportation service is provided equitably and without regard to race, color, national origin, or income” (Chapter II, part 1a) and to “avoid, minimize, or mitigate disproportionately high and adverse human health and environmental effects, including social and economic effects of programs and activities on minority populations and low-income populations” (Chapter II, part 1b). </P>
                <P>
                    <E T="03">Comments:</E>
                     FTA received comments on this section from two organizations. One commenter suggested that the language in Chapter II, part 1a inappropriately mixed Title VI and environmental justice concepts and would result in a requirement to distribute government resources equitably rather than ensuring a straightforward ban on discrimination against protected classes. A second commenter requested that the reference at Chapter II, part 1b to “disproportionately high” effects be changed to “disproportionate” effects to eliminate confusion over what constitutes a “high” effect and to clarify that the circular should have the effect of eliminating any disproportionate effect on minority and low-income populations. 
                </P>
                <P>
                    <E T="03">FTA Response:</E>
                     FTA has revised the “Objectives” section to state that the guidance and procedures in the circular will allow FTA recipients and subrecipients to “ensure that the level and quality of transportation service is provided without regard to race, color, or national origin.” (Circular 4702.1A, Chapter II, part 1a). This modified language clarifies that one of the objectives of the circular is to ensure nondiscrimination under Title VI. The final circular retains the reference to “disproportionately high” effects because this term is consistent with the terms used in the DOT Order on Environmental Justice. 
                </P>
                <HD SOURCE="HD2">Definitions </HD>
                <P>Chapter II, part 6 of the proposed circular included a section defining terms that appear elsewhere in the document. </P>
                <P>
                    <E T="03">Comments:</E>
                     Six entities commented on the proposed circular's definition of “adverse effect,” listed at Chapter II, part 6a. One commenter noted that the distinction between an “adverse effect” and “disparate effect” is confusing. Two commenters requested that the proposed circular use the definition of “adverse effect” found in the DOT Order on Environmental Justice. Another commenter stated that the proposed definition is too broad and impractical for purposes of evaluating projects; however, the problem could be alleviated if the recipient has discretion to decide which effects need to be evaluated based on the given project. Another commenter stated that the definition should be amended to take into account adverse effects that can be mitigated. Another commenter stated that the proposed definition extends the Federal reach into areas of traditional State and local purview. 
                </P>
                <P>
                    <E T="03">FTA Response:</E>
                     The final circular retains the definition of “adverse effect” in the proposed circular because it is the definition used in the DOT Order on Environmental Justice. Although the definition of “adverse effect” in the DOT Order and the circular includes a wide range of possible effects, recipients have discretion to decide which effects need to be evaluated in detail based on the nature of the proposed project and the characteristics of the physical and natural environment where the project is located. Recipients can also receive approval from FTA after demonstrating that the adverse effects identified will be avoided, minimized, or mitigated. NEPA's scoping process is used to determine which specific adverse effects need to be addressed. Circular 4702.1A reinforces DOT's longstanding position that attention to any disproportionately high and adverse effects to minority and low-income communities should be incorporated into the NEPA process, but it does not alter the NEPA requirements at 23 CFR part 117 or extend the Federal reach into areas of traditional State and local purview. The final circular also includes DOJ's definition of “disparate impact,” to resolve confusion over the two terms. 
                </P>
                <P>
                    <E T="03">Comments:</E>
                     One entity commented on the proposed circular's definition of “compliance” and “deficient” listed at Section 6(c) and 6(e), respectively. One commenter stated that the definitions of these terms are inconsistent with how they are used in Section 5 of Chapter II. 
                </P>
                <P>
                    <E T="03">FTA Response:</E>
                     The final circular includes a definition of “deficiency” and uses this term consistently. 
                </P>
                <P>
                    <E T="03">Comments:</E>
                     Two organizations commented on the proposed circular's definition of “discrimination” listed at Section 6d. One commenter suggested that the definition of discrimination be modified to include any intentional or unintentional “act” as well as “pattern or practice,” because the prohibition on discrimination at 49 CFR Section 21.5 includes a reference to actions of discrimination. A second commenter requested that “discrimination” be defined in terms of “disproportionate effects” as opposed to the proposed definition of an act that subjects a person to “unequal treatment.” 
                </P>
                <P>
                    <E T="03">FTA Response:</E>
                     The final circular adopts the definition of “discrimination” based on the definition used in the FHWA Title VI complaint manual. Under this definition, “discrimination” refers to “any act or inaction, whether intentional or unintentional, in any program or activity of a Federal aid recipient, subrecipient, or contractor that results in disparate treatment, disparate impact, or perpetuating the effects of prior discrimination based on race, color, or national origin.” The final circular also includes definitions for “disparate treatment” and “disparate impact” that are incorporated from the FHWA manual. 
                </P>
                <P>
                    <E T="03">Comments:</E>
                     Five entities commented on the proposed circular's definition of “disproportionate effect” listed at Section 6f. Two commenters requested that FTA replace this definition with the definition of an “adverse and disproportionately high effect” contained in the DOT Order on Environmental Justice. A third commenter stated that the different subdefinitions of the term are confusing and that the subdefinition at 6f(2) was more commonly used than the one at 6(f)(3). A fourth commenter requested that the reference to the term “predominantly” in the language on “effects predominantly borne by 
                    <PRTPAGE P="18738"/>
                    members of a minority race, color or national origin population * * *” at Section 6(f)(1) be replaced by the word “disproportionately” and that the word “significantly” at 6f(3) be deleted. Another commenter suggested that FTA amend the definition reference “adverse” effects that are predominantly borne by minority and low-income populations and that the definition to take into account adverse effects that can be mitigated. 
                </P>
                <P>
                    <E T="03">FTA Response:</E>
                     The final circular adopts the definition of “disproportionately high and adverse effect” used in the DOT Order on Environmental Justice in place of the “disproportionate effect” definition used in the proposed circular. 
                </P>
                <P>
                    <E T="03">Comments:</E>
                     One entity commented on the proposed circular's definition of “fixed guideway” listed at Section 6h. The commenter requested that FTA interpret this definition to exclude commuter rail lines with shared rights of way. 
                </P>
                <P>
                    <E T="03">FTA Response:</E>
                     The definition of “fixed guideway” in the final circular is taken, word-for-word, from FTA's authorizing legislation, which defines the term “fixed guideway” at 49 U.S.C. 5302(a)(4). FTA interprets “fixed guideways” to include commuter lines with shared rights of way. 
                </P>
                <P>
                    <E T="03">Comments:</E>
                     Four entities commented on the proposed circular's definition of “low-income person” listed at Section 6l. Three commenters requested that this definition be modified to allow agencies to develop local definitions of “low-income.” Two commenters requested that this definition be consistent with the definition in the U.S. Census. 
                </P>
                <P>
                    <E T="03">FTA Response:</E>
                     The final circular keeps the draft circular's definition of “low-income” because this term is adopted from the DOT Order on Environmental Justice. Although this definition references the Department of Health and Human Services' (HHS) poverty guidelines, it should be noted that HHS develops this level based on poverty data collected from the U.S. Census. FTA recipients can use Census data to determine the number and proportion of low-income people located in their service area. 
                </P>
                <P>While the circular does not require that recipients identify low-income populations using any definition other than the one adopted in the final circular, it does give recipients flexibility to collect demographic information on their beneficiaries using locally developed methods (see Chapter V, Section 1c). Grantees could adopt a locally developed definition of “low-income,” such as any household with an income of 25 to 50 percent of the metropolitan area's median household income. </P>
                <P>
                    <E T="03">Comments:</E>
                     One organization commented on the proposed circular's definition of “low-income population” listed at Section 6m and “minority population” listed at Section 6o. The commenter stated that these definitions are impractical as they fail to set a standard for determining whether a group is “readily identifiable.” 
                </P>
                <P>
                    <E T="03">FTA Response:</E>
                     The final circular retains the definitions of “minority population” and “low-income population,” which are adopted from the DOT Order on Environmental Justice. This notice clarifies that a “readily identifiable” population is one that can be identified using data from the U.S. Census. 
                </P>
                <P>
                    <E T="03">Comments:</E>
                     Four entities commented on the proposed circular's definition of a “predominantly minority area” in Section 6r and a “predominantly low-income area” in Section 6s. One commenter requested that the circular delete the reference to “predominantly” minority or low-income areas. A second commenter requested that the definition is over-inclusive and that the document should be modified to define “predominantly minority” and “predominantly low-income” areas as areas where the minority population and low-income population proportion is two times or greater the proportion of these populations in the transit service area. A third commenter requested that the definition's reference to “traffic analysis zone” be deleted. A fourth commenter requested that the definition be used consistently throughout the circular. 
                </P>
                <P>
                    <E T="03">FTA Response:</E>
                     The final circular retains the definition of “predominantly minority area” as “a geographic area, such as a neighborhood, Census tract, or traffic analysis zone, where the proportion of minority people residing in that area exceeds the average proportion of minority people in the recipient's service area.” The revised circular also retains the definition of a “predominantly low-income area” as “a geographic area, such as a neighborhood, Census tract, or traffic analysis zone, where the proportion of low-income people residing in that area exceeds the average proportion of low-income people in the recipient's service area.” Pursuant to Chapter V, Section 1c, recipients have flexibility to collect demographic information on their beneficiaries using thresholds for “predominantly minority” and “predominantly low-income” areas that are different from the terms as defined in Chapter II, Sections 6v and 6w of the final circular. For example, under the guidance offered in Chapter V, Section 1c, a recipient could implement a map-making procedure in order to highlight those Census tracts where the minority or low-income population was twice the average of the service area. This modification might be useful for recipients that serve regions with high overall minority or low-income populations and who wanted to ensure that their service was reaching areas where minority and low-income people were highly concentrated. In addition, the guidance at Chapter V, Section 1c of the final circular gives recipients the flexibility to prepare maps based on either Census tracts or traffic analysis zones. The final circular uses the terms “predominantly minority” and “predominantly low-income” consistently throughout the document. 
                </P>
                <HD SOURCE="HD2">Title VI Requirements for Applicants </HD>
                <P>Chapter III of the proposed circular describes the procedures that all applicants for FTA financial assistance, including those entities applying for FTA assistance for the first time, should follow to comply with the DOT Title VI regulations. </P>
                <P>
                    <E T="03">Comments:</E>
                     FTA received one comment on this chapter. The commenter noted that the Web link to the text of FTA's annual certifications and assurances no longer exists. The commenter also remarked that the circular offers no provisions to ensure that first-time applicants for Federal financial assistance have complied with Title VI. 
                </P>
                <P>
                    <E T="03">FTA Response:</E>
                     The final circular does not include a specific Web link for FTA's annual certifications and assurances because the exact link may change over time. However, applicants should be aware that the text of these certifications and assurances will generally be posted on FTA's Web site, 
                    <E T="03">http://www.fta.dot.gov.</E>
                     The circular does not offer provisions to ensure that applicants who have never before received Federal financial assistance have complied with Title VI because Title VI does not apply to entities that do not receive financial assistance from the Federal government. 
                </P>
                <HD SOURCE="HD2">General Reporting Requirements </HD>
                <P>Chapter IV of the proposed circular describes the procedures that all FTA recipients and subrecipients shall follow to ensure that their activities comply with the DOT Title VI regulations and/or the DOT Order on Environmental Justice and the DOT LEP Guidance. </P>
                <P>
                    <E T="03">Comments:</E>
                     FTA received comments from one organization on the purpose of 
                    <PRTPAGE P="18739"/>
                    this chapter. The commenter stressed that Title VI analyses should be done and provided to communities prior to asking for community input on alternatives, the development of alternatives should be informed by community participation, and obtaining input from minority and low-income communities on their transit needs should be the starting place, not a validation of decisions already made. 
                </P>
                <P>
                    <E T="03">FTA Response:</E>
                     The final circular states that an environmental justice analyses of construction projects should be incorporated into the agency's NEPA compliance (see Chapter IV, Section 2 of Circular 4702.1A). NEPA and the DOT NEPA regulations require early and continuous public involvement in the identification of social, economic, and environmental impacts related to proposed projects. In addition, the public participation requirement for all recipients and subrecipients at Chapter IV, Section 3 of Circular 4702.1A includes language stating, “An agency's public participation strategy shall offer early and continuous opportunities for the public to be involved in the identification of social, economic, and environmental impacts of proposed transportation decisions.” 
                </P>
                <HD SOURCE="HD2">Environmental Justice Analysis of Construction Projects </HD>
                <P>Chapter IV, Section 2 of the proposed circular required recipients and subrecipients to include an environmental justice analysis in their applications for a documented Categorical Exclusion (CE), Environmental Assessment (EA), and Environmental Impact Statements (EISs) that precede construction projects. This section also recommended information that should be included in the recipient's or subrecipient's environmental justice analysis. </P>
                <P>
                    <E T="03">Comments:</E>
                     FTA received six comments on this provision. One commenter noted that portions of this section refer to minority and low-income “populations” while other portions refer to minority and low-income “communities” and minority and low-income “neighborhoods” and that the varying terms are confusing. Three commenters suggested either that agencies should not have to conduct a separate environmental justice analysis for projects subject to a Class II(d) CE or that decisions as to when such analyses are performed should be left to FTA's legal counsel. A third commenter requested that FTA modify its reference to major renovation or rehabilitation projects so that construction projects that do not increase a facility's space or use should be exempted from an environmental justice analysis. Other commenters sought clarification on the information that should be collected as part of the environmental justice analysis. 
                </P>
                <P>
                    <E T="03">FTA Response:</E>
                     The environmental justice analysis of construction projects in the final circular eliminates confusing references to “communities, neighborhoods, and populations” with a consistent reference to minority and low-income populations within the study area of the project. Recipients and subrecipients do not have to perform an environmental justice analysis for any construction, renovation, or rehabilitation project that is not already subject to FTA's NEPA documentation requirements. However, if a recipient is required to submit an EIS, EA, or application for a CE, an environmental justice analysis should be part of the documentation that FTA already requires. The final circular recommends what information should be collected as part of an agency's environmental justice analysis. 
                </P>
                <HD SOURCE="HD2">Inclusive Public Involvement </HD>
                <P>Chapter IV, Section 3 of the proposed circular required recipients and subrecipients to seek out and consider the viewpoints of minority and low-income populations in the course of conducing public outreach and involvement activities. This section also provided examples of public involvement measures targeted to overcome linguistic, institutional, cultural, economic, historical, or other barriers to participation. </P>
                <P>
                    <E T="03">Comments:</E>
                     FTA received four comments on this provision of the proposed circular. One commenter suggested that FTA clarify it is the recipients' obligation to seek out and ensure participation by minority and low-income populations and include additional examples of effective information gathering in minority and low-income areas. The commenter suggested that the circular include examples of community-based strategies, where agencies have taken the initiative to seek input from transit-dependant people in their communities. The commenter stated that this section should also address variations in learning and communication styles and that the circular should state the importance of face-to-face contact and direct, easy-to-understand communication. A second commenter suggested that this section be retitled “public participation” to be consistent with terms used in SAFETEA-LU. A third commenter noted that this section does not propose a minimum standard of how, when, or how often public involvement should take place. A fourth commenter stated that the section's reference to accessibility for people with disabilities repeats requirements found in other laws and regulations and is confusing. 
                </P>
                <P>
                    <E T="03">FTA Response:</E>
                     This section of the final circular is now titled “Guidance on Promoting Inclusive Public Participation,” and Appendix D to the final circular includes references to documents that feature additional examples of public involvement that are community based and that address variations in learning and communication styles. On the issue of standards for how, when, or how often public involvement should take place, it should be noted that the DOT NEPA regulations contain specific requirements for public notification and public hearings in conjunction with proposed transportation projects subject to EAs and EISs, and Section 5307 of the Federal Transit Laws requires that grantees must have a locally developed process to solicit and consider public comment before raising fares or carrying out a major reduction of transportation. (FTA also requires that this process offer the opportunity for a public hearing or public meeting.) These requirements notwithstanding, FTA does not find it appropriate to set sweeping standards for such factors as the time of day that public hearings should be held, where meetings should be located, or how often the public should be consulted, as these process decisions are most widely accepted when the recipient or subrecipient, in consultation with the public in its jurisdiction, develops a local approach. The guidance in this section and the references in Appendix D are designed to offer effective practices that can be used as local circumstances warrant.
                </P>
                <P>The final circular eliminates the preexisting reference to providing assistance to people with disabilities in the course of public involvement only because the final circular is designed to offer guidance pursuant to the DOT Title VI regulations and the DOT Order on Environmental Justice, which do not explicitly cover disability. However, this modification to the circular does not alter the obligation of grantees under the DOT ADA regulations at 49 CFR parts 27, 37, and 38 and Section 504 of the Rehabilitation Act to ensure that their activities are accessible for people with disabilities. </P>
                <HD SOURCE="HD2">Language Access </HD>
                <P>
                    Chapter IV, Section 4 of the proposed circular required recipients and subrecipients to administer programs and activities consistent with the DOT 
                    <PRTPAGE P="18740"/>
                    LEP Guidance. This policy guidance describes recipients' obligations to provide language services and recommends that recipients prepare language access implementation plans describing how reasonable steps will be taken to ensure meaningful access by LEP people to recipients' programs and activities. 
                </P>
                <P>
                    <E T="03">Comments:</E>
                     FTA received seven comments on this provision. Two commenters stated that it would be unduly burdensome to require their agencies to prepare a language assistance plan. The first commenter suggested that operators with less than 100 buses should be exempt from developing a language implementation plan and the second suggested that agencies be encouraged but not required to follow the DOT LEP Guidance. Another commenter requested that FTA clarify how agencies can apply the DOT LEP Guidance to LEP people who have low literacy in their native language or who have a disability that contributes to their limited English proficiency. Another commenter requested that the entire text of the DOT LEP Guidance be incorporated into the Title VI Circular. Another commenter noted that the circular's treatment of the DOT LEP Guidance does not establish standards, but instead merely lists the components that a plan should have. Another commenter questioned the appropriateness of carrying forward a legal interpretation of national origin discrimination that was not present at the passage of the Civil Rights Act of 1964. Another commenter recommended that the DOT LEP Guidance be updated to modify the document's “safe harbor” provisions and that FTA work with the Census Bureau to develop data that would assist transit providers in meeting the DOT LEP guidance. 
                </P>
                <P>
                    <E T="03">FTA Response:</E>
                     Title VI and its implementing regulations require that FTA recipients take responsible steps to ensure meaningful access to the benefits, services, information, and other important portions of their programs and activities for individuals who are Limited English Proficient (LEP). The Final Circular provides recipients and subrecipients with guidance on how to meet this requirement. In general, agencies should demonstrate that they have taken responsible steps to provide language assistance by developing and implementing a language assistance plan according to the recommendations in the DOT LEP Guidance. The final circular clarifies that certain FTA recipients or subrecipients, such as those serving very few LEP people or those with very limited resources may choose not to develop a written LEP plan. However, the absence of a written LEP plan does not obviate the underlying obligation to ensure meaningful access by LEP people to the benefits, services, information, and other important portions of their programs and activities. Appropriate language assistance should be based on the recipient's analysis of the number or proportion of LEP people eligible to be served or likely to be encountered by a program, activity, or service; the frequency with which those people come into contact with the program; the nature and importance of the program, activity, or service to people with LEP; the resources available to the agency, and the cost of providing language assistance. 
                </P>
                <P>Recipients whose LEP population includes members with low literacy in their native language or people with disabilities that contribute to language barriers should consider using symbol signs, pictograms, and oral translation or providing accessible features consistent with DOT's requirements under Section 504 of the Rehabilitation Act, the ADA, and the ADAAG. </P>
                <P>
                    The final circular does not include the text of the entire DOT LEP Guidance because merging this guidance into the circular would make the document much longer and less usable by grantees. A link to the DOT LEP Guidance can be found at FTA's Title VI Web site, 
                    <E T="03">http://www.fta.dot.gov/civilrights/civil_rights_5088.html</E>
                    . The circular does not modify any provisions of the DOT LEP guidance, as this directive is under the purview of the Office of the Secretary of Transportation. 
                </P>
                <HD SOURCE="HD2">Title VI Complaint Procedures </HD>
                <P>Chapter IV, Section 5 of the proposed circular instructed recipients and subrecipients to develop procedures for investigating and tracking Title VI complaints filed against them and make their procedures for filing a complaint available to members of the public upon request. </P>
                <P>
                    <E T="03">Comments:</E>
                     One organization commented on this provision. The commenter noted that there is no requirement for recipients and subrecipients to develop procedures for investigating and tracking environmental justice and limited English proficiency complaints, to notify the public on how to file an environmental justice or LEP complaint, or to include a list of such complaints in its report to FTA. 
                </P>
                <P>
                    <E T="03">FTA Response:</E>
                     Recipients and subrecipients who receive complaints that beneficiaries were denied the benefits of, excluded from participation in, or subject to discrimination due to the beneficiaries' limited English proficiency should treat these complaints as complaints of national origin discrimination under Title VI and do not need to establish separate procedures for investigating complaints based on limited English proficiency. Recipients may wish to track such complaints as “Title VI/LEP” complaints if such a tracking system assists the organization in processing and resolving complaints. Recipients and subrecipients who receive complaints filed by members of minority and low-income populations can also investigate these complaints under Title VI's prohibition of discrimination on the basis of race and may wish to track such complaints as “Title VI/EJ” complaints. Recipients should not investigate complaints filed under Title VI alleging discrimination solely on the basis of socioeconomic status (e.g., income), as this is not a protected class under Title VI and DOT Order 5610.2 does not establish a requirement to investigate complaints filed on the basis of income or social class. 
                </P>
                <HD SOURCE="HD2">Record of Title VI Complaints, Investigations, and Lawsuits </HD>
                <P>Chapter IV, Section 6 of the proposed circular instructed recipients and subrecipients to prepare and maintain a list of any active investigations, lawsuits, or complaints naming the recipient and/or subrecipient that allege discrimination on the basis of race, color, or national origin. </P>
                <P>
                    <E T="03">Comments:</E>
                     One organization commented on this provision. The commenter stated that the circular offers no objective criteria for the contents of the required log of complaints, investigations, and lawsuits. 
                </P>
                <P>
                    <E T="03">FTA Response:</E>
                     This section of the final circular states that the record of complaints, lawsuits, or investigations “shall include the date the investigation, lawsuit, or complaint was filed; a summary of the allegation(s); the status of the investigation, lawsuit, or complaint; and actions taken by the recipient or subrecipient in response to the investigation, lawsuit, or complaint” (see Chapter IV, Section 6). This language establishes an objective criterion for the contents of the log. 
                </P>
                <HD SOURCE="HD2">Notifying Beneficiaries of Protection under Title VI </HD>
                <P>
                    Chapter IV, Section 7 of the proposed circular instructed recipients and subrecipients to provide information to beneficiaries regarding their agencies' 
                    <PRTPAGE P="18741"/>
                    Title VI obligations and apprise beneficiaries of protections against discrimination afforded to them by Title VI. 
                </P>
                <P>
                    <E T="03">Comments:</E>
                     One entity commented on this provision. The organization stated that the section's guidance and reference to disability, age, and gender discrimination repeats requirements found in other regulations and is confusing. 
                </P>
                <P>
                    <E T="03">FTA Response:</E>
                     FTA acknowledges that this guidance overlaps with other civil rights requirements, but the final circular retains the suggestion that recipients and subrecipients publish a single, consolidated notice of their nondiscrimination obligations rather than separate notices that pertain to race, disability, age, gender, etc. (see Chapter IV, Section 7 of Circular 4702.1A). The public is well served when grantees provide a simple, comprehensive notice of all pertinent nondiscrimination obligations. 
                </P>
                <HD SOURCE="HD2">Additional Information </HD>
                <P>Chapter IV, Section 8 of the proposed circular states that, at the discretion of FTA, information other than that required by this circular may be requested in writing from a recipient or subrecipient to resolve compliance questions with Title VI and that failure to provide this information may result in a finding of noncompliance. </P>
                <P>
                    <E T="03">Comments:</E>
                     One organization commented on this provision, stating that the paragraph inappropriately creates a carte blanche ability within FTA to create reporting requirements and that this section would render compliance a “moving target.” 
                </P>
                <P>
                    <E T="03">FTA Response:</E>
                     Chapter IV Section 6 of the final circular retains FTA's right to request information other than that specifically required by the circular in order to resolve Title VI compliance concerns. This provision is necessary to ensure that FTA fulfills Section 21.11(c) of the DOT Title VI regulations. This section states that “the Secretary will make a prompt investigation whenever a compliance review, report, complaint, or any other information indicates a possible failure to comply with this part. The investigation will include, where appropriate, a review of the pertinent practices and policies of the recipient, the circumstances under which this part occurred, and other factors relevant to a determination as to whether the recipient has failed to comply with this part.” In most cases, FTA should be able to resolve allegations of discrimination by requesting and reviewing the specific information required in Circular 4702.1A. On an infrequent basis, FTA may request additional information in order to ensure that pertinent practices and policies of the recipient are reviewed. This flexibility to request additional information does not alter how FTA will determine whether a recipient is noncompliant with Title VI (discussed in Chapter II, Section 5 of the final circular) or the procedures for effecting compliance that FTA will take to ensure compliance (discussed in Chapter X of the final circular). 
                </P>
                <HD SOURCE="HD2">Program-Specific Guidance for Recipients Serving Large Urbanized Areas </HD>
                <P>Chapter V of the proposed circular provided program-specific guidance for recipients providing service to urbanized areas of 200,000 persons or more under 49 U.S.C. 5307. </P>
                <P>
                    <E T="03">Comments:</E>
                     Two organizations commented on the scope of this chapter. One commenter asked whether this chapter's requirements apply to transit providers that provide service within an urbanized area of 200,000 people or greater but whose service area (as defined by the population residing within a three-fourth mile boundary of the system's transit routes) is under 200,000. Another commenter stated that under the proposed circular, the agency would need to respond to the general reporting requirements since the majority of its service area lies within an urbanized area with a population over 200,000; however, the agency, which has a total of 32 busses and 2,100 daily boardings, lacks the resources to prepare the same level of analysis required of large transit operators. 
                </P>
                <P>
                    <E T="03">FTA Response:</E>
                     The final circular clarifies that the program-specific requirements in Chapter V apply to those entities that are authorized to provide transit service to jurisdiction(s) where the total population of the jurisdiction(s) is 200,000 or greater. For example, a recipient with a charter to provide transit service to a specific city that happens to have a population of 50,000 would not need to comply with the requirements of this chapter even if the city is located within an urbanized area with a total population of 200,000 people or more. Alternatively, a recipient that is chartered to provide service to a county with a total population of 250,000 would be required to comply with the requirements of this chapter even if the total population residing within a certain distance of the recipient's existing fixed routes is less than 200,000. 
                </P>
                <HD SOURCE="HD2">Data Collection and Policy Setting Requirements </HD>
                <P>Chapter V, Section 1a of the proposed circular required agencies to which this chapter applies to prepare demographic service profile maps and charts that will help the recipient determine whether transit service is available to all segments of a recipient's population. Subsequent sections recommended how these maps and charts should be prepared. </P>
                <P>
                    <E T="03">Comments:</E>
                     Three organizations commented on this provision. One commenter stated that the circular should clarify that maps should identify areas where the percentage of the total minority or low-income population exceeds the average minority or low-income population. Another commenter asked FTA to clarify that producing maps alone does not demonstrate compliance with Title VI. A third commenter applauded the language in this provision that recommended but did not require that maps and overlays be prepared using Geographic Information System (GIS) technology. 
                </P>
                <P>
                    <E T="03">FTA Response:</E>
                     Chapter V, Section 1a(2) of the final circular clarifies that transit agencies may produce maps that highlight areas where the percentage of minority and/or low-income people exceeds the average proportion for the recipient's service area. The final version retains language that does not require that maps be prepared using GIS. The proposed circular would allow recipients to prepare demographic maps and overlays in order to demonstrate that they are in compliance with the requirement at 49 CFR Section 21.9(b) that recipients have available racial and ethnic data showing the extent to which members of minority groups are beneficiaries of programs receiving Federal financial assistance. Recipients can also choose to fulfill this obligation by implementing the options for collecting demographic information at Chapter V, Sections 1b, or 1c of the final circular. 
                </P>
                <P>Section 1(a)(1) of the proposed circular recommended that agencies prepare a base map of their transit service area that includes fixed transit facilities, major activity centers, and trip generators and that this map should highlight those facilities that were recently modernized or are scheduled for modernization in the next five years. </P>
                <P>
                    <E T="03">Comments:</E>
                     Three entities commented on this provision. One commenter asked for clarification on the provision's reference to “transit service area,” asking whether the agencies should map their service area or the urbanized area in which their service is located. 
                    <PRTPAGE P="18742"/>
                    Another commenter suggested that recipients reference the financial cost of facilities as well as mapping them, to present a spatial distribution of the agency's investments and ensure that investments can be proportionately distributed among all service areas. Another commenter stated that the circular should define facility “modernization.” Two commenters stated that this section be amended to clarify that only transit facilities subject to modernization should be mapped. 
                </P>
                <P>
                    <E T="03">FTA response:</E>
                     The final circular clarifies that transit agencies should prepare maps of the jurisdiction(s) where they are authorized to provide service as opposed to the urbanized area where the service is located and that the maps should identify those transit facilities subject to modernization. The final circular does not require that recipients identify the financial cost of the facilities that would be modernized because FTA does not want to imply that, in order to comply with Title VI, recipients must invest equal amounts of money in facilities that were located in or would serve different demographic groups. 
                </P>
                <P>Section 1(a)(2) of the proposed circular recommended that agencies prepare a demographic map that plots the information in Section 1(a)(1) and also shades those Census tracts or traffic analysis zones where the percentage of the total minority and low-income population residing in these areas exceeds the average minority and low-income population for the service area as a whole. </P>
                <P>
                    <E T="03">Comments:</E>
                     One organization commented on this provision, stating that the proposed inclusion of low-income populations in demographic maps complicates the analysis and is not required under Title VI. 
                </P>
                <P>
                    <E T="03">FTA response:</E>
                     The final circular retains the recommendation to identify areas with predominantly low-income populations, as this guidance is consistent with DOT Order 5610.2's instructions to obtain information on the race, color, national origin, and income level of the population served and/or affected by a DOT component (see Order 5610.2, Section 7b). 
                </P>
                <P>Chapter V, Section 1b of the proposed circular instructed agencies to which this chapter applies to collect information on the race, color, national origin, income, and travel patterns of their riders necessary to identify any disparate effects of proposed service and fare changes and to assess the level and quality of service provided to minority, low-income, and LEP people. </P>
                <P>
                    <E T="03">Comments:</E>
                     Seven entities commented on this provision of the proposed circular. Three transit agencies expressed reluctance to asking questions about the race, national origin, or income of their riders and stated that including this information in customer surveys would make the surveys more difficult to administer. Two commenters suggested that agencies collect demographic information on beneficiaries through Census data as opposed to on-board surveys. Another commenter stated that it would not be feasible to administer survey information at the route level and the sample size required to produce a statistically significant sample would be burdensome. This commenter noted that surveys conducted at the modal level might be feasible. Another commenter stated that this provision's guidance to administer surveys in multiple languages could be costly for large agencies in particular. Other commenters asked that the circular define or modify terms such as “travel patterns” and “transportation options” that FTA recommends be included in the agency's customer surveys and that the circular include a recommendation for how often recipients shall be required to collect survey data. 
                </P>
                <P>
                    <E T="03">FTA response:</E>
                     The final circular offers recipients the option of collecting demographic information on their customers by using ridership surveys but does not require that recipients take this step. In lieu of collecting demographic information through ridership surveys, recipients can prepare demographic maps and overlays pursuant to Chapter V, Section 1a or implement an independent, locally developed procedure, pursuant to Chapter V, Section 1c. Those recipients that do choose to incorporate requests for demographic information into their customer surveys are not required to conduct surveys on a route-by-route basis. Administering surveys in multiple languages may be an effective way for the agency to ensure that their surveys present an accurate snapshot of their ridership. The final circular has modified the references to “travel patterns” and “transportation options” consistent with the comments received. 
                </P>
                <HD SOURCE="HD2">Service Standards and Policies </HD>
                <P>Chapter V, Section 1c instructs recipients to which this chapter applies to adopt system-wide service standards necessary to guard against arbitrary or discriminatory service design or operational decisions. This section also recommends that agencies adopt some specific service standards or policies, which are described in Section c (1) through c (7). </P>
                <P>
                    <E T="03">Comments:</E>
                     Seven organizations commented on this provision of the proposed circular. One commenter requested that the circular clarify that the service standards and policies in this section might not be applicable to ADA complementary paratransit service providers. Another commenter asked that the final circular distinguish between system-wide service “standards,” which are defined by quantitative thresholds, and system-wide service “policies” and noted that the proposed service standards for vehicle assignment and transit security are difficult to associate with a measurable standard. Another commenter stated that this section would require grantees to adopt undefined service standards or define a metric for a standard that is recommended. Another commenter asked FTA to clarify whether the standards listed in the proposed circular are required or optional. A final commenter stated that this section imposes heavy and detailed requirements for what have been traditionally local decisions. A final commenter approved of the proposed circular's language that allowed grantees to define their own service standards. 
                </P>
                <P>
                    <E T="03">FTA response:</E>
                     The final circular requires that recipients adopt quantitative system-wide service standards and that recipients also adopt system-wide policies. System-wide policies differ from service standards in that they are not necessarily based on a quantitative threshold. What specific standards and policies are adopted, as well as how standards and policies are defined, remain local decisions. The final circular offers some examples of standards and policies that recipients could adopt but clarifies that recipients can choose to set standards and policies for other indicators. Providers of ADA complementary paratransit are not required to adopt service standards under Chapter V, Section 2. The DOT ADA complementary paratransit regulations at 49 CFR Section 37.131 provide service criteria for providers of ADA complementary paratransit. 
                </P>
                <P>Section 1(c)(1) suggests that recipients adopt a system-wide standard for vehicle load, which the circular describes as a ratio of passengers to the number of seats on a vehicle. </P>
                <P>
                    <E T="03">Comments:</E>
                     One organization commented on this provision of the circular. The commenter suggested that this section define how vehicle load should be measured, including how agencies should select the location along a route for measurement. The commenter also stated that agencies should have the flexibility to define 
                    <PRTPAGE P="18743"/>
                    vehicle load in terms of passengers per vehicle at its maximum load point as opposed to a ratio between passengers and the number of seats on a vehicle. 
                </P>
                <P>
                    <E T="03">FTA Response:</E>
                     The final circular states that vehicle load can be expressed as the ratio of passengers per vehicle or the ratio of passengers to the number of seats on a vehicle during a vehicle's maximum load point. Agencies have flexibility to measure vehicle load using locally developed procedures. 
                </P>
                <P>Section 1(c)(2) suggests that agencies adopt a system-wide standard for vehicle assignment, which is described in the circular as the process by which transit vehicles are placed into service in depots and routes through the recipient's system. </P>
                <P>
                    <E T="03">Comments:</E>
                     Two organizations commented on this provision of the circular. One commenter asked whether FTA expects agencies to set vehicle assignment standards at the route level, and noted that it would not be practical for the agency to equalize the age of vehicles on all routes. The commenter also asked for guidance to clarify what types of vehicles qualify as “clean fuel” vehicles and suggested that FTA not create a hierarchy of clean fuel vehicles. Another commenter suggested that the circular include a measurement standard to be used to evaluate clean fuel vehicle deployment. 
                </P>
                <P>
                    <E T="03">FTA response:</E>
                     The final circular gives recipients the discretion to set vehicle assignment policies at the route or at the system level but does not require that the age of vehicles on all routes be equal. Rather than defining “clean fuel vehicles” the revised section includes references to vehicles equipped with technology designed to reduce emissions. The policy gives an example of a measurement standard that recipients could use to evaluate the deployment of such vehicles. 
                </P>
                <P>Section 1(c)(4) suggests that agencies adopt system-wide standards for on-time performance, described as a measure of the percentage of runs completed as scheduled. </P>
                <P>
                    <E T="03">Comments:</E>
                     Two organizations commented on this provision. The commenters stated that on-time performance is not a reasonable measurement for Title VI evaluations and that too many factors influence whether vehicles arrive on time. 
                </P>
                <P>
                    <E T="03">FTA Response:</E>
                     The final circular includes a service standard for on-time performance as an example of a system-wide standard that could be adopted. Recipients can decline to adopt this standard if they do not consider it a useful performance indicator. 
                </P>
                <P>Section 1(c)(5) suggests that agencies adopt system-wide standards for the distribution of transit amenities, described as items of comfort and convenience available to the general riding public. </P>
                <P>
                    <E T="03">Comments:</E>
                     Five organizations commented on this provision. Two commenters agreed with the section's guidance that transit agencies should not set standards for amenities, such as bus shelters, which are solely installed and maintained by a separate jurisdiction. Another two commenters requested that the circular encourage agencies to survey and account for bus shelters and stops provided by third parties or local municipalities. Another commenter suggested that agencies set standards for distributing amenities within transit modes but that the standard for distributing amenities be allowed to vary between modes. 
                </P>
                <P>
                    <E T="03">FTA response:</E>
                     The final circular does not modify the proposed circular's language on the distribution of transit amenities. Agencies are not required to survey or account for bus shelters and stops provided by parties not under their control; however, agencies may do so if they determine that such action would assist them in complying with Title VI or provide better customer service in general. 
                </P>
                <P>Section 1(c)(6) suggests that recipients set system-wide standards for service availability, described as a general measure of the distribution of routes within a transit district. </P>
                <P>
                    <E T="03">Comments:</E>
                     Two organizations commented on this provision. One commenter sought clarification on whether the reference to a “transit district” refers to an agency's service area or the urbanized area where the agency is providing service. Another commenter noted that this section offers the same guidance as the “transit access” provision in Circular 4702.1. 
                </P>
                <P>
                    <E T="03">FTA response:</E>
                     Chapter V, Section 2a(4) of the final circular references the recipient's “service area” as defined in Chapter II, Section 6 of the final circular. This notice confirms that this provision is comparable to the “transit access” service standard in Circular 4702.1. 
                </P>
                <P>Section 1(c)(7) suggests that recipients set system-wide standards for transit security, described as measures taken to protect a recipient's employees and the public against any intentional act or threat of violence or personal harm, either from a criminal or terrorist act. </P>
                <P>
                    <E T="03">Comments:</E>
                     Five organizations commented on this provision. One commenter applauded FTA for including this standard. Another asked FTA to consider providing more specific guidance on how to eliminate racial profiling in the context of transit security. Another commenter stated that this standard should only be required when the transit agency, as opposed to local law enforcement agencies, is responsible for providing security on its system. A fourth commenter stated that this standard would mean that local law enforcement activities would come under Federal review. A fifth commenter noted that without the proper risk and vulnerability assessments conducted and supported by FTA, a local authority would be forming its own standard in a vacuum. The commenter stated that a clear national standard and process will guarantee individual liberties while protecting transit infrastructure. 
                </P>
                <P>
                    <E T="03">FTA response:</E>
                     Appendix D includes a reference to DOT's policy statement, “Carrying Out Transportation Inspection and Safety Responsibilities in a Nondiscriminatory Manner,” which can be found at 
                    <E T="03">http://airconsumer.ost.dot.gov/rules/20011012.htm.</E>
                     This statement is a reminder to DOT employees and those carrying out transportation inspection and enforcement responsibilities with DOT financial support of longstanding DOT policy prohibiting unlawful discrimination against individuals because of their race, color, religion, ethnicity, or national origin. As was referenced in this notice's discussion of standards for the distribution of transit amenities, a recipient should only set system-wide policies for those aspects of transit security that it has the authority to implement. As with the other service standards, system-wide security policies will be set at the local level and FTA will not dictate what a recipient's policies should be. The circular's reference to transit security does not conflict with prior FTA directives to conduct risk and vulnerability assessments and to develop consistent policies. 
                </P>
                <HD SOURCE="HD2">Equity Analysis of Service and Fare Changes </HD>
                <P>Chapter V, Section 1d of the proposed circular instructed recipients to which this chapter applies to evaluate significant system-wide service and fare changes and proposed improvements at the planning and programming stages to determine whether those changes have a discriminatory impact. </P>
                <P>
                    <E T="03">Comments:</E>
                     Four organizations commented on this provision. Two commenters stated that the circular should provide direction for evaluating service restructuring and improvements as well as reductions in transit service. One commenter suggested that the circular clarify that Title VI evaluations be done at the same time that options 
                    <PRTPAGE P="18744"/>
                    are being proposed. Another commenter suggested that the circular adopt their agency's definition of a “major service reduction.” Another commenter expressed concern that their agency would need to evaluate service changes that had already gone into effect using the updated guidance. 
                </P>
                <P>
                    <E T="03">FTA response:</E>
                     The final circular requires that recipients to which this chapter applies shall evaluate significant system-wide service and fare changes and proposed improvements at the planning and programming stages to determine whether those changes have a discriminatory impact. For service changes, this requirement applies to “major service changes” only. The recipient should have established guidelines or thresholds for what it considers a “major” change to be. Often, this is defined as a numerical standard, such as a change that affects 25 percent of service hours of a route. FTA recommends that recipients evaluate the impacts of their service and/or fare changes using one of two options (see Circular 4702.1A, Chapter V, Section 4). The final version of this provision continues to state that the recipient's evaluation should occur at the planning and programming stages. Recipients will not be required to include in their compliance reports to FTA an analysis of service changes that went into effect before the final circular was published. The final circular does not adopt a specific definition for a major service reduction to ensure that recipients can establish their own guidelines or thresholds for what they consider major service changes to be. 
                </P>
                <P>Section 1(d)1(1)(a) of the proposed circular recommended that recipients evaluate the effects of proposed route eliminations on minority and low-income populations by mapping the routes that would be eliminated overlaid on a demographic map that highlights those Census tracts where the minority and low-income population exceeds the service area average. </P>
                <P>
                    <E T="03">Comments:</E>
                     Three organizations commented on this provision. One commenter stated that the circular should clarify that data from ridership surveys as well as maps should be used to evaluate the impacts of route eliminations. In contrast, another agency stated that customer survey data is not extensive enough to support an analysis of the effects of eliminating individual routes. Another agency stated that requiring a new map for each proposed service change would be burdensome and that agencies should be encouraged to use the evaluation methods that are most effective. 
                </P>
                <P>
                    <E T="03">FTA response:</E>
                     The final circular gives agencies the option of evaluating service and fare changes according to the procedures in Chapter V, Section 4a. Agencies also have the option to prepare an evaluation based on a modified version of these procedures or to develop their own methodology in order to determine whether system-wide service and fare changes would have adverse and disproportionately high effects. Chapter V, Section 4b states that any locally developed alternative shall include a description of the methodology used to determine the impact of the service and fare change, a determination as to whether the proposed change would have discriminatory impacts, and a description of what, if any, action was taken by the agency in response to the analysis conducted. 
                </P>
                <P>Section 1(d)(3) of the proposed circular recommended that agencies consider, as part of their evaluation of the impacts of service changes on protected groups, actions that the agency would take to minimize, mitigate, or offset any adverse effects of fare and service changes on minority and low-income populations. </P>
                <P>
                    <E T="03">Comments:</E>
                     One organization commented on this provision. The commenter stated that this section could result in the requirement for non-minority passengers to subsidize fare increases for minority passengers. 
                </P>
                <P>
                    <E T="03">FTA response:</E>
                     The final circular retains the recommendation that agencies take minimizing, mitigating, and offsetting actions into account when analyzing the effects of their service or fare changes. This provision is consistent with the considerations expressed in the DOT Order on Environmental Justice to avoid, minimize, and/or mitigate disproportionately high and adverse environmental and public health effects and interrelated social and economic effects, and provide offsetting benefits and opportunities to enhance communities, neighborhoods, and individuals affected by DOT programs, policies, and activities (see DOT Order 5610.2, Section 7(c)(2)). 
                </P>
                <P>Section 1(d)(4) of the proposed circular recommended that agencies determine which, if any, of the service or fare change proposals under consideration would disproportionately affect minority and low-income riders. The section advised recipients that they can implement a fare increase or major service reduction that would have disproportionate effects if the recipient demonstrates that the action meets a substantial need that is in the public interest and that alternatives would have more severe adverse effects than the preferred alternative. </P>
                <P>
                    <E T="03">Comments:</E>
                     Two entities commented on this provision. One commenter suggested that the circular clarify that an analysis of disproportionate effects would require a comparison of the effects of the change on minority versus non-minority riders. Another commenter stated that this section would mistakenly transform the internal data collection and analysis guidelines contained in the DOT Order on Environmental Justice into requirements for grantees to use in distributing transit resources and, as such, would severely impact State and local decisions on how to spend State and local tax and bond revenues. 
                </P>
                <P>
                    <E T="03">FTA response:</E>
                     Chapter V, Section 4a(4) of the final circular recommends that, as part of their evaluation of service and fare changes, recipients should determine which, if any, of the proposals under consideration would have a disproportionately high and adverse effect (as defined in Chapter II, Section 6) on minority and low-income riders. Because the DOT Order 5610.2 applies to policies, programs, and other activities undertaken, funded, or approved by FTA, including policy decisions and systems planning, the circular's guidance that recipients identify and address the impacts of service and fare change proposals on minority and low-income populations is appropriate. This guidance does not mean that FTA will dictate or even recommend what specific service or fare changes the agency should ultimately adopt. Pursuant to 49 U.S.C. Section 5334(11)(b)(1), FTA is prohibited from regulating operations and charges. The provisions in the final circular are included to ensure that recipients take proactive action to ensure that no person is excluded from participation in or denied the benefits of programs or activities on the grounds of race, color, and national origin (pursuant to 49 CFR Section 21.5(b)(7)) and to ensure that planning and programming activities that have the potential to have a disproportionately high and adverse effect on human health or the environment include explicit consideration of the effects on minority populations and low-income populations, (pursuant to DOT Order 5610.2 Section 4b(1)). 
                </P>
                <HD SOURCE="HD2">Monitoring Requirements </HD>
                <P>
                    Chapter V, Section 2 of the proposed circular instructed recipients to monitor the level and quality of the transit service they provide to ensure that service is being provided on an equitable basis. This section also 
                    <PRTPAGE P="18745"/>
                    recommended specific methodologies that recipients could use to monitor the level and quality of service. 
                </P>
                <P>
                    <E T="03">Comments:</E>
                     Two organizations commented on this provision. One commenter suggested that the circular require that agencies take corrective action if monitoring confirms disparities in the level and quality of transit service. A second commenter stated that the proposed methodology for analyzing results of customer surveys at Chapter V, Section 2c of the proposed circular is inconsistent with the quality of service methodology at Chapter V, Section 2b of the proposed circular, even though both methodologies seek to determine whether there are significant differences in the quality of service being provided to different demographic groups. 
                </P>
                <P>
                    <E T="03">FTA response:</E>
                     Chapter V, Section 5 of the final circular states that if recipient monitoring determines that prior decisions have resulted in disparate impacts, agencies shall take corrective action to remedy the disparities. The final circular eliminates the inconsistency between the recommended customer survey monitoring procedures in Chapter V, Section 1b and the customer surveying procedures in Chapter V, Section 5c. 
                </P>
                <HD SOURCE="HD2">Preparing and Submitting a Title VI Report </HD>
                <P>Chapter V, Section 3 instructs recipients to which this chapter applies to prepare and submit a Title VI report that documents their compliance with the requirements of Chapter V as well as with the requirements for all recipients listed in Chapter IV. </P>
                <P>
                    <E T="03">Comments:</E>
                     Two organizations commented on this provision. One commenter stated that the terms used to describe the list of items that should be submitted to FTA should reference the terms used earlier in the chapter. A second commenter said that FTA should set time frames for its review and approval of the Title VI submittals required in this section. 
                </P>
                <P>
                    <E T="03">FTA response:</E>
                     The final circular uses terms consistently throughout the document. The guidance on reporting does not include a set time frame for when FTA will approve or disapprove a submission; however, FTA's Office of Civil Rights strives to provide a prompt response to the se submittals. FTA is exploring the option of allowing grantees to submit their reports via FTA's Transportation Electronic Award Management System (TEAM-Web), which should expedite the submission and review of these reports. 
                </P>
                <HD SOURCE="HD2">Statewide Transportation Planning Activities </HD>
                <P>Chapter VI, Section 1 of the proposed circular instructed State DOTs to have an analytic basis in place for certifying their compliance with Title VI. </P>
                <P>
                    <E T="03">Comments:</E>
                     Three organizations commented on this provision. Two organizations suggested that, prior to certifying compliance with Title VI, State DOTs be required to develop and conduct specific statewide analytical processes to meet this requirement. One commenter stated that such disparity studies should include comparisons of investment and spending in different urban areas within the state. The commenter said that State DOTs need to undertake their own analytical process rather than compiling the analytical efforts conducted by the MPOs in the state. A second commenter stated that there is no requirement for corrective action should the analytical process disclose disparities. 
                </P>
                <P>
                    <E T="03">FTA response:</E>
                     The final circular offers guidance that State Departments of Transportation integrate, into statewide planning activities, considerations expressed in the DOT Order on Environmental Justice, by having an analytic basis in place for certifying compliance with Title VI. This analysis should evaluate the state's own planning activities and should not consist of a summary of the analysis conducted by MPOs. State DOTs can compare investments and spending in different urban areas within the state as part of their efforts to meet this requirement. If, after conducting a State Management Review, Compliance Review, or investigation in response to a discrimination complaint, FTA determines that a state has taken action that is inconsistent with the DOT Title VI regulations in the context of transportation planning, FTA will require the State DOT to take corrective action. 
                </P>
                <HD SOURCE="HD2">Program Administration </HD>
                <P>Chapter VI, Section 2 of the proposed circular instructed State DOTs or other State administrating agencies to document that they pass through Federal funds to subrecipients without regard to race, color, and national origin. </P>
                <P>
                    <E T="03">Comments:</E>
                     Two organizations commented on this provision. One commenter stated that FTA should ensure that this section is consistent with FTA's proposed guidance for public transit-human services coordination. A second commenter stated that the criteria that States may use to determine whether a subrecipient provides transit service to a predominantly minority and low-income population (included in Section 2b) is inconsistent with the definitions section in Chapter II. 
                </P>
                <P>
                    <E T="03">FTA response:</E>
                     FTA has determined that the language in the final circular is consistent with the language in FTA's proposed circulars for the Job Access and Reverse Commute (JARC) program, the New Freedom program, and the Elderly Individuals and Individuals with Disabilities program. The terms used in this chapter are consistent with the definitions in Chapter II. 
                </P>
                <HD SOURCE="HD2">Metropolitan Transportation Planning Requirements </HD>
                <P>Chapter VII of the proposed circular instructed MPOs to have an analytic basis in place for certifying their compliance with Title VI. </P>
                <P>
                    <E T="03">Comments:</E>
                     One organization commented on this provision. The commenter stated that the proposed circular does not require MPOs take corrective action should their analytical process disclose disparities. The commenter also suggested that FTA acknowledge that not all MPOs are subrecipients of State DOTs and those that are not should not be required to report through the State DOT. 
                </P>
                <P>
                    <E T="03">FTA response:</E>
                     The proposed and the final circular both included language recommending that MPOs have an analytical process in place for addressing as well as identifying imbalances in transportation to different demographic groups if such imbalances are identified (see Circular 4702.1A, Chapter VII, Section 1c). The final circular also clarifies that those MPOs that receive funds directly from FTA should report to FTA (Circular 4702.1A, Chapter VII, Section 2). 
                </P>
                <HD SOURCE="HD2">Compliance Reviews </HD>
                <P>Chapter VIII of the proposed circular described the review process that FTA will follow when determining a recipient's or subrecipient's compliance after the award of Federal financial assistance and what information and actions are expected from recipients and subrecipients that are subject to these reviews. </P>
                <P>
                    <E T="03">Comments:</E>
                     Two organizations commented on provisions in this chapter. Both commenters stated that FTA should create an objective, non-exhaustive list of factors for determining which recipients will be selected for compliance reviews and that the compliance review procedures could be clarified by use of a flow chart or description of a sample review. 
                </P>
                <P>
                    <E T="03">FTA response:</E>
                     Chapter VIII, Section 2 of the final circular issues an objective 
                    <PRTPAGE P="18746"/>
                    criteria for which recipients will be selected for a post-award compliance review. This chapter also includes a flow chart of the compliance review process.
                </P>
                <HD SOURCE="HD2">Complaints</HD>
                <P>Chapter IX of the proposed circular described how FTA will respond to complaints of discrimination under Title VI that are filed with FTA against a recipient or subrecipient of FTA funds.</P>
                <P>
                    <E T="03">Comments:</E>
                     Four organizations commented on the provisions in this chapter. Two commenters asked for more information on when and in what format FTA will notify the public of its procedures for accepting and investigating Title VI complaints. Another commenter stated that FTA should require that recipients have free and fair access to complaints filed against them and that FTA have a standard to determine when a complaint is timely and that grant recipients have sufficient time to respond to the complaint. Another commenter stated that favorable reviews of recipients' Title VI programs should have some bearing in expediting FTA action on Title VI complaints.
                </P>
                <P>
                    <E T="03">FTA response:</E>
                     FTA's Office of Civil Rights handles Title VI complaints pursuant to the regulations at 49 CFR Section 21.11 and using guidance contained in the “Investigation Procedures Manual for the Investigation and Resolution of Complaints Alleging Violations of Title VI and Other Nondiscrimination Statutes.” This manual was published by DOJ's Civil Rights Division and can be found at 
                    <E T="03">http://www.usdoj.gov/crt/cor/coord/invmanual.htm</E>
                    . In addition, DOT's Office of Civil Rights is developing an External Civil Rights Complaint Processing Manual that contains guidance modeled after the DOJ manual. Once this document is finalized FTA will investigate discrimination complaints based on the procedures contained therein. In general, and pursuant to the guidance in the DOJ manual, timely complaints are those filed within 180 days of the occurrence of the alleged discrimination. FTA strives to balance the need to promptly investigate and resolve discrimination complaints with the need to give recipients adequate time to respond to allegations of discrimination. In practice, FTA's Office of Civil Rights typically asks recipients to respond to a complaint within 30 to 60 days of the date of the request.
                </P>
                <P>In addition, the final circular has been modified to state that once the complainant agrees to release the complaint to the recipient or subrecipient, FTA will provide the agency with the complaint. If the complainant does not agree to release the complaint to the recipient or subrecipient, FTA may administratively close the complaint (see Chapter IX, Section 2).</P>
                <HD SOURCE="HD2">Effecting Compliance</HD>
                <P>Chapter X of the proposed circular outlined FTA's procedures for effecting compliance when it determines that a grantee is in noncompliance with Title VI.</P>
                <P>
                    <E T="03">Comments:</E>
                     Two entities commented on the provisions in this chapter. The commenters stated that FTA should identify in this chapter or elsewhere its own commitment to Title VI and provide a benchmark for grantees and the public as to what they can expect regarding diligent enforcement. The commenters also stated that relevant parts of the Supreme Court's decision in 
                    <E T="03">Alexander</E>
                     v. 
                    <E T="03">Sandoval</E>
                    , 532 U.S. 275 (2001), be discussed in the circular. In this decision, the Supreme Court foreclosed a private right of action to enforce DOJ and DOT regulations. The commenters stated that, given the outcome of this decision, FTA should verify if there are limitations to the “Judicial Review” procedures discussed in Chapter X, Section 3.
                </P>
                <P>
                    <E T="03">FTA response:</E>
                     Both the proposed circular and the final circular contain detailed guidelines as to when and under what circumstances FTA will initiate proceedings. The guidance in this Chapter is consistent with the requirement at 49 CFR Section 21.9(a) that the primary means of effecting compliance with Title VI is through voluntary compliance agreements with the recipients and that fund suspension or termination or referrals to DOJ are means of last resort. These guidelines should also allow FTA to balance its duty to permit informal resolution of findings of noncompliance against its duty to effectuate, without undue delay, the prohibition of continued assistance to programs or activities that discriminate.
                </P>
                <P>
                    The final circular does not incorporate language from the 
                    <E T="03">Sandoval</E>
                     decision; however, FTA is aware that, pursuant to this decision, filing an administrative complaint with a recipient or with FTA is the only recourse for individuals alleging that a recipient has engaged in disparate impact discrimination in violation of the 49 CFR Section 21.5(b)(2). FTA takes seriously its obligation to provide due process to parties involved in such complaints as well as its obligation to set clear expectations for recipients on how to avoid disparate impact discrimination.
                </P>
                <HD SOURCE="HD2">Appendices</HD>
                <P>The proposed circular included three checklists that listed the reporting requirements that should be prepared and submitted to FTA.</P>
                <P>
                    <E T="03">Comments:</E>
                     Four entities commented on these appendices. Two commenters stated that the checklists were beneficial tools and that it would be helpful to add to the charts a column that referenced the specific sections of the regulations that the reporting requirements apply to. Another commenter stated that Appendix A should identify the FTA Office to which a recipient or subrecipient should submit the information and another commenter stated that it would be helpful to add an index.
                </P>
                <P>
                    <E T="03">FTA response:</E>
                     The final circular includes appendices that have been modified consistent with these comments (see Circular 4702.1A, Appendices A, B, and C) and includes an index.
                </P>
                <SIG>
                    <DATED>Issued in Washington, DC, this 6th day of April 2007.</DATED>
                    <NAME>James S. Simpson,</NAME>
                    <TITLE>Administrator.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. E7-7066 Filed 4-12-07; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-57-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF THE TREASURY </AGENCY>
                <SUBJECT>Submission for OMB Review; Comment Request </SUBJECT>
                <DATE>April 9, 2007. </DATE>
                <P>The Department of the 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 May 14, 2007 to be assured of consideration. 
                </P>
                <HD SOURCE="HD1">Alcohol and Tobacco Tax and Trade Bureau (TTB) </HD>
                <P>
                    <E T="03">OMB Number:</E>
                     1513-XXXX. 
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Existing collection in use without an OMB Control Number. 
                </P>
                <P>
                    <E T="03">Title:</E>
                     Distilled Spirits Bond. 
                </P>
                <P>
                    <E T="03">Form:</E>
                     TTB 5110.56. 
                    <PRTPAGE P="18747"/>
                </P>
                <P>
                    <E T="03">Description:</E>
                     TTB F 5110.56 is used by proprietors of Distilled Spirits Plants (DSPs) and Alcohol Fuel Plants to file bond coverage with TTB. Using this form, these proprietors may file coverage and/or withdraw coverage for one plant or multiple plants. With this form proprietors of DSPs may also provide operations coverage for adjacent wine cellars. The bond may be secured through a surety company or it may be secured with collateral (cash, Treasury Bonds or Treasury Notes). The bond protects the revenue by ensuring adequate assets are available to pay tax liabilities. 
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Business and other for profits. 
                </P>
                <P>
                    <E T="03">Estimated Total Burden Hours:</E>
                     232 hours. 
                </P>
                <P>
                    <E T="03">Clearance Officer:</E>
                     Frank Foote, (202) 927-9347, Alcohol and Tobacco Tax and Trade Bureau, Room 200 East, 1310 G. Street, NW.,  Washington, DC 20005. 
                </P>
                <P>
                    <E T="03">OMB Reviewer:</E>
                     Alexander T. Hunt, (202) 395-7316, Office of Management and Budget, Room 10235, New Executive Office Building, Washington, DC 20503. 
                </P>
                <SIG>
                    <NAME>Michael A. Robinson, </NAME>
                    <TITLE>Treasury PRA Clearance Officer.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC> [FR Doc. E7-7033 Filed 4-12-07; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4810-31-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF THE TREASURY</AGENCY>
                <SUBJECT>Departmental Offices; Debt Management Advisory Committee Meeting</SUBJECT>
                <P>Notice is hereby given, pursuant to 5 U.S.C. App. 2, 10(a)(2), that a meeting will be held at the Hay-Adams Hotel, 16th Street and Pennsylvania Avenue, NW., Washington, DC., on May 1, 2007 at 11:30 a.m. of the following debt management advisory committee:</P>
                <EXTRACT>
                    <P>Treasury Borrowing Advisory Committee of the Bond Market Association (to be know upon amendment of its charter as the Treasury Borrowing Advisory Committee of The Securities Industry and Financial Markets Association).</P>
                </EXTRACT>
                <P>The agenda for the meeting provides for a charge by the Secretary of the Treasury or his designate that the Committee discuss particular issues, and a working session. Following the working session, the Committee will present a written report of its recommendations. The meeting will be closed to the public, pursuant to 5 U.S.C. App. 2, 10(d) and Pub. L. 103-202, 202(c)(1)(B) (31 U.S.C. 3121 note).</P>
                <P>This notice shall constitute my determination, pursuant to the authority placed in heads of agencies by 5 U.S.C. App. 2 10(d) and vested in me by Treasury Department Order No. 101-05, that the meeting will consist of discussions and debates of the issues presented to the Committee by the Secretary of the Treasury and the making of recommendations of the Committee to the Secretary, pursuant to Pub. L. 103-202, 202(c)(1)(B). Thus, this information is exempt from disclosure under that provision and 5 U.S.C. 552b(c)(3)(B). In addition, the meeting is concerned with information that is exempt from disclosure under 5 U.S.C. 552b(c)(9)(A). The public interest requires that such meetings be closed to the public because the Treasury Department requires frank and full advice from representatives of the financial community prior to making its final decisions on major financing operations. Historically, this advise has been offered by debt  management advisory committees established by the several major segments of the financial community. When so utilized, such a committee is recognized to be an advisory  committee under 5 U.S.C. App. 2, 3.</P>
                <P>Although the Treasury's final announcement of financing plans may not reflect the recommendations provided in reports of the Committee, premature disclosure of the Committee's deliberations and reports would be likely to lead to significant financial speculation in the securities market. Thus, this meeting falls within the exemption covered by 5 U.S.C. 552b(c)(9)(A).</P>
                <P>Treasury staff will provide a technical briefing to the press on the day before the Committee meeting, following the release of a statement of economic conditions, financing estimates and technical charts. This briefing will give the press an opportunity to ask questions about financing projections and technical charts. The day after the Committee meeting, Treasury will release the minutes of the meeting, any charts that were discussed at the meeting, and the Committee's report to the Secretary.</P>
                <P>The Office of Debt Management is responsible for maintaining records of debt management advisory committee meetings and for providing annual reports setting forth a summary of Committee activities and such other matters as may be informative to the public consistent with the policy of 5 U.S.C. 552(b). The Designated Federal Officer or other responsible agency official who may be contacted for additional information is Karthik Ramahnathan, Director, Office of Debt Management, at (202) 622-2042.</P>
                <SIG>
                    <DATED>Dated: April 6, 2007.</DATED>
                    <NAME>Anthony W. Ryan,</NAME>
                    <TITLE>Assistant Secretary Financial Markets.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 07-1826  Filed 4-12-07; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4810-25-M</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF THE TREASURY </AGENCY>
                <SUBAGY>Internal Revenue Service </SUBAGY>
                <SUBJECT>Proposed Collection; Comment Request for Form 6524 </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Internal Revenue Service (IRS), Treasury. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice and request for comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Department of the Treasury, 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, Pub. L. 104-13 (44 U.S.C. 3506(c)(2)(A)). Currently, the IRS is soliciting comments concerning Form 6524, Office of Chief Counsel—Application. </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Written comments should be received on or before June 12, 2007 to be assured of consideration. </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Direct all written comments to Glenn P. Kirkland, Internal Revenue Service, room 6516, 1111 Constitution Avenue, NW., Washington, DC 20224. </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Requests for additional information or copies of the form and instructions should be directed to Allan Hopkins, at Internal Revenue Service, room 6516, 1111 Constitution Avenue, NW., Washington, DC 20224, or at (202) 622-6665, or through the internet at 
                        <E T="03">Allan.M.Hopkins@irs.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P SOURCE="NPAR">
                    <E T="03">Title:</E>
                     Office of Chief Counsel—Application. 
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1545-0796. 
                </P>
                <P>
                    <E T="03">Form Number:</E>
                     6524. 
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     Form 6524 is used as a screening device to evaluate an applicant's qualifications for employment as an attorney with the Office of Chief Counsel. It provides data deemed critical for evaluating an applicant's qualifications such as Law School Admission Test (LSAT) score, bar admission status, type of work preference, law school, and class standing. 
                </P>
                <P>
                    <E T="03">Current Actions:</E>
                     There are no changes being made to the form at this time. 
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension of a currently approved collection.
                    <PRTPAGE P="18748"/>
                </P>
                <P>
                    <E T="03">Affected Public:</E>
                     Individuals. 
                </P>
                <P>
                    <E T="03">Estimated Number of Respondents:</E>
                     3,000. 
                </P>
                <P>
                    <E T="03">Estimated Time per Respondent:</E>
                     18 minutes. 
                </P>
                <P>
                    <E T="03">Estimated Total Annual Burden Hours:</E>
                     900. 
                </P>
                <P>The following paragraph applies to all of the collections of information covered by this notice: </P>
                <P>An agency may not conduct or sponsor, and a person is not required to respond to, a collection of information unless the collection of information displays a valid OMB control number. Books or records relating to a collection of information must be retained as long as their contents may become material in the administration of any internal revenue law. Generally, tax returns and tax return information are confidential, as required by 26 U.S.C. 6103. </P>
                <P>
                    <E T="03">Request for Comments:</E>
                     Comments submitted in response to this notice will be summarized and/or included in the request for OMB approval. All comments will become a matter of public record. 
                </P>
                <P>
                    <E T="03">Comments are invited on:</E>
                     (a) Whether the 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 collection of information; (c) ways to enhance the quality, utility, and clarity of the information to be collected; (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; and (e) estimates of capital or start-up costs and costs of operation, maintenance, and purchase of services to provide information. 
                </P>
                <SIG>
                    <DATED>Approved: April 2, 2007. </DATED>
                    <NAME>Glenn P. Kirkland, </NAME>
                    <TITLE>IRS Reports Clearance Officer. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. E7-6973 Filed 4-12-07; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4830-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF THE TREASURY </AGENCY>
                <SUBAGY>Internal Revenue Service </SUBAGY>
                <SUBJECT>Proposed Collection; Comment Request for Form 4598 </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Internal Revenue Service (IRS), Treasury. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice and request for comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Department of the Treasury, 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, Pub. L. 104-13 (44 U.S.C. 3506(c)(2)(A)). Currently, the IRS is soliciting comments concerning Form 4598, Form W-2, 1098, or 1099 Not Received, Incorrect or Lost. </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Written comments should be received on or before June 12, 2007 to be assured of consideration. </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Direct all written comments to Glenn P. Kirkland, Internal Revenue Service, room 6516, 1111 Constitution Avenue, NW., Washington, DC 20224. </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Requests for additional information or copies of the form and instructions should be directed to Allan Hopkins, at Internal Revenue Service, room 6516, 1111 Constitution Avenue, NW., Washington, DC 20224, or at (202) 622-6665, or through the internet at 
                        <E T="03">Allan.M.Hopkins@irs.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P SOURCE="NPAR">
                    <E T="03">Title:</E>
                     Form W-2, 1098, or 1099 Not Received, Incorrect or Lost. 
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1545-0597. 
                </P>
                <P>
                    <E T="03">Form Number:</E>
                     4598. 
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     Form 4598 is used to resolve taxpayer inquiries concerning the non-receipt of, incorrect or lost, Forms W-2, 1098 or 1099. Part one of Form 4598 is mailed to the employer or payer for response to the IRS and, if necessary, to the taxpayer. Part two is mailed to the taxpayer advising the taxpayer of the action taken on their behalf. 
                </P>
                <P>
                    <E T="03">Current Actions:</E>
                     There are no changes being made to the form at this time. 
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension of a currently approved collection. 
                </P>
                <P>
                    <E T="03">Affected Public:</E>
                     Individuals, business or other for-profit organizations, farms, and Federal, state, local or tribal governments. 
                </P>
                <P>
                    <E T="03">Estimated Number of Responses:</E>
                     850,000. 
                </P>
                <P>
                    <E T="03">Estimated Time Per Respondent:</E>
                     15 minutes. 
                </P>
                <P>
                    <E T="03">Estimated Total Annual Burden Hours:</E>
                     212,500. 
                </P>
                <P>The following paragraph applies to all of the collections of information covered by this notice: </P>
                <P>An agency may not conduct or sponsor, and a person is not required to respond to, a collection of information unless the collection of information displays a valid OMB control number. </P>
                <P>Books or records relating to a collection of information must be retained as long as their contents may become material in the administration of any internal revenue law. Generally, tax returns and tax return information are confidential, as required by 26 U.S.C. 6103. </P>
                <P>
                    <E T="03">Request for Comments:</E>
                     Comments submitted in response to this notice will be summarized and/or included in the request for OMB approval. All comments will become a matter of public record. 
                </P>
                <P>
                    <E T="03">Comments are invited on:</E>
                     (a) Whether the 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 collection of information; (c) ways to enhance the quality, utility, and clarity of the information to be collected; (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; and (e) estimates of capital or start-up costs and costs of operation, maintenance, and purchase of services to provide information. 
                </P>
                <SIG>
                    <DATED>Approved: April 2, 2007. </DATED>
                    <NAME>Glenn P. Kirkland, </NAME>
                    <TITLE>IRS Reports Clearance Officer. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. E7-6974 Filed 4-12-07; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4830-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF THE TREASURY</AGENCY>
                <SUBAGY>Internal Revenue Service</SUBAGY>
                <SUBJECT>Proposed Collection; Comment Request for Forms 943, 943-PR, 943-A, and 943A-PR</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Internal Revenue Service (IRS), Treasury.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice and request for comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Department of the Treasury, 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, Pub. L. 104-13 (44 U.S.C. 3506(c)(2)(A)). Currently, the IRS is soliciting comments concerning Forms 943, Employer's Annual Tax Return for Agricultural Employees, 943-PR, Planilla Para La Declarcion Anual De La Contribucion Federal Del Patrono De Empleados Agricolas, 943-A, Agricultural Employer's Record of Federal Tax Liability, and 943A-PR, Registro De La Obligacion Contributiva Del Patrono Agricola.</P>
                </SUM>
                <DATES>
                    <PRTPAGE P="18749"/>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Written comments should be received on or before June 12, 2007 to be assured of consideration.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Direct all written comments to Glenn P. Kirkland, Internal Revenue Service, room 6516, 1111 Constitution Avenue, NW., Washington, DC 20224.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Requests for additional information or copies of the forms and instructions should be directed to Allan Hopkins at Internal Revenue Service, room 6516, 1111 Constitution Avenue, NW., Washington, DC 20224, or at (202) 622-6665, or through the internet at 
                        <E T="03">Allan.M.Hopkins@irs.gov</E>
                        .
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P SOURCE="NPAR">
                    <E T="03">Title:</E>
                     Employer's Annual Tax Return for Agricultural Employees (Form 943), Planilla Para La Declarcion Anual De La Contribucion Federal Del Patrono De Empleados Agricolas (Form 943-PR), Agricultural Employer's Record of Federal Tax Liability (Form 943-A), and Registro De La Obligacion Contributiva Del Patrono Agricola (Form 943A-PR).
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1545-0035.
                </P>
                <P>
                    <E T="03">Form Numbers:</E>
                     943, 943-PR, 943-A, and 943A-PR.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     Agricultural employers must prepare and file Form 943 and Form 943-PR (Puerto Rico only) to report and pay FICA taxes and income tax voluntarily withheld (Form 943 only). Agricultural employees may attach Forms 943-A and 943A-PR to Forms 943 and 943-PR to show their tax liabilities for semiweekly periods. The information is used to verify that the correct tax has been paid.
                </P>
                <P>
                    <E T="03">Current Actions:</E>
                     There are no changes being made to the forms at this time.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension of a currently approved collection.
                </P>
                <P>
                    <E T="03">Affected Public:</E>
                     Business or other for-profit organizations.
                </P>
                <P>
                    <E T="03">Estimated Number of Respondents:</E>
                     684,444.
                </P>
                <P>
                    <E T="03">Estimated Time Per Respondent:</E>
                     10 hr., 29 min.
                </P>
                <P>
                    <E T="03">Estimated Total Annual Burden Hours:</E>
                     8,972,974.
                </P>
                <P>The following paragraph applies to all of the collections of information covered by this notice:</P>
                <P>An agency may not conduct or sponsor, and a person is not required to respond to, a collection of information unless the collection of information displays a valid OMB control number.</P>
                <P>Books or records relating to a collection of information must be retained as long as their contents may become material in the administration of any internal revenue law. Generally, tax returns and tax return information are confidential, as required by 26 U.S.C. 6103.</P>
                <P>
                    <E T="03">Request for Comments:</E>
                     Comments submitted in response to this notice will be summarized and/or included in the request for OMB approval. All comments will become a matter of public record.
                </P>
                <P>
                    <E T="03">Comments are invited on:</E>
                     (a) Whether the 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 collection of information; (c) ways to enhance the quality, utility, and clarity of the information to be collected; (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; and (e) estimates of capital or start-up costs and costs of operation, maintenance, and purchase of services to provide information.
                </P>
                <SIG>
                    <DATED>Approved: April 6, 2007.</DATED>
                    <NAME>Glenn P. Kirkland,</NAME>
                    <TITLE>IRS Reports Clearance Officer.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. E7-6975 Filed 4-12-07; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4830-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF THE TREASURY </AGENCY>
                <SUBAGY>Internal Revenue Service </SUBAGY>
                <SUBJECT>Proposed Collection; Comment Request for Form 8916 </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Internal Revenue Service (IRS), Treasury. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice and request for comments. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Department of the Treasury, 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)). Currently, the IRS is soliciting comments concerning Form 8916, Reconciliation of Schedule M-3 Taxable Income with Tax Return Taxable Income for Mixed Groups. </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Written comments should be received on or before June 12, 2007 to be assured of consideration. </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Direct all written comments to Glenn Kirkland, Internal Revenue Service, room 6516, 1111 Constitution Avenue, NW., Washington, DC 20224. </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Requests for additional information or copies of the form and instructions should be directed to Allan Hopkins, at (202) 622-6665, or at Internal Revenue Service, room 6516, 1111 Constitution Avenue, NW., Washington, DC 20224, or through the Internet, at 
                        <E T="03">Allan.M.Hopkins@irs.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P SOURCE="NPAR">
                    <E T="03">Title:</E>
                     Reconciliation of Schedule M-3 Taxable Income with Tax Return Taxable Income for Mixed Groups. 
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1545-2062. 
                </P>
                <P>
                    <E T="03">Form Number:</E>
                     Form 8916. 
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     Form 8916 reconciles taxable income per the Schedule M-3 for the Forms 1120, 1120-L, or 1120-PC with the taxable income on mixed groups filing Form 1120, 1120-L, or 1120-PC. This is necessary because certain special adjustments are required to match taxable income of mixed groups as reported on the Schedule M-3 with taxable income they report on Forms 1120, 1120-L, for 1120-PC. 
                </P>
                <P>
                    <E T="03">Current Actions:</E>
                     There are no changes being made to Form 8689 at this time. 
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension of a currently approved collection. 
                </P>
                <P>
                    <E T="03">Affected Public:</E>
                     Business or other for-profit institutions. 
                </P>
                <P>
                    <E T="03">Estimated Number of Respondents:</E>
                     500. 
                </P>
                <P>
                    <E T="03">Estimated Time per Respondent:</E>
                     6 Hours, 46 minutes. 
                </P>
                <P>
                    <E T="03">Estimated Total Annual Burden Hours:</E>
                     3,385. 
                </P>
                <P>The following paragraph applies to all of the collections of information covered by this notice: </P>
                <P>An agency may not conduct or sponsor, and a person is not required to respond to, a collection of information unless the collection of information displays a valid OMB control number. Books or records relating to a collection of information must be retained as long as their contents may become material in the administration of any internal revenue law. Generally, tax returns and tax return information are confidential, as required by 26 U.S.C. 6103. </P>
                <P>
                    <E T="03">Request for Comments</E>
                    : Comments submitted in response to this notice will be summarized and/or included in the request for OMB approval. All comments will become a matter of public record. 
                </P>
                <P>
                    <E T="03">Comments are invited on:</E>
                     (a) Whether the 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 collection of information; (c) ways to enhance the quality, utility, and clarity of the information to be collected; (d) ways to minimize the burden of the 
                    <PRTPAGE P="18750"/>
                    collection of information on respondents, including through the use of automated collection techniques or other forms of information technology; and (e) estimates of capital or start-up costs and costs of operation, maintenance, and purchase of services to provide information. 
                </P>
                <SIG>
                    <DATED>Approved: April 2, 2007. </DATED>
                    <NAME>Glenn Kirkland, </NAME>
                    <TITLE>IRS Reports Clearance Officer. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC> [FR Doc. E7-6976 Filed 4-12-07; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4830-01-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF THE TREASURY</AGENCY>
                <SUBAGY>Internal Revenue Service</SUBAGY>
                <DEPDOC>[LR 2013 and EE-155-78]</DEPDOC>
                <SUBJECT>Proposed Collection; Comment Request for Regulation Project</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Internal Revenue Service (IRS), Treasury.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice and request for comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Department of the Treasury, 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)). Currently, the IRS is soliciting comments concerning existing final regulations, LR 2013 (TD 7533), Disc Rules on Procedure and Administration; Rules on Export Trade Corporations, and EE-155-78 (TD 7896), Income From Trade Shows (§§ 1.6071-1 and 1.6072-2).</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Written comments should be received on or before June 12, 2007 to be assured of consideration.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Direct all written comments to Glenn P. Kirkland, Internal Revenue Service, room 6516, 1111 Constitution Avenue NW., Washington, DC 20224.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Requests for additional information or copies of the regulations should be directed to Allan Hopkins, at Internal Revenue Service, room 6516, 1111 Constitution Avenue, NW., Washington, DC 20224, or at (202) 622-6665, or through the Internet at 
                        <E T="03">Allan.M.Hopkins@irs.gov</E>
                        .
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P SOURCE="NPAR">
                    <E T="03">Title:</E>
                     LR 2013 (TD 7533), Disc Rules on Procedure and Administration; Rules on Export Trade Corporations, and EE-155-78 (TD 7896), Income From Trade Shows.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1545-0807.
                </P>
                <P>
                    <E T="03">Regulation Project Numbers:</E>
                     LR 2013 and EE-155-78.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     Regulation section 1.6071-1(b) requires that when a taxpayer files a late return for a short period, proof of unusual circumstances for late filing must be given to the District Director. Sections 6072(b), (c), (d), and (e) of the Internal Revenue Code deal with the filing dates of certain corporate returns. Regulation section 1.6072-2 provides additional information concerning these filing dates.
                </P>
                <P>
                    <E T="03">Current Actions:</E>
                     There is no change to these existing regulations.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension of OMB approval.
                </P>
                <P>
                    <E T="03">Affected Public:</E>
                     Individual or households, business or other for-profit organizations, not-for-profit institutions, farms, and state, local or tribal governments.
                </P>
                <P>
                    <E T="03">Estimated Number of Respondents:</E>
                     12,417.
                </P>
                <P>
                    <E T="03">Estimated Time per Respondent:</E>
                     15 minutes.
                </P>
                <P>
                    <E T="03">Estimated Total Annual Burden Hours:</E>
                     3,104.
                </P>
                <P>The following paragraph applies to all of the collections of information covered by this notice:</P>
                <P>An agency may not conduct or sponsor, and a person is not required to respond to, a collection of information unless the collection of information displays a valid OMB control number. Books or records relating to a collection of information must be retained as long as their contents may become material in the administration of any internal revenue law. Generally, tax returns and tax return information are confidential, as required by 26 U.S.C. 6103.</P>
                <P>
                    <E T="03">Request for Comments:</E>
                     Comments submitted in response to this notice will be summarized and/or included in the request for OMB approval. All comments will become a matter of public record.
                </P>
                <P>
                    <E T="03">Comments are invited on:</E>
                     (a) Whether the 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 collection of information; (c) ways to enhance the quality, utility, and clarity of the information to be collected; (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; and (e) estimates of capital or start-up costs and costs of operation, maintenance, and purchase of services to provide information.
                </P>
                <SIG>
                    <DATED>Approved: April 2, 2007.</DATED>
                    <NAME>Glenn P. Kirkland,</NAME>
                    <TITLE>IRS Reports Clearance Officer.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. E7-6977 Filed 4-12-07; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4830-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF THE TREASURY</AGENCY>
                <SUBAGY>Internal Revenue Service</SUBAGY>
                <SUBJECT>Internal Revenue Service Advisory Council (IRSAC); Nominations</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Internal Revenue Service, Department of Treasury.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Request for nominations.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Internal Revenue Service (IRS) requests nominations of individuals to be considered for selection as Internal Revenue Service Advisory Council (IRSAC) members. Interested parties may nominate themselves and/or one other qualified person for membership. Nominations will be accepted for current vacancies and should describe and document the applicants qualifications for membership. IRSAC is comprised of twenty-seven (27) members; approximately one-third of these appointments will expire in December 2007. It is important that the IRSAC continue to represent a diverse taxpayer and stakeholder base. Accordingly, to maintain membership diversity, selection is based on the applicant's qualifications as well as the segment or group that he/she represents.</P>
                    <P>The Internal Revenue Service Advisory Council (IRSAC) provides an organized public forum for IRS officials and representatives of the public to discuss relevant tax administration issues. The council advises the IRS on issues that have a substantive effect on federal tax administration. As an advisory body designed to focus on broad policy matters, the IRSAC reviews existing tax policy and/or recommends policies with respect to emerging tax administration issues. The IRSAC suggests operational improvements, offers constructive observations regarding current or proposed IRS policies, programs, and procedures, and advises the IRS with respect to issues having substantive effect on federal tax administration.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Written nominations must be received on or before June 15, 2007.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Nominations should be sent to Ms. Jacqueline Tilghman, National Public Liaison, CL:NPL:P, Room 7559 IR, 1111 Constitution Avenue, NW., Washington, DC 20224, Attn: IRSAC Nominations; or by e-mail: 
                        <E T="03">*public_liaison@irs.gov</E>
                        . Applications 
                        <PRTPAGE P="18751"/>
                        may be submitted by mail to the address above or faxed to 202-927-5253. Application packages are available on the Tax Professional's Page, which is located on the IRS Internet Web site at 
                        <E T="03">http://www.irs.gov/taxpros/index.html</E>
                        .
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Ms. Jacqueline Tilghman,</P>
                    <P>202-622-6440 (not a toll-free number).</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>IRSAC was authorized under the Federal Advisory Committee Act, Public Law No. 92-463., the first Advisory Group to the Commissioner of Internal Revenue—or the Commissioner's Advisory Group (“CAG”)—was established in 1953 as a “national policy and/or issue advisory committee.” Renamed in 1998, the Internal Revenue Service Advisory Council (IRSAC) reflects the agency-wide scope of its focus as an advisory body to the entire agency. The IRSAC's primary purpose is to provide an organized public forum for senior IRS executives and representatives of the public to discuss relevant tax administration issues.</P>
                <P>Conveying the public's perception of IRS activities, the IRSAC is comprised of individuals who bring substantial, disparate experience and diverse backgrounds on the Council's activities. Membership is balanced to include representation from the taxpaying public, the tax professional community, small and large businesses, state tax administration, and the payroll community.</P>
                <P>IRSAC members are appointed by the Commissioner of the Internal Revenue Service and serve a term of three years. There are three subcommittees that mirror three of the Operating Divisions (Small Business/Self Employed (SB/SE); Large Mid-Size Business (LMSB); and Wage &amp; Investment (W&amp;I); Tax Exempt and Government Entities (TEGE) has its own advisory committee. Due to the increased concerns regarding the tax gap, IRSAC has formed a fourth subcommittee on tax gap analysis used to measure voluntary compliance.</P>
                <P>Members are not paid for their services. However, travel expenses for working sessions, public meetings and orientation sessions, such as airfare, per diem, and transportation to and from airports, train stations, etc., are reimbursed within prescribed federal travel limitations.</P>
                <P>Receipt of nominations will be acknowledged, nominated individuals contacted, and immediately thereafter, biographical information must be completed and returned to Ms. Jacqueline Tilghman in National Public Liaison within fifteen (15) days of receipt. In accordance with Department of Treasury Directive 21-03, a clearance process including, fingerprints, annual tax checks, a Federal Bureau of Investigation criminal and subversive name check, and a practitioner check with the Office of Professional Responsibility will be conducted.</P>
                <P>Equal opportunity practices will be followed for all appointments to the IRSAC in accordance with the Department of Treasury and IRS policies. To ensure that the recommendations of the IRSAC have taken into account the needs of the diverse groups served by the IRS, membership shall include individuals who demonstrate the ability to represent minorities, women, and persons with disabilities.</P>
                <SIG>
                    <DATED>Dated; March 30, 2007.</DATED>
                    <NAME>Candice Cromling,</NAME>
                    <TITLE>Director, National Public Liaison.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. E7-6978 Filed 4-12-07; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4830-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF THE TREASURY </AGENCY>
                <SUBAGY>Internal Revenue Service </SUBAGY>
                <SUBJECT>Open Meeting of the Area 4 Committee of the Taxpayer Advocacy Panel (Including the States of Illinois, Indiana, Kentucky, Michigan, Ohio, Tennessee, and Wisconsin) </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Internal Revenue Service (IRS), Treasury. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>An open meeting of the Area 4 Committee of the Taxpayer Advocacy Panel will be conducted (via teleconference). The Taxpayer Advocacy Panel is soliciting public comment, ideas, and suggestions on improving customer service at the Internal Revenue Service. </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The meeting will be held Tuesday, May 15, 2007, at 10 a.m., Central Time. </P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Mary Ann Delzer at 1-888-912-1227, or (414) 231-2360. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    Notice is hereby given pursuant to Section 10(a)(2) of the Federal Advisory Committee Act, 5 U.S.C. App. (1988) that a meeting of the Area 4 Committee of the Taxpayer Advocacy Panel will be held Tuesday, May 15, 2007, at 10 a.m., Central Time via a telephone conference call. You can submit written comments to the Panel by faxing the comments to (414) 231-2363, or by mail to Taxpayer Advocacy Panel, Stop 1006MIL, P.O. Box 3205, Milwaukee, WI 53201-3205, or you can contact us at 
                    <E T="03">www.improveirs.org.</E>
                     This meeting is not required to be open to the public, but because we are always interested in community input we will accept public comments. Please contact Mary Ann Delzer at 1-888-912-1227 or (414) 231-2360 for dial-in information. 
                </P>
                <P>
                    <E T="03">The agenda will include the following:</E>
                     Various IRS issues. 
                </P>
                <SIG>
                    <DATED>Dated: April 6, 2007. </DATED>
                    <NAME>John Fay, </NAME>
                    <TITLE>Acting Director, Taxpayer Advocacy Panel.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC> [FR Doc. E7-6967 Filed 4-12-07; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4830-01-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF THE TREASURY </AGENCY>
                <SUBAGY>Internal Revenue Service </SUBAGY>
                <SUBJECT>Open Meeting of the Joint Committee of the Taxpayer Advocacy Panel </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Internal Revenue Service (IRS), Treasury. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>An open meeting of the Joint Committee of the Taxpayer Advocacy Panel will be conducted via teleconference. The Taxpayer Advocacy Panel is soliciting public comment, ideas, and suggestions on improving customer service at the Internal Revenue Service. </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The meeting will be held Wednesday, May 2, 2007, at 1 p.m., Eastern Time. </P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Barbara Toy at 1-888-912-1227, or (414) 231-2360. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>Notice is hereby given pursuant to Section 10(a)(2) of the Federal Advisory Committee Act, 5 U.S.C. App. (1988) that an open meeting of the Joint Committee of the Taxpayer Advocacy Panel (TAP) will be held Wednesday, May 2, 2007, at 1 p.m. Eastern Time via a telephone conference call. If you would like to have the Joint Committee of TAP consider a written statement, please call 1-888-912-1227 or (414) 231-2360, or write Barbara Toy, TAP Office, MS-1006-MIL, P.O. Box 3205, Milwaukee, WI 53201-2105, or Fax to (414) 231-2363, or you can contact us at www.improveirs.org. Due to limited conference lines, notification of intent to participate in the telephone conference call meeting must be made with Barbara Toy. </P>
                <P>
                    <E T="03">The agenda will include the following:</E>
                     discussion of issues and responses brought to the Joint Committee, office report, and discussion of next meeting. 
                </P>
                <SIG>
                    <PRTPAGE P="18752"/>
                    <DATED>Dated: April 6, 2007. </DATED>
                    <NAME>John Fay, </NAME>
                    <TITLE>Acting Director Taxpayer Advocacy Panel.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC> [FR Doc. E7-6968 Filed 4-12-07; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4830-01-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF THE TREASURY</AGENCY>
                <SUBAGY>Internal Revenue Service</SUBAGY>
                <SUBJECT>Open Meeting of the Taxpayer Advocacy Panel Volunteer Income Tax Assistance (VITA) Issue Committee</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Internal Revenue Service (IRS), Treasury.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of meeting.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>An open meeting of the Taxpayer Advocacy Panel VITA Issue Committee will be conducted. The Taxpayer Advocacy Panel is soliciting public comment, ideas, and suggestions on improving customer service at the Internal Revenue Service.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The meeting will be held Tuesday, May 1, 2007, at Noon Eastern Time.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Barbara Toy at 1-888-912-1227, or (414) 231-2360.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    Notice is hereby given pursuant to Section 10(a)(2) of the Federal Advisory Committee Act, 5 U.S.C. App. (1988) that a meeting of the Taxpayer Advocacy Panel VITA Issue Committee will be held Tuesday, May 1, 2007, at Noon, Eastern Time via a telephone conference call. Public comments will be welcome during the meeting. You can submit written comments to the Panel by faxing to (414) 231-2363, or by mail to Taxpayer Advocacy Panel, Stop 1006MIL, P.O. Box 3205, Milwaukee, WI 53201-3205, or you can contact us at 
                    <E T="03">www.improveirs.org.</E>
                     Please contact Barbara Toy at 1-888-912-1227 or (414) 231-2360 for additional information.
                </P>
                <P>
                    <E T="03">The agenda will include the following:</E>
                     Various VITA Issues.
                </P>
                <SIG>
                    <DATED>Dated: April 6, 2007.</DATED>
                    <NAME>John Fay,</NAME>
                    <TITLE>Acting Director Taxpayer Advocacy Panel.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. E7-6969 Filed 4-12-07; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4830-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF THE TREASURY </AGENCY>
                <SUBAGY>Internal Revenue Service </SUBAGY>
                <SUBJECT>Open Meeting of the Area 5 Committee of the Taxpayer Advocacy Panel (Including the States of Iowa, Kansas, Minnesota, Missouri, Nebraska, Oklahoma, and Texas) </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Internal Revenue Service (IRS), Treasury. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of meeting.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>An open meeting of the Area 5 Committee of the Taxpayer Advocacy Panel will be conducted. The Taxpayer Advocacy Panel is soliciting public comment, ideas, and suggestions on improving customer service at the Internal Revenue Service. </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The meeting will be held Sunday, May 6, 2007, 3 p.m. to 6 p.m., and Monday, May 7, 2007, 9 a.m. to 4 p.m. Central Time. </P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Mary Ann Delzer at 1-888-912-1227, or (414) 231-2360. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    Notice is hereby given pursuant to Section 10(a)(2) of the Federal Advisory Committee Act, 5 U.S.C. App. (1988) that a meeting of the Area 5 Committee of the Taxpayer Advocacy Panel will be held Sunday, May 6, 2007, 3 p.m. to 6 p.m., and Monday, May 7, 2007, 9 a.m. to 4 p.m. Central Time, at the Westin Hotel, 1 East Pershing Road, Kansas City, MO 64108. You can submit written comments to the Panel by faxing the comments to (414) 231-2363, or by mail to Taxpayer Advocacy Panel, Stop 1006MIL, P.O. Box 3205, Milwaukee, WI 53201-3205, or you can contact us at 
                    <E T="03">www.improveirs.org.</E>
                     Please contact Mary Ann Delzer at 1-888-912-1227 or (414) 231-2360 for more information. 
                </P>
                <P>
                    <E T="03">The agenda will include the following:</E>
                     Various IRS issues. 
                </P>
                <SIG>
                    <DATED>Dated: April 6, 2007. </DATED>
                    <NAME>John Fay, </NAME>
                    <TITLE>Acting Director Taxpayer Advocacy Panel.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. E7-6971 Filed 4-12-07; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4830-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF THE TREASURY </AGENCY>
                <SUBAGY>Internal Revenue Service </SUBAGY>
                <SUBJECT>Open Meeting of the Area 1 Taxpayer Advocacy Panel (Including the States of New York, Connecticut, Massachusetts, Rhode Island, New Hampshire, Vermont and Maine) </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Internal Revenue Service (IRS), Treasury. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>An open meeting of the Area 1 Taxpayer Advocacy Panel will be conducted at The University of Connecticut, Stamford Campus located at One University Place, Stamford, Connecticut 06901-2315. The Taxpayer Advocacy Panel is soliciting public comments, ideas and suggestions on improving customer service at the Internal Revenue Service. </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The meeting will be held on Friday, May 11, 2007 and Saturday, May 12, 2007. </P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Audrey Y. Jenkins at 1-888-912-1227 (toll-free), or 718-488-2085 (non toll-free). </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    An open meeting of the Area 1 Taxpayer Advocacy Panel will be held Thursday, May 11, 2007 from 9 a.m. to 12 p.m. ET in room 131 and Saturday, May 12, 2007 from 9 a.m. to 10 a.m. ET in room 132 at The University of Connecticut, Stamford Campus located at One University Place, Stamford Connecticut, 06901-2315. Individual comments will be limited to 5 minutes. If you would like to have the TAP consider a written statement, please call 1-888-912-1227 or 718-488-2085, or write Audrey Y. Jenkins, TAP Office, 10 MetroTech Center, 625 Fulton Street, Brooklyn, NY 11201. Due to limited time, notification of intent to participate in the meeting must be made with Audrey Y. Jenkins. Ms. Jenkins can be reached at 1-888-912-1227 or 718-488-2085, or post comments to the Web site: 
                    <E T="03">http://www.improveirs.org.</E>
                </P>
                <P>The agenda will include various IRS issues. </P>
                <SIG>
                    <DATED>Dated: April 6, 2007. </DATED>
                    <NAME>John Fay, </NAME>
                    <TITLE>Acting Director Taxpayer Advocacy Panel.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. E7-6972 Filed 4-12-07; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4830-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF VETERANS AFFAIRS </AGENCY>
                <SUBJECT>Privacy Act of 1974; System of Records </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Department of Veterans Affairs (VA). </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of publication of new system of records. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The Privacy Act of 1974 (Title 5, United States Code (U.S.C.), Section 552 requires that all agencies publish in the 
                        <E T="04">Federal Register</E>
                         a notice of the existence of and character of their systems of records. Notice is hereby given that the Department of Veterans Affairs (VA) is adding a new system of 
                        <PRTPAGE P="18753"/>
                        records entitled “Non-Health Data Analyses and Projections for VA Policy and Planning—VA” (149VA008A). 
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments on the amendment of this system of records must be received no later than May 14, 2007. If no public comment is received, the new system will become effective May 14, 2007. </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Written comments may be submitted through 
                        <E T="03">http://www.Regulations.gov</E>
                        ; by mail or hand-delivery to the Director, Regulations Management (00REG), Department of Veterans Affairs, 810 Vermont Ave., NW., Room 1068, Washington, DC 20420; or by fax to (202) 273-9026. Copies of comments received will be available for public inspection in the Office of Regulation Policy and Management, Room 1063B, between the hours of 8 a.m. and 4:30 p.m. Monday through Friday (except holidays). Please call (202) 273-9515 for an appointment. In addition, during the comment period, comments may be viewed online through the Federal Docket Management System. 
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Dat Tran, Director, Office of Data Development and Analysis, (008A3), U.S. Department of Veterans Affairs, 810 Vermont Ave., NW., Washington, DC 20420, (202) 273-6482. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <HD SOURCE="HD1">I. Description of the Proposed System of Records </HD>
                <P>
                    The “Non-Health Data Analyses and Projections for VA Policy and Planning” system of records is a collection of non-health-related database extracts utilized by the Department of Veterans Affairs' Office of Policy and Planning (OPP) to perform its statutory mission under title 38, U.S.C. 527. OPP supports VA's Office of the Secretary, Administrations, and staff offices through qualitative, quantitative, and actuarial analyses, projections, and evaluations regarding all non-health-related benefits issues involving service members, veterans, survivors, and dependents. A more complete description of the duties and activities of Office of Policy and Planning (OPP) is at 
                    <E T="03">http://www1.va.gov/op3/docs/008_org.pdf</E>
                    . 
                </P>
                <P>The extracts are provided from master databases under the jurisdiction of the Veterans Benefits Administration, Department of Defense (DoD), and other Federal and State agencies. This system of records will not contain protected health information covered by the HIPAA Privacy and Security Rules. </P>
                <P>
                    These data extracts contain personal identifiers (
                    <E T="03">e.g.</E>
                    , social security numbers and military service numbers etc.), residential and professional contact data (
                    <E T="03">e.g.</E>
                    , address and telephone numbers etc.), population demographics (
                    <E T="03">e.g.</E>
                    , gender and zip codes etc.), military service-related data (
                    <E T="03">e.g.</E>
                    , branch of service and service dates etc.), financial-related data (
                    <E T="03">e.g.</E>
                    , amount of historic benefit payments etc.), claims processing codes and information (
                    <E T="03">e.g.</E>
                    , disability compensation and pension award codes etc.), and other VA and non-VA Federal information. 
                </P>
                <P>The information is retrievable by social security number, military service number, claim or file number, non-VA Federal benefit identifiers, and other personal identifiers. Consequently, a Privacy Act system of records must be established in order to protect this information. </P>
                <HD SOURCE="HD1">II. Proposed Routine Use of Disclosures of Data in the System </HD>
                <P>VA is proposing to establish the following routine use disclosures of the information that will be maintained in the system. </P>
                <P>1. Upon suspicion or confirmation of compromised data in this system of records, OPP may disclose any system records to law enforcement and security entities, as necessary, for the investigations of any data security, identity theft, and fraud issues. </P>
                <P>2. Disclosure may be made to a Member of Congress or to a Congressional staff member in response to an inquiry of the Congressional office made at the written request of the constituent about whom the record is maintained. </P>
                <P>3. Any system records disclosure may be made to the National Archives and Records Administration in records management inspections under title 44, U.S.C. </P>
                <P>4. Any information in this system may be disclosed to the Department of Justice (DOJ), including United States (U.S.) Attorneys, upon its official request in order for VA to respond to pleadings, interrogatories, orders or inquiries from DOJ and to supply DOJ with information to enable DOJ to represent the U.S. Government in any phase of litigation or in any case or controversy involving VA. </P>
                <P>5. Any system records may be disclosed to a Federal agency for the conduct of research and data analysis to perform a statutory purpose of that Federal agency upon the prior written request of that agency, provided that there is legal authority under all applicable confidentiality statutes and regulations to provide the data and OPP has determined prior to the disclosure that OPP data handling requirements are satisfied. OPP may disclose limited individual identification information to another Federal agency for the purpose of matching and acquiring information held by that agency for OPP to use for the purposes stated for this system of records. </P>
                <P>6. Any system records may be disclosed to individuals, organizations, private or public agencies, or other entities or individuals with whom VA has a contract or agreement to perform such services as VA may deem practicable for the purposes of laws administered by VA, in order for the contractor, subcontractor, public or private agency, or other entity or individual with whom VA has an agreement or contract to perform the services of the contract or agreement. This routine use includes disclosures by the individual or entity performing the service for VA to any secondary entity or individual to perform an activity that is necessary for individuals, organizations, private or public agencies, or other entities or individuals with whom VA has a contract or agreement to provide the service to VA. </P>
                <P>7. Any system records disclosure may be made to the Office of Management and Budget (OMB) in order for them to perform their statutory responsibilities for evaluating federal programs. </P>
                <P>8. Upon receipt of a written request, VA may disclose information to any state, tribe, county, or municipal agency for the purposes of outreach to a benefit under Title 38 Code of Federal Regulations (CFR). </P>
                <P>9. Any records may be disclosed to appropriate agencies, entities, and persons under the following circumstances: When (1) It is suspected or confirmed that the security or confidentiality of information in the system of records has been compromised; (2) the Department has determined that as a result of the suspected or confirmed compromise there is a risk of embarrassment or harm to the reputations of the record subjects, harm to economic or property interests, identity theft or fraud, or harm to the security or integrity of this system or other systems or programs (whether maintained by the Department or another agency or entity) that rely upon the compromised information; and (3) the disclosure is made to such agencies, entities, and persons who are reasonably necessary to assist in connection with the Department's efforts to respond to the suspected or confirmed compromise and prevent, minimize, or remedy such harm. </P>
                <P>
                    10. VA may disclose information in this system of records to the Department of Justice (DoJ), either on VA's initiative or in response to DoJ's request for the information, after either VA or DoJ 
                    <PRTPAGE P="18754"/>
                    determines that such information is relevant to DoJ's representation of the United States or any of its components in legal proceedings before a court or adjudicative body, provided that, in each case, the agency also determines prior to disclosure that disclosure of the records to the Department of Justice is a use of the information contained in the records that is compatible with the purpose for which VA collected the records. VA, on its own initiative, may disclose records in this system of records in legal proceedings before a court or administrative body after determining that the disclosure of the records to the court or administrative body is a use of the information contained in the records that is compatible with the purpose for which VA collected the records. 
                </P>
                <P>
                    In determining whether to disclose records under this routine use, VA will comply with the guidance promulgated by the Office of Management and Budget in a May 24, 1985, memorandum entitled “Privacy Act Guidance—Update”, currently posted at 
                    <E T="03">http://www.whitehouse.gov/omb/inforeg/guidance1985.pdf.</E>
                </P>
                <P>11. VA may disclose on its own initiative any information in this system, except the names and home addresses of veterans and their dependents, which is relevant to a suspected or reasonably imminent violation of law, whether civil, criminal or regulatory in nature, and whether arising by general or program statute or by regulation, rule or order issued pursuant thereto, to a Federal, State, local, tribal, or foreign agency charged with the responsibility of investigating or prosecuting such violation, or charged with enforcing or implementing the statute, regulation, rule or order. On its own initiative, VA may also disclose the names and addresses of veterans and their dependents to a Federal agency charged with the responsibility of investigating or prosecuting civil, criminal or regulatory violations of law, or charged with enforcing or implementing the statute, regulation, rule or order issued pursuant thereto. </P>
                <HD SOURCE="HD1">III. Compatibility of the Proposed Routine Uses </HD>
                <P>The Privacy Act permits VA to disclose information about individuals without their consent for a routine use when the information will be used for a purpose that is compatible with the purpose for which we collected the information. In all of the routine use disclosures, either the recipient of the information will use the information in connection with a matter relating to one of VA's programs, or will use the information to provide a benefit to VA, or disclosure is required by law. </P>
                <P>The “notice of intent to publish” and an advance copy of the system notice have been sent to the appropriate Congressional committees and the OMB's Director as required by title 5, U.S.C. a(r) (Privacy Act) and guidelines issued by OMB on December 12, 2000 (65FR77677). </P>
                <SIG>
                    <DATED>Approved: March 29, 2007. </DATED>
                    <NAME>Gordon H. Mansfield, </NAME>
                    <TITLE>Deputy Secretary of Veterans Affairs.</TITLE>
                </SIG>
                <PRIACT>
                    <HD SOURCE="HD1">149VA008A </HD>
                    <HD SOURCE="HD2">SYSTEM NAME: </HD>
                    <P>“Non-Health Data Analyses and Projections for VA Policy and Planning—VA”. </P>
                    <HD SOURCE="HD2">SYSTEM LOCATION:</HD>
                    <P>One location for electronic and paper records, following VA-approved procedures, is in the Office of the Director, Office of Data Development and Analysis, (008A3), U.S. Department of Veterans Affairs, 810 Vermont Ave., NW., Washington, DC 20420. Electronic records are also placed on a Department of Veterans Affairs' (VA's) secured server housed at VA's Austin Automation Center, 1615 Woodward St., Austin, TX 78772. Records necessary for a contractor to perform a contract with VA are located at the respective contractor's facility. </P>
                    <HD SOURCE="HD2">CATEGORIES OF INDIVIDUALS COVERED BY THE SYSTEM:</HD>
                    <P>1. Service members and veterans who have applied for any non-health-related benefits under title 38, U.S.C. </P>
                    <P>2. Veterans' spouse, surviving spouse, previous spouse, children, and parents who have applied for any non-health-related benefit under title 38, U.S.C. </P>
                    <P>3. Beneficiaries of other Federal agencies or other governmental entities. </P>
                    <P>4. Individuals who have applied for any non-health-related benefits under title 38, U.S.C., but who do not meet the requirements under Title 38 to receive such benefits. </P>
                    <HD SOURCE="HD2">CATEGORIES OF RECORDS IN THE SYSTEM:</HD>
                    <P>
                        The records may include personal identifiers (
                        <E T="03">e.g.</E>
                        , social security numbers and military service numbers etc.), residential and professional contact data (
                        <E T="03">e.g.</E>
                        , address and telephone numbers etc.), population demographics (
                        <E T="03">e.g.</E>
                        , gender and zip codes etc.), military service-related data (
                        <E T="03">e.g.</E>
                        , branch of service and service dates etc.), financial-related data (
                        <E T="03">e.g.</E>
                        , amount of historic benefit payments etc.), claims processing codes and information (
                        <E T="03">e.g.</E>
                        , disability compensation and pension award codes etc.), and other VA and non-VA Federal information. 
                    </P>
                    <HD SOURCE="HD2">AUTHORITY FOR MAINTENANCE OF THE SYSTEM:</HD>
                    <P>Title 38, U.S.C. 527. </P>
                    <HD SOURCE="HD2">PURPOSE(S):</HD>
                    <P>
                        Non-health-related qualitative, quantitative, and actuarial analyses and projections to support policy analyses and recommendations to improve VA services for veterans and their families. Analysis and review of policy and long-term planning issues affecting veterans programs to support legislative, regulatory and policy recommendations, decisions and initiatives. These activities are conducted for the Secretary, VA Administrations and Staff Offices, special programs and projects within the Department (
                        <E T="03">e.g.</E>
                        , special studies, advisory committees and task forces etc.), and entities external to VA, such as the Office of Management and Budget (OMB), and the United States (U.S.) Congress. 
                    </P>
                    <HD SOURCE="HD2">ROUTINE USES OF RECORDS MAINTAINED IN THE SYSTEM, INCLUDING CATEGORIES OF USERS AND THE PURPOSES OF SUCH USES: </HD>
                    <NOTE>
                        <HD SOURCE="HED">Note:</HD>
                        <P>To the extent that records contained in the system include individually-identifiable information protected by title 38, U.S.C. 7332, that information cannot be disclosed under any of the following routine uses unless there is also specific disclosure authority in title 38, U.S.C. 7332. </P>
                    </NOTE>
                    <P>1. Upon suspicion or confirmation of compromised data in this system of records, Office of Policy and Planning (OPP) may disclose any system records to law enforcement and security entities, as necessary, for the investigations of any data security, identity theft, and fraud issues. </P>
                    <P>2. Disclosure may be made to a Member of Congress or to a Congressional staff member in response to an inquiry of the Congressional office made at the written request of the constituent about whom the record is maintained. </P>
                    <P>3. Any system records disclosure may be made to the National Archives and </P>
                    <P>Records Administration in records management inspections under title 44, U.S.C. </P>
                    <P>4. Any information in this system may be disclosed to the Department of Justice (DOJ), including U.S. Attorneys, upon its official request in order for VA to respond to pleadings, interrogatories, orders or inquiries from DOJ and to supply DOJ with information to enable DOJ to represent the U.S. Government in any phase of litigation or in any case or controversy involving VA. </P>
                    <P>
                        5. Any system records may be disclosed to a Federal agency for the 
                        <PRTPAGE P="18755"/>
                        conduct of research and data analysis to perform a statutory purpose of that Federal agency upon the prior written request of that agency, provided that there is legal authority under all applicable confidentiality statutes and regulations to provide the data and OPP has determined prior to the disclosure that OPP data handling requirements are satisfied. OPP may disclose limited individual identification information to another Federal agency for the purpose of matching and acquiring information held by that agency for OPP to use for the purposes stated for this system of records. 
                    </P>
                    <P>6. Any system records may be disclosed to individuals, organizations, private or public agencies, or other entities or individuals with whom VA has a contract or agreement to perform such services as VA may deem practicable for the purposes of laws administered by VA, in order for the contractor, subcontractor, public or private agency, or other entity or individual with whom VA has an agreement or contract to perform the services of the contract or agreement. This routine use includes disclosures by the individual or entity performing the service for VA to any secondary entity or individual to perform an activity that is necessary for individuals, organizations, private or public agencies, or other entities or individuals with whom VA has a contract or agreement to provide the service to VA. </P>
                    <P>7. Any system records disclosure may be made to the OMB in order for them to perform their statutory responsibilities for evaluating Federal programs. </P>
                    <P>8. Upon receipt of a written request, VA may disclose information to any state, tribe, county, or municipal agency for the purposes of outreach to a benefit under Title 38 Code of Federal Regulations (CFR). </P>
                    <P>9. Any records may be disclosed to appropriate agencies, entities, and persons under the following circumstances: When (1) It is suspected or confirmed that the security or confidentiality of information in the system of records has been compromised; (2) the Department has determined that as a result of the suspected or confirmed compromise there is a risk of embarrassment or harm to the reputations of the record subjects, harm to economic or property interests, identity theft or fraud, or harm to the security or integrity of this system or other systems or programs (whether maintained by the Department or another agency or entity) that rely upon the compromised information; and (3) the disclosure is made to such agencies, entities, and persons who are reasonably necessary to assist in connection with the Department's efforts to respond to the suspected or confirmed compromise and prevent, minimize, or remedy such harm. </P>
                    <P>10. VA may disclose information in this system of records to the Department of Justice (DoJ), either on VA's initiative or in response to DoJ's request for the information, after either VA or DoJ determines that such information is relevant to DoJ's representation of the United States or any of its components in legal proceedings before a court or adjudicative body, provided that, in each case, the agency also determines prior to disclosure that disclosure of the records to the Department of Justice is a use of the information contained in the records that is compatible with the purpose for which VA collected the records. VA, on its own initiative, may disclose records in this system of records in legal proceedings before a court or administrative body after determining that the disclosure of the records to the court or administrative body is a use of the information contained in the records that is compatible with the purpose for which VA collected the records. </P>
                    <P>
                        In determining whether to disclose records under this routine use, VA will comply with the guidance promulgated by the Office of Management and Budget in a May 24, 1985, memorandum entitled “Privacy Act Guidance—Update”, currently posted at 
                        <E T="03">http://www.whitehouse.gov/omb/inforeg/guidance1985.pdf.</E>
                    </P>
                    <P>11. VA may disclose on its own initiative any information in this system, except the names and home addresses of veterans and their dependents, which is relevant to a suspected or reasonably imminent violation of law, whether civil, criminal or regulatory in nature, and whether arising by general or program statute or by regulation, rule or order issued pursuant thereto, to a Federal, State, local, tribal, or foreign agency charged with the responsibility of investigating or prosecuting such violation, or charged with enforcing or implementing the statute, regulation, rule or order. On its own initiative, VA may also disclose the names and addresses of veterans and their dependents to a Federal agency charged with the responsibility of investigating or prosecuting civil, criminal or regulatory violations of law, or charged with enforcing or implementing the statute, regulation, rule or order issued pursuant thereto. </P>
                    <HD SOURCE="HD2">DISCLOSURE TO CONSUMER REPORTING AGENCIES:</HD>
                    <P>The Department will not make disclosures from this system of records to consumer reporting agencies. </P>
                    <HD SOURCE="HD2">POLICIES AND PRACTICES FOR STORING, RETRIEVING, ACCESSING, RETAINING, AND DISPOSING OF RECORDS IN THE SYSTEM: </HD>
                    <HD SOURCE="HD2">STORAGE: </HD>
                    <P>OPP's records are maintained electronically or in hard-copy form. All portable electronic storage devices and media are stored in a combination-locked safe which is secured inside a key-accessed room at the U.S. Department of Veterans Affairs, 810 Vermont Ave., NW., Washington, DC 20420. Other electronic data is placed on VA's segregated server which is housed at VA's Austin Automation Center, 615 Woodward St., Austin, TX 78772. Information stored on paper is kept locked in file cabinets when not in immediate use. All imported and exported OPP data is handled and housed via the provisions of signed data use agreements and current VA data security policies, procedures, and directives. When contractors must have access to data in this system of records in order to perform the contract, contractors house VA data in their own facilities in accordance with current VA data security policies, procedures and directives. </P>
                    <HD SOURCE="HD2">RETRIEVABILITY: </HD>
                    <P>OPP's records may be retrieved by using an individual's social security number, military service number, VA claim or file number, non-VA Federal benefit identifiers, and other personal identifiers. </P>
                    <HD SOURCE="HD2">SAFEGUARDS:</HD>
                    <P>All VA offices are protected from outside access by security personnel seven days a week. Entrances and exits are monitored by security cameras and protected by an alarm system. All VA staff and visitors are required to either have a VA-issued employment identification card or a temporary visitor identification badge. All work stations are secured during daytime and evening hours. </P>
                    <P>
                        Electronic data located in Washington, DC is stored in a combination-key-locked safe which is secured inside a limited-access room. Authorized employee access to the limited-access room and the safe is based upon strict business needs as determined by OPP's Assistant Secretary. Textual data is stored in key-locked cabinets inside secured rooms. Access to the server in the Austin Automation Center in Austin, TX is 
                        <PRTPAGE P="18756"/>
                        generally limited by appropriate locking devices and restricted to authorized VA personnel. The Austin Automation Center is a secure facility. 
                    </P>
                    <P>All data requests must be in writing, reviewed by a panel of OPP personnel, concurred on by OPP's Assistant Secretary, and released under the auspices of a signed data use agreement. File extracts provided for specific official uses will be limited to contain only the information fields needed for the analysis. Data used for analyses will have individual identifying characteristics removed or encrypted whenever possible. Unencrypted sensitive variables will only be used for analysis as a last resort. </P>
                    <P>Security complies with applicable Federal Information Processing Standards (FIPS) issued by the National Institute of Standards and Technology (NIST). Health information files containing unique identifiers such as social security numbers are encrypted to NIST-verified FIPS 140-2 standard or higher for storage, transport, or transmission. All files stored or transmitted on laptops, workstations, data storage devices and media are encrypted. Files are kept encrypted at all times except when data is in immediate use, per specifications by VA Office of Information Technology. NIST publications were consulted in development of security for this system of records. </P>
                    <P>In the event of a contract or special project, VA may secure the services of contractors and/or subcontractors. In such cases, VA will maximize the utilization of encrypted data, when possible. Contractors and their subcontractors are required to maintain the same level of security as VA staff for non-health care information that has been disclosed to them. Unless explicitly authorized in writing by the VA, sensitive or protected data made available to the contractor and subcontractors shall not be divulged or made known in any manner to any person. </P>
                    <P>All VA employees and contractors are mandated to complete annual cyber security and privacy training. </P>
                    <HD SOURCE="HD2">RETENTION AND DISPOSAL: </HD>
                    <P>
                        In accordance with Title 36, CFR, Section 1234.34, 
                        <E T="03">Destruction of Electronic Records,</E>
                         “electronic records may be destroyed only in accordance with a records disposition schedule approved by the Archivist of the United States, including General Records Schedules.” This Office's electronic files are destroyed or deleted when no longer needed for administrative, legal, audit, or other operational purposes in accordance with records disposition authority approved by the Archivist. 
                    </P>
                    <P>If the Archivist has not approved disposition authority for any records covered by the system notice, the System Manager will take immediate action to have the disposition of records in the system reviewed and paperwork initiated to obtain an approved records disposition authority in accordance with VA Handbook 6300.1, Records Management Procedures. The records may not be destroyed until VA obtains an approved records disposition authority. OPP will publish an amendment to this notice upon issuance of a NARA-approved disposition authority. </P>
                    <HD SOURCE="HD2">SYSTEM MANAGER(S) AND ADDRESS(ES): </HD>
                    <P>OPP's system manager is the Director, Office of Data Development and Analysis, (008A3), U.S. Department of Veterans Affairs, 810 Vermont Ave., NW., Washington, DC 20420. </P>
                    <HD SOURCE="HD2">NOTIFICATION PROCEDURE: </HD>
                    <P>An individual who wishes to determine whether a record is being maintained in this system under his or her name or other personal identifier, or wants to determine the contents of such record, should submit a written request to the Director, Office of Data Development and Analysis, (008A3), U.S. Department of Veterans Affairs, 810 Vermont Ave., NW., Washington, DC 20420. Such requests must contain a reasonable description of the records requested. In addition, identification of the individual requesting the information will be required in the written request and will minimally consist of the requester's name, signature, social security number, address, telephone number, and return address. </P>
                    <HD SOURCE="HD2">RECORD ACCESS PROCEDURES: </HD>
                    <P>(See Notification procedure above.) </P>
                    <HD SOURCE="HD2">CONTESTING RECORDS PROCEDURES: </HD>
                    <P>(See Notification procedure above.) </P>
                    <HD SOURCE="HD2">RECORD SOURCE CATEGORIES: </HD>
                    <P>This Office's information is obtained from VA's benefits-related databases, the DoD, Federal and State agencies, and other organizations whose data is necessary to accomplish the purpose for this system of records.</P>
                </PRIACT>
            </SUPLINF>
            <FRDOC> [FR Doc. E7-6982 Filed 4-12-07; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 8320-01-P </BILCOD>
        </NOTICE>
    </NOTICES>
    <VOL>72</VOL>
    <NO>71</NO>
    <DATE>Friday, April 13, 2007</DATE>
    <UNITNAME>Presidential Documents</UNITNAME>
    <PRESDOCS>
        <PRESDOCU>
            <PRMEMO>
                <TITLE3>Title 3—</TITLE3>
                <PRES>
                    The President
                    <PRTPAGE P="18561"/>
                </PRES>
                <MEMO>Memorandum of April 10, 2007</MEMO>
                <HD SOURCE="HED">Assignment of Functions Relating to the Information Sharing Environment</HD>
                <HD SOURCE="HED">Memorandum for the Director of National Intelligence</HD>
                <FP>By the authority vested in me as President by the Constitution and laws of the United States of America, including section 301 of title 3, United States Code, the functions of the President under section 1016(b) of the Intelligence Reform and Terrorism Prevention Act of 2004 (Public Law 108-458) (the “Act”) are hereby assigned to the Director of National Intelligence (Director).</FP>
                <FP>The Director shall perform such functions in a manner consistent with direction and guidance issued by the President, including (1) the Memorandum for the Heads of Executive Departments and Agencies of June 2, 2005, entitled “Strengthening Information Sharing, Access, and Integration—Organizational, Management, and Policy Development Structures for Creating the Terrorism Information Sharing Environment,” and (2) the Memorandum for the Heads of Executive Departments and Agencies of December 16, 2005, entitled “Guidelines and Requirements in Support of the Information Sharing Environment;” provided that the Director shall ensure that the official within the Office of the Director of National Intelligence previously designated as the program manager responsible for information sharing across the Federal Government pursuant to the Act shall be the assistant to the Director in carrying out the functions delegated by this memorandum.</FP>
                <FP>
                    You are authorized and directed to publish this memorandum in the 
                    <E T="04">Federal Register</E>
                    .
                </FP>
                <GPH SPAN="1" DEEP="75" HTYPE="RIGHT">
                    <GID>GWBOLD.EPS</GID>
                </GPH>
                <PSIG> </PSIG>
                <FRDOC>[FR Doc. 07-1875</FRDOC>
                <FILED>Filed 4-12-07; 8:45 am]</FILED>
                <BILCOD>Billing code 3910-A7-M</BILCOD>
            </PRMEMO>
        </PRESDOCU>
    </PRESDOCS>
    <VOL>72</VOL>
    <NO>71</NO>
    <DATE>Friday, April 13, 2007</DATE>
    <UNITNAME>Rules and Regulations</UNITNAME>
    <NEWPART>
        <PTITLE>
            <PRTPAGE P="18757"/>
            <PARTNO>Part II</PARTNO>
            <AGENCY TYPE="P">Department of Defense</AGENCY>
            <CFR>32 CFR Part 310</CFR>
            <TITLE>Department of Defense Privacy Program; Final Rule</TITLE>
        </PTITLE>
        <RULES>
            <RULE>
                <PREAMB>
                    <PRTPAGE P="18758"/>
                    <AGENCY TYPE="S">DEPARTMENT OF DEFENSE </AGENCY>
                    <SUBAGY>Office of the Secretary </SUBAGY>
                    <DEPDOC>[DoD-2006-OS-0129] </DEPDOC>
                    <RIN>RIN 0790-AB03 </RIN>
                    <CFR>32 CFR Part 310 </CFR>
                    <SUBJECT>Department of Defense Privacy Program </SUBJECT>
                    <AGY>
                        <HD SOURCE="HED">AGENCY:</HD>
                        <P>Department of Defense. </P>
                    </AGY>
                    <ACT>
                        <HD SOURCE="HED">ACTION:</HD>
                        <P>Final rule. </P>
                    </ACT>
                    <SUM>
                        <HD SOURCE="HED">SUMMARY:</HD>
                        <P>The Department of Defense is updating policies and responsibilities for the Defense Privacy Program which implements the Privacy Act of 1974. </P>
                    </SUM>
                    <EFFDATE>
                        <HD SOURCE="HED">EFFECTIVE DATE:</HD>
                        <P>April 13, 2007. </P>
                    </EFFDATE>
                    <FURINF>
                        <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                        <P>Mr. Vahan Moushegian, Jr., at (703) 607-2943. </P>
                    </FURINF>
                </PREAMB>
                <SUPLINF>
                    <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                    <P>
                        The proposed rule was published in the 
                        <E T="04">Federal Register</E>
                         on July 14, 2006 at 71 FR 40282. No public comments were received. Some administrative changes were made as a result of comments on the corresponding DoD issuance and Office of Management and Budget guidance. Changes involve revision of the terms for personal and compromised information; the incorporation of additional considerations when determining if a social security number will be collected; a reorganization of the procedures involving Congressional or General Accountability Office access to records; an expanded explanation of record disposal procedures and the access exemption; additional consideration involving training and technical/special security requirements; and new notification procedures when there is a loss or theft of information. 
                    </P>
                    <HD SOURCE="HD1">Executive Order (E.O.) 12866, “Regulatory Planning and Review” </HD>
                    <P>It has been determined that 32 CFR part 310 is not a significant regulatory action. The rule does not </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 governments 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; or </P>
                    <P>(4) Raise novel legal or policy issues arising out of legal mandates, the President's priorities, or the principles set forth in this Executive Order. </P>
                    <HD SOURCE="HD1">Public Law 96-354, “Regulatory Flexibility Act” (5 U.S.C. Chapter 6) </HD>
                    <P>It has been determined that this rule is not subject to the Regulatory Flexibility Act because it would not, if promulgated, have a significant economic impact on a substantial number of small entities because it is only concerned with the administration of Privacy Program within the Department of Defense. </P>
                    <HD SOURCE="HD1">Public Law 96-511, “Paperwork Reduction Act” (44 U.S.C. Chapter 35) </HD>
                    <P>It has been determined that this rule does not impose information requirements beyond the Department of Defense and that the information collected within the Department of Defense is necessary and consistent with 5 U.S.C. 552a, known as the Privacy Act of 1974. </P>
                    <HD SOURCE="HD1">Section 202, Public Law 104-4, “Unfunded Mandates Reform Act” </HD>
                    <P>It has been determined that the rule does not involve 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 million or more in any one year. </P>
                    <HD SOURCE="HD1">Executive Order 13132, “Federalism” </HD>
                    <P>It has been determined that this rule does not have federalism implications. The rule does not have substantial direct effects on the States, the relationship between the National Government and the States, or on the distribution of power and responsibilities among the various levels of government. </P>
                    <LSTSUB>
                        <HD SOURCE="HED">List of Subjects in 32 CFR Part 310 </HD>
                        <P>Privacy.</P>
                    </LSTSUB>
                    <REGTEXT TITLE="32" PART="310">
                        <AMDPAR>Accordingly, 32 CFR part 310 is revised as follows. </AMDPAR>
                        <PART>
                            <HD SOURCE="HED">PART 310—DOD PRIVACY PROGRAM </HD>
                            <CONTENTS>
                                <SUBPART>
                                    <HD SOURCE="HED">Subpart A—DoD Policy </HD>
                                    <SECHD>Sec. </SECHD>
                                    <SECTNO>310.1 </SECTNO>
                                    <SUBJECT>Reissuance. </SUBJECT>
                                    <SECTNO>310.2 </SECTNO>
                                    <SUBJECT>Purpose. </SUBJECT>
                                    <SECTNO>310.3 </SECTNO>
                                    <SUBJECT>Applicability and scope. </SUBJECT>
                                    <SECTNO>310.4 </SECTNO>
                                    <SUBJECT>Definitions. </SUBJECT>
                                    <SECTNO>310.5 </SECTNO>
                                    <SUBJECT>Policy. </SUBJECT>
                                    <SECTNO>310.6 </SECTNO>
                                    <SUBJECT>Responsibilities. </SUBJECT>
                                    <SECTNO>310.7 </SECTNO>
                                    <SUBJECT>Information requirements. </SUBJECT>
                                    <SECTNO>310.8 </SECTNO>
                                    <SUBJECT>Rules of conduct. </SUBJECT>
                                    <SECTNO>310.9 </SECTNO>
                                    <SUBJECT>Privacy boards and office, composition and responsibilities. </SUBJECT>
                                </SUBPART>
                                <SUBPART>
                                    <HD SOURCE="HED">Subpart B—Systems of Records </HD>
                                    <SECTNO>310.10 </SECTNO>
                                    <SUBJECT>General. </SUBJECT>
                                    <SECTNO>310.11 </SECTNO>
                                    <SUBJECT>Standards of accuracy. </SUBJECT>
                                    <SECTNO>310.12 </SECTNO>
                                    <SUBJECT>Government contractors. </SUBJECT>
                                    <SECTNO>310.13 </SECTNO>
                                    <SUBJECT>Safeguarding personal information. </SUBJECT>
                                    <SECTNO>310.14 </SECTNO>
                                    <SUBJECT>Notification when information is lost, stolen, or compromised. </SUBJECT>
                                </SUBPART>
                                <SUBPART>
                                    <HD SOURCE="HED">Subpart C—Collecting Personal Information </HD>
                                    <SECTNO>310.15 </SECTNO>
                                    <SUBJECT>General considerations. </SUBJECT>
                                    <SECTNO>310.16 </SECTNO>
                                    <SUBJECT>Forms. </SUBJECT>
                                </SUBPART>
                                <SUBPART>
                                    <HD SOURCE="HED">Subpart D—Access by Individuals </HD>
                                    <SECTNO>310.17 </SECTNO>
                                    <SUBJECT>Individual access to personal information. </SUBJECT>
                                    <SECTNO>310.18 </SECTNO>
                                    <SUBJECT>Denial of individual access. </SUBJECT>
                                    <SECTNO>310.19 </SECTNO>
                                    <SUBJECT>Amendment of records. </SUBJECT>
                                    <SECTNO>310.20 </SECTNO>
                                    <SUBJECT>Reproduction fees. </SUBJECT>
                                </SUBPART>
                                <SUBPART>
                                    <HD SOURCE="HED">Subpart E—Disclosure of Personal Information to Other Agencies and Third Parties </HD>
                                    <SECTNO>310.21 </SECTNO>
                                    <SUBJECT>Conditions of disclosure. </SUBJECT>
                                    <SECTNO>310.22 </SECTNO>
                                    <SUBJECT>Non-consensual conditions of disclosure. </SUBJECT>
                                    <SECTNO>310.23 </SECTNO>
                                    <SUBJECT>Disclosures to commercial enterprises. </SUBJECT>
                                    <SECTNO>310.24 </SECTNO>
                                    <SUBJECT>Disclosures to the public from medical records. </SUBJECT>
                                    <SECTNO>310.25 </SECTNO>
                                    <SUBJECT>Disclosure accounting. </SUBJECT>
                                </SUBPART>
                                <SUBPART>
                                    <HD SOURCE="HED">Subpart F—Exemptions </HD>
                                    <SECTNO>310.26 </SECTNO>
                                    <SUBJECT>Use and establishment of exemptions. </SUBJECT>
                                    <SECTNO>310.27 </SECTNO>
                                    <SUBJECT>Access exemption. </SUBJECT>
                                    <SECTNO>310.28 </SECTNO>
                                    <SUBJECT>General exemption. </SUBJECT>
                                    <SECTNO>310.29 </SECTNO>
                                    <SUBJECT>Specific exemptions. </SUBJECT>
                                </SUBPART>
                                <SUBPART>
                                    <HD SOURCE="HED">Subpart G—Publication Requirements </HD>
                                    <SECTNO>310.30 </SECTNO>
                                    <SUBJECT>
                                        <E T="04">Federal Register</E>
                                         publication. 
                                    </SUBJECT>
                                    <SECTNO>310.31 </SECTNO>
                                    <SUBJECT>Exemption rules. </SUBJECT>
                                    <SECTNO>310.32 </SECTNO>
                                    <SUBJECT>System notices. </SUBJECT>
                                    <SECTNO>310.33 </SECTNO>
                                    <SUBJECT>New and altered record systems. </SUBJECT>
                                    <SECTNO>310.34 </SECTNO>
                                    <SUBJECT>Amendment and deletion of system notices. </SUBJECT>
                                </SUBPART>
                                <SUBPART>
                                    <HD SOURCE="HED">Subpart H—Training Requirements </HD>
                                    <SECTNO>310.35 </SECTNO>
                                    <SUBJECT>Statutory training requirements. </SUBJECT>
                                    <SECTNO>310.36 </SECTNO>
                                    <SUBJECT>OMB training guidelines. </SUBJECT>
                                    <SECTNO>310.37 </SECTNO>
                                    <SUBJECT>DoD training programs. </SUBJECT>
                                    <SECTNO>310.38 </SECTNO>
                                    <SUBJECT>Training methodology and procedures. </SUBJECT>
                                    <SECTNO>310.39 </SECTNO>
                                    <SUBJECT>Funding for training. </SUBJECT>
                                </SUBPART>
                                <SUBPART>
                                    <HD SOURCE="HED">Subpart I—Reports </HD>
                                    <SECTNO>310.40 </SECTNO>
                                    <SUBJECT>Requirement for reports. </SUBJECT>
                                    <SECTNO>310.41 </SECTNO>
                                    <SUBJECT>Suspense for submission of reports. </SUBJECT>
                                    <SECTNO>310.42 </SECTNO>
                                    <SUBJECT>Reports control symbol. </SUBJECT>
                                </SUBPART>
                                <SUBPART>
                                    <HD SOURCE="HED">Subpart J—Inspections </HD>
                                    <SECTNO>310.43 </SECTNO>
                                    <SUBJECT>Privacy Act inspections. </SUBJECT>
                                    <SECTNO>310.44 </SECTNO>
                                    <SUBJECT>Inspection reporting. </SUBJECT>
                                </SUBPART>
                                <SUBPART>
                                    <HD SOURCE="HED">Subpart K—Privacy Act Violations </HD>
                                    <SECTNO>310.45 </SECTNO>
                                    <SUBJECT>Administrative remedies. </SUBJECT>
                                    <SECTNO>310.46 </SECTNO>
                                    <SUBJECT>Civil actions. </SUBJECT>
                                    <SECTNO>310.47 </SECTNO>
                                    <SUBJECT>Civil remedies. </SUBJECT>
                                    <SECTNO>310.48 </SECTNO>
                                    <SUBJECT>Criminal penalties. </SUBJECT>
                                    <SECTNO>310.49 </SECTNO>
                                    <SUBJECT>Litigation status sheet. </SUBJECT>
                                    <SECTNO>310.50 </SECTNO>
                                    <SUBJECT>Lost, stolen, or compromised information. </SUBJECT>
                                </SUBPART>
                                <SUBPART>
                                    <HD SOURCE="HED">Subpart L—Computer Matching Program Procedures </HD>
                                    <SECTNO>310.51 </SECTNO>
                                    <SUBJECT>General. </SUBJECT>
                                    <SECTNO>310.52 </SECTNO>
                                    <SUBJECT>Computer matching publication and review requirements. </SUBJECT>
                                    <SECTNO>310.53 </SECTNO>
                                    <SUBJECT>Computer matching agreements (CMAs). </SUBJECT>
                                </SUBPART>
                                <FP SOURCE="FP-2">Appendix A to Part 310—Safeguarding Personally Identifiable Information </FP>
                                <FP SOURCE="FP-2">
                                    Appendix B to Part 310—Sample Notification Letter 
                                    <PRTPAGE P="18759"/>
                                </FP>
                                <FP SOURCE="FP-2">Appendix C to Part 310—DoD Blanket Routine Uses </FP>
                                <FP SOURCE="FP-2">Appendix D to Part 310—Provisions of the Privacy Act From Which a General or Specific Exemption May Be Claimed </FP>
                                <FP SOURCE="FP-2">
                                    Appendix E to Part 310—Sample of New or Altered System of Records Notice in 
                                    <E T="04">Federal Register</E>
                                     Format 
                                </FP>
                                <FP SOURCE="FP-2">Appendix F to Part 310—Format for New or Altered System Report </FP>
                                <FP SOURCE="FP-2">
                                    Appendix G to Part 310—Sample Amendments or Deletions to System Notices in 
                                    <E T="04">Federal Register</E>
                                     Format 
                                </FP>
                                <FP SOURCE="FP-2">Appendix H to Part 310—Litigation Status Sheet </FP>
                            </CONTENTS>
                            <AUTH>
                                <HD SOURCE="HED">Authority:</HD>
                                <P>Pub. L. 93-579, 88 Stat. 1896 (5 U.S.C. 552a). </P>
                            </AUTH>
                            <SUBPART>
                                <HD SOURCE="HED">Subpart A—DoD Policy </HD>
                                <SECTION>
                                    <SECTNO>§ 310.1 </SECTNO>
                                    <SUBJECT>Reissuance. </SUBJECT>
                                    <P>
                                        This part consolidates into a single location (32 CFR part 310) Department of Defense (DoD) policies and procedures for implementing the Privacy Act of 1974, as amended (5 U.S.C. 552a) by authorizing the development, publication and maintenance of the DoD Privacy Program set forth by DoD Directive 5400.11 
                                        <SU>1</SU>
                                        <FTREF/>
                                         and 5400.11-R,
                                        <SU>2</SU>
                                        <FTREF/>
                                         both entitled: “DoD Privacy Program.” 
                                    </P>
                                    <FTNT>
                                        <P>
                                            <SU>1</SU>
                                             Copies may be obtained at 
                                            <E T="03">http://www.dtic.mil/whs/directives.</E>
                                        </P>
                                    </FTNT>
                                    <FTNT>
                                        <P>
                                            <SU>2</SU>
                                             See footnote 1 to § 310.1.
                                        </P>
                                    </FTNT>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 310.2 </SECTNO>
                                    <SUBJECT>Purpose. </SUBJECT>
                                    <P>This part:</P>
                                    <P>(a) Updates policies and responsibilities of the DoD Privacy Program under 5 U.S.C. 552a and OMB Circular A-130. </P>
                                    <P>(b) Authorizes the Defense Privacy Board, the Defense Privacy Board Legal Committee, and the Defense Data Integrity Board. </P>
                                    <P>(c) Continues to authorize the publication of DoD 5400.11-R. </P>
                                    <P>(d) Continues to delegate authorities and responsibilities for the effective administration of the DoD Privacy Program. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 310.3 </SECTNO>
                                    <SUBJECT>Applicability and scope. </SUBJECT>
                                    <P>This part:</P>
                                    <P>(a) Applies to the Office of the Secretary of Defense (OSD), the Military Departments, the Chairman of the Joint Chiefs of Staff, the Combatant Commands, the Office of the Inspector General of the Department of Defense (IG, DoD), the Defense Agencies, the DoD Field Activities, and all other organizational entities in the Department of Defense (hereinafter referred to collectively as “the DoD Components”). </P>
                                    <P>(b) Shall be made applicable to DoD contractors who are operating a system of records on behalf of a DoD Component, to include any of the activities, such as collecting and disseminating records, associated with maintaining a system of records. </P>
                                    <P>(c) This part does not apply to: </P>
                                    <P>
                                        (1) Requests for information made under the Freedom of Information Act. They are processed in accordance with DoD 5400.7-R.
                                        <SU>3</SU>
                                        <FTREF/>
                                    </P>
                                    <FTNT>
                                        <P>
                                            <SU>3</SU>
                                             See footnote 1 to § 310.3(c)(1). 
                                        </P>
                                    </FTNT>
                                    <P>(2) Requests for information from systems of records controlled by the Office of Personnel Management (OPM), although maintained by a DoD Component. These are processed in accordance with policies established by OPM “Privacy Procedures for Personnel Records” (5 CFR 297). </P>
                                    <P>
                                        (3) Requests for personal information from the General Accounting Office. These are processed in accordance with DoD Directive 7650.1.
                                        <SU>4</SU>
                                        <FTREF/>
                                    </P>
                                    <FTNT>
                                        <P>
                                            <SU>4</SU>
                                             See footnote 1 to § 310.3(c)(1). 
                                        </P>
                                    </FTNT>
                                    <P>(4) Requests for personal information from Congress. These are processed in accordance with DoD Directive 5400.4 except those specific provisions in Subpart E—Disclosure of Personal Information to Other Agencies and Third Parties. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 310.4. </SECTNO>
                                    <SUBJECT>Definitions. </SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">Access</E>
                                        . The review of a record or a copy of a record or parts thereof in a system of records by any individual. 
                                    </P>
                                    <P>
                                        (b) 
                                        <E T="03">Agency</E>
                                        . For the purposes of disclosing records subject to the Privacy Act among the DoD Components, the Department of Defense is a considered a single agency. For all other purposes to include requests for access and amendment, denial of access or amendment, appeals from denials, and record keeping as relating to release of records to non-DoD Agencies, each DoD Component is considered an agency within the meaning of the Privacy Act. 
                                    </P>
                                    <P>
                                        (c) 
                                        <E T="03">Computer Matching Program</E>
                                        . The computerized comparison of two or more automated systems of records or a system of records with non-Federal records. Manual comparison of systems of records or a system of records with non-Federal records are not covered. 
                                    </P>
                                    <P>
                                        (d) 
                                        <E T="03">Confidential source</E>
                                        . A person or organization who has furnished information to the Federal Government under an express promise, if made on or after September 27, 1975, that the person's or the organization's identity shall be held in confidence or under an implied promise of such confidentiality if this implied promise was made on or before September 26, 1975. 
                                    </P>
                                    <P>
                                        (e) 
                                        <E T="03">Disclosure</E>
                                        . The transfer of any personal information from a system of records by any means of communication (such as oral, written, electronic, mechanical, or actual review) to any person, private entity, or Government Agency, other than the subject of the record, the subject's designated agent or the subject's legal guardian. 
                                    </P>
                                    <P>
                                        (f) 
                                        <E T="03">Federal benefit program</E>
                                        . A program administered or funded by the Federal Government, or by any agent or State on behalf of the Federal Government, providing cash or in-kind assistance in the form of payments, grants, loans, or loan guarantees to individuals.
                                    </P>
                                    <P>
                                        (g) 
                                        <E T="03">Federal personnel</E>
                                        . Officers and employees of the Government of the United States, members of the uniformed services (including members of the Reserve Components), individuals entitled to receive immediate or deferred retirement benefits under any retirement program of the United States (including survivor benefits). 
                                    </P>
                                    <P>
                                        (h) 
                                        <E T="03">Individual</E>
                                        . A living person who is a citizen of the United States or an alien lawfully admitted for permanent residence. The parent of a minor or the legal guardian of any individual also may act on behalf of an individual. Members of the United States Armed Forces are “individuals.” Corporations, partnerships, sole proprietorships, professional groups, businesses, whether incorporated or unincorporated, and other commercial entities are not “individuals” when acting in an entrepreneurial capacity with the Department of Defense but are “individuals” otherwise (e.g., security clearances, entitlement to DoD privileges or benefits, etc.). 
                                    </P>
                                    <P>
                                        (i) 
                                        <E T="03">Individual access</E>
                                        . Access to information pertaining to the individual by the individual or his or her designated agent or legal guardian. 
                                    </P>
                                    <P>
                                        (j) 
                                        <E T="03">Lost, stolen, or compromised information</E>
                                        . Actual or possible loss of control, unauthorized disclosure, or unauthorized access of personal information where persons other than authorized users gain access or potential access to such information for an other than authorized purpose where one or more individuals will be adversely affected. Such incidents also are known as 
                                        <E T="03">breaches</E>
                                        . 
                                    </P>
                                    <P>
                                        (k) 
                                        <E T="03">Maintain</E>
                                        . To maintain, collect, use, or disseminate records contained in a system of records. 
                                    </P>
                                    <P>
                                        (l) 
                                        <E T="03">Non-Federal agency</E>
                                        . Any state or local government, or agency thereof, which receives records contained in a system of records from a source agency for use in a computer matching program. 
                                    </P>
                                    <P>
                                        (m) 
                                        <E T="03">Official use</E>
                                        . Within the context of this part, this term is used when officials and employees of a DoD Component have a demonstrated a need for the record or the information 
                                        <PRTPAGE P="18760"/>
                                        contained therein in the performance of their official duties, subject to DoD 5200.1-R.
                                        <SU>5</SU>
                                        <FTREF/>
                                    </P>
                                    <FTNT>
                                        <P>
                                            <SU>5</SU>
                                             See footnote 1 to § 310.1. 
                                        </P>
                                    </FTNT>
                                    <P>
                                        (n) 
                                        <E T="03">Personal information</E>
                                        . Information about an individual that identifies, links, relates, or is unique to, or describes him or her, e.g., a social security number; age; military rank; civilian grade; marital status; race; salary; home/office phone numbers; other demographic, biometric, personnel, medical, and financial information, etc. Such information also is known as 
                                        <E T="03">personally identifiable information</E>
                                         (i.e., information which can be used to distinguish or trace an individual's identity, such as their name, social security number, date and place of birth, mother's maiden name, biometric records, including any other personal information which is linked or linkable to a specified individual). 
                                    </P>
                                    <P>
                                        (o) 
                                        <E T="03">Privacy Act request</E>
                                        . A request from an individual for notification as to the existence of, access to, or amendment of records pertaining to that individual. These records must be maintained in a system of records. 
                                    </P>
                                    <P>
                                        (p) 
                                        <E T="03">Member of the public</E>
                                        . Any individual or party acting in a private capacity to include Federal employees or military personnel. 
                                    </P>
                                    <P>
                                        (q) 
                                        <E T="03">Recipient agency</E>
                                        . Any agency, or contractor thereof, receiving records contained in a system of records from a source agency for use in a computer matching program. 
                                    </P>
                                    <P>
                                        (r) 
                                        <E T="03">Record</E>
                                        . Any item, collection, or grouping of information, whatever the storage media (e.g., paper, electronic, etc.), about an individual that is maintained by a DoD Component, including, but not limited to, his or her education, financial transactions, medical history, criminal or employment history, and that contains his or her name, or the identifying number, symbol, or other identifying particular assigned to the individual, such as a finger or voice print or a photograph. 
                                    </P>
                                    <P>
                                        (s) 
                                        <E T="03">Risk assessment</E>
                                        . An analysis considering information sensitivity, vulnerabilities, and cost in safeguarding personal information processed or stored in the facility or activity. 
                                    </P>
                                    <P>
                                        (t) 
                                        <E T="03">Routine use</E>
                                        . The disclosure of a record outside the Department of Defense for a use that is compatible with the purpose for which the information was collected and maintained by the Department of Defense. The routine use must be included in the published system notice for the system of records involved. 
                                    </P>
                                    <P>
                                        (u) 
                                        <E T="03">Source agency</E>
                                        . Any agency which discloses records contained in a system of records to be used in a computer matching program, or any state or local government, or agency thereof, which discloses records to be used in a computer matching program. 
                                    </P>
                                    <P>
                                        (v) 
                                        <E T="03">Statistical record</E>
                                        . A record maintained only for statistical research or reporting purposes and not used in whole or in part in making determinations about specific individuals.
                                    </P>
                                    <P>
                                        (w) 
                                        <E T="03">System of records</E>
                                        . A group of records under the control of a DoD Component from which personal information about an individual is retrieved by the name of the individual or by some other identifying number, symbol, or other identifying particular assigned, that is unique to the individual. 
                                    </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 310.5 </SECTNO>
                                    <SUBJECT>Policy. </SUBJECT>
                                    <P>It is DoD policy that: </P>
                                    <P>(a) The privacy of an individual is a personal and fundamental right that shall be respected and protected. </P>
                                    <P>(1) The Department's need to collect, maintain, use, or disseminate personal information about individuals for purposes of discharging its statutory responsibilities shall be balanced against the right of the individual to be protected against unwarranted invasions of their privacy. </P>
                                    <P>(2) The legal rights of individuals, as guaranteed by Federal law, regulation, and policy, shall be protected when collecting, maintaining, using, or disseminating personal information about individuals. </P>
                                    <P>(3) DoD personnel, to include contractors, have an affirmative responsibility to protect an individual's privacy when collecting, maintaining, using, or disseminating personal information about an individual. </P>
                                    <P>(4) Departmental legislative, regulatory, or other policy proposals shall be evaluated to ensure that privacy implications, including those relating to the collection, maintenance, use, or dissemination of personal information, are assessed, to include, when required and consistent with the Privacy Provision of the E-Government Act of 2002 (44 U.S.C. 3501, Note), the preparation of a Privacy Impact Assessment. </P>
                                    <P>(b) Personal information shall be collected, maintained, used, or disclosed to ensure that: </P>
                                    <P>(1) It shall be relevant and necessary to accomplish a lawful DoD purpose required to be accomplished by statute or Executive order. </P>
                                    <P>(2) It shall be collected to the greatest extent practicable directly from the individual. </P>
                                    <P>(3) The individual shall be informed as to why the information is being collected, the authority for collection, what uses will be made of it, whether disclosure is mandatory or voluntary, and the consequences of not providing that information. </P>
                                    <P>(4) It shall be relevant, timely, complete, and accurate for its intended use; and </P>
                                    <P>(5) Appropriate administrative, technical, and physical safeguards shall be established, based on the media (e.g., paper, electronic, etc.) involved, to ensure the security of the records and to prevent compromise or misuse during storage, transfer, or use, including working at authorized alternative worksites. </P>
                                    <P>(c) No record shall be maintained on how an individual exercises rights guaranteed by the First Amendment to the Constitution, except as follows: </P>
                                    <P>(1) When specifically authorized by statute; </P>
                                    <P>(2) When expressly authorized by the individual on whom the record is maintained; or </P>
                                    <P>(3) When the record is pertinent to and within the scope of an authorized law enforcement activity. </P>
                                    <P>
                                        (d) Notices shall be published in the 
                                        <E T="04">Federal Register</E>
                                         and reports shall be submitted to Congress and the Office of Management and Budget, in accordance with, and as required by, 5 U.S.C. 552a, OMB Circular A-130, and DoD 5400.11-R, as to the existence and character of any system of records being established or revised by the DoD Components. Information shall not be collected, maintained, used, or disseminated until the required publication and review requirements, as set forth in 5 U.S.C. 552a, OMB Circular A-130, and DoD 5400.11-R, are satisfied. 
                                    </P>
                                    <P>(e) Individuals shall be permitted, to the extent authorized by 5 U.S.C. 552a and DoD 5400.11-R, to: </P>
                                    <P>(1) Determine what records pertaining to them are contained in a system of records. </P>
                                    <P>(2) Gain access to such records and obtain a copy of those records or a part thereof. </P>
                                    <P>(3) Correct or amend such records once it has been determined that the records are not accurate, relevant, timely, or complete. </P>
                                    <P>(4) Appeal a denial of access or a request for amendment. </P>
                                    <P>
                                        (f) Disclosure of records pertaining to an individual from a system of records shall be prohibited except with the consent of the individual or as otherwise authorized by 5 U.S.C. 552a, DoD 5400.11-R, and DoD 5400.7-R. When disclosures are made, the individual shall be permitted, to the 
                                        <PRTPAGE P="18761"/>
                                        extent authorized by references 5 U.S.C. 552a and/or DoD 5400.11-R, to seek an accounting of such disclosures from the DoD Component making the release. 
                                    </P>
                                    <P>
                                        (g) Disclosure of records pertaining to personnel of the National Security Agency, the Defense Intelligence Agency, the National Reconnaissance Office, and the National Geospatial-Intelligence Agency shall be prohibited to the extent authorized by Public Law 86-36 (1959) and 10 U.S.C. 424. Disclosure of records pertaining to personnel of overseas, sensitive, or routinely deployable units shall be prohibited to the extent authorized by 10 U.S.C. 130b. Disclosure of medical records is prohibited except as authorized by DoD 6025.18-R.
                                        <SU>6</SU>
                                        <FTREF/>
                                    </P>
                                    <FTNT>
                                        <P>
                                            <SU>6</SU>
                                             See footnote 1 to § 310.1. 
                                        </P>
                                    </FTNT>
                                    <P>(h) Computer matching programs between the DoD Components and the Federal, State, or local governmental agencies shall be conducted in accordance with the requirements of 5 U.S.C. 552a, OMB Circular A-130, and DoD 5400.11-R. </P>
                                    <P>(i) DoD personnel and system managers shall conduct themselves consistent with established rules of conduct 310.8 so that personal information to be stored in a system of records only shall be collected, maintained, used, and disseminated as is authorized by this part, 5 U.S.C. 552a and DoD 5400.11-R. </P>
                                    <P>(j) DoD personnel, including but not limited to family members, retirees, contractor employees, and volunteers, shall be notified, in a timely manner, consistent with the requirements of DoD 5400.11-R, if their personal information, whether or not included in a system of records, is lost, stolen, or compromised. </P>
                                    <P>(k) DoD Field Activities shall receive Privacy Program support from the Director, Washington Headquarters Services. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 310.6 </SECTNO>
                                    <SUBJECT>Responsibilities. </SUBJECT>
                                    <P>(a) The Director of Administration and Management, Office of the Secretary of Defense, shall: </P>
                                    <P>(1) Serve as the Senior Privacy Official for the Department of Defense.</P>
                                    <P>(2) Provide policy guidance for, and coordinate and oversee administration of, the DoD Privacy Program to ensure compliance with policies and procedures in 5 U.S.C. 552a and OMB Circular A-130. </P>
                                    <P>(3) Publish DoD 5400.11-R and other guidance, including Defense Privacy Board Advisory Opinions, to ensure timely and uniform implementation of the DoD Privacy Program. </P>
                                    <P>(4) Serve as the Chair to the Defense Privacy Board and the Defense Data Integrity Board (see § 310.9). </P>
                                    <P>(5) Supervise and oversee the activities of the Defense Privacy Office (see § 310.9). </P>
                                    <P>(b) The Director, WHS, under the DA&amp;M, shall provide Privacy Program support for DoD Field Activities. </P>
                                    <P>(c) The General Counsel of the Department of Defense shall: </P>
                                    <P>(1) Provide advice and assistance on all legal matters arising out of, or incident to, the administration of the DoD Privacy Program. </P>
                                    <P>(2) Review and be the final approval authority on all advisory opinions issued by the Defense Privacy Board or the Defense Privacy Board Legal Committee. </P>
                                    <P>(3) Serve as a member of the Defense Privacy Board, the Defense Data Integrity Board, and the Defense Privacy Board Legal Committee (310.9). </P>
                                    <P>(d) The Secretaries of the Military Departments and the Heads of the Other DoD Components, except as noted in § 310.5(k), shall: </P>
                                    <P>(1) Provide adequate funding and personnel to establish and support an effective DoD Privacy Program, to include the appointment of a senior official to serve as the principal point of contact (POC) for DoD Privacy Program matters. </P>
                                    <P>(2) Establish procedures, as well as rules of conduct, necessary to implement this part and DoD 5400.11-R to ensure compliance with the requirements of 5 U.S.C. 552a and OMB Circular A-130. </P>
                                    <P>(3) Conduct training, consistent with the requirements of DoD 5400.11-R, on the provisions of this part, 5 U.S.C. 552a, OMB Circular A-130, and DoD 5400.11-R, for assigned, employed and detailed, to include contractor, personnel and individuals having primary responsibility for implementing the DoD Privacy Program. </P>
                                    <P>(4) Ensure all Component legislative proposals, policies, or programs having privacy implications, such as the DoD Privacy Impact Assessment Program, are evaluated to ensure consistency with the information privacy principles of this part and DoD 5400.11-R. </P>
                                    <P>(5) Assess the impact of technology on the privacy of personal information and, when feasible, adopt privacy-enhancing technology both to preserve and protect personal information contained in Component systems of records and to permit auditing of compliance with the requirements of this part and DoD 5400.11-R. </P>
                                    <P>(6) Ensure the DoD Privacy Program periodically shall be reviewed by the Inspectors General or other officials, who shall have specialized knowledge of the DoD Privacy Program. </P>
                                    <P>(7) Submit reports, consistent with the requirements of DoD 5400.11-R, as mandated by 5 U.S.C. 552a and OMB Circular A-130, and DoD Directive 5500.1, and as otherwise directed by the DPO.</P>
                                    <P>
                                        (e) The Secretaries of the Military Departments shall provide support to the Combatant Commands, as identified in DoD Directive 5100.3,
                                        <SU>7</SU>
                                        <FTREF/>
                                         in the administration of the DoD Privacy Program. 
                                    </P>
                                    <FTNT>
                                        <P>
                                            <SU>7</SU>
                                             See footnote 1 to § 310.1.
                                        </P>
                                    </FTNT>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 310.7 </SECTNO>
                                    <SUBJECT>Information requirements. </SUBJECT>
                                    <P>The reporting requirements in § 310.6(d)(7) are assigned Report Control Symbol DD-DA&amp;M(A)1379. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 310.8 </SECTNO>
                                    <SUBJECT>Rules of conduct. </SUBJECT>
                                    <P>(a) DoD personnel shall: </P>
                                    <P>(1) Take such actions, as considered appropriate, to ensure that personal information contained in a system of records, to which they have access to or are using incident to the conduct of official business, shall be protected so that the security and confidentiality of the information shall be preserved. </P>
                                    <P>(2) Not disclose any personal information contained in any system of records except as authorized by DoD 5400.11-R or other applicable law or regulation. Personnel willfully making such a disclosure when knowing that disclosure is prohibited are subject to possible criminal penalties and/or administrative sanctions. </P>
                                    <P>(3) Report any unauthorized disclosures of personal information from a system of records or the maintenance of any system of records that are not authorized by this part to the applicable Privacy POC for his or her DoD Component. </P>
                                    <P>(b) DoD System Managers for each system of records shall: </P>
                                    <P>(1) Ensure that all personnel who either shall have access to the system of records or who shall develop or supervise procedures for handling records in the system of records shall be aware of their responsibilities and are properly trained to safeguard personal information being collected and maintained under the DoD Privacy Program. </P>
                                    <P>
                                        (2) Prepare promptly any required new, amended, or altered system notices for the system of records and submit them through their DoD Component Privacy POC to the DPO for publication in the 
                                        <E T="04">Federal Register</E>
                                        . 
                                    </P>
                                    <P>
                                        (3) Not maintain any official files on individuals which are retrieved by name or other personal identifier without first 
                                        <PRTPAGE P="18762"/>
                                        ensuring that a notice for the system of records shall have been published in the 
                                        <E T="04">Federal Register</E>
                                        . Any official who willfully maintains a system of records without meeting the publication requirements, as prescribed by 5 U.S.C. 552a, OMB Circular A-130, and DoD 5400.11-R, is subject to possible criminal penalties and/or administrative sanctions. 
                                    </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 310.9 </SECTNO>
                                    <SUBJECT>Privacy boards and office, composition and responsibilities. </SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">The Defense Privacy Board</E>
                                        —(1) 
                                        <E T="03">Membership.</E>
                                         The Board shall consist of the DA&amp;M, OSD, who shall serve as the Chair; the Director of the DPO, DA&amp;M, who shall serve as the Executive Secretary and as a member; the representatives designated by the Secretaries of the Military Departments; and the following officials or their designees: the Deputy Under Secretary of Defense for Program Integration (DUSD(PI)); the Assistant Secretary of Defense for Health Affairs; the Assistant Secretary of Defense for Networks and Information Integration (ASD) (NII)/Chief Information Officer (CIO); the Director, Executive Services and Communications Directorate, WHS; the GC, DoD; and the Director for Information Technology Management Directorate (ITMD), WHS. The designees also may be the principal POC for the DoD Component for privacy matters. 
                                    </P>
                                    <P>
                                        (2) 
                                        <E T="03">Responsibilities.</E>
                                         (i) The Board shall have oversight responsibility for implementation of the DoD Privacy Program. It shall ensure the policies, practices, and procedures of that Program are premised on the requirements of 5 U.S.C. 552a and OMB Circular A-130, as well as other pertinent authority, and the Privacy Programs of the DoD Component are consistent with, and in furtherance of, the DoD Privacy Program. 
                                    </P>
                                    <P>(ii) The Board shall serve as the primary DoD policy forum for matters involving the DoD Privacy Program, meeting as necessary, to address issues of common concern so as to ensure uniform and consistent policy shall be adopted and followed by the DoD Components. The Board shall issue advisory opinions as necessary on the DoD Privacy Program so as to promote uniform and consistent application of 5 U.S.C. 552a, OMB Circular A-130, and DoD 5400.11-R. </P>
                                    <P>(iii) Perform such other duties as determined by the Chair or the Board. </P>
                                    <P>
                                        (b) 
                                        <E T="03">The Defense Data Integrity Board</E>
                                        —(1) 
                                        <E T="03">Membership.</E>
                                         The Board shall consist of the DA&amp;M, OSD, who shall serve as the Chair; the Director of the DPO, DA&amp;M, who shall serve as the Executive Secretary; and the following officials or their designees: the representatives designated by the Secretaries of the Military Departments; the DUSD(PI); the (ASD) (NII)/CIO; the GC, DoD; the Inspector General, DoD; the ITMD, WHS; and the Director, Defense Manpower Data Center. The designees also may be the principal points of contact for the DoD Component for privacy matters. 
                                    </P>
                                    <P>
                                        (2) 
                                        <E T="03">Responsibilities.</E>
                                         (i) The Board shall oversee and coordinate, consistent with the requirements of 5 U.S.C. 552a, OMB Circular A-130, and DoD 5400.11-R, all computer matching programs involving personal records contained in system of records maintained by the DoD Components. 
                                    </P>
                                    <P>(ii) The Board shall review and approve all computer matching agreements between the Department of Defense and the other Federal, State or local governmental agencies, as well as memoranda of understanding when the match is internal to the Department of Defense, to ensure, under 5 U.S.C. 552a, OMB Circular A-130, and DoD 5400.11-R, appropriate procedural and due process requirements shall have been established before engaging in computer matching activities. </P>
                                    <P>
                                        (c) 
                                        <E T="03">The Defense Privacy Board Legal Committee</E>
                                        —(1) 
                                        <E T="03">Membership.</E>
                                         The Committee shall consist of the Director, DPO, DA&amp;M, who shall serve as the Chair and the Executive Secretary; the GC, DoD, or designee; and civilian and/or military counsel from each of the DoD Components. The General Counsels (GCs) and The Judge Advocates General of the Military Departments shall determine who shall provide representation for their respective Department to the Committee. This does not preclude representation from each office. The GCs of the other DoD Components shall provide legal representation to the Committee. Other DoD civilian or military counsel may be appointed by the Executive Secretary, after coordination with the DoD Component concerned, to serve on the Committee on those occasions when specialized knowledge or expertise shall be required. 
                                    </P>
                                    <P>
                                        (2) 
                                        <E T="03">Responsibilities.</E>
                                         (i) The Committee shall serve as the primary legal forum for addressing and resolving all legal issues arising out of or incident to the operation of the DoD Privacy Program. 
                                    </P>
                                    <P>(ii) The Committee shall consider legal questions regarding the applicability of 5 U.S.C. 552a, OMB Circular A-130, and DoD 5400.11-R and questions arising out of or as a result of other statutory and regulatory authority, to include the impact of judicial decisions, on the DoD Privacy Program. The Committee shall provide advisory opinions to the Defense Privacy Board and, on request, to the DoD Components. </P>
                                    <P>
                                        (d) 
                                        <E T="03">The DPO</E>
                                        —(1) 
                                        <E T="03">Membership.</E>
                                         It shall consist of a Director and a staff. The Director also shall serve as the Executive Secretary and a member of the Defense Privacy Board; as the Executive Secretary to the Defense Data Integrity Board; and as the Chair and the Executive Secretary to the Defense Privacy Board Legal Committee. 
                                    </P>
                                    <P>
                                        (2) 
                                        <E T="03">Responsibilities.</E>
                                         (i) Manage activities in support of the Privacy Program oversight responsibilities of the DA&amp;M. 
                                    </P>
                                    <P>(ii) Provide operational and administrative support to the Defense Privacy Board, the Defense Data Integrity Board, and the Defense Privacy Board Legal Committee. </P>
                                    <P>(iii) Direct the day-to-day activities of the DoD Privacy Program. </P>
                                    <P>(iv) Provide guidance and assistance to the DoD Components in their implementation and execution of the DoD Privacy Program. </P>
                                    <P>(v) Review DoD legislative, regulatory, and other policy proposals which implicate information privacy issues relating to the Department's collection, maintenance, use, or dissemination of personal information, to include any testimony and comments having such implications under DoD Directive 5500.1. </P>
                                    <P>
                                        (vi) Review proposed new, altered, and amended systems of records, to include submission of required notices for publication in the 
                                        <E T="04">Federal Register</E>
                                         and, when required, providing advance notification to the OMB and the Congress, consistent with 5 U.S.C. 552a, OMB Circular A-130, and DoD 5400.11-R. 
                                    </P>
                                    <P>(vii) Review proposed DoD Component privacy rulemaking, to include submission of the rule to the Office of the Federal Register for publication and providing to the OMB and the Congress reports, consistent with 5 U.S.C. 552a, OMB Circular A-130, and DoD 5400.11-R. </P>
                                    <P>
                                        (viii) Develop, coordinate, and maintain all DoD computer matching agreements, to include the submission of required match notices for publication in the 
                                        <E T="04">Federal Register</E>
                                         and the provision of advance notification to the OMB and the Congress, consistent with 5 U.S.C. 552a, OMB Circular A-130, and DoD 5400.11-R. 
                                    </P>
                                    <P>(ix) Provide advice and support to the DoD Components to ensure: </P>
                                    <P>
                                        (A) All information requirements developed to collect or maintain personal data conform to DoD Privacy Program standards; 
                                        <PRTPAGE P="18763"/>
                                    </P>
                                    <P>(B) Appropriate procedures and safeguards shall be developed, implemented, and maintained to protect personal information when it is stored in either a manual and/or automated system of records or transferred by electronic or non-electronic means; and </P>
                                    <P>(C) Specific procedures and safeguards shall be developed and implemented when personal data is collected and maintained for research purposes. </P>
                                    <P>(x) Serve as the principal POC for coordination of privacy and related matters with the OMB and other Federal, State, and local governmental agencies. </P>
                                    <P>(xi) Compile and submit the “Biennial Matching Activity Report” to the OMB as required by OMB Circular A-130 and DoD 5400.11-R, and the Quarterly and Annual Federal Information Security Management Agency (FISMA) Privacy Reports, as required by 44 U.S.C. 3544(c), such other reports as may be required. </P>
                                    <P>(xii) Update and maintain this part and DoD 5400.11-R. </P>
                                </SECTION>
                            </SUBPART>
                            <SUBPART>
                                <HD SOURCE="HED">Subpart B—Systems of Records </HD>
                                <SECTION>
                                    <SECTNO>§ 310.10 </SECTNO>
                                    <SUBJECT>General. </SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">System of Records.</E>
                                         To be subject to the provisions of this part, a “system of records” must: 
                                    </P>
                                    <P>(1) Consist of “records” (as defined in 310.4(r)) that are retrieved by the name of an individual or some other personal identifier; and </P>
                                    <P>(2) Be under the control of a DoD Component. </P>
                                    <P>
                                        (b) 
                                        <E T="03">Retrieval practices.</E>
                                         (1) Records in a group of records that MAY be retrieved by a name or personal identifier are not covered by this part even if the records contain personal data and are under control of a DoD Component. The records MUST be retrieved by name or other personal identifier to become a system of records for the purpose of this part. 
                                    </P>
                                    <P>(i) When records are contained in an automated (Information Technology) system that is capable of being manipulated to retrieve information about an individual, this does not automatically transform the system into a system of records as defined in this part. </P>
                                    <P>(ii) In determining whether an automated system is a system of records that is subject to this part, retrieval policies and practices shall be evaluated. If DoD Component policy is to retrieve personal information by the name or other unique personal identifier, it is a system of records. If DoD Component policy prohibits retrieval by name or other identifier, but the actual practice of the Component is to retrieve information by name or identifier, even if done infrequently, it is a system of records. </P>
                                    <P>(2) If records are retrieved by name or personal identifier, a system notice must be submitted in accordance with § 310.33. </P>
                                    <P>(3) If records are not retrieved by name or personal identifier but then are rearranged in such a manner that they are retrieved by name or personal identifier, a new systems notice must be submitted in accordance with § 310.33. </P>
                                    <P>(4) If records in a system of records are rearranged so that retrieval is no longer by name or other personal identifier, the records are no longer subject to this part and the system notice for the records shall be deleted in accordance with § 310.34. </P>
                                    <P>
                                        (c) 
                                        <E T="03">Relevance and necessity.</E>
                                         Information or records about an individual shall only be maintained in a system of records that is relevant and necessary to accomplish a DoD Component purpose required by a Federal statute or an Executive Order. 
                                    </P>
                                    <P>
                                        (d) 
                                        <E T="03">Authority to establish systems of records.</E>
                                         Identify the specific statute or the Executive Order that authorizes maintaining personal information in each system of records. The existence of a statute or Executive Order mandating the maintenance of a system of records does not abrogate the responsibility to ensure that the information in the system of records is relevant and necessary. If a statute or Executive Order does not expressly direct the creation of a system of records, but the establishment of a system of records is necessary in order to discharge the requirements of the statute or Executive Order, the statute or Executive Order shall be cited as authority. 
                                    </P>
                                    <P>
                                        (e) 
                                        <E T="03">Exercise of First Amendment rights.</E>
                                         (1) Do not maintain any records describing how an individual exercises his or her rights guaranteed by the First Amendment of the U.S. Constitution except when: 
                                    </P>
                                    <P>(i) Expressly authorized by Federal statute;</P>
                                    <P>(ii) Expressly authorized by the individual; or </P>
                                    <P>(iii) Maintenance of the information is pertinent to and within the scope of an authorized law enforcement activity. </P>
                                    <P>(2) First Amendment rights include, but are not limited to, freedom of religion, freedom of political beliefs, freedom of speech, freedom of the press, the right to assemble, and the right to petition. </P>
                                    <P>
                                        (f) 
                                        <E T="03">System Manager's evaluation.</E>
                                         (1) Evaluate the information to be included in each new system before establishing the system and evaluate periodically the information contained in each existing system of records for relevancy and necessity. Such a review shall also occur when a system notice alteration or amendment is prepared (see § 310.33 and § 310.34). 
                                    </P>
                                    <P>(2) Consider the following: </P>
                                    <P>(i) The relationship of each item of information retained and collected to the purpose for which the system is maintained; </P>
                                    <P>(ii) The specific impact on the purpose or mission of not collecting each category of information contained in the system; </P>
                                    <P>(iii) The possibility of meeting the informational requirements through use of information not individually identifiable or through other techniques, such as sampling; </P>
                                    <P>(iv) The length of time each item of personal information must be retained; </P>
                                    <P>(v) The cost of maintaining the information; and </P>
                                    <P>(vi) The necessity and relevancy of the information to the purpose for which it was collected. </P>
                                    <P>
                                        (g) 
                                        <E T="03">Discontinued information requirements.</E>
                                         (1) Stop collecting immediately any category or item of personal information for which retention is no longer justified. Also delete this information from existing records, when feasible. 
                                    </P>
                                    <P>(2) Do not destroy any records that must be retained in accordance with disposal authorizations established under 44 U.S.C. 3303a, Examination by Archivist of Lists and Schedules of Records Lacking Preservation Value; Disposal of Records.” </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 310.11 </SECTNO>
                                    <SUBJECT>Standards of accuracy. </SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">Accuracy of information maintained.</E>
                                         Maintain all personal information used or may be used to make any determination about an individual with such accuracy, relevance, timeliness, and completeness as is reasonably necessary to ensure fairness to the individual in making any such determination. 
                                    </P>
                                    <P>
                                        (b) 
                                        <E T="03">Accuracy determinations before dissemination.</E>
                                         Before disseminating any personal information from a system of records to any person outside the Department of Defense, other than a Federal Agency, make reasonable efforts to ensure the information to be disclosed is accurate, relevant, timely, and complete for the purpose it is being maintained (see § 310.21(d)). 
                                    </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 310.12 </SECTNO>
                                    <SUBJECT>Government contractors. </SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">Applicability to government contractors.</E>
                                         (1) When a DoD Component contract requires the operation or maintenance of a system of records or a portion of a system of records or 
                                        <PRTPAGE P="18764"/>
                                        requires the performance of any activities associated with maintaining a system of records, including the collection, use, and dissemination of records, the record system or the portion of the record system affected are considered to be maintained by the DoD Component and are subject to this part. The Component is responsible for applying the requirements of this part to the contractor. The contractor and its employees are to be considered employees of the DoD Component for purposes of the criminal provisions of 5 U.S.C 552a(i) during the performance of the contract. Consistent with the Federal Acquisition Regulation (FAR), Part 24.1, contracts requiring the maintenance or operation of a system of records or the portion of a system of records shall include in the solicitation and resulting contract such terms as are prescribed by the FAR. 
                                    </P>
                                    <P>(2) If the contractor must use, have access to, or disseminate individually identifiable information subject to this part in order to perform any part of a contract, and the information would have been collected, maintained, used, or disseminated by the DoD Component but for the award of the contract, these contractor activities are subject to this part. </P>
                                    <P>(3) The restriction in paragraphs (a)(1) and (2) of this section do not apply to records: </P>
                                    <P>(i) Established and maintained to assist in making internal contractor management decisions, such as records maintained by the contractor for use in managing the contract; </P>
                                    <P>(ii) Maintained as internal contractor employee records even when used in conjunction with providing goods and services to the Department of Defense; or </P>
                                    <P>(iii) Maintained as training records by an educational organization contracted by a DoD Component to provide training when the records of the contract students are similar to and commingled with training records of other students (for example, admission forms, transcripts, academic counseling and similar records). </P>
                                    <P>(iv) Maintained by a consumer reporting agency to which records have been disclosed under contract in accordance with the Federal Claims Collection Act of 1966, 31 U.S.C. 3711(e). </P>
                                    <P>(v) Maintained by the contractor incident to normal business practices and operations. </P>
                                    <P>(4) The DoD Components shall publish instructions that: </P>
                                    <P>(i) Furnish DoD Privacy Program guidance to their personnel who solicit, award, or administer Government contracts; </P>
                                    <P>(ii) Inform prospective contractors of their responsibilities, and provide training as appropriate, regarding the DoD Privacy Program; and </P>
                                    <P>(iii) Establish an internal system of contractor performance review to ensure compliance with the DoD Privacy Program. </P>
                                    <P>
                                        (b) 
                                        <E T="03">Contracting procedures.</E>
                                         The Defense Acquisition Regulations Council shall develop the specific policies and procedures to be followed when soliciting bids, awarding contracts or administering contracts that are subject to this part. 
                                    </P>
                                    <P>
                                        (c) 
                                        <E T="03">Contractor compliance.</E>
                                         Through the various contract surveillance programs, ensure contractors comply with the procedures established in accordance with § 310.12(b). 
                                    </P>
                                    <P>
                                        (d) 
                                        <E T="03">Disclosure of records to contractors.</E>
                                         Disclosure of records contained in a system of records by a DoD Component to a contractor for use in the performance of a DoD contract is considered a disclosure within the Department of Defense (see § 310.21(b)). The contractor is considered the agent of the contracting DoD Component and to be maintaining and receiving the records for that Component. 
                                    </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 310.13 </SECTNO>
                                    <SUBJECT>Safeguarding personal information. </SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">General responsibilities.</E>
                                         DoD Components shall establish appropriate administrative, technical and physical safeguards to ensure that the records in each system of records are protected from unauthorized access, alteration, or disclosure and that their confidentiality is preserved and protected. Records shall be protected against reasonably anticipated threats or hazards that could result in substantial harm, embarrassment, inconvenience, or unfairness to any individual about whom information is kept. 
                                    </P>
                                    <P>
                                        (b) 
                                        <E T="03">Minimum standards.</E>
                                         (1) Tailor system safeguards to conform to the type of records in the system, the sensitivity of the personal information stored, the storage medium used and, to a degree, the number of records maintained. 
                                    </P>
                                    <P>(2) Treat all unclassified records that contain personal information that normally would be withheld from the public under Freedom of Information Exemption Numbers 6 and 7 of 286.12, subpart C of 32 CFR part 286 (“DoD Freedom of Information Act Program”) as “For Official Use Only,” and safeguard them accordingly, in accordance with DoD 5200.1-R even if they are not actually marked “For Official Use Only.” </P>
                                    <P>(3) Personal information that does not meet the criteria discussed in paragraph (b)(2) of this section shall be accorded protection commensurate with the nature and type of information involved. </P>
                                    <P>(4) Special administrative, physical, and technical procedures are required to protect data that is stored or processed in an information technology system to protect against threats unique to an automated environment (see Appendix A). </P>
                                    <P>(5) Tailor safeguards specifically to the vulnerabilities of the system. </P>
                                    <P>
                                        (c) 
                                        <E T="03">Records disposal.</E>
                                         (1) Dispose of records containing personal data so as to prevent inadvertent compromise. Disposal methods are those approved by the Component or the National Institute of Standards and Technology. For paper records, disposal methods, such as tearing, burning, melting, chemical decomposition, pulping, pulverizing, shredding, or mutilation are acceptable. For electronic records, and media, disposal methods, such as overwriting, degaussing, disintegration, pulverization, burning, melting, incineration, shredding or sanding, are acceptable. 
                                    </P>
                                    <P>(2) Disposal methods are considered adequate if the personal data is rendered unrecognizable or beyond reconstruction. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 310.14 </SECTNO>
                                    <SUBJECT>Notification when information is lost, stolen, or compromised. </SUBJECT>
                                    <P>(a) If records containing personal information are lost, stolen, or compromised, the potential exists that the records may be used for unlawful purposes, such as identity theft, fraud, stalking, etc. The personal impact on the affected individual may be severe if the records are misused. To assist the individual, the Component shall promptly notify the individual of any loss, theft, or compromise (See also, § 310.50 for reporting of the breach to Senior Component Official for Privacy and the Defense Privacy Office). </P>
                                    <P>(1) The notification shall be made whenever a breach occurs that involves personal information pertaining to a service member, civilian employee (appropriated or non-appropriated fund), military retiree, family member, DoD contractor, other persons that are affiliated with the Component (e.g., volunteer), and/or any other member of the public on whom information is maintained by the Component or by a contractor on behalf of the Component. </P>
                                    <P>
                                        (2) The notification shall be made as soon as possible, but not later than 10 working days after the loss, theft, or compromise is discovered and the identities of the individuals ascertained. 
                                        <PRTPAGE P="18765"/>
                                    </P>
                                    <P>(i) The 10 day period begins to run after the Component is able to determine the identities of the individuals whose records were lost. </P>
                                    <P>(ii) If the Component is only able to identify some but not all of the affected individuals, notification shall be given to those that can be identified with follow-up notifications made to those subsequently identified. </P>
                                    <P>(iii) If the Component cannot readily identify the affected individuals or will not be able to identify the individuals, the Component shall provide a generalized notice to the potentially impacted population by whatever means the Component believes is most likely to reach the affected individuals. </P>
                                    <P>(3) When personal information is maintained by a DoD contractor on behalf of the Component, the contractor shall notify the Component immediately upon discovery that a loss, theft or compromise has occurred. </P>
                                    <P>(i) The Component shall determine whether the Component or the contractor shall make the required notification. </P>
                                    <P>(ii) If the contractor is to notify the impacted population, it shall submit the notification letters to the Component for review and approval. The Component shall coordinate with the Contractor to ensure the letters meet the requirements of § 310.14. </P>
                                    <P>(4) Subject to paragraph (a)(2) of this section, the Component shall inform the Deputy Secretary of Defense of the reasons why notice was not provided to the individuals or the affected population within the 10-day period. </P>
                                    <P>(i) If for good cause (e.g., law enforcement authorities request delayed notification as immediate notification will jeopardize investigative efforts), notice can be delayed, but the delay shall only be for a reasonable period of time. In determining what constitutes a reasonable period of delay, the potential harm to the individual must be weighed against the necessity for delayed notification. </P>
                                    <P>(ii) The required notification shall be prepared and forwarded to the Senior Component Official for Privacy who shall forward it to the Defense Privacy Office. The Defense Privacy Office, in coordination with the Office of the Under Secretary of Defense for Personnel and Readiness, shall forward the notice to the Deputy Secretary. </P>
                                    <P>(5) The notice to the individual, at a minimum, shall include the following: </P>
                                    <P>(i) The individuals shall be advised of what specific data was involved. It is insufficient to simply state that personal information has been lost. Where names, social security numbers, and dates of birth are involved, it is critical that the individual be advised that these data elements potentially have been compromised. </P>
                                    <P>(ii) The individual shall be informed of the facts and circumstances surrounding the loss, theft, or compromise. The description of the loss should be sufficiently detailed so that the individual clearly understands how the compromise occurred. </P>
                                    <P>
                                        (iii) The individual shall be informed of what protective actions the Component is taking or the individual can take to mitigate against potential future harm. The Component should refer the individual to the Federal Trade Commission's public Web site on identity theft at 
                                        <E T="03">http://www.consumer.gov/idtheft/con_steps.htm.</E>
                                         The site provides valuable information as to what steps individuals can take to protect themselves if their identities potentially have been or are stolen. 
                                    </P>
                                    <P>(iv) A sample notification letter is at Appendix B. </P>
                                    <P>(b) The notification shall be made whether or not the personal information is contained in a system of records (See § 310.10(a)). </P>
                                </SECTION>
                            </SUBPART>
                            <SUBPART>
                                <HD SOURCE="HED">Subpart C—Collecting Personal Information </HD>
                                <SECTION>
                                    <SECTNO>§ 310.15 </SECTNO>
                                    <SUBJECT>General considerations. </SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">Collect directly from the individual.</E>
                                         Collect to the greatest extent practicable personal information directly from the individual to whom it pertains if the information may result in adverse determination about an individual's rights, privileges, or benefits under any Federal program. 
                                    </P>
                                    <P>
                                        (b) 
                                        <E T="03">Collecting social security numbers (SSNs).</E>
                                         (1) It is unlawful for any Federal, State, or local governmental agency to deny an individual any right, benefit, or privilege provided by law because the individual refuses to provide his or her SSN. However, if a Federal statute requires the SSN be furnished or if the SSN is furnished to a DoD Component maintaining a system of records in existence that was established and in operation before January 1, 1975, and the SSN was required under a statute or regulation adopted prior to this date for purposes of verifying the identity of an individual, this restriction does not apply. 
                                    </P>
                                    <P>(2) When an individual is requested to provide his or her SSN, he or she must be told: </P>
                                    <P>(i) What uses will be made of the SSN; </P>
                                    <P>(ii) The statute, regulation, or rule authorizing the solicitation of the SSN; and </P>
                                    <P>(iii) Whether providing the SSN is voluntary or mandatory. </P>
                                    <P>(3) Include in any systems notice for any system of records that contains SSNs a statement indicating the authority for maintaining the SSN. </P>
                                    <P>(4) E.O. 9397,”Numbering System for Federal Accounts Relating to Individual Persons”, November 30, 1943, authorizes solicitation and use of SSNs as a numerical identifier for Federal personnel that are identified in most Federal record systems. However, it does not constitute authority for mandatory disclosure of the SSN. </P>
                                    <P>(5) Upon entrance into military service or civilian employment with the Department of Defense, individuals are asked to provide their SSNs. The SSN becomes the service or employment number for the individual and is used to establish personnel, financial, medical, and other official records. The notification in paragraph (b)(2) of this section shall be provided the individual when originally soliciting his or her SSN. The notification is not required if an individual is requested to furnish his SSN for identification purposes and the SSN is solely used to verify the SSN that is contained in the records. However, if the SSN is solicited and retained for any purposes other than verifying the existing SSN in the records, the requesting official shall provide the individual the notification required by paragraph (b)(2) of this section. </P>
                                    <P>(6) Components shall ensure that the SSN is only collected when there is a demonstrated need for collection. If collection is not essential for the purposes for which the record or records are being maintained, it should not be solicited. </P>
                                    <P>(7) DoD Components shall continually review their use of the SSN to determine whether such use can be eliminated, restricted, or concealed in Component business processes, systems and paper and electronic forms. While use of the SSN may be essential for program integrity and national security when information about an individual is disclosed outside the DoD, it may not be as critical when the information is being used for internal Departmental purposes. </P>
                                    <P>
                                        (c) 
                                        <E T="03">Collecting personal information from third parties.</E>
                                         When information being solicited is of an objective nature and is not subject to being altered, the information should first be collected from the individual. But it may not be practicable to collect personal information first from the individual in all cases. Some examples of this are: 
                                    </P>
                                    <P>
                                        (1) Verification of information through third-party sources for security 
                                        <PRTPAGE P="18766"/>
                                        or employment suitability determinations; 
                                    </P>
                                    <P>(2) Seeking third-party opinions such as supervisor comments as to job knowledge, duty performance, or other opinion-type evaluations; </P>
                                    <P>(3) When obtaining information first from the individual may impede rather than advance an investigative inquiry into the actions of the individual; and </P>
                                    <P>(4) Contacting a third party at the request of the individual to furnish certain information such as exact periods of employment, termination dates, copies of records, or similar information. </P>
                                    <P>(d) Privacy Act Statements. (1) When an individual is requested to furnish personal information about himself or herself for inclusion in a system of records, a Privacy Act Statement is required regardless of the medium used to collect the information (forms, personal interviews, telephonic interviews, or other methods). The Privacy Act Statement consists of the elements set forth in paragraph (d)(2)of this section. The statement enables the individual to make an informed decision whether to provide the information requested. If the personal information solicited is not to be incorporated into a system of records, the statement need not be given. However, personal information obtained without a Privacy Act Statement shall not be incorporated into any system of records. When soliciting SSNs for any purpose, see paragraph (b)(2) of this section. </P>
                                    <P>(2) The Privacy Act Statement shall include: </P>
                                    <P>(i) The Federal statute or Executive Order that authorizes collection of the requested information (See § 310.10(d)). </P>
                                    <P>(ii) The principal purpose or purposes for which the information is to be used; </P>
                                    <P>(iii) The routine uses that will be made of the information (See § 310.22(d)); </P>
                                    <P>(iv) Whether providing the information is voluntary or mandatory (See paragraph (e) of this section); and </P>
                                    <P>(v) The effects on the individual if he or she chooses not to provide the requested information. </P>
                                    <P>(3) The Privacy Act Statement shall be concise, current, and easily understood. </P>
                                    <P>(4) The Privacy Act statement may appear as a public notice (sign or poster), conspicuously displayed in the area where the information is collected, such as at check-cashing facilities or identification photograph facilities (but see § 310.16(a)). </P>
                                    <P>(5) The individual normally is not required to sign the Privacy Act Statement. </P>
                                    <P>(6) The individual shall be provided a written copy of the Privacy Act Statement upon request. This must be done regardless of the method chosen to furnish the initial advisement. </P>
                                    <P>
                                        (e) 
                                        <E T="03">Mandatory as opposed to voluntary disclosures.</E>
                                         Include in the Privacy Act Statement specifically whether furnishing the requested personal data is mandatory or voluntary. A requirement to furnish personal data is mandatory only when the DoD Component is authorized to impose a penalty on the individual for failure to provide the requested information. If a penalty cannot be imposed, disclosing the information is always voluntary. 
                                    </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 310.16 </SECTNO>
                                    <SUBJECT>Forms. </SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">DoD Forms.</E>
                                         (1) DoD Instruction 7750.7 
                                        <SU>8</SU>
                                        <FTREF/>
                                         provides guidance for preparing Privacy Act Statements for use with forms (see also paragraph (b) of this section). 
                                    </P>
                                    <FTNT>
                                        <P>
                                            <SU>8</SU>
                                             See footnote 1 to § 310.1.
                                        </P>
                                    </FTNT>
                                    <P>(2) When forms are used to collect personal information, the Privacy Act Statement shall appear as follows (listed in the order of preference): </P>
                                    <P>(i) In the body of the form, preferably just below the title so that the reader will be advised of the contents of the statement before he or she begins to complete the form; </P>
                                    <P>(ii) On the reverse side of the form with an appropriate annotation under the title giving its location; </P>
                                    <P>(iii) On a tear-off sheet attached to the form; or </P>
                                    <P>(iv) As a separate supplement to the form. </P>
                                    <P>
                                        (b) 
                                        <E T="03">Forms issued by non-DoD activities.</E>
                                         (1) Forms subject to the Privacy Act issued by other Federal Agencies must have a Privacy Act Statement. Always ensure the statement prepared by the originating Agency is adequate for the purpose for which the form shall be used by the DoD activity. If the Privacy Act Statement provided is inadequate, the DoD Component concerned shall prepare a new statement or a supplement to the existing statement before using the form. 
                                    </P>
                                    <P>(2) Forms issued by agencies not subject to the Privacy Act (State, municipal, and other local agencies) do not contain Privacy Act Statements. Before using a form prepared by such agencies to collect personal data subject to this part, an appropriate Privacy Act Statement must be added. </P>
                                </SECTION>
                            </SUBPART>
                            <SUBPART>
                                <HD SOURCE="HED">Subpart D—Access by Individuals </HD>
                                <SECTION>
                                    <SECTNO>§ 310.17 </SECTNO>
                                    <SUBJECT>Individual access to personal information. </SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">Individual access.</E>
                                         (1) The access provisions of this part are intended for use by individuals who seek access to records about themselves that are maintained in a system of records. Release of personal information to individuals under this part is not considered public release of the information. 
                                    </P>
                                    <P>(2) Make available to the individual to whom the record pertains all of the personal information contained in the system of records except where access may be denied pursuant to an exemption claimed for the system (see subpart F to this part). However, when the access provisions of this subpart are not available to the individual due to a claimed exemption, the request shall be processed to provide information that is disclosable pursuant to the DoD Freedom of Information Act program (see 32 CFR, part 286). </P>
                                    <P>
                                        (b) 
                                        <E T="03">Individual requests for access.</E>
                                         Individuals shall address requests for access to personal information in a system of records to the system manager or to the office designated in the DoD Component procedural rules or the system notice. 
                                    </P>
                                    <P>
                                        (c) 
                                        <E T="03">Verification of identity.</E>
                                         (1) Before granting access to personal data, an individual may be required to provide reasonable proof of his or her identity. 
                                    </P>
                                    <P>(2) Identity verification procedures shall not: </P>
                                    <P>(i) Be so complicated as to discourage unnecessarily individuals from seeking access to information about themselves; or </P>
                                    <P>(ii) Be required of an individual seeking access to records that normally would be available under the DoD Freedom of Information Act Program (see 32 CFR, part 286). </P>
                                    <P>(iii) When an individual seeks personal access to records pertaining to themselves in person, proof of identity is normally provided by documents that an individual ordinarily possesses, such as employee and military identification cards, driver's license, other licenses, permits or passes used for routine identification purposes. </P>
                                    <P>
                                        (iv) When access is requested by mail, identity verification may consist of the individual providing certain minimum identifying data, such as full name, date and place of birth, or such other personal information necessary to locate the record sought and information that is ordinarily only known to the individual. If the information sought is of a sensitive nature, additional identifying data may be required. An unsworn declaration under penalty of perjury (28 U.S.C. 1746, “Unsworn Declaration under Penalty of Perjury”) or notarized signatures are acceptable as a means of proving the identity of the individual. 
                                        <PRTPAGE P="18767"/>
                                    </P>
                                    <P>(A) If an unsworn declaration is executed within the United States, its territories, possessions, or commonwealths, it shall read “I declare (or certify, verify, or state) under penalty of perjury that the foregoing is true and correct. Executed on (date). (Signature).”</P>
                                    <P>(B) If an unsworn declaration is executed outside the United States, it shall read “I declare (or certify, verify, or state) under penalty of perjury under the laws of the United States of America that the foregoing is true and correct. Executed on (date). (Signature).” </P>
                                    <P>(v) If an individual wishes to be accompanied by a third party when seeking access to his or her records or to have the records released directly to a third party, the individual may be required to furnish a signed access authorization granting the third-party access. </P>
                                    <P>(vi) An individual shall not be refused access to his or her record solely because he or she refuses to divulge his or her SSN unless the SSN is the only method by which retrieval can be made. (See § 310.15(b).) </P>
                                    <P>(vii) The individual is not required to explain or justify his or her need for access to any record under this part. </P>
                                    <P>(viii) Only a denial authority may deny access and the denial must be in writing and contain the information required by 310.18. </P>
                                    <P>
                                        (d) 
                                        <E T="03">Granting individual access to records.</E>
                                         (1) Grant the individual access to the original record or an exact copy of the original record without any changes or deletions, except when deletions have been made in accordance with paragraph (e) of this Section. For the purpose of granting access, a record that has been amended under § 310.19(b)is considered to be the original. See paragraph (e) of this Section for the policy regarding the use of summaries and extracts. 
                                    </P>
                                    <P>(2) Provide exact copies of the record when furnishing the individual copies of records under this part. </P>
                                    <P>(3) Explain in terms understood by the requestor any record or portion of a record that is not clear. </P>
                                    <P>
                                        (e) 
                                        <E T="03">Illegible, incomplete, or partially exempt records.</E>
                                         (1) Do not deny an individual access to a record or a copy of a record solely because the physical condition or format of the record does not make it readily available (for example, deteriorated state or on magnetic tape). Either prepare an extract or recopy the document exactly. 
                                    </P>
                                    <P>(2) If a portion of the record contains information that is exempt from access, an extract or summary containing all of the information in the record that is releasable shall be prepared. </P>
                                    <P>(3) When the physical condition of the record or its state makes it necessary to prepare an extract for release, ensure the extract can be understood by the requester. </P>
                                    <P>(4) Explain to the requester all deletions or changes to the records. </P>
                                    <P>
                                        (f) 
                                        <E T="03">Access to medical records.</E>
                                         (1) Access to medical records is not only governed by the access provisions of this part but also by the access provisions of DoD 6025.18-R. The Privacy Act, as implemented by this part, however, provides greater access to an individual's medical record than that authorized by DoD 6025.18-R. 
                                    </P>
                                    <P>(2) Medical records in a system of records shall be disclosed to the individual to whom they pertain, even if a minor, but when it is believed that access to such records could have an adverse effect on the mental or physical health of the individual or may result in harm to a third party, the following special procedures apply. </P>
                                    <P>(i) If a determination is made in consultation with a medical doctor that release of the medical information may be harmful to the mental or physical health of the individual or to a third party, the Component shall: </P>
                                    <P>(A) Send the record to a physician named by the individual; and </P>
                                    <P>(B) In the transmittal letter to the physician explain why access by the individual without proper professional supervision could be harmful (unless it is obvious from the record). </P>
                                    <P>(ii) The Component shall not require the physician to request the records for the individual. </P>
                                    <P>(3) If the individual refuses or fails to designate a physician, the record shall not be provided. Such refusal of access is not considered a denial under the Privacy Act (see paragraph (a) of § 310.18). </P>
                                    <P>(4) If records are provided the designated physician, but the physician declines or refuses to provide the records to the individual, the DoD Component is under an affirmative duty to take action to deliver the records to the individual by whatever means deemed appropriate. Such action should be taken expeditiously especially if there has been a significant delay between the time the records were furnished the physician and the decision by the physician not to release the records. </P>
                                    <P>(5) Access to a minor's medical records may be granted to his or her parents or legal guardians. However, access is subject to the restrictions as set forth at paragraph C9.7.3 of DoD 6025.18-R. </P>
                                    <P>(6) All members of the Military Services and all married persons are not considered minors regardless of age, and the parents of these individual do not have access to their medical records without written consent of the individual. </P>
                                    <P>
                                        (g) 
                                        <E T="03">Access to information compiled in anticipation of civil action (see § 310.27).</E>
                                    </P>
                                    <P>
                                        (h) 
                                        <E T="03">Non-Agency Records.</E>
                                         (1) Certain documents under the physical control of DoD personnel and used to assist them in performing official functions, are not considered “Agency records” within the meaning of this part. Uncirculated personal notes and records that are not disseminated or circulated to any person or organization (for example, personal telephone lists or memory aids) that are retained or discarded at the author's discretion and over which the Component exercises no direct control are not considered Agency records. However, if personnel are officially directed or encouraged, either in writing or orally, to maintain such records, they may become “Agency records,” and may be subject to this part. 
                                    </P>
                                    <P>(2) The personal uncirculated handwritten notes of unit leaders, office supervisors, or military supervisory personnel concerning subordinates are not systems of records within the meaning of this part. Such notes are an extension of the individual's memory. These notes, however, must be maintained and discarded at the discretion of the individual supervisor and not circulated to others. Any established requirement to maintain such notes (such as, written or oral directives, regulations, or command policy) may transform these notes into “Agency records” and they then must be made a part of a system of records. If the notes are circulated, they must be made a part of a system of records. Any action that gives personal notes the appearance of official Agency records is prohibited, unless the notes have been incorporated into a system of records. </P>
                                    <P>
                                        (i) 
                                        <E T="03">Relationship between the Privacy Act (5 U.S.C. 552a) and the FOIA (5 U.S.C. 552).</E>
                                         Not all requesters are knowledgeable of the appropriate statutory authority to cite when requesting records. In some instances, they may cite neither Act, but will imply one or both Acts. The below guidelines are provided to ensure requesters are given the maximum amount of information as authorized under both statutes. 
                                    </P>
                                    <P>(1) Process requests for individual access as follows: </P>
                                    <P>
                                        (i) If the records are required to be released under the Privacy Act, the FOIA (32 CFR part 286) does not bar release even if a FOIA exemption could 
                                        <PRTPAGE P="18768"/>
                                        be invoked if the request had been processed solely under FOIA. Conversely, if the records are required to be released under the FOIA, the Privacy Act does not bar disclosure. 
                                    </P>
                                    <P>(ii) Requesters who seek records about themselves contained in a Privacy Act system of records, and who cite or imply only the Privacy Act, will have their records processed under the provisions of this part and the FOIA (32 CFR part 286). If the system of records is exempt from the access provisions of this part, and if the records, or any portion thereof, are exempt under the FOIA, the requester shall be advised and informed of the appropriate Privacy and FOIA exemption. Only if the records can be denied under both statutes may the Department withhold the records from the individual. Appeals shall be processed under both Acts. </P>
                                    <P>(iii) Requesters who seek records about themselves that are not contained in a Privacy Act system of records, and who cite or imply only the Privacy Act, will have their requests processed under the provisions of the FOIA (32 CFR part 286), because the access provisions of this part do not apply. Appeals shall be processed under the FOIA. </P>
                                    <P>(iv) Requesters who seek records about themselves that are contained in a Privacy Act system of records, and who cite or imply the FOIA or both Acts, will have their requests processed under the provisions of this part and the FOIA (32 CFR part 286). If the system of records is exempt from the access provisions of this part, and if the records, or any portion thereof, are exempt under the FOIA, the requester shall be advised and informed of the appropriate Privacy and FOIA exemption. Appeals shall be processed under both Acts. </P>
                                    <P>(v) Requesters who seek records about themselves that are not contained in a Privacy Act system of records, and who cite or imply the Privacy Act and FOIA, will have their requests processed under the FOIA (32 CFR part 286), because the access provisions of this part do not apply. Appeals shall be processed under the FOIA. </P>
                                    <P>(2) Do not deny individuals' access to personal information concerning themselves that would otherwise be releasable to them under either Act solely because they fail to cite or imply either Act or cite the wrong Act or part. </P>
                                    <P>(3) Explain to the requester which Act(s) was(were) used when granting or denying access under either Act. </P>
                                    <P>
                                        (j) 
                                        <E T="03">Time limits.</E>
                                         DoD Components normally shall acknowledge requests for access within 10 working days after receipt and provide access within 30 working days. 
                                    </P>
                                    <P>
                                        (k) 
                                        <E T="03">Privacy case file.</E>
                                         Establish a Privacy Act case file when required. (See paragraph (p) of § 310.19.) 
                                    </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 310.18 </SECTNO>
                                    <SUBJECT>Denial of individual access. </SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">Denying individual access.</E>
                                         (1) An individual may be denied access to a record pertaining to him or her only if the record: 
                                    </P>
                                    <P>(i) Was compiled in reasonable anticipation of a civil action or proceeding (see § 310.27). </P>
                                    <P>(ii) Is in a system of records that has been exempted from the access provisions of this part under one of the permitted exemptions. (See § 310.28 and § 310.29.) </P>
                                    <P>(iii) Contains classified information that has been exempted from the access provision of this part under the blanket exemption for such material claimed for all DoD records systems. (See § 310.26(c).). </P>
                                    <P>(iv) Is contained in a system of records for which access may be denied under some other Federal statute that excludes the record from coverage of the Privacy Act (5 U.S.C. 552a). </P>
                                    <P>(2) Where a basis for denial exists, do not deny the record, or portions of the record, if denial does not serve a legitimate governmental purpose. </P>
                                    <P>
                                        (b) 
                                        <E T="03">Other reasons to refuse access:</E>
                                    </P>
                                    <P>(1) An individual may be refused access if: </P>
                                    <P>(i) The record is not described well enough to enable it to be located with a reasonable amount of effort on the part of an employee familiar with the file; or </P>
                                    <P>(ii) Access is sought by an individual who fails or refuses to comply with the established procedural requirements, including refusing to name a physician to receive medical records when required (see paragraph (f) of § 310.17) or to pay fees (see § 310.20). </P>
                                    <P>(2) Always explain to the individual the specific reason access has been refused and how he or she may obtain access. </P>
                                    <P>
                                        (c) 
                                        <E T="03">Notifying the individual.</E>
                                         Formal denials of access must be in writing and include as a minimum: 
                                    </P>
                                    <P>(1) The name, title or position, and signature of a designated Component denial authority. </P>
                                    <P>(2) The date of the denial. </P>
                                    <P>(3) The specific reason for the denial, including specific citation to the appropriate sections of the Privacy Act (5 U.S.C. 552a) or other statutes, this part, DoD Component instructions, or CFR authorizing the denial; </P>
                                    <P>(4) Notice to the individual of his or her right to appeal the denial through the Component appeal procedure within 60 calendar days; and </P>
                                    <P>(5) The title or position and address of the Privacy Act appeals official for the Component. </P>
                                    <P>
                                        (d) 
                                        <E T="03">DoD Component appeal procedures.</E>
                                         Establish internal appeal procedures that, as a minimum, provide for: 
                                    </P>
                                    <P>(1) Review by the Head of the Component or his or her designee of any appeal by an individual from a denial of access to Component records. </P>
                                    <P>(2) Formal written notification to the individual by the appeal authority that shall: </P>
                                    <P>(i) If the denial is sustained totally or in part, include as a minimum: </P>
                                    <P>(A) The exact reason for denying the appeal to include specific citation to the provisions of the Act or other statute, this part, Component instructions or the CFR upon which the determination is based; </P>
                                    <P>(B) The date of the appeal determination; </P>
                                    <P>(C) The name, title, and signature of the appeal authority; and </P>
                                    <P>(D) A statement informing the applicant of his or her right to seek judicial relief. </P>
                                    <P>(ii) If the appeal is granted, notify the individual and provide access to the material to which access has been granted. </P>
                                    <P>(3) The written appeal notification granting or denying access is the final Component action as regards access. </P>
                                    <P>(4) The individual shall file any appeal from denial of access within no less than 60 calendar days of receipt of the denial notification. </P>
                                    <P>(5) Process all appeals within 30 days of receipt unless the appeal authority determines that a fair and equitable review cannot be made within that period. Notify the applicant in writing if additional time is required for the appellate review. The notification must include the reasons for the delay and state when the individual may expect an answer to the appeal. </P>
                                    <P>
                                        (e) 
                                        <E T="03">Denial of appeals by failure to act.</E>
                                         A requester may consider his or her appeal formally denied if the appeal authority fails: 
                                    </P>
                                    <P>(1) To act on the appeal within 30 days; </P>
                                    <P>(2) To provide the requester with a notice of extension within 30 days; or </P>
                                    <P>(3) To act within the time limits established in the Component's notice of extension (see paragraph (d)(5) of this section). </P>
                                    <P>
                                        (f) 
                                        <E T="03">Denying access to OPM records held by the DoD Components.</E>
                                         (1) The records in all systems of records maintained in accordance with the OPM Government-wide system notices are technically only in the temporary custody of the Department of Defense. 
                                    </P>
                                    <P>
                                        (2) All requests for access to these records must be processed in accordance with 5 CFR part 297 as well as applicable Component procedures. 
                                        <PRTPAGE P="18769"/>
                                    </P>
                                    <P>(3) When a DoD Component refuses to grant access to a record in an OPM system, the Component shall advise the individual that his or her appeal must be directed to the Assistant Director for Workforce Information, Personnel Systems and Oversight Group, U.S. Office of Personnel Management, 1900 E Street, NW., Washington, DC, in accordance with the procedures of 5 CFR part 297. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 310.19 </SECTNO>
                                    <SUBJECT>Amendment of records. </SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">Individual review and correction.</E>
                                         Individuals are encouraged to review the personal information being maintained about them by the DoD Components periodically and to avail themselves of the procedures established by this part and other Regulations to update their records. 
                                    </P>
                                    <P>
                                        (b) 
                                        <E T="03">Amending records.</E>
                                         (1) An individual may request the amendment of any record contained in a system of records pertaining to him or her unless the system of records has been exempted specifically from the amendment procedures of this part under paragraph (b) of § 310.26. Normally, amendments under this part are limited to correcting factual matters and not matters of official judgment, such as performance ratings, promotion potential, and job performance appraisals. 
                                    </P>
                                    <P>(2) While a Component may require that the request for amendment be in writing, this requirement shall not be used to discourage individuals from requesting valid amendments or to burden needlessly the amendment process. </P>
                                    <P>(3) A request for amendment must include: </P>
                                    <P>(i) A description of the item or items to be amended; </P>
                                    <P>(ii) The specific reason for the amendment; </P>
                                    <P>(iii) The type of amendment action sought (deletion, correction, or addition); and </P>
                                    <P>(iv) Copies of available documentary evidence supporting the request. </P>
                                    <P>
                                        (c) 
                                        <E T="03">Burden of proof.</E>
                                         The applicant must support adequately his or her claim. 
                                    </P>
                                    <P>
                                        (d) 
                                        <E T="03">Identification of requesters.</E>
                                         (1) Individuals may be required to provide identification to ensure that they are indeed seeking to amend a record pertaining to themselves and not, inadvertently or intentionally, the record of others. 
                                    </P>
                                    <P>(2) The identification procedures shall not be used to discourage legitimate requests or to burden needlessly or delay the amendment process. (See paragraph (c) of § 310.17.) </P>
                                    <P>
                                        (e) 
                                        <E T="03">Limits on attacking evidence previously submitted.</E>
                                         (1) The amendment process is not intended to permit the alteration of records presented in the course of judicial or quasi-judicial proceedings. Any amendments or changes to these records normally are made through the specific procedures established for the amendment of such records. 
                                    </P>
                                    <P>(2) Nothing in the amendment process is intended or designed to permit a collateral attack upon what has already been the subject of a judicial or quasi-judicial determination. However, while the individual may not attack the accuracy of the judicial or quasi-judicial determination under this part, he or she may challenge the accuracy of the recording of that action. </P>
                                    <P>
                                        (f) 
                                        <E T="03">Sufficiency of a request to amend.</E>
                                         Consider the following factors when evaluating the sufficiency of a request to amend: 
                                    </P>
                                    <P>(1) The accuracy of the information; and </P>
                                    <P>(2) The relevancy, timeliness, completeness, and necessity of the recorded information. </P>
                                    <P>
                                        (g) 
                                        <E T="03">Time limits.</E>
                                         (1) Provide written acknowledgement of a request to amend within 10 working days of its receipt by the appropriate systems manager. There is no need to acknowledge a request if the action is completed within 10 working days and the individual is so informed. 
                                    </P>
                                    <P>(2) The letter of acknowledgement shall clearly identify the request and advise the individual when he or she may expect to be notified of the completed action. </P>
                                    <P>(3) Only under the most exceptional circumstances shall more than 30 days be required to reach a decision on a request to amend. Document fully and explain in the Privacy Act case file (see paragraph (p) of this section) any such decision that takes more than 30 days to resolve. </P>
                                    <P>
                                        (h) 
                                        <E T="03">Agreement to amend.</E>
                                         If the decision is made to grant all or part of the request for amendment, amend the record accordingly and notify the requester. 
                                    </P>
                                    <P>
                                        (i) 
                                        <E T="03">Notification of previous recipients.</E>
                                         (1) Notify all previous recipients of the record, as reflected in the disclosure accounting records, that an amendment has been made and the substance of the amendment. Recipients who are known to be no longer retaining the information need not be advised of the amendment. All DoD Components and Federal agencies known to be retaining the record or information, even if not reflected in a disclosure record, shall be notified of the amendment. Advise the requester of these notifications. 
                                    </P>
                                    <P>(2) Honor all requests by the requester to notify specific Federal agencies of the amendment action. </P>
                                    <P>
                                        (j) 
                                        <E T="03">Denying amendment.</E>
                                         If the request for amendment is denied in whole or in part, promptly advise the individual in writing of the decision to include: 
                                    </P>
                                    <P>(1) The specific reason and authority for not amending; </P>
                                    <P>(2) Notification that he or she may seek further independent review of the decision by the Head of the DoD Component or his or her designee; </P>
                                    <P>(3) The procedures for appealing the decision citing the position and address of the official to whom the appeal shall be addressed; and </P>
                                    <P>(4) Where he or she can receive assistance in filing the appeal. </P>
                                    <P>
                                        (k) 
                                        <E T="03">DoD Component appeal procedures.</E>
                                         Establish procedures to ensure the prompt, complete, and independent review of each amendment denial upon appeal by the individual. These procedures must ensure: 
                                    </P>
                                    <P>(1) The appeal with all supporting materials both that furnished the individual and that contained in Component records is provided to the reviewing official; and </P>
                                    <P>(2) If the appeal is denied completely or in part, the individual is notified in writing by the reviewing official that: </P>
                                    <P>(i) The appeal has been denied and the specific reason and authority for the denial; </P>
                                    <P>(ii) The individual may file a statement of disagreement with the appropriate authority and the procedures for filing this statement; </P>
                                    <P>(iii) If filed properly, the statement of disagreement shall be included in the records, furnished to all future recipients of the records, and provided to all prior recipients of the disputed records who are known to hold the record; and </P>
                                    <P>(iv) The individual may seek a judicial review of the decision not to amend. </P>
                                    <P>(3) If the record is amended, ensure: </P>
                                    <P>(i) The requester is notified promptly of the decision; </P>
                                    <P>(ii) All prior known recipients of the records who are known to be retaining the record are notified of the decision and the specific nature of the amendment (see (l) of this Section); and </P>
                                    <P>(iii) The requester is notified which DoD Components and Federal agencies have been told of the amendment. </P>
                                    <P>
                                        (4) Process all appeals within 30 days unless the appeal authority determines that a fair review cannot be made within this time limit. If additional time is required for the appeal, notify the requester, in writing, of the delay, the reason for the delay, and when he or she may expect a final decision on the 
                                        <PRTPAGE P="18770"/>
                                        appeal. Document fully all requirements for additional time in the Privacy Case File. (See paragraph (p) of this section.) 
                                    </P>
                                    <P>
                                        (l) 
                                        <E T="03">Denying amendment of OPM records held by the DoD Components.</E>
                                         (1) The records in all systems of records controlled by the OPM Government-wide system notices are technically only temporarily in the custody of the Department of Defense. 
                                    </P>
                                    <P>(2) All requests for amendment of these records must be processed in accordance with 5 CFR part 297. The Component denial authority may deny a request. However, when an amendment request is denied, the DoD Component shall advise the individual that his or her appeal must be directed to the Assistant Director for Workforce Information, Personnel Systems and Oversight Group, U.S. Office of Personnel Management, 1900 E Street, Washington, DC 20415 in accordance with the procedures of 5 CFR 297. </P>
                                    <P>
                                        (m) 
                                        <E T="03">Statements of disagreement submitted by individuals.</E>
                                         (1) If the appellate authority refuses to amend the record as requested, the individual may submit a concise statement of disagreement setting forth his or her reasons for disagreeing with the decision not to amend. 
                                    </P>
                                    <P>(2) If an individual chooses to file a statement of disagreement, annotate the record to indicate that the statement has been filed (see paragraph (n) of this section). </P>
                                    <P>(3) Furnish copies of the statement of disagreement to all DoD Components and Federal agencies that have been provided copies of the disputed information and who may be maintaining the information. </P>
                                    <P>
                                        (n) 
                                        <E T="03">Maintaining statements of disagreement.</E>
                                         (1) When possible, incorporate the statement of disagreement into the record. 
                                    </P>
                                    <P>(2) If the statement cannot be made a part of the record, establish procedures to ensure that it is apparent from the records a statement of disagreement has been filed and maintain the statement so that it can be obtained readily when the disputed information is used or disclosed. </P>
                                    <P>(3) Automated record systems that are not programmed to accept statements of disagreement shall be annotated or coded so they clearly indicate that a statement of disagreement is on file, and clearly identify the statement with the disputed information in the system. </P>
                                    <P>(4) Provide a copy of the statement of disagreement whenever the disputed information is disclosed for any purpose. </P>
                                    <P>
                                        (o) 
                                        <E T="03">The DoD Component statement of reasons for refusing to amend.</E>
                                         (1) A statement of reasons for refusing to amend may be included with any record for which a statement of disagreement is filed. 
                                    </P>
                                    <P>(2) Include in this statement only the reasons furnished to the individual for not amending the record. Do not comment on or respond to comments contained in the statement of disagreement. Normally, both statements are filed together. </P>
                                    <P>(3) When disclosing information for which a statement of reasons has been filed, a copy of the statement may be released whenever the record and the statement of disagreement are disclosed. </P>
                                    <P>
                                        (p) 
                                        <E T="03">Privacy case files.</E>
                                         (1) Establish a separate Privacy case file to retain the documentation received and generated during the amendment or access process. 
                                    </P>
                                    <P>(2) The Privacy case file shall contain as a minimum: </P>
                                    <P>(i) The request for amendment and access. </P>
                                    <P>(ii) Copies of the DoD Component's reply granting or denying the request; </P>
                                    <P>(iii) Any appeals from the individual; </P>
                                    <P>(iv) Copies of the action regarding the appeal with supporting documentation that is not in the basic file; and </P>
                                    <P>(v) Any other correspondence generated in processing the appeal, to include coordination documentation. </P>
                                    <P>(3) Only the items listed in paragraphs (p)(4) and (p)(5) of this section may be included in the system of records challenged for amendment or for which access is sought. Do not retain copies of the original record in the basic record system if the request for amendment is granted and the record has been amended. </P>
                                    <P>(4) The following items relating to an amendment request may be included in the disputed record system: </P>
                                    <P>(i) Copies of the amended record. </P>
                                    <P>(ii) Copies of the individual's statement of disagreement (see paragraph (m) of this section). </P>
                                    <P>(iii) Copies of the Component's statement of reasons for refusing to amend (see paragraph (o) of this section). </P>
                                    <P>(iv) Supporting documentation submitted by the individual. </P>
                                    <P>(5) The following items relating to an access request may be included in the basic records system: </P>
                                    <P>(i) Copies of the request; </P>
                                    <P>
                                        (ii) Copies of the Component's action granting total or partial access. (
                                        <E T="04">Note:</E>
                                         A separate Privacy case file need not be created in such cases.) 
                                    </P>
                                    <P>(iii) Copies of the Component's action denying access. </P>
                                    <P>(iv) Copies of any appeals filed. </P>
                                    <P>(v) Copies of the reply to the appeal. </P>
                                    <P>(6) Privacy case files shall not be furnished or disclosed to anyone for use in making any determination about the individual other than determinations made under this part. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 310.20 </SECTNO>
                                    <SUBJECT>Reproduction fees. </SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">Assessing fees.</E>
                                         (1) Charge the individual only the direct cost of reproduction. 
                                    </P>
                                    <P>(2) Do not charge reproduction fees if copying is: </P>
                                    <P>(i) The only means to make the record available to the individual (for example, a copy of the record must be made to delete classified information); or </P>
                                    <P>(ii) For the convenience of the DoD Component (for example, the Component has no reading room where an individual may review the record, or reproduction is done to keep the original in the Component's file). </P>
                                    <P>(iii) No fees shall be charged when the record may be obtained without charge under any other Regulation, Directive, or statute. </P>
                                    <P>(iv) Do not use fees to discourage requests. </P>
                                    <P>
                                        (b) 
                                        <E T="03">No minimum fees authorized.</E>
                                         Use fees only to recoup direct reproduction costs associated with granting access. Minimum fees for duplication are not authorized and there is no automatic charge for processing a request. 
                                    </P>
                                    <P>
                                        (c) 
                                        <E T="03">Prohibited fees.</E>
                                         Do not charge or collect fees for: 
                                    </P>
                                    <P>(1) Search and retrieval of records; </P>
                                    <P>(2) Review of records to determine releasability; </P>
                                    <P>(3) Copying records for the DoD Component convenience or when the individual has not specifically requested a copy; </P>
                                    <P>(4) Transportation of records and personnel; or </P>
                                    <P>(5) Normal postage. </P>
                                    <P>
                                        (d) 
                                        <E T="03">Waiver of fees.</E>
                                         (1) Normally, fees are waived automatically if the direct costs of a given request are less than $30. This fee waiver provision does not apply when a waiver has been granted to the individual before, and later requests appear to be an extension or duplication of that original request. A DoD Component may, however, set aside this automatic fee waiver provision when, on the basis of good evidence, it determines the waiver of fees is not in the public interest. 
                                    </P>
                                    <P>(2) Decisions to waive or reduce fees that exceed the automatic waiver threshold shall be made on a case-by-case basis. </P>
                                    <P>
                                        (e) 
                                        <E T="03">Fees for Members of Congress.</E>
                                         Do not charge members of Congress for copying records furnished even when the records are requested under the Privacy Act on behalf of a constituent (See § 310.22(i)). When replying to a constituent inquiry and the fees involved are substantial, consider 
                                        <PRTPAGE P="18771"/>
                                        suggesting to the Congressman that the constituent can obtain the information directly by writing to the appropriate offices and paying the costs. When practical, suggest to the Congressman that the record can be examined at no cost if the constituent wishes to visit the custodian of the record. 
                                    </P>
                                    <P>
                                        (f) 
                                        <E T="03">Reproduction fees computation.</E>
                                         Compute fees using the appropriate portions of the fee schedule in 32 CFR part 286. 
                                    </P>
                                </SECTION>
                            </SUBPART>
                            <SUBPART>
                                <HD SOURCE="HED">Subpart E—Disclosure of Personal Information to Other Agencies and Third Parties </HD>
                                <SECTION>
                                    <SECTNO>§ 310.21 </SECTNO>
                                    <SUBJECT>Conditions of disclosure. </SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">Disclosures to third parties.</E>
                                         (1) The Privacy Act only compels disclosure of records from a system of records to the individuals to whom they pertain unless the records are contained in a system for which an exemption to the access provisions of this part has been claimed. 
                                    </P>
                                    <P>(2) Requests by other individuals (third parties) for the records of individuals that are contained in a system of records shall be processed under 32 CFR part 286 except for requests by the parents of a minor or the legal guardian of an individual for access to the records pertaining to the minor or individual. </P>
                                    <P>
                                        (b) 
                                        <E T="03">Disclosures among the DoD Components.</E>
                                         For the purposes of disclosure and disclosure accounting, the Department of Defense is considered a single agency (see § 310.22(a)). 
                                    </P>
                                    <P>
                                        (c) 
                                        <E T="03">Disclosures outside the Department of Defense.</E>
                                         Do not disclose personal information from a system of records outside the Department of Defense unless: 
                                    </P>
                                    <P>(1) The record has been requested by the individual to whom it pertains. </P>
                                    <P>(2) The written consent of the individual to whom the record pertains has been obtained for release of the record to the requesting Agency, activity, or individual; or </P>
                                    <P>(3) The release is authorized pursuant to one of the specific non-consensual conditions of disclosure as set forth in § 310.22. </P>
                                    <P>
                                        (d) 
                                        <E T="03">Validation before disclosure.</E>
                                         Except for releases made in accordance with 32 CFR part 286, the following steps shall be taken before disclosing any records to any recipient outside the Department of Defense, other than a Federal agency or the individual to whom it pertains: 
                                    </P>
                                    <P>(1) Ensure the records are accurate, timely, complete, and relevant for agency purposes; </P>
                                    <P>(2) Contact the individual, if reasonably available, to verify the accuracy, timeliness, completeness, and relevancy of the information, if this cannot be determined from the record; or </P>
                                    <P>(3) If the information is not current and the individual is not reasonably available, advise the recipient that the information is believed accurate as of a specific date and any other known factors bearing on its accuracy and relevancy. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 310.22 </SECTNO>
                                    <SUBJECT>Non-consensual conditions of disclosure. </SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">Disclosures within the Department of Defense.</E>
                                         (1) Records pertaining to an individual may be disclosed to a DoD official or employee provided: 
                                    </P>
                                    <P>(i) The requester has a need for the record in the performance of his or her assigned duties. The requester shall articulate in sufficient detail why the records are required so the custodian of the records may make an informed decision regarding their release; </P>
                                    <P>(ii) The intended use of the record generally relates to the purpose for which the record is maintained; and </P>
                                    <P>(iii) Only those records as are minimally required to accomplish the intended use are disclosed. The entire record is not released if only a part of the record will be responsive to the request. </P>
                                    <P>(2) Rank, position, or title alone does not authorize access to personal information about others. </P>
                                    <P>
                                        (b) 
                                        <E T="03">Disclosures required by the FOIA.</E>
                                         (1) All records must be disclosed if their release is required by FOIA (5 U.S.C. 552), as implemented by 32 CFR part 286. The FOIA requires records be made available to the public unless withholding is authorized pursuant to one of nine exemptions or one of three law enforcement exclusions under the Act. 
                                    </P>
                                    <P>(i) The DoD Component must be in receipt of a FOIA request and a determination made that the records are not withholdable pursuant to a FOIA exemption or exclusion before the records may be disclosed.</P>
                                    <P>(ii) Records that have traditionally been released to the public by the Components may be disclosed whether or not a FOIA request has been received. </P>
                                    <P>(2) The standard for exempting most personal records, such as personnel, medical, and similar records, is FOIA Exemption 6 (32 CFR part 286.12(e)). Under that exemption, records can be withheld when disclosure, if other than to the individual about whom the information pertains, would result in a clearly unwarranted invasion of the individual's personal privacy. </P>
                                    <P>(3) The standard for exempting personal records compiled for law enforcement purposes, including personnel security investigation records, is FOIA Exemption 7(C) (32 CFR part 286.12(g)). Under that exemption, records can be withheld when disclosure, if other than to the individual about whom the information pertains, would result in an unwarranted invasion of the individual's personal privacy. </P>
                                    <P>(4) If records or information are exempt from disclosure pursuant to the standards set forth in paragraphs (b)(2) and/or (b)(3) of this section, and the records are contained in a system of records (See § 310.10(a) of subpart B, the Privacy Act (5 U.S.C. 552a) prohibits release. </P>
                                    <P>
                                        (5) 
                                        <E T="03">Personal information that is normally releasable.</E>
                                         (i) 
                                        <E T="03">DoD civilian employees.</E>
                                         (A) Some examples of personal information regarding DoD civilian employees that normally may be released without a clearly unwarranted invasion of personal privacy include: 
                                    </P>
                                    <P>
                                        <E T="03">(1)</E>
                                         Name. 
                                    </P>
                                    <P>
                                        <E T="03">(2)</E>
                                         Present and past position titles. 
                                    </P>
                                    <P>
                                        <E T="03">(3)</E>
                                         Present and past grades. 
                                    </P>
                                    <P>
                                        <E T="03">(4)</E>
                                         Present and past annual salary rates. 
                                    </P>
                                    <P>
                                        <E T="03">(5)</E>
                                         Present and past duty stations. 
                                    </P>
                                    <P>
                                        <E T="03">(6)</E>
                                         Office and duty telephone numbers. 
                                    </P>
                                    <P>
                                        <E T="03">(7)</E>
                                         Position descriptions. 
                                    </P>
                                    <P>(B) All disclosures of personal information regarding Federal civilian employees shall be made in accordance with OPM release policies (see 5 CFR part 293.311). </P>
                                    <P>
                                        (ii) 
                                        <E T="03">Military members.</E>
                                         (A) While it is not possible to identify categorically information that must be released or withheld from military personnel records in every instance, the following items of personal information regarding military members normally may be disclosed without a clearly unwarranted invasion of their personal privacy: 
                                    </P>
                                    <P>
                                        <E T="03">(1)</E>
                                         Full name. 
                                    </P>
                                    <P>
                                        <E T="03">(2)</E>
                                         Rank. 
                                    </P>
                                    <P>
                                        <E T="03">(3)</E>
                                         Date of rank. 
                                    </P>
                                    <P>
                                        <E T="03">(4)</E>
                                         Gross salary. 
                                    </P>
                                    <P>
                                        <E T="03">(5)</E>
                                         Past duty assignments. 
                                    </P>
                                    <P>
                                        <E T="03">(6)</E>
                                         Present duty assignment. 
                                    </P>
                                    <P>
                                        <E T="03">(7)</E>
                                         Future assignments that are officially established. 
                                    </P>
                                    <P>
                                        <E T="03">(8)</E>
                                         Office or duty telephone numbers. 
                                    </P>
                                    <P>
                                        <E T="03">(9)</E>
                                         Source of commission. 
                                    </P>
                                    <P>
                                        <E T="03">(10)</E>
                                         Promotion sequence number. 
                                    </P>
                                    <P>
                                        <E T="03">(11)</E>
                                         Awards and decorations. 
                                    </P>
                                    <P>
                                        <E T="03">(12)</E>
                                         Attendance at professional military schools. 
                                    </P>
                                    <P>
                                        <E T="03">(13)</E>
                                         Duty status at any given time. 
                                    </P>
                                    <P>
                                        <E T="03">(14)</E>
                                         Home of record (identification of the state only). 
                                    </P>
                                    <P>
                                        <E T="03">(15)</E>
                                         Length of military service. 
                                    </P>
                                    <P>
                                        <E T="03">(16)</E>
                                         Basic Pay Entry Date. 
                                    </P>
                                    <P>
                                        <E T="03">(17)</E>
                                         Official Photo. 
                                    </P>
                                    <P>
                                        (B) All disclosures of personal information regarding military members 
                                        <PRTPAGE P="18772"/>
                                        shall be made in accordance with 32 CFR part 286. 
                                    </P>
                                    <P>
                                        (iii) 
                                        <E T="03">Civilian employees not under the authority of OPM.</E>
                                         (A) While it is not possible to identify categorically those items of personal information that must be released regarding civilian employees not subject to 5 CFR parts 293, 294, and 297, such as nonappropriated fund employees, normally the following items may be released without a clearly unwarranted invasion of personal privacy: 
                                    </P>
                                    <P>
                                        <E T="03">(1)</E>
                                         Full name. 
                                    </P>
                                    <P>
                                        <E T="03">(2)</E>
                                         Grade or position. 
                                    </P>
                                    <P>
                                        <E T="03">(3)</E>
                                         Date of grade. 
                                    </P>
                                    <P>
                                        <E T="03">(4)</E>
                                         Gross salary. 
                                    </P>
                                    <P>
                                        <E T="03">(5)</E>
                                         Present and past assignments. 
                                    </P>
                                    <P>
                                        <E T="03">(6)</E>
                                         Future assignments, if officially established. 
                                    </P>
                                    <P>
                                        <E T="03">(7)</E>
                                         Office or duty telephone numbers. 
                                    </P>
                                    <P>(B) All releases of personal information regarding civilian personnel in this category shall be made in accordance with 32 CFR part 286. </P>
                                    <P>(6) When military or civilian personnel are assigned, detailed, or employed by the National Security Agency, the Defense Intelligence Agency, the National Reconnaissance Office, or the National Geospatial-Intelligence agency, information about such personnel may only be disclosed as authorized by Public Law 86-36 (“National Security Agency-Officers and Employees”) and 10 U.S.C 424 (“Disclosure of Organizational and Personnel Information: Exemption for Specified Intelligence Agencies”). When military and civilian personnel are assigned, detailed or employed by an overseas unit, a sensitive unit, or to a routinely deployable unit, information about such personnel may only be disclosed as authorized by 10 U.S.C. 130b (“Personnel in Overseas, Sensitive, or Routinely Deployed Units: Nondisclosure of Personally Identifying Information”).</P>
                                    <P>(7) Information about military or civilian personnel that otherwise may be disclosable consistent with § 310.22(b)(5) may not be releasable if a requester seeks listings of personnel currently or recently assigned/detailed/employed within a particular component, unit, organization or office with the Department of Defense if the disclosure of such a list would pose a privacy or security threat. </P>
                                    <P>
                                        (c) 
                                        <E T="03">Disclosures for established routine uses.</E>
                                         (1) Records may be disclosed outside the Department of Defense pursuant to a routine use that has been established for the system of records that contains the records. 
                                    </P>
                                    <P>(2) A routine use shall: </P>
                                    <P>(i) Be compatible with the purpose for which the record was collected; </P>
                                    <P>(ii) Identify the persons or organizations to whom the record may be released; </P>
                                    <P>(iii) Identify specifically the intended uses of the information by the persons or organization; and </P>
                                    <P>
                                        (iv) Have been published in the 
                                        <E T="04">Federal Register</E>
                                         (see § 310.32(i)). 
                                    </P>
                                    <P>(3) If a Federal statute or an E.O. of the President directs records contained in a system of records be disclosed outside the Department of Defense, the statute or E.O. serves as authority for the establishment of a routine use. </P>
                                    <P>
                                        (4) New or altered routine uses must be published in the 
                                        <E T="04">Federal Register</E>
                                         at least 30 days before any records may be disclosed pursuant to the terms of the routine use (see subpart G of this part). 
                                    </P>
                                    <P>
                                        (5) In addition to the specific routine uses established for each of the individual system notices, blanket routine uses have been established (see Appendix 3) that are applicable to all DoD system of records. However, in order for the blanket routine uses to apply to a specific system of records, the system notice shall expressly state that the blanket routine uses apply. These blanket routine uses are published only at the beginning of the listing of system notices for each Component in the 
                                        <E T="04">Federal Register</E>
                                        .
                                    </P>
                                    <P>
                                        (d) 
                                        <E T="03">Disclosures to the Bureau of the Census.</E>
                                         Records in DoD systems of records may be disclosed without the consent of the individuals to whom they pertain to the Bureau of the Census for purposes of planning or carrying out a census survey or related activities pursuant to the provisions of 13 U.S.C. 6 (“Information from other Federal Departments and Agencies”). 
                                    </P>
                                    <P>
                                        (e) 
                                        <E T="03">Disclosures for statistical research or reporting.</E>
                                         (1) Records may be disclosed for statistical research or reporting but only after the intended recipient provides, in writing, the purpose for which the records are sought and assurances that the records will be used only for statistical research or reporting purposes. 
                                    </P>
                                    <P>(2) The records shall be transferred to the requester in a form that is not individually identifiable. DoD Components disclosing records under this provision are required to assure information being disclosed cannot reasonably be used in any way to make determinations about individuals. </P>
                                    <P>(3) The records will not be used, in whole or in part, to make any determination about the rights, benefits, or entitlements of specific individuals. </P>
                                    <P>(4) The written statement by the requester shall be made part of the Component's accounting of disclosures (See paragraph (a) of 310.25). </P>
                                    <P>
                                        (f) 
                                        <E T="03">Disclosures to the National Archives and Record Administration (NARA), General Services Administration (GSA).</E>
                                         (1) Records may be disclosed to the NARA if they: 
                                    </P>
                                    <P>(i) Have historical or other value to warrant continued preservation; or </P>
                                    <P>(ii) For evaluation by the Archivist of the United States, or his or her designee, to determine if a record has such historical or other value. </P>
                                    <P>(2) Records transferred to a Federal Records Center (FRC) for safekeeping and storage do not fall within this category. These records are owned by the Component and remain under the control of the transferring Component. FRC personnel are considered agents of the Component that retains control over the records. No disclosure accounting is required for the transfer of records to the FRCs. </P>
                                    <P>
                                        (g) 
                                        <E T="03">Disclosures for law enforcement purposes.</E>
                                         (1) Records may be disclosed to another Agency or an instrumentality of any Governmental jurisdiction within or under the control of the United States for a civil or criminal law enforcement activity, provided: 
                                    </P>
                                    <P>(i) The civil or criminal law enforcement activity is authorized by law; </P>
                                    <P>(ii) The head of the law enforcement activity or a designee has made a written request specifying the particular records desired and the law enforcement purpose (such as criminal investigations, enforcement of a civil law, or a similar purpose) for which the record is sought; and </P>
                                    <P>(iii) There is no Federal statute that prohibits the disclosure of the records. </P>
                                    <P>(2) Blanket requests for any and all records pertaining to an individual shall not be honored absent justification. </P>
                                    <P>(3) When a record is released to a law enforcement activity under this subparagraph, the disclosure accounting (see § 310.25) for the release shall not be made available to the individual to whom the record pertains if the law enforcement activity requests that the disclosure not be disclosed. </P>
                                    <P>(4) The blanket routine use for law enforcement (Appendix C, Section A) applies to all DoD Component systems notices (see paragraph (b)(6) of this section). This permits Components, on their own initiative, to report indications of violations of law found in a system of records to a law enforcement activity. </P>
                                    <P>
                                        (5) Disclosures may be made to Federal, State, or local, but not foreign law enforcement agencies. Disclosures to Foreign law enforcement agencies may be made if a routine use has been established for the system of records 
                                        <PRTPAGE P="18773"/>
                                        from which the records are to be released. 
                                    </P>
                                    <P>
                                        (h) 
                                        <E T="03">Emergency disclosures.</E>
                                         (1) Records may be disclosed if disclosure is made under compelling circumstances affecting the health or safety of any individual. The affected individual need not be the subject of the record disclosed. 
                                    </P>
                                    <P>(2) When such a disclosure is made, the Component shall notify the individual who is the subject of the record. Notification sent to the last known address of the individual as known to the Component is sufficient. </P>
                                    <P>(3) The specific data to be disclosed is at the discretion of the Component. </P>
                                    <P>(4) Emergency medical information may be released by telephone. </P>
                                    <P>
                                        (i) 
                                        <E T="03">Disclosures to Congress.</E>
                                         (1) Records may be disclosed to either House of the Congress or to any committee, joint committee or subcommittee of Congress if the release pertains to a matter within the jurisdiction of the committee. Disclosure is only authorized when in response to an official request on behalf of either House, committee, subcommittee, or joint committee. 
                                    </P>
                                    <P>(2) Requests from members of Congress who are seeking records in their individual capacity or on behalf of a constituent. </P>
                                    <P>(i) Requests made in their individual capacity. Request for records shall be processed under the provisions of DoD 5400.7-R. </P>
                                    <P>(ii) Requests made on behalf of constituents. </P>
                                    <P>(A) The blanket routine use for “Congressional Inquiries” (see Appendix C, section D) applies to all systems. When an individual requests the assistance of the Congressional member, the blanket routine use permits the disclosure of records pertaining to the individual without the express written consent of the individual. </P>
                                    <P>(B) If necessary, accept constituent letters requesting a member of Congress to investigate a matter pertaining to the individual as written authorization to provide access to the records to the congressional member or his or her staff. </P>
                                    <P>(C) When a Congressional inquiry indicates that the request is being made on the basis of a request from the individual to whom the record pertains, consent can be inferred even if the constituent request is not provided the Component. The verbal statement by a Congressional staff member is acceptable to establish that a request has been received by the Member of Congress from the person to whom the records pertain. </P>
                                    <P>(D) If the constituent inquiry is being made on behalf of someone other than the individual to whom the record pertains, the Member of Congress shall be provided only that information releasable under DoD 5400.7-R. Advise the Congressional member that the written consent of the individual to whom the record pertains is required before any additional information may be disclosed. Do not contact individuals to obtain their consents for release to Congressional members unless a Congressional office specifically requests that this be done. </P>
                                    <P>(E) Nothing in paragraph (i)(2)(ii)(A) of this section prohibits a Component, when appropriate, from providing the record directly to the individual and notifying the Congressional office that this has been done without providing the record to the Congressional member. </P>
                                    <P>(3) See paragraph (e) of § 310.20 for the policy on assessing fees for Members of Congress. </P>
                                    <P>(4) Make a disclosure accounting each time a record is disclosed to either House of Congress, to any committee, joint committee, or subcommittee of Congress, or to any congressional member. </P>
                                    <P>
                                        (j) 
                                        <E T="03">Disclosures to the General Accountability Office.</E>
                                         Records may be disclosed to the Comptroller General, or any of his authorized representatives, in the course of the performance of the duties of the General Accountability Office. 
                                    </P>
                                    <P>
                                        (k) 
                                        <E T="03">Disclosures under court orders.</E>
                                         (1) Records may be disclosed without the consent of the person to whom they pertain under a court order signed by a judge of a court of competent jurisdiction. 
                                    </P>
                                    <P>(2) When a record is disclosed under this provision, make reasonable efforts to notify the individual to whom the record pertains, if the legal process is a matter of public record. </P>
                                    <P>(3) If the process is not a matter of public record at the time it is issued, seek information as to when the process is to be made public and make reasonable efforts to notify the individual at that time. </P>
                                    <P>(4) Notification sent to the last known address of the individual as reflected in the records is considered a reasonable effort to notify. </P>
                                    <P>(5) Make a disclosure accounting each time a record is disclosed under a court order or compulsory legal process.</P>
                                    <P>
                                        (l) 
                                        <E T="03">Disclosures to Consumer Reporting Agencies.</E>
                                         (1) Certain personal information may be disclosed to consumer reporting agencies as provided in the Federal Claims Collection Act (31 U.S.C. 3711(e)). 
                                    </P>
                                    <P>(2) Under the provisions of paragraph (l)(1) of this section, the following information may be disclosed to a consumer reporting agency:</P>
                                    <P>(i) Name, address, taxpayer identification number (SSN), and other information necessary to establish the identity of the individual. </P>
                                    <P>(ii) The amount, status, and history of the claim. </P>
                                    <P>(iii) The Agency or program under which the claim arose. </P>
                                    <P>(3) The Federal Claims Collection Act (31 U.S.C. 3711(e)) requires the system notice for the system of records from which the information will be disclosed, indicates that the information may be disclosed to a consumer reporting agency. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 310.23 </SECTNO>
                                    <SUBJECT>Disclosures to commercial enterprises. </SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">General policy.</E>
                                         (1) Make releases of personal information to commercial enterprises under the criteria established by 32 CFR part 286. 
                                    </P>
                                    <P>(2) The relationship of commercial enterprises to their clients or customers and to the Department of Defense is not changed by this part. </P>
                                    <P>(3) The DoD policy on personal indebtedness for military personnel is contained 32 CFR part 112, “Indebtedness of Military Personnel,” and for civilian employees in 5 CFR part 735. </P>
                                    <P>
                                        (b) 
                                        <E T="03">Release of personal information.</E>
                                         (1) Any information that must be released under 32 CFR part 286, the “DoD Freedom of Information Act Program,” may be released to a commercial enterprise without the individual's consent (see paragraph (b) of § 310.22). 
                                    </P>
                                    <P>(2) Commercial enterprises may present a signed consent statement setting forth specific conditions for release of personal information. Statements such as the following, if signed by the individual, are considered valid: </P>
                                    <EXTRACT>
                                        <FP>I hereby authorize the Department of Defense to verify my Social Security Number or other identifying information and to disclose my home address and telephone number to authorized representatives of (name of commercial enterprise) so that they may use this information in connection with my commercial dealings with that enterprise. All information furnished shall be used in connection with my financial relationship with (name of commercial enterprise). </FP>
                                    </EXTRACT>
                                    <P>(3) When a statement of consent as outlined in paragraph (b)(2) of this section is presented, provide the requested information if its release is not prohibited by some other regulation or statute. </P>
                                    <P>
                                        (4) Blanket statements of consent that do not identify the Department of Defense or any of its Components, or 
                                        <PRTPAGE P="18774"/>
                                        that do not specify exactly the type of information to be released, may be honored if it is clear the individual in signing the consent statement intended to obtain a personal benefit (for example, a loan to buy a house) and was aware of the type of information that would be sought. Care should be exercised in these situations to release only the minimum amount of personal information essential to obtain the benefit sought. 
                                    </P>
                                    <P>(5) Do not honor requests from commercial enterprises for official evaluation of personal characteristics, such as evaluation of personal financial habits. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 310.24 </SECTNO>
                                    <SUBJECT>Disclosures to the public from medical records. </SUBJECT>
                                    <P>(a) Disclosures from medical records are not only governed by the requirement of this part but also by the disclosure provisions of DoD 6025.18-R.” </P>
                                    <P>(b) Any medical records that are subject to both this part and DoD 6025.18-R may only be disclosed if disclosure is authorized under both. If disclosure is permitted under this part (e.g., pursuant to a routine use), but the disclosure is not authorized under DoD 6025.18-R, disclosure is not authorized. If a disclosure is authorized under DoD 6025.18-R (e.g., releases outside the Department of Defense), but the disclosure is not authorized under this part, disclosure is not authorized. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 310.25 </SECTNO>
                                    <SUBJECT>Disclosure accounting. </SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">Disclosure accountings.</E>
                                         (1) 
                                        <E T="03">Keep an accurate record of all disclosures made from any system of records except disclosures:</E>
                                    </P>
                                    <P>(i) To DoD personnel for use in the performance of their official duties; or </P>
                                    <P>(ii) Under 5 U.S.C. 552, the FOIA. </P>
                                    <P>(2) In all other cases a disclosure accounting is required even if the individual has consented to the disclosure of the information. </P>
                                    <P>(3) Disclosure accountings: </P>
                                    <P>(i) Permit individuals to determine to whom information has been disclosed; </P>
                                    <P>(ii) Enable the activity to notify past recipients of disputed or corrected information (§ 310.19(i)); and </P>
                                    <P>(iii) Provide a method of determining compliance with paragraph (c) of § 310.21. </P>
                                    <P>
                                        (b) 
                                        <E T="03">Contents of disclosure accountings.</E>
                                         As a minimum, disclosure accounting shall contain: 
                                    </P>
                                    <P>(1) The date of the disclosure. </P>
                                    <P>(2) A description of the information released. </P>
                                    <P>(3) The purpose of the disclosure. </P>
                                    <P>(4) The name and address of the person or Agency to whom the disclosure was made. </P>
                                    <P>
                                        (c) 
                                        <E T="03">Methods of disclosure accounting.</E>
                                         Use any system of disclosure accounting that shall provide readily the necessary disclosure information (see paragraph (a)(3) of this section). 
                                    </P>
                                    <P>
                                        (d) 
                                        <E T="03">Accounting for mass disclosures.</E>
                                         When numerous similar records are released, identify the category of records disclosed and include the data required by paragraph (b) of this section in a form that can be used to construct an accounting disclosure record for individual records if required (see paragraph (a)(3) of this section). 
                                    </P>
                                    <P>
                                        (e) 
                                        <E T="03">Disposition of disclosure accounting records.</E>
                                         Retain disclosure accounting records for 5 years after the disclosure or the life of the record, whichever is longer. 
                                    </P>
                                    <P>
                                        (f) 
                                        <E T="03">Furnishing disclosure accountings to the individual.</E>
                                         (1) Make available to the individual to whom the record pertains all disclosure accountings except when: 
                                    </P>
                                    <P>(i) The disclosure has been made to a law enforcement activity under paragraph (g) of § 310.22 and the law enforcement activity has requested that disclosure not be made; or </P>
                                    <P>(ii) The system of records has been exempted from the requirement to furnish the disclosure accounting under the provisions of § 310.26(b). </P>
                                    <P>(2) If disclosure accountings are not maintained with the record and the individual requests access to the accounting, prepare a listing of all disclosures (see paragraph (b) of this section) and provide this to the individual upon request. </P>
                                </SECTION>
                            </SUBPART>
                            <SUBPART>
                                <HD SOURCE="HED">Subpart F—Exemptions </HD>
                                <SECTION>
                                    <SECTNO>§ 310.26 </SECTNO>
                                    <SUBJECT>Use and establishment of exemptions. </SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">Types of exemptions.</E>
                                         (1) There are three types of exemptions permitted by the Privacy Act (5 U.S.C. 552a). 
                                    </P>
                                    <P>(i) An access exemption that exempts records compiled in reasonable anticipation of a civil action or proceeding from the access provisions of the Act. </P>
                                    <P>(ii) General exemptions that authorize the exemption of a system of records from all but certain specifically identified provisions of the Act (see Appendix D). </P>
                                    <P>(iii) Specific exemptions that allow a system of records to be exempted only from certain designated provisions of the Act (see Appendix D). </P>
                                    <P>(2) Nothing in the Act permits exemption of any system of records from all provisions of the Act. </P>
                                    <P>
                                        (b) 
                                        <E T="03">Establishing exemptions.</E>
                                         (1) The access exemption is self-executing. It does not require an implementing rule to be effective. 
                                    </P>
                                    <P>
                                        (2) Neither a general nor a specific exemption is established automatically for any system of records. The Heads of the DoD Components maintaining the system of records must make a determination whether the system is one for which an exemption properly may be claimed and then propose and establish an exemption rule for the system. No system of records within the Department of Defense shall be considered exempted until the Head of the Component has approved the exemption and an exemption rule has been published as a final rule in the 
                                        <E T="04">Federal Register</E>
                                         (See § 310.30(e).) 
                                    </P>
                                    <P>(3) Only the Head of the DoD Component or an authorized designee may claim an exemption for a system of records. </P>
                                    <P>(4) A system of records is considered exempt only from those provision of the Privacy Act (5 U.S.C. 552a) that are identified specifically in the Component exemption rule for the system and that are authorized by the Privacy Act. </P>
                                    <P>(5) To establish an exemption rule, see § 310.31. </P>
                                    <P>
                                        (c) 
                                        <E T="03">Blanket exemption for classified material.</E>
                                         (1) Component rules shall include a blanket exemption under 5 U.S.C. 552a(k)(1) of the Privacy Act from the access provisions (5 U.S.C. 552a(d)) and the notification of access procedures (5 U.S.C. 522a(e)(4)(H)) of the Act for all classified material in any systems of records maintained. 
                                    </P>
                                    <P>(2) Do not claim specifically an exemption under section 552a(k)(1) of the Privacy Act for any system of records. The blanket exemption affords protection to all classified material in all system of records maintained. </P>
                                    <P>
                                        (d) 
                                        <E T="03">Provisions from which exemptions may be claimed.</E>
                                         The Head of a DoD Component may claim an exemption from any provision of the Act from which an exemption is allowed (see Appendix D). 
                                    </P>
                                    <P>
                                        (e) 
                                        <E T="03">Use of exemptions.</E>
                                         (1) Use exemptions only for the specific purposes set forth in the exemption rules (see paragraph (b) of § 310.31). 
                                    </P>
                                    <P>(2) Use exemptions only when they are in the best interest of the Government and limit them to the specific portions of the records requiring protection. </P>
                                    <P>(3) Do not use an exemption to deny an individual access to any record to which he or she would have access under 32 CFR part 286. </P>
                                    <P>
                                        (f) 
                                        <E T="03">Exempt records in non-exempt systems.</E>
                                         (1) Exempt records temporarily in the custody of another Component are considered the property of the originating Component. Access to these records is controlled by the system 
                                        <PRTPAGE P="18775"/>
                                        notices and rules of the originating Component. 
                                    </P>
                                    <P>(2) Exempt records that have been incorporated into a nonexempt system of records are still exempt but only to the extent to which the provisions of the Act for which an exemption has been claimed are identified and an exemption claimed for the system of records from which the record is obtained and only when the purposes underlying the exemption for the record are still valid and necessary to protect the contents of the record. </P>
                                    <P>(3) If a record is accidentally misfiled into a system of records, the system notice and rules for the system in which it should actually be filed shall govern. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 310.27 </SECTNO>
                                    <SUBJECT>Access exemption. </SUBJECT>
                                    <P>(a) An individual is not entitled to access information that is compiled in reasonable anticipation of a civil action or proceeding. </P>
                                    <P>(b) The term “civil action or proceeding” is intended to include court proceedings, preliminary judicial steps, and quasi-judicial administrative hearings or proceedings (i.e., adversarial proceedings that are subject to rules of evidence). </P>
                                    <P>(c) Any information prepared in anticipation of such actions or proceedings, to include information prepared to advise the DoD Component officials of the possible legal or other consequences of a given course of action, is protected. </P>
                                    <P>(d) The exemption is similar to the attorney work-product privilege except that it applies even when the information is prepared by nonattorneys. </P>
                                    <P>(e) The exemption does not apply to information compiled in anticipation of criminal actions or proceedings. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 310.28 </SECTNO>
                                    <SUBJECT>General exemption. </SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">Use of specific exemptions.</E>
                                         A DoD Component is not authorized to claim the exemption for records maintained by the Central Intelligence Agency established by 5 U.S.C. 552a(j)(1) of the Privacy Act. 
                                    </P>
                                    <P>(b) The general exemption established by 5 U.S.C. 552a(j)(2) of the Privacy Act may be claimed to protect investigative records created and maintained by law-enforcement activities of a DoD Component. </P>
                                    <P>(c) To qualify for the (j)(2) exemption, the system of records must be maintained by a DoD Component, or element thereof, that performs as its principal function any activity pertaining to the enforcement of criminal laws, such as the U.S. Army Criminal Investigation Command, the Naval Investigative Service, the Air Force Office of Special Investigations, and military police activities. However, where DoD offices perform multiple functions, but have an investigative component, such as the DoD Inspector General Defense Criminal Investigative Service or Criminal Law Divisions of Staff Judge Advocates Offices, the exemption may be claimed. Law enforcement includes police efforts to detect, prevent, control, or reduce crime, to apprehend or identify criminals; and the activities of military trial counsel, correction, probation, pardon, or parole authorities. </P>
                                    <P>(d) Information that may be protected under the (j)(2) exemption includes: </P>
                                    <P>(1) Records compiled for the purpose of identifying criminal offenders and alleged offenders consisting only of identifying data and notations of arrests, the nature and disposition of criminal charges, sentencing, confinement, release, parole, and probation status (so-called criminal history records); </P>
                                    <P>(2) Reports and other records compiled during criminal investigations, including supporting documentation. </P>
                                    <P>(3) Other records compiled at any stage of the criminal law enforcement process from arrest or indictment through the final release from parole supervision, such as pre-sentence and parole reports. </P>
                                    <P>(e) The (j)(2) exemption does not apply to: </P>
                                    <P>(1) Investigative records prepared or maintained by activities without primary law-enforcement missions. It may not be claimed by any activity that does not have law enforcement as its principal function except as indicated in paragraph (c) of this section. </P>
                                    <P>(2) Investigative records compiled by any activity concerning employee suitability, eligibility, qualification, or for individual access to classified material regardless of the principal mission of the compiling DoD Component. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 310.29 </SECTNO>
                                    <SUBJECT>Specific exemptions. </SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">Use of specific exemptions.</E>
                                         The specific exemption established by 5 U.S.C. 552a(k) of the Privacy Act may be claimed to protect records that meet the following criteria (parenthetical references are to the appropriate subsection of the Act: 
                                    </P>
                                    <P>
                                        (1) 
                                        <E T="03">(k)(1).</E>
                                         Information subject to 5 U.S.C. 552(b)(1), (DoD 5200.1-R) (see also paragraph (c) of this section). 
                                    </P>
                                    <P>
                                        (2) 
                                        <E T="03">(k)(2).</E>
                                         Investigatory information compiled for law-enforcement purposes, other than information that is covered by the general exemption (see § 310.28). If an individual is denied any right, privilege or benefit he or she is otherwise entitled by Federal law or for which he or she would otherwise be eligible as a result of the maintenance of the information, the individual shall be provided access to the information except to the extent that disclosure would reveal the identity of a confidential source. This exemption provides limited protection of investigative reports maintained in a system of records used in personnel or administrative actions. 
                                    </P>
                                    <P>(i) The information must be compiled for some investigative law enforcement purpose, such as a criminal investigation by a DoD office, whose principal function is not law enforcement, or a civil investigation. </P>
                                    <P>(ii) The exemption does not apply to investigations conducted solely for the purpose of a routine background investigation (see paragraph (a)(5) of this section), but will apply if the investigation is for the purpose of investigating DoD personnel who are suspected of violating statutory or regulatory authority. </P>
                                    <P>(iii) The exemption can continue to be claimed even after the investigation has concluded and there is no future likelihood of further enforcement proceedings. </P>
                                    <P>
                                        (3) 
                                        <E T="03">(k)(3).</E>
                                         Records maintained in connection with providing protective services to the President and other individuals under 18 U.S.C. 3056, “Powers, Authorities, and Duties of United States Secret Service.” 
                                    </P>
                                    <P>
                                        (4) 
                                        <E T="03">(k)(4).</E>
                                         Records maintained solely for statistical research or program evaluation purposes and that are not used to make decisions on the rights, benefits, or entitlement of an individual except for census records that may be disclosed under 13 U.S.C. 6, “Information for other Federal Departments and Agencies. 
                                    </P>
                                    <P>
                                        (5) 
                                        <E T="03">(k)(5).</E>
                                         Investigatory material compiled solely for the purpose of determining suitability, eligibility, or qualifications for Federal civilian employment, military service, Federal contracts, or access to classified information, but only to the extent such material would reveal the identity of a confidential source. 
                                    </P>
                                    <P>(i) This exemption permits protection of confidential sources used in background investigations, employment inquiries, and similar inquiries that are for personnel screening to determine suitability, eligibility, or qualifications. </P>
                                    <P>
                                        (ii) This exemption is applicable not only to investigations conducted prior to the hiring of an employee, but it also applies to investigations conducted to determine continued employment suitability or eligibility. 
                                        <PRTPAGE P="18776"/>
                                    </P>
                                    <P>
                                        (6) 
                                        <E T="03">(k)(6).</E>
                                         Testing or examination material used solely to determine individual qualifications for appointment or promotion in the Federal or military service, if the disclosure would compromise the objectivity or fairness of the test or examination process. 
                                    </P>
                                    <P>
                                        (7) 
                                        <E T="03">(k)(7).</E>
                                         Evaluation material used to determine potential for promotion in the Military Services, but only to the extent that the disclosure of such material would reveal the identity of a confidential source. 
                                    </P>
                                    <P>
                                        (b) 
                                        <E T="03">Promises of confidentiality.</E>
                                         (1) Only the identity of sources that have been given an express promise of confidentiality may be protected from disclosure under paragraphs (a)(1), (5), and (7) of this section. However, the identity of sources who were given implied promises of confidentiality in inquiries conducted before September 27, 1975, also may be protected from disclosure. 
                                    </P>
                                    <P>(2) Ensure promises of confidentiality are not automatically given but are used sparingly. Establish appropriate procedures and identify fully categories of individuals who may make such promises. Promises of confidentiality shall be made only when they are essential to obtain the information sought (see 5 CFR part 736). </P>
                                    <P>
                                        (c) 
                                        <E T="03">Access to records for which specific exemptions are claimed.</E>
                                         Deny the individual access only to those portions of the records for which the claimed exemption applies. 
                                    </P>
                                </SECTION>
                            </SUBPART>
                            <SUBPART>
                                <HD SOURCE="HED">Subpart G—Publication Requirements </HD>
                                <SECTION>
                                    <SECTNO>§ 310.30 </SECTNO>
                                    <SUBJECT>Federal Register publication. </SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">What must be published in the</E>
                                          
                                        <E T="04">Federal Register</E>
                                        . 
                                    </P>
                                    <P>
                                        (1) Four types of documents relating to the Privacy Program must be published in the 
                                        <E T="04">Federal Register</E>
                                        : 
                                    </P>
                                    <P>(i) DoD Component Privacy Procedural rules; </P>
                                    <P>(ii) DoD Component exemption rules; and </P>
                                    <P>(iii) System notices. </P>
                                    <P>(iv) Match notices (See subpart L to this part). </P>
                                    <P>
                                        (2) See DoD 5025.1-M,
                                        <SU>9</SU>
                                        <FTREF/>
                                         “Directive Systems Procedures” and Administrative Instruction (AI) No. 102,
                                        <SU>10</SU>
                                        <FTREF/>
                                         “Office of the Secretary of Defense Federal Register System” for information pertaining to the preparation of documents for publication in the 
                                        <E T="04">Federal Register</E>
                                        . 
                                    </P>
                                    <FTNT>
                                        <P>
                                            <SU>9</SU>
                                             See footnote 1 to § 310.1.
                                        </P>
                                    </FTNT>
                                    <FTNT>
                                        <P>
                                            <SU>10</SU>
                                             See footnote 1 to § 310.1.
                                        </P>
                                    </FTNT>
                                    <P>
                                        (b) 
                                        <E T="03">The effect of publication in the</E>
                                          
                                        <E T="7462">Federal Register</E>
                                        . Publication of a document in the 
                                        <E T="04">Federal Register</E>
                                         constitutes official public notice of the existence and content of the document. 
                                    </P>
                                    <P>
                                        (c) 
                                        <E T="03">DoD Component rules.</E>
                                         (1) Component Privacy Program procedures and Component exemption rules are subject to the rulemaking procedures prescribed in AI 102. 
                                    </P>
                                    <P>
                                        (2) System notices are not subject to formal rulemaking and are published in the 
                                        <E T="04">Federal Register</E>
                                         as “Notices,” not rules. 
                                    </P>
                                    <P>(3) Privacy procedural and exemption rules are incorporated automatically into the CFR. System notices are not published in the CFR. </P>
                                    <P>
                                        (d) 
                                        <E T="03">Submission of rules for publication.</E>
                                         (1) Submit to the DPO, ODA&amp;M, all proposed rules implementing this part in proper format (see DoD 5025.1-M and AI 102) for publication in the 
                                        <E T="04">Federal Register</E>
                                        . 
                                    </P>
                                    <P>
                                        (2) This part has been published as a final rule in the 
                                        <E T="04">Federal Register</E>
                                        . Therefore, incorporate it into your Component rules rather than by republication (see AI 102). 
                                    </P>
                                    <P>
                                        (3) DoD Component procedural rules that simply implement this Regulation need only be published as final rules in the 
                                        <E T="04">Federal Register</E>
                                         (see DoD 5025.1-M and AI 102). If the Component procedural rule supplements this part in any manner, they must be published as a proposed rule before being published as a final rule. 
                                    </P>
                                    <P>(4) Amendments to Component rules are submitted like the basic rules. </P>
                                    <P>
                                        (5) The DPO submits the rules and amendments thereto to the 
                                        <E T="04">Federal Register</E>
                                         for publication. 
                                    </P>
                                    <P>
                                        (e) 
                                        <E T="03">Submission of exemption rules for publication.</E>
                                         (1) No system of records within the Department of Defense shall be considered exempt from any provision of this part until the exemption and the exemption rule for the system has been published as a final rule in the 
                                        <E T="04">Federal Register</E>
                                        . 
                                    </P>
                                    <P>
                                        (2) Submit exemption rules in proper format to the DPO. All exemption rules are coordinated with the DoD Office of General Counsel. After coordination, the DPO shall submit the rules to the 
                                        <E T="04">Federal Register</E>
                                         for publication. 
                                    </P>
                                    <P>(3) Exemption rules require publication both as proposed rules and final rules (see AI 102). </P>
                                    <P>(4) § 310.31(b) discusses the content of an exemption rule. </P>
                                    <P>(5) Submit amendments to exemption rules in the same manner used for establishing these rules. </P>
                                    <P>
                                        (f) 
                                        <E T="03">Submission of system notices for publication.</E>
                                         (1) System notices are not subject to formal rulemaking procedures. However, the Privacy Act (5 U.S.C. 552a) requires a system notice be published in the 
                                        <E T="04">Federal Register</E>
                                         of the existence and character of a new or altered system of records. Until publication of the notice, DoD Components shall not begin to operate the system of records (i.e., collect and use the information). The notice procedures require: 
                                    </P>
                                    <P>(i) The system notice describes what kinds of records are in the system, on whom they are maintained, what uses are made of the records, and how an individual may access, or contest, the records contained in the system. </P>
                                    <P>(ii) The public be given 30 days to comment on any proposed routine uses before any disclosures are made pursuant to the routine use; and </P>
                                    <P>(iii) The notice contain the date on which the system shall become effective. </P>
                                    <P>
                                        (2) Submit system notices to the DPO in the 
                                        <E T="04">Federal Register</E>
                                         format (see AI 102 and Appendix E to this part). The DPO transmits the notices to the 
                                        <E T="04">Federal Register</E>
                                         for publication. 
                                    </P>
                                    <P>(3) § 310.32 discusses the specific elements required in a system notice. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 310.31 </SECTNO>
                                    <SUBJECT>Exemption rules. </SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">General procedures.</E>
                                         Subpart F of this part provides the general guidance for establishing exemptions for systems of records. 
                                    </P>
                                    <P>
                                        (b) 
                                        <E T="03">Contents of exemption rules.</E>
                                         (1) Each exemption rule submitted for publication must contain the following: 
                                    </P>
                                    <P>(i) The record system identifier and title of the system for which the exemption is claimed. (See § 310.32(b) and (c)); </P>
                                    <P>(ii) The specific sections of the Privacy Act under which the exemption for the system is claimed (for example, 5 U.S.C. 552a(j)(2), 5 U.S.C. 552a(k)(3); or 5 U.S.C. 552a(k)(7); </P>
                                    <P>(iii) The specific sections of the Privacy Act from which the system is to be exempted (for example, 5 U.S.C. 552a(c)(3), or 5 U.S.C. 552a(d)(l)-(5)) (see Appendix D)); and </P>
                                    <P>(iv) The specific reasons why an exemption is being claimed from each section of the Act identified. </P>
                                    <P>(2) Do not claim an exemption for classified material for individual systems of records. The blanket exemption applies. (See paragraph (c) of § 310.26.) </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 310.32 </SECTNO>
                                    <SUBJECT>System notices. </SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">Contents of the system notices.</E>
                                         (1) The following data captions are included in each system notice: 
                                    </P>
                                    <P>(i) Systems identifier. (see paragraph (b) of this section). </P>
                                    <P>(ii) System name. (see paragraph (c) of this section). </P>
                                    <P>
                                        (iii) System location. (see paragraph (d) of this section). 
                                        <PRTPAGE P="18777"/>
                                    </P>
                                    <P>(iv) Categories of individuals covered by the system. (see paragraph (e) of this section). </P>
                                    <P>(v) Categories of records in the system. (see paragraph (f) of this section). </P>
                                    <P>(vi) Authority for maintenance of the system. (see paragraph (g) of this section). </P>
                                    <P>(vii) Purpose(s). (see paragraph (h) of this section). </P>
                                    <P>(viii) Routine uses of records maintained in the system, including categories of users and the purposes of such uses. (see paragraph (i) of this section). </P>
                                    <P>(ix) Disclosure to Consumer Reporting Agencies. This element is optional but required when disclosing to consumer reporting agencies (See paragraph (l) of § 310.22.) </P>
                                    <P>(x) Policies and practices for storing, retrieving, accessing, retaining, and disposing of records in the system. (see paragraph (j) of this section). </P>
                                    <P>(xi) Systems manager(s) and address. (see paragraph (k) of this section). </P>
                                    <P>(xii) Notification procedure. (see paragraph (l) of this section). </P>
                                    <P>(xiii) Record access procedures. (see paragraph (m) of this section). </P>
                                    <P>(xiv) Contesting records procedures. (see paragraph (n) of this section). </P>
                                    <P>(xv) Record source categories. (see paragraph (o) of this section). </P>
                                    <P>(xvi) Exemptions claimed for the system. (see paragraph (p) of this section). </P>
                                    <P>(2) The captions listed in paragraph (a)(1) of this Section have been mandated by the Office of Federal Register and must be used exactly as presented. </P>
                                    <P>(3) A sample system notice is shown in Appendix E of this part. </P>
                                    <P>
                                        (b) 
                                        <E T="03">System Identifier.</E>
                                         The system identifier must appear on all system notices and is limited to 21 positions, unless an exception is granted by the DPO, including Component code, file number and symbols, punctuation, and spacing. 
                                    </P>
                                    <P>
                                        (c) 
                                        <E T="03">System Name.</E>
                                         (1) The name of the system reasonably identifies the general purpose of the system and, if possible, the general categories of individuals involved. 
                                    </P>
                                    <P>(2) Use acronyms only parenthetically following the title or any portion thereof, such as, “Joint Uniform Military Pay System (JUMPS).” Do not use acronyms not commonly known unless they are preceded by an explanation. </P>
                                    <P>(3) The system name may not exceed 55 character positions, unless an exception is granted by the DPO, including punctuation and spacing. </P>
                                    <P>(4) The system name should not be the name of the database or the IT system if the name does not meet the criteria in paragraph (c)(1) of this section. </P>
                                    <P>
                                        (d) 
                                        <E T="03">System Location.</E>
                                         (1) For systems maintained in a single location provide the exact office name, organizational identity, and address. 
                                    </P>
                                    <P>(2) For geographically or organizationally decentralized systems, specify each level of organization or element that maintains a segment of the system, to include their mailing address, or indicate the official mailing addresses are published as an Appendix to the Component's compilation of system of records notices, or provide an address where a complete listing of locations can be obtained. </P>
                                    <P>(3) Use the standard U.S. Postal Service two-letter State abbreviation symbols and 9-digit Zip Codes for all domestic addresses. </P>
                                    <P>
                                        (e) 
                                        <E T="03">Categories of individuals covered by the system.</E>
                                         (1) Set forth the specific categories of individuals to whom records in the system pertain in clear, easily understood, non-technical terms. 
                                    </P>
                                    <P>(2) Avoid the use of broad over-general descriptions, such as “all Army personnel” or “all military personnel” unless this actually reflects the category of individuals involved. </P>
                                    <P>
                                        (f) 
                                        <E T="03">Categories of records in the system.</E>
                                         (1) Describe in clear, non-technical terms the types of records maintained in the system. 
                                    </P>
                                    <P>(2) Only documents actually maintained in the system of records shall be described, not source documents that are used only to collect data and then destroyed. </P>
                                    <P>
                                        (g) 
                                        <E T="03">Authority for maintenance of system.</E>
                                         (1) Cite the specific provision of the Federal statute or E.O. that authorizes the maintenance of the system.
                                    </P>
                                    <P>(2) Include with citations for statutes the popular names, when appropriate (for example, Section 2103 of title 51, United States Code, “Tea-Tasters Licensing Act”), and for E.O.s, the official title (for example, E.O. No. 9397, “Numbering System for Federal Accounts Relating to Individual Persons”). </P>
                                    <P>(3) If direct statutory authority or an Executive Order does not exist, indirect statutory authority may be cited if the authority requires the operation or administration of a program, the execution of which will require the collection and maintenance of a system of records. </P>
                                    <P>(4) If direct or indirect authority does not exist, the Department of Defense, as well as the Army, Navy, and Air Force general “housekeeping” statutes (i.e., 5 U.S.C. 301 (“Departmental Regulations”), 10 U.S.C. 3013 (“Secretary of the Army”), 5013 (“Secretary of the Navy”), and 8013 (“Secretary of the Air Force”) may be cited if the Secretary, or those offices to which responsibility has been delegated, are required to collect and maintain systems of records in order to discharge assigned responsibilities. If the housekeeping statute is cited, the regulatory authority implementing the statute within the Department or Component also shall be identified. </P>
                                    <P>(5) If the social security number is being collected and maintained, E.O. 9397 (“Numbering Systems for Federal Accounts Relating to Indivdiual Persons”) shall be cited. </P>
                                    <P>
                                        (h) 
                                        <E T="03">Purpose or Purposes.</E>
                                         (1) List the specific purposes for maintaining the system of records by the Component. 
                                    </P>
                                    <P>(2) All internal uses of the information within the Department or Component shall be identified. Such uses are the so-called “internal routine uses.” </P>
                                    <P>
                                        (i) 
                                        <E T="03">Routine Uses.</E>
                                         (1) Except as otherwise authorized by subpart E of this part, disclosure of information from a system of records to any person or entity outside the Department of Defense (see § 310.21(b)) may only be made pursuant to a routine use that has been established for the specific system of records. Such uses are the so-called “external routine uses.” 
                                    </P>
                                    <P>(2) Each routine use shall include to whom the information is being disclosed and what use and purpose the information will be used. Routine uses shall be written as follows: </P>
                                    <P>(i) “To* * *.[person or entity outside of DoD that will receive the information] to* * *.[what will be done with the information] for the purpose(s) of * * *[what objective is sought to be achieved].” </P>
                                    <P>(ii) To the extent practicable, general statements, such as “to other Federal agencies as required” or “to any other appropriate Federal agency” shall be avoided. </P>
                                    <P>(3) Blanket routine uses (Appendix C to this part) have been adopted that apply to all Component system notices. The blanket routine uses appear at the beginning of each Component's compilation of its system notices. </P>
                                    <P>(i) Each system notice shall contain a statement whether or not the blanket routine uses apply to the system. </P>
                                    <P>(ii) Each notice may state that none of the blanket routine uses apply or that one or more do not apply. </P>
                                    <P>
                                        (j) 
                                        <E T="03">Policies and Practices For Storing, Retiring, Accessing, Retaining, and Disposing of Records</E>
                                        . This caption is subdivided into four parts: 
                                    </P>
                                    <P>
                                        (1) 
                                        <E T="03">Storage.</E>
                                         Indicate the medium in which the records are maintained. (For 
                                        <PRTPAGE P="18778"/>
                                        example, a system may be “automated, maintained on compact disks, diskettes,” “manual, maintained in paper files,” or “hybrid, maintained in a combination of paper and automated form.”) Storage does not refer to the container or facility in which the records are kept. 
                                    </P>
                                    <P>
                                        (2) 
                                        <E T="03">Retrievability.</E>
                                         Specify how the records are retrieved (for example, name, SSN, or some other unique personal identifier assigned the individual). 
                                    </P>
                                    <P>
                                        (3) 
                                        <E T="03">Safeguards.</E>
                                         Identify the system safeguards (such as storage in safes, vaults, locked cabinets or rooms, use of guards, visitor registers, personnel screening, or password protected IT systems). Also identify personnel who have access to the systems. Do not describe safeguards in such detail as to compromise system security. 
                                    </P>
                                    <P>
                                        (4) 
                                        <E T="03">Retention and Disposal.</E>
                                         Indicate how long the record is retained. When appropriate, also state the length of time the records are maintained by the Component, when they are transferred to a FRC, time of retention at the Records Center and when they are transferred to the National Archivist or are destroyed. A reference to a Component regulation without further detailed information is insufficient. If records are eventually destroyed as opposed to being retired, identify the method of destruction (e.g., shredding, burning, pulping, etc). 
                                    </P>
                                    <P>
                                        (k) 
                                        <E T="03">System manager or managers and address.</E>
                                         (1) List the title and address of the official responsible for the management of the system. 
                                    </P>
                                    <P>(2) If the title of the specific official is unknown, such as for a local system, specify the local commander or office head as the systems manager. </P>
                                    <P>(3) For geographically separated or organizationally decentralized activities for which individuals may deal directly with officials at each location in exercising their rights, list the position or duty title of each category of officials responsible for the system or a segment thereof. </P>
                                    <P>(4) Do not include business or duty addresses if they are listed in the Component address directory. </P>
                                    <P>
                                        (l) 
                                        <E T="03">Notification Procedures.</E>
                                         (1) Describe how an individual may determine if there are records pertaining to him or her in the system. The procedural rules may be cited, but include a brief procedural description of the needed data. Provide sufficient information in the notice to allow an individual to exercise his or her rights without referral to the formal rules. 
                                    </P>
                                    <P>(2) As a minimum, the caption shall include: </P>
                                    <P>(i) The official title (normally the system manager) and official address to which the request is to be directed. </P>
                                    <P>(ii) The specific information required to determine if there is a record of the individual in the system. </P>
                                    <P>(iii) Identification of the offices through which the individual may obtain notification; and </P>
                                    <P>(iv) A description of any proof of identity required. (see § 310.17(c)). </P>
                                    <P>(3) When appropriate, the individual may be referred to a Component official who shall provide this information to him or her. </P>
                                    <P>
                                        (m) 
                                        <E T="03">Record Access Procedures.</E>
                                         (1) Describe how an individual can gain access to the records pertaining to him or her in the system. The procedural rules may be cited, but include a brief procedural description of the needed data. Provide sufficient information in the notice to allow an individual to exercise his or her rights without referral to the formal rules. 
                                    </P>
                                    <P>(2) As a minimum, the caption shall include: </P>
                                    <P>(i) The official title (normally the system manager) and official address to which the request is to be directed. </P>
                                    <P>(ii) A description of any proof of identity required. (see § 310.17(c)). </P>
                                    <P>(iii) When appropriate, the individual may be referred to a Component official who shall provide the records to him or her. </P>
                                    <P>
                                        (n) 
                                        <E T="03">Contesting Record Procedures.</E>
                                         (1) Describe how an individual may contest the content of a record pertaining to him or her in the system. 
                                    </P>
                                    <P>
                                        (2) The detailed procedures for contesting a record need not be identified if the Component procedural rules are readily available to the public. (For example, “The Office of the Secretary of Defense” rules for contesting contents are contained in 32 CFR 311.) All Component procedural rules are set forth at a Departmental public Web site (
                                        <E T="03">http://www.defenselink.mil/privacy/cfr-rules.html</E>
                                        ). 
                                    </P>
                                    <P>(3) The individual may also be referred to the system manager to determine these procedures. </P>
                                    <P>
                                        (o) 
                                        <E T="03">Record Source Categories.</E>
                                         (1) Describe where (the individual, other Component documentation, other Federal agencies, etc) the information contained in the system was obtained. 
                                    </P>
                                    <P>(2) Specific individuals or institutions need not be identified by name, particularly if these sources have been granted confidentiality. (see § 310.29(b)). </P>
                                    <P>
                                        (p) 
                                        <E T="03">Exemptions claimed for the System.</E>
                                         (1) If no exemption has been claimed for the system, indicate “None.” 
                                    </P>
                                    <P>(2) If an exemption is claimed, cite the exemption as well as identifying the CFR section containing the exemption rule for the system. </P>
                                    <P>
                                        (q) 
                                        <E T="03">Maintaining the Master DoD System Notice Registry.</E>
                                         (1) The DPO maintains a master registry of all DoD record systems notices. 
                                    </P>
                                    <P>
                                        (2) The DPO also posts all DoD system notices to a public Web site (see 
                                        <E T="03">http://www.defenselink.mil/privacy/notices</E>
                                        ). 
                                    </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 310.33 </SECTNO>
                                    <SUBJECT>New and altered record systems. </SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">Criteria for a new record system.</E>
                                         (1) If a Component is maintaining a system of records as contemplated by § 310.10(a), and a system notice has not been published for it in the 
                                        <E T="04">Federal Register</E>
                                        , the Component shall establish a system notice consistent with the requirements of this subpart. 
                                    </P>
                                    <P>
                                        (2) If a notice for a system of records has been canceled or deleted but a determination is subsequently made that the system will be reinstated or reused, the system may not be operated (i.e., information collected or used) until a new notice is published in the 
                                        <E T="04">Federal Register</E>
                                        . 
                                    </P>
                                    <P>
                                        (b) 
                                        <E T="03">Criteria for an altered record system.</E>
                                         A system is considered altered whenever one of the following actions occurs or is proposed: 
                                    </P>
                                    <P>(1) A significant increase or change in the number or type of individuals about whom records are maintained. </P>
                                    <P>(i) Only changes that alter significantly the character and purpose of the record system are considered alterations. </P>
                                    <P>(ii) Increases in numbers of individuals due to normal growth are not considered alterations unless they truly alter the character and purpose of the system. </P>
                                    <P>(iii) Increases that change significantly the scope of population covered (for example, expansion of a system of records covering a single command's enlisted personnel to include all of the Component's enlisted personnel would be considered an alteration). </P>
                                    <P>(iv) A reduction in the number of individuals covered is not an alteration, but only an amendment. (see § 310.34(a).) </P>
                                    <P>(v) All changes that add new categories of individuals to system coverage require a change to the “Categories of individuals covered by the system” caption of the notice (see § 310.32(e)) and may require changes to the “Purpose(s)” caption (see § 310.32(h)). </P>
                                    <P>(2) An expansion in the types or categories of information maintained. </P>
                                    <P>
                                        (i) The addition of any new category of records not described under the 
                                        <PRTPAGE P="18779"/>
                                        “Categories of Records in the System” caption is considered an alteration. 
                                    </P>
                                    <P>(ii) Adding a new data element that is clearly within the scope of the categories of records described in the existing notice is an amendment. (see § 310.34(a)). An amended notice may not be required if the data element is clearly covered by the record category identified in the existing system notice. </P>
                                    <P>(iii) All changes under this criterion require a change to the “Categories of Records in the System” caption of the notice. (see § 310.32(f)). </P>
                                    <P>(3) An alteration of how the records are organized or the manner in which the records are indexed and retrieved. </P>
                                    <P>(i) The change must alter the nature of use or scope of the records involved (for example, combining records systems in a reorganization). </P>
                                    <P>(ii) Any change under this criteria requires a change in the “Retrievability” caption of the system notice. (see § 310.32(j)(2)). </P>
                                    <P>(iii) If the records are no longer retrieved by name or personal identifier cancel the system notice. (see § 310.10(b)). </P>
                                    <P>(4) A change in the purpose for which the information in the system is used. </P>
                                    <P>(i) The new purpose must not be compatible with the existing purposes for which the system is maintained. </P>
                                    <P>(ii) If the use is compatible and reasonably expected, there is no change in purpose and no alteration occurs. </P>
                                    <P>(iii) Any change under this criterion requires a change in the “Purpose(s)” caption (see § 310.32(h)) and may require a change in the “Authority for maintenance of the system” caption (see § 310.32). </P>
                                    <P>(5) Changes that alter the computer environment (such as changes to equipment configuration, software, or procedures) so as to create the potential for greater or easier access. </P>
                                    <P>(i) Increasing the number of offices with direct access is an alteration. </P>
                                    <P>(ii) Software applications, such as operating systems and system utilities, that provide for easier access are considered alterations. </P>
                                    <P>(iii) The addition of an on-line capability to a previously batch-oriented system is an alteration. </P>
                                    <P>(iv) The addition of peripheral devices such as tape devices, disk devices, card readers, printers, and similar devices to an existing IT system constitute an amendment if system security is preserved. (see § 310.34). </P>
                                    <P>(v) Changes to existing equipment configuration with on-line capability need not be considered alterations to the system if: </P>
                                    <P>(A) The change does not alter the present security posture; or </P>
                                    <P>(B) The addition of terminals does not extend the capacity of the current operating system and existing security is preserved. </P>
                                    <P>(vi) The connecting of two or more formerly independent automated systems or networks together creating a potential for greater access is an alteration. </P>
                                    <P>(vii) Any change under this caption requires a change to the “Storage” caption element of the systems notice. (see § 310.32(j)(i)). </P>
                                    <P>
                                        (c) 
                                        <E T="03">Reports of new and altered systems.</E>
                                         (1) Components shall submit a report for all new or altered systems to the DPO consistent with the requirements of this subpart and in the format prescribed at Appendix F of this part. 
                                    </P>
                                    <P>
                                        (i) Components shall include the following when submitting an alteration for a system notice for publication in the 
                                        <E T="04">Federal Register</E>
                                        : 
                                    </P>
                                    <P>(A) The system identifier and name. (see § 310.32(b) and (c)). </P>
                                    <P>(B) A description of the nature and specific changes proposed. </P>
                                    <P>(ii) The full text of the system notice need not be submitted if the master registry contains a current system notice for the system. (see § 310.32(q)). </P>
                                    <P>(2) The DPO coordinates all reports of new and altered systems with the Office of the Assistant Secretary of Defense (Legislative Affairs), Department of Defense. </P>
                                    <P>(3) The DPO prepares and sends a transmittal letter that forwards the report, as well as the new or altered system notice, to OMB and Congress. </P>
                                    <P>
                                        (4) The DPO shall publish in the 
                                        <E T="04">Federal Register</E>
                                         a system notice for new or altered systems. 
                                    </P>
                                    <P>
                                        (d) 
                                        <E T="03">Time restrictions on the operation of a new or altered system.</E>
                                         (1) The reports, and the new or altered system notice, must be provided OMB and Congress at least 40 days prior to the operation of the new or altered system. The 40 day review period begins on the date the transmittal letters are signed and dated. 
                                    </P>
                                    <P>
                                        (2) The system notice must be published in the 
                                        <E T="04">Federal Register</E>
                                         before a Component begins to operate the system (i.e., collect and use the information). If the new system has routine uses or the altered system adds a new routine use, no records may be disclosed pursuant to the routine use until the public has had 30 days to comment on the proposed use. 
                                    </P>
                                    <P>(3) The time periods run concurrently. </P>
                                    <P>
                                        (e) 
                                        <E T="03">Exemptions for new systems.</E>
                                         See § 310.30(e) for the procedures to follow in submitting exemption rules for a new system of records or for submitting an exemption rule for an existing system of records. 
                                    </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 310.34 </SECTNO>
                                    <SUBJECT>Amendment and deletion of system notices. </SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">Criteria for an amended system notice.</E>
                                         (1) Certain minor changes to published systems notices are considered amendments and not alterations. (see § 310.33(b)). 
                                    </P>
                                    <P>
                                        (2) Amendments do not require a report of an altered system (see § 310.33(c)), but must be published in the 
                                        <E T="04">Federal Register</E>
                                        . 
                                    </P>
                                    <P>
                                        (b) 
                                        <E T="03">System notices for amended systems.</E>
                                         Components shall include the following when submitting an amendment for a system notice for publication in the 
                                        <E T="04">Federal Register</E>
                                        :
                                    </P>
                                    <P>(1) The system identifier and name. (see § 310.32 (b) and (c)). </P>
                                    <P>(2) A description of the nature and specific changes proposed. </P>
                                    <P>(3) The full text of the system notice need not be submitted if the master registry contains a current system notice for the system. (see § 310.32(q)). </P>
                                    <P>
                                        (c) 
                                        <E T="03">Deletion of system notices.</E>
                                         (1) Whenever a system is discontinued, combined into another system, or determined no longer to be subject to this part, a deletion notice is required. 
                                    </P>
                                    <P>(2) The notice of deletion shall include: </P>
                                    <P>(i) The system identification and name. </P>
                                    <P>(ii) The reason for the deletion. </P>
                                    <P>(3) When the system is eliminated through combination or merger, identify the successor system or systems in the deletion notice. </P>
                                    <P>
                                        (d) 
                                        <E T="03">Submission of amendments and deletions for publication.</E>
                                         (1) Submit amendments and deletions to the DPO for transmittal to the 
                                        <E T="04">Federal Register</E>
                                         for publication. 
                                    </P>
                                    <P>(2) Multiple deletions and amendments may be combined into a single submission. </P>
                                </SECTION>
                            </SUBPART>
                            <SUBPART>
                                <HD SOURCE="HED">Subpart H—Training Requirements </HD>
                                <SECTION>
                                    <SECTNO>§ 310.35 </SECTNO>
                                    <SUBJECT>Statutory training requirements. </SUBJECT>
                                    <P>The Privacy Act (5 U.S.C. 552a) requires each Agency to establish rules of conduct for all persons involved in the design, development, operation, and maintenance of any system of record and to train these persons with respect to these rules. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 310.36 </SECTNO>
                                    <SUBJECT>OMB training guidelines. </SUBJECT>
                                    <P>The OMB guidelines (OMB Privacy Guidelines, 40 FR 28948 (July 9, 1975) require all agencies additionally to: </P>
                                    <P>
                                        (a) Instruct their personnel in their rules of conduct and other rules and procedures adopted in implementing the Act, to ensure that they are reminded of their specific 
                                        <PRTPAGE P="18780"/>
                                        responsibilities for safeguarding personally identifiable information, the rules for acquiring and using such information, and the penalties for non-compliance. 
                                    </P>
                                    <P>(b) Incorporate training on the special requirements of the Act into both formal and informal (on-the-job) training programs.</P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 310.37 </SECTNO>
                                    <SUBJECT>DoD training programs. </SUBJECT>
                                    <P>(a) The training shall include information regarding information privacy laws, regulations, policies and procedures governing the Department's collection, maintenance, use, or dissemination of personal information. The objective is to establish a culture of sensitivity to, and knowledge about, privacy issues involving individuals throughout the Department. </P>
                                    <P>(b) To meet these training requirements, Components may establish three general levels of training for those persons, to include contractor personnel, who are involved in any way with the design, development, operation, or maintenance of privacy protected systems of records. These are: </P>
                                    <P>
                                        (1) 
                                        <E T="03">Orientation</E>
                                        . Training that provides basic understanding of this part as it applies to the individual's job performance. This training shall be provided to personnel, as appropriate, and should be a prerequisite to all other levels of training. 
                                    </P>
                                    <P>
                                        (2) 
                                        <E T="03">Specialized training</E>
                                        . Training that provides information as to the application of specific provisions of this part to specialized areas of job performance. Personnel of particular concern include, but are not limited to medical, personnel, and intelligence specialists, finance officers, DoD personnel who may be expected to deal with the news media or the public, special investigators, paperwork managers, and other specialists (reports, forms, records, and related functions), computer systems development personnel, computer systems operations personnel, statisticians dealing with personal data and program evaluations, contractors that will either operate systems of records on behalf of the Component or will have access to such systems incident to performing the contract, and anyone responsible for implementing or carrying out functions under this part. 
                                    </P>
                                    <P>
                                        (3) 
                                        <E T="03">Management</E>
                                        . Training designed to identify for responsible managers (such as, senior system managers, denial authorities, and decision-makers) considerations that they shall take into account when making management decisions regarding operational programs and activities having privacy implications. 
                                    </P>
                                    <P>(c) Include Privacy Act training in other courses of training when appropriate. Stress individual responsibilities and advise individuals of their rights and responsibilities under this part to ensure that it is understood that, where personally identifiable information is involved, individuals should handle and treat the information as if it was their information. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 310.38 </SECTNO>
                                    <SUBJECT>Training methodology and procedures. </SUBJECT>
                                    <P>(a) Each DoD Component is responsible for the development of training procedures and methodology. </P>
                                    <P>(b) The DPO shall assist the Components in developing these training programs and may develop privacy training programs for use by all DoD Components. </P>
                                    <P>(c) Components shall conduct training as frequently as believed necessary so that personnel who are responsible for or are in receipt of information protected by 5 U.S.C. 552a are sensitive to the requirements of this part, especially the access, use, and dissemination restrictions. Components shall give consideration to whether annual training and/or annual certification should be mandated for all or specified personnel whose duties and responsibilities require daily interaction with personally identifiable information. </P>
                                    <P>(d) Components shall conduct training that reaches the widest possible audience. Web-based training and video conferencing have been effective means to provide such training. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 310.39 </SECTNO>
                                    <SUBJECT>Funding for training. </SUBJECT>
                                    <P>Each DoD Component shall fund its own privacy training program. </P>
                                </SECTION>
                            </SUBPART>
                            <SUBPART>
                                <HD SOURCE="HED">Subpart I—Reports </HD>
                                <SECTION>
                                    <SECTNO>§ 310.40 </SECTNO>
                                    <SUBJECT>Requirement for reports. </SUBJECT>
                                    <P>The DPO shall establish requirements for DoD Privacy Reports and the DoD Components may be required to provide data. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 310.41 </SECTNO>
                                    <SUBJECT>Suspense for submission of reports. </SUBJECT>
                                    <P>The suspenses for submission of all reports shall be established by the DPO. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 310.42 </SECTNO>
                                    <SUBJECT>Reports control symbol. </SUBJECT>
                                    <P>Any report established by this subpart in support of the Privacy Program shall be assigned Report Control Symbol DD-COMP(A)1379. </P>
                                </SECTION>
                            </SUBPART>
                            <SUBPART>
                                <HD SOURCE="HED">Subpart J—Inspections </HD>
                                <SECTION>
                                    <SECTNO>§ 310.43 </SECTNO>
                                    <SUBJECT>Privacy Act inspections. </SUBJECT>
                                    <P>During internal inspections, Component inspectors shall be alert for compliance with this part and for managerial, administrative, and operational problems associated with the implementation of the Defense Privacy Program. Programs shall be reviewed as frequently as considered necessary by Components or the Component Inspector General. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 310.44 </SECTNO>
                                    <SUBJECT>Inspection reporting. </SUBJECT>
                                    <P>(a) Document the findings of the inspectors in official reports that are furnished the responsible Component officials. These reports, when appropriate, shall reflect overall assets of the Component Privacy Program inspected, or portion thereof, identify deficiencies, irregularities, and significant problems. Also document remedial actions taken to correct problems identified. </P>
                                    <P>(b) Retain inspections reports and later follow-up reports in accordance with established records disposition standards. These reports shall be made available to the Privacy Program officials concerned upon request. </P>
                                </SECTION>
                            </SUBPART>
                            <SUBPART>
                                <HD SOURCE="HED">Subpart K—Privacy Act Violations </HD>
                                <SECTION>
                                    <SECTNO>§ 310.45 </SECTNO>
                                    <SUBJECT>Administrative remedies. </SUBJECT>
                                    <P>Any individual who believes he or she has a legitimate complaint or grievance against the Department of Defense or any DoD employee concerning any right granted by this part shall be permitted to seek relief through appropriate administrative channels. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 310.46 </SECTNO>
                                    <SUBJECT>Civil actions. </SUBJECT>
                                    <P>An individual may file a civil suit against a DoD Component if the individual believes his or her rights under the Act have been violated. (See 5 U.S.C. 552a(g).) </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 310.47 </SECTNO>
                                    <SUBJECT>Civil remedies. </SUBJECT>
                                    <P>In addition to specific remedial actions, the Privacy Act provides for the payment of damages, court costs, and attorney fees in some cases. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 310.48 </SECTNO>
                                    <SUBJECT>Criminal penalties. </SUBJECT>
                                    <P>(a) The Act also provides for criminal penalties. (See 5 U.S.C. 552a(i).) Any official or employee may be found guilty of a misdemeanor and fined not more than $5,000 if he or she willfully: </P>
                                    <P>(1) Discloses information from a system of records, knowing dissemination is prohibited to anyone not entitled to receive the information (see subpart E of this part); or </P>
                                    <P>
                                        (2) Maintains a system of records without publishing the required public notice in the 
                                        <E T="04">Federal Register</E>
                                        . (See subpart G of this part.) 
                                    </P>
                                    <P>
                                        (b) Any person who knowingly and willfully requests or obtains access to 
                                        <PRTPAGE P="18781"/>
                                        any record concerning another individual under false pretenses may be found guilty of misdemeanor and fined up to $5,000. 
                                    </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 310.49 </SECTNO>
                                    <SUBJECT>Litigation status sheet. </SUBJECT>
                                    <P>Whenever a complaint citing the Privacy Act is filed in a U.S. District Court against the Department of Defense, a DoD Component, or any DoD employee, the responsible system manager shall notify the DPO. The litigation status sheet at Appendix H to this part provides a standard format for this notification. The initial litigation status sheet forwarded shall, as a minimum, provide the information required by items 1 through 6 of the status sheet. A revised litigation status sheet shall be provided at each stage of the litigation. When a court renders a formal opinion or judgment, copies of the judgment and opinion shall be provided to the DPO with the litigation status sheet reporting that judgment or opinion. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 310.50 </SECTNO>
                                    <SUBJECT>Lost, stolen, or compromised information. </SUBJECT>
                                    <P>(a) When a loss, theft, or compromise of information occurs (see § 310.14), the breach shall be reported to: </P>
                                    <P>
                                        (1) The United States Computer Emergency Readiness Team (US CERT) within one hour of discovering that a breach of personally identifiable information has occurred. Components shall establish procedures to ensure that US CERT reporting is accomplished in accordance with the guidance set forth at 
                                        <E T="03">http://www.us-cert.gov</E>
                                        . 
                                    </P>
                                    <P>(i) The underlying incident that led to the loss or suspected loss of PII (e.g., computer incident, theft, loss of material, etc.) shall continue to be reported in accordance with established procedures (e.g., to designated Computer Network Defense (CND) Service Providers (reference (z)), law enforcement authorities, the chain of command, etc.). </P>
                                    <P>(ii) [Reserved] </P>
                                    <P>(2) The Senior Component Official for Privacy within 24 hours of discovering that a breach of personally identifiable information has occurred. The Senior Component Official for Privacy, or their designee, shall notify the Defense Privacy Office of the breach within 48 hours upon being notified that a loss, theft, or compromise has occurred. The notification shall include the following information: </P>
                                    <P>(i) Identify the Component/organization involved. </P>
                                    <P>(ii) Specify the date of the breach and the number of individuals impacted, to include whether they are DoD civilian, military, or contractor personnel; DoD civilian or military retirees; family members; other Federal personnel or members of the public, etc. </P>
                                    <P>(iii) Briefly describe the facts and circumstances surrounding the loss, theft, or compromise. </P>
                                    <P>(iv) Briefly describe actions taken in response to the breach, to include whether the incident was investigated and by whom; the preliminary results of the inquiry if then known; actions taken to mitigate any harm that could result from the breach; whether the affected individuals are being notified, and if this will not be accomplished within 10 working days, that action will be initiated to notify the Deputy Secretary (see § 310.14); what remedial actions have been, or will be, taken to prevent a similar such incident in the future, e.g., refresher training conducted, new or revised guidance issued; and any other information considered pertinent as to actions to be taken to ensure that information is properly safeguarded. </P>
                                    <P>(2) The Component shall determine whether administrative or disciplinary action is warranted and appropriate for those individuals determined to be responsible for the loss, theft, or compromise. </P>
                                </SECTION>
                            </SUBPART>
                            <SUBPART>
                                <HD SOURCE="HED">Subpart L—Computer Matching Program Procedures </HD>
                                <SECTION>
                                    <SECTNO>§ 310.51 </SECTNO>
                                    <SUBJECT>General. </SUBJECT>
                                    <P>(a) A computer matching program covers two kinds of matching programs (see OMB Matching Guidelines, 54 FR 25818 (June 19, 1989)). If covered, the matches are subject to the requirements of this subpart. The covered programs are: </P>
                                    <P>(1) Matches using records from Federal personnel or payroll systems of records, or </P>
                                    <P>(2) Matches involving Federal benefits program if: </P>
                                    <P>(i) To determine eligibility for a Federal benefit, </P>
                                    <P>(ii) To determine compliance with benefit program requirements, or </P>
                                    <P>(iii) To effect recovery of improper payments or delinquent debts under a Federal benefit program. </P>
                                    <P>(b) The requirements of this part do not apply if matches are: </P>
                                    <P>(1) Performed solely to produce aggregated statistical data without any personal identifiers. Personally identifying data can be used for purposes of conducting the match. However, the results of the match shall be stripped of any data that would identify an individual. Under no circumstances shall match results be used to take action against specific individuals. </P>
                                    <P>(2) Performed to support research or statistical projects. Personally identifying data can be used for purposes of conducting the match and the match results may contain identifying data about individuals. However, the match results shall not be used to make a decision that affects the rights, benefits, or privileges of specific individuals. </P>
                                    <P>(3) Performed by an agency, or a component thereof, whose principal function is the enforcement of criminal laws, subsequent to the initiation of a specific criminal or civil law enforcement investigation of a named individual or individuals. </P>
                                    <P>(i) The match must flow from an investigation already underway which focuses on a named person or persons. “Fishing expeditions” in which the subjects are generically identified, such as “program beneficiaries” are not covered. </P>
                                    <P>(ii) The match must be for the purpose of gathering evidence against the named individual or individuals. </P>
                                    <P>(4) Performed for tax information-related purposes. </P>
                                    <P>(5) Performed for routine administrative purposes using records relating to Federal personnel. </P>
                                    <P>(i) The records to be used in the match must predominantly relate to Federal personnel (i.e., the percentage of records in the system of records that are about Federal personnel must be greater than of any other category). </P>
                                    <P>(ii) The purpose of the match must not be for purposes of taking any adverse financial, personnel, disciplinary, or other unfavorable action against an individual. </P>
                                    <P>(6) Performed using only records from systems of records maintained by an agency. </P>
                                    <P>(i) The purpose of the match must not be for purposes of taking any adverse financial, personnel, disciplinary, or other unfavorable action against an individual. </P>
                                    <P>(ii) A match of DoD personnel using records in a system of records for purposes of identifying fraud, waste, and abuse is not covered. </P>
                                    <P>(7) Performed to produce background checks for security clearances of Federal or contractor personnel or performed for foreign counter-intelligence purposes. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 310.52 </SECTNO>
                                    <SUBJECT>Computer matching publication and review requirements. </SUBJECT>
                                    <P>
                                        (a) DoD Components shall identify the systems of records that will be used in the match to ensure the publication requirements of subpart G have been satisfied. If the match will require disclosure of records outside the Department of Defense, Components shall ensure a routine use has been established, and that the publication 
                                        <PRTPAGE P="18782"/>
                                        and review requirements have been met, before any disclosures are made (see subpart G of this part). 
                                    </P>
                                    <P>(b) If a computer matching program is contemplated, the DoD Component shall contact the DPO and provide information regarding the contemplated match. The DoD DPO shall ensure that any proposed computer matching program satisfies the requirements of the Privacy Act (5 U.S.C. 552a) and OMB Matching Guidelines (54 FR 25818 (June 19, 1989)). </P>
                                    <P>(c) A computer matching agreement (CMA) shall be prepared by the Component, consistent with the requirements of § 310.53 of this subpart and submitted to the DPO. If the CMA satisfies the requirements of the Privacy Act (5 U.S.C. 552a) and OMB Matching Guidelines (54 FR 25818 (June 19, 1989)), as well as this subpart, it shall be forwarded to the Defense Data Integrity Board (DIB) for approval or disapproval. </P>
                                    <P>(1) If the CMA is approved by the DIB, the DPO shall prepare and forward a report to both Houses of Congress and to OMB as required by, and consistent with, OMB Circular A-130, “Management of Federal Information Resources,” February 8, 1996, as amended. Congress and OMB shall have 40 days to review and comment on the proposed match. Any comments received must be resolved before matching can take place. </P>
                                    <P>
                                        (2) If the CMA is approved by the DIB, the DPO shall prepare and forward a match notice as required by OMB Circular A-130, “Management of Federal Information Resources,” February 8, 1996, as amended, for publication in the 
                                        <E T="04">Federal Register</E>
                                        . The public shall be given 30 days to comment on the proposed match. Any comments received must be resolved before matching can take place. 
                                    </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 310.53 </SECTNO>
                                    <SUBJECT>Computer matching agreements (CMAs). </SUBJECT>
                                    <P>(a) If a match is to be conducted internally within DoD, a memorandum of understanding (MOU) shall be prepared. It shall contain the same elements as a CMA, except as otherwise indicated in paragraph (b)(4)(ii) of this section. </P>
                                    <P>(b) A CMA shall contain the following elements: </P>
                                    <P>
                                        (1) 
                                        <E T="03">Purpose</E>
                                        . Why the match is being proposed and what will be achieved by conducting the match. 
                                    </P>
                                    <P>
                                        (2) 
                                        <E T="03">Legal authority</E>
                                        . What is the Federal or state statutory or regulatory basis for conducting the match. The Privacy Act does not constitute independent authority for matching. Other legal authority shall be identified.
                                    </P>
                                    <P>
                                        (3) 
                                        <E T="03">Justification and expected results</E>
                                        . Explain why computer matching as opposed to some other administrative means is being proposed and what the expected results will be, including a specific estimate of any savings (see paragraph (b)(13) of this section). 
                                    </P>
                                    <P>
                                        (4) 
                                        <E T="03">Records description</E>
                                        . Identify: 
                                    </P>
                                    <P>
                                        (i) The system of records or non-Federal records. For DoD systems of records, provide the 
                                        <E T="04">Federal Register</E>
                                         citation for the system notice; 
                                    </P>
                                    <P>(ii) The specific routine use in the system notice if records are to be disclosed outside the Department of Defense (see § 310.22(c)). If records are disclosed within the Department of Defense for an internal match, disclosures are permitted pursuant to paragraph (a) of § 310.22. </P>
                                    <P>(iii) The number of records involved; </P>
                                    <P>(iv) The data elements to be included in the match; </P>
                                    <P>(v) The projected start and completion dates of the match. CMAs remain in effect for 18 months but can be renewed for an additional 12 months provided: </P>
                                    <P>(A) The match will be conducted without any change, and </P>
                                    <P>(B) Each party to the match certifies in writing that the program has been conducted in compliance with the CMA or MOU. </P>
                                    <P>(vi) How frequently will the records be matched. </P>
                                    <P>
                                        (5) 
                                        <E T="03">Records accuracy assessment</E>
                                        . Provide an assessment by the source and recipient agencies as to the quality of the information that will be used for the match. The poorer the quality, the more likely that the program will not be cost-effective. 
                                    </P>
                                    <P>
                                        (6) 
                                        <E T="03">Notice Procedures</E>
                                        . Identify what direct and indirect means will be used to inform individuals that matching will take place. 
                                    </P>
                                    <P>
                                        (i) 
                                        <E T="03">Direct notice</E>
                                        . Indicate whether the individual is advised that matching may be conducted when he or she applies for a Federal benefit program. Such an advisory should normally be part of the Privacy Act Statement that is contained in the application for benefits. Individual notice sometimes is provided by a separate notice that is furnished the individual upon receipt of the benefit. 
                                    </P>
                                    <P>
                                        (ii) 
                                        <E T="03">Indirect notice</E>
                                        . Indicate whether the individual is advised that matching may be conducted by constructive notice. Indirect or constructive notice is achieved by publication of a routine use in the 
                                        <E T="04">Federal Register</E>
                                         when the matching is between agencies or is achieved by publication of the match notice in the 
                                        <E T="04">Federal Register</E>
                                        . 
                                    </P>
                                    <P>
                                        (7) 
                                        <E T="03">Verification procedures</E>
                                        . Explain how information produced as a result of the match will be independently verified to ensure any adverse information obtained is that of the individual identified in the match. 
                                    </P>
                                    <P>
                                        (8) 
                                        <E T="03">Due process procedures</E>
                                        . Describe what procedures will be used to notify individuals of any adverse information uncovered as a result of the match and to give such individuals an opportunity to either explain the information or how to contest the information. No adverse action shall be taken against the individual until the due process procedures have been satisfied. 
                                    </P>
                                    <P>(i) Unless other statutory or regulatory authority provides for a longer period of time, the individual shall be given 30 calendar days from the date of the notice to respond to the notice. </P>
                                    <P>(ii) If an individual contacts the agency within the notice period and indicates his or her acceptance of the validity of the adverse information, the agency may take final action. If the period expires without a response, the agency may take final action. </P>
                                    <P>(iii) If the agency determines that there is a potentially significant effect on public health or safety, it may take appropriate action notwithstanding the due process provisions. </P>
                                    <P>
                                        (9) 
                                        <E T="03">Security procedures</E>
                                        . Describe the administrative, technical, and physical safeguards that will be established to preserve and protect the privacy and confidentiality of the records involved in the match. The level of security must be commensurate with the level of the sensitivity of the records. 
                                    </P>
                                    <P>
                                        (10) 
                                        <E T="03">Records usage, duplication, and redisclosure restrictions</E>
                                        . Describe any restrictions imposed by the source agency or by statute or regulation on the collateral uses of the records. Recipient agencies may not use the records obtained for matching purposes for any other purpose absent a specific statutory requirement or where the disclosure is essential to the conduct of the matching program. 
                                    </P>
                                    <P>
                                        (11) 
                                        <E T="03">Disposition procedures</E>
                                        . Clearly state that the records used in the match will be retained only for the time required for conducting the match. Once the matching purpose has been achieved, the records will be destroyed unless the records must be retained as directed by other legal authority. Unless the source agency requests that the records be returned, identify the means by which destruction will occur, i.e., shredding, burning, electronic erasure, etc. 
                                    </P>
                                    <P>
                                        (12) 
                                        <E T="03">Comptroller General access</E>
                                        . Include a statement that the Comptroller General may have access to all records of the recipient agency to monitor or verify compliance with the terms of the CMA. 
                                    </P>
                                    <P>
                                        (13) 
                                        <E T="03">Cost-benefit analysis</E>
                                        . 
                                        <PRTPAGE P="18783"/>
                                    </P>
                                    <P>(i) A cost-benefit analysis shall be conducted for the proposed computer matching program unless: </P>
                                    <P>(A) The Data Integrity Board waives the requirement, or </P>
                                    <P>(B) The matching program is required by a specific statute. </P>
                                    <P>(ii) The analysis must demonstrate that the program is likely to be cost-effective. This analysis is to ensure agencies are following sound management practices. The analysis provides an opportunity to examine the programs and to reject those that will only produce marginal results. </P>
                                    <APPENDIX>
                                        <HD SOURCE="HED">Appendix A to Part 310—Safeguarding Personally Identifiable Information (PII)</HD>
                                        <FP>(See § 310.13 of Subpart B) </FP>
                                        <HD SOURCE="HD1">A. General </HD>
                                        <P>1. The IT environment subjects personal information to special hazards as to unauthorized compromise, alteration, dissemination, and use. Therefore, special considerations must be given to safeguarding personal information in IT systems consistent with the requirements of DoD Directive 8500.1 and DoD Instruction 8500.2. </P>
                                        <P>2. Personally identifiable information must also be protected while it is being processed or accessed in computer environments outside the data processing installation (such as, remote job entry stations, terminal stations, minicomputers, microprocessors, and similar activities). </P>
                                        <P>3. IT facilities authorized to process classified material have adequate procedures and security for the purposes of this Regulation. However, all unclassified information subject to this Regulation must be processed following the procedures used to process and access information designated “For Official Use Only.” (See DoD 5200.1-R.) </P>
                                        <HD SOURCE="HD1">B. Risk Management and Safeguarding Standards </HD>
                                        <P>1. Establish administrative, technical, and physical safeguards that are adequate to protect the information against unauthorized disclosure, access, or misuse. (See OMB Circular A-130 and DoD Instruction 8500.2.) </P>
                                        <P>2. Tailor safeguards to the type of system, the nature of the information involved, and the specific threat to be countered. </P>
                                        <HD SOURCE="HD1">C. Minimum Administrative Safeguards </HD>
                                        <P>The minimum safeguarding standards as set forth in § 310.13(b) apply to all personal data within any IT system. In addition: </P>
                                        <P>1. Consider the following when establishing IT safeguards: </P>
                                        <P>a. The sensitivity of the data being processed, stored and accessed. </P>
                                        <P>b. The installation environment. </P>
                                        <P>c. The risk of exposure. </P>
                                        <P>d. The cost of the safeguard under consideration. </P>
                                        <P>2. Label or designate media products containing personal information that do not contain classified material in such a manner as to alert those using or handling the information of the need for special protection. Designating products “For Official Use Only” in accordance with the requirements of DoD 5200.1-R satisfies this requirement. </P>
                                        <P>3. Mark and protect all computer products containing classified data in accordance with the requirements of DoD 5200.1-R and DoD Directive 8500.1. </P>
                                        <P>4. Mark and protect all computer products containing “For Official Use Only” material in accordance with the requirements of DoD 5200.1-R. </P>
                                        <P>5. Ensure that safeguards for protected information stored at secondary sites are appropriate. </P>
                                        <P>6. If there is a computer failure, restore all protected information being processed at the time of the failure using proper recovery procedures to ensure data integrity. </P>
                                        <P>7. Train personnel involved in processing information subject to this Regulation in proper safeguarding procedures. </P>
                                        <HD SOURCE="HD1">D. Physical Safeguards </HD>
                                        <P>1. For all unclassified facilities, areas, and devices that process information subject to this Regulation, establish physical safeguards that protect the information against reasonably identifiable threats that could result in unauthorized access or alteration. </P>
                                        <P>2. Develop access procedures for unclassified computer rooms, tape libraries, micrographic facilities, decollating shops, product distribution areas, or other direct support areas that process or contain personal information subject to this Regulation that control adequately access to these areas. </P>
                                        <P>3. Safeguard on-line devices directly coupled to IT systems that contain or process information from systems of records to prevent unauthorized disclosure, use, or alteration. </P>
                                        <P>4. Dispose of paper records following appropriate record destruction procedures. (See § 310.13(c) and DoD 5200.1-R.) </P>
                                        <HD SOURCE="HD1">E. Technical Safeguards </HD>
                                        <P>1. Components are to ensure that all PII not explicitly cleared for public release is protected according to Confidentially Level Sensitive, as established in DoD Instruction 8500.2. In addition, all DoD information and data owners shall conduct risk assessments of compilations of PII and identify those needing more stringent protection for remote access or mobile computing. </P>
                                        <P>2. Encrypt unclassified personal information in accordance with current Information Assurance (IA) policies and procedures, as issued. </P>
                                        <P>3. Remove personal data stored on magnetic storage media by methods that preclude reconstruction of the data. </P>
                                        <P>4. Ensure that personal information is not inadvertently disclosed as residue when transferring magnetic media between activities. </P>
                                        <P>5. Only DoD authorized devices shall be used for remote access. Any remote access, whether for user or privileged functions, must conform to IA controls specified in DoD Instruction 8500.2. </P>
                                        <P>6. Remote access for processing PII should comply with the latest IA policies and procedures. </P>
                                        <P>7. Minimize access to data fields necessary to accomplish an employee's task-normally, access shall be granted only to those data elements (fields) required for the employee to perform his or her job rather than granting access to the entire database. </P>
                                        <P>8. Do not totally rely on proprietary software products to protect personnel data during processing or storage. </P>
                                        <HD SOURCE="HD1">F. Special Procedures </HD>
                                        <P>1. Managers shall: </P>
                                        <P>a. Prepare and submit for publication all system notices and amendments and alterations thereto. (See § 310.30(f).) </P>
                                        <P>b. Identify required controls and individuals authorized access to PII and maintain updates to the access authorizations. </P>
                                        <P>c. When required, ensure Privacy Impact Assessments are prepared consistent with the requirements of the DoD Deputy Chief Information Officer Memorandum, “DoD Privacy Impact Assessment Guidance,” October 28, 2005. </P>
                                        <P>d. Train all personnel whose official duties require access to the system of records in the proper safeguarding and use of the information and ensure that they receive Privacy Act training. </P>
                                        <HD SOURCE="HD1">G. Record Disposal </HD>
                                        <P>1. Dispose of records subject to this Regulation so as to prevent compromise. (See § 310.13(c).) Magnetic tapes or other magnetic medium may be cleared by degaussing, overwriting, or erasing. (See DoD Memorandum, “Disposition of Unclassified DoD Computer Hard Drives,” June 4, 2001.) </P>
                                        <P>2. Do not use respliced waste computer products containing personal data. </P>
                                    </APPENDIX>
                                    <APPENDIX>
                                        <HD SOURCE="HED">Appendix B to Part 310—Sample Notification Letter </HD>
                                        <FP>(See § 310.14 of subpart C) </FP>
                                        <FP>Dear Mr. John Miller: </FP>
                                        <P>On January 1, 2006, a Department of Defense (DoD) laptop computer was stolen from the parked car of a DoD employee in Washington, DC after normal duty hours while the employee was running a personal errand. The laptop contained personally identifying information on 100 DoD employees who were participating in the xxx Program. The compromised information is the name, social security number, residential address, date of birth, office and home email address, office and home telephone numbers of the Program participants. </P>
                                        <P>The theft was immediately reported to local and DoD law enforcement authorities who are now conducting a joint inquiry into the loss. </P>
                                        <P>
                                            We believe that the laptop was the target of the theft as opposed to any information that the laptop might contain. Because the information in the laptop was password protected and encrypted, we also believe that the probability is low that the information will be acquired and used for an unlawful purpose. However, we cannot say with certainty that this might not occur. We therefore believe that you should consider taking such actions as are possible to protect against the potential that someone might use the information to steal your identity. 
                                            <PRTPAGE P="18784"/>
                                        </P>
                                        <P>
                                            You should be guided by the actions recommended by the Federal Trade Commission at its Web site at 
                                            <E T="03">http://www.consumer.gov/idtheft/con_steps.htm.</E>
                                             The FTC urges that you immediately place an initial fraud alert on your credit file. The Fraud alert is for a period of 90 days, during which, creditors are required to contact you before a new credit card is issued or an existing card changed. The site also provides other valuable information that can be taken now or in the future if problems should develop. 
                                        </P>
                                        <P>The DoD takes this loss very seriously and is reviewing its current policies and practices with a view of determining what must be changed to preclude a similar occurrence in the future. At a minimum, we will be providing additional training to personnel to ensure that they understand that personally identifiable information must at all times be treated in a manner that preserves and protects the confidentiality of the data. </P>
                                        <P>We deeply regret and apologize for any inconvenience and concern this theft may cause you. </P>
                                        <P>Should you have any questions, please call ______.</P>
                                        <FP>Sincerely, </FP>
                                        <FP>Signature Block </FP>
                                        <FP>(Directorate level or higher)</FP>
                                    </APPENDIX>
                                    <APPENDIX>
                                        <HD SOURCE="HED">Appendix C to Part 310—DoD Blanket Routine Uses </HD>
                                        <FP>(See paragraph (c) of § 310.22 of subpart E) </FP>
                                        <HD SOURCE="HD1">A. Routine Use—Law Enforcement </HD>
                                        <P>If a system of records maintained by a DoD Component to carry out its functions indicates a violation or potential violation of law, whether civil, criminal, or regulatory in nature, and whether arising by general statute or by regulation, rule, or order issued pursuant thereto, the relevant records in the system of records may be referred, as a routine use, to the agency concerned, whether Federal, State, local, or foreign, charged with the responsibility of investigating or prosecuting such violation or charged with enforcing or implementing the statute, rule, regulation, or order issued pursuant thereto. </P>
                                        <HD SOURCE="HD1">B. Routine Use—Disclosure When Requesting Information </HD>
                                        <P>A record from a system of records maintained by a Component may be disclosed as a routine use to a Federal, State, or local agency maintaining civil, criminal, or other relevant enforcement information or other pertinent information, such as current licenses, if necessary to obtain information relevant to a Component decision concerning the hiring or retention of an employee, the issuance of a security clearance, the letting of a contract, or the issuance of a license, grant, or other benefit. </P>
                                        <HD SOURCE="HD1">C. Routine Use—Disclosure Of Requested Information </HD>
                                        <P>A record from a system of records maintained by a Component may be disclosed to a Federal agency, in response to its request, in connection with the hiring or retention of an employee, the issuance of a security clearance, the reporting of an investigation of an employee, the letting of a contract, or the issuance of a license, grant, or other benefit by the requesting agency, to the extent that the information is relevant and necessary to the requesting agency's decision on the matter. </P>
                                        <HD SOURCE="HD1">D. Routine Use—Congressional Inquiries </HD>
                                        <P>Disclosure from a system of records maintained by a Component may be made to a congressional office from the record of an individual in response to an inquiry from the congressional office made at the request of that individual. </P>
                                        <HD SOURCE="HD1">E. Routine Use—Private Relief Legislation </HD>
                                        <P>Relevant information contained in all systems of records of the Department of Defense published on or before August 22, 1975, may be disclosed to the Office of Management and Budget in connection with the review of private relief legislation as set forth in OMB Circular A-19 at any stage of the legislative coordination and clearance process as set forth in that circular. </P>
                                        <HD SOURCE="HD1">F. Routine Use—Disclosures Required By International Agreements </HD>
                                        <P>A record from a system of records maintained by a Component may be disclosed to foreign law enforcement, security, investigatory, or administrative authorities to comply with requirements imposed by, or to claim rights conferred in, international agreements and arrangements, including those regulating the stationing and status in foreign countries of Department of Defense military and civilian personnel. </P>
                                        <HD SOURCE="HD1">G. Routine Use—Disclosure to State and Local Taxing Authorities </HD>
                                        <P>Any information normally contained in Internal Revenue Service (IRS) Form W-2 which is maintained in a record from a system of records maintained by a Component may be disclosed to State and local taxing authorities with which the Secretary of the Treasury has entered into agreements under 5 U.S.C., sections 5516, 5517, 5520, and only to those State and local taxing authorities for which an employee or military member is or was subject to tax regardless of whether tax is or was withheld. This routine use is in accordance with Treasury Fiscal Requirements Manual Bulletin No. 76-07. </P>
                                        <HD SOURCE="HD1">H. Routine Use—Disclosure to the Office of Personnel Management </HD>
                                        <P>A record from a system of records subject to the Privacy Act and maintained by a Component may be disclosed to the Office of Personnel Management (OPM) concerning information on pay and leave, benefits, retirement reductions, and any other information necessary for the OPM to carry out its legally authorized government-wide personnel management functions and studies. </P>
                                        <HD SOURCE="HD1">I. Routine Use—Disclosure to the Department of Justice for Litigation</HD>
                                        <P>A record from a system of records maintained by a Component may be disclosed as a routine use to any component of the Department of Justice for the purpose of representing the Department of Defense, or any officer, employee or member of the Department in pending or potential litigation to which the record is pertinent. </P>
                                        <HD SOURCE="HD1">J. Routine Use—Disclosure to Military Banking Facilities </HD>
                                        <P>Information as to current military addresses and assignments may be provided to military banking facilities who provide banking services overseas and who are reimbursed by the Government for certain checking and loan losses. For personnel separated, discharged, or retired from the Armed Forces, information as to last known residential or home of record address may be provided to the military banking facility upon certification by a banking facility officer that the facility has a returned or dishonored check negotiated by the individual or the individual has defaulted on a loan and that if restitution is not made by the individual, the U.S. Government will be liable for the losses the facility may incur. </P>
                                        <HD SOURCE="HD1">K. Routine Use—Disclosure of Information to the General Services Administration </HD>
                                        <P>A record from a system of records maintained by a Component may be disclosed as a routine use to the General Services Administration (GSA) for the purpose of records management inspections conducted under authority of 44 U.S.C. 2904 and 2906. </P>
                                        <HD SOURCE="HD1">L. Routine Use—Disclosure of Information to the National Archives and Records Administration </HD>
                                        <P>A record from a system of records maintained by a Component may be disclosed as a routine use to the National Archives and Records Administration (NARA) for the purpose of records management inspections conducted under authority of 44 U.S.C. 2904 and 2906. </P>
                                        <HD SOURCE="HD1">M. Routine Use—Disclosure to the Merit Systems Protection Board </HD>
                                        <P>A record from a system of records maintained by a Component may be disclosed as a routine use to the Merit Systems Protection Board, including the Office of the Special Counsel, for the purpose of litigation, including administrative proceedings, appeals, special studies of the civil service and other merit systems, review of OPM or Component rules and regulations, investigation of alleged or possible prohibited personnel practices, including administrative proceedings involving any individual subject of a DoD investigation, and such other functions, promulgated in 5 U.S.C. 1205 and 1206 or as may be authorized by law. </P>
                                        <HD SOURCE="HD1">N. Routine Use—Counterintelligence Purposes </HD>
                                        <P>A record from a system of records maintained by a Component may be disclosed as a routine use outside the Department of Defense (DoD) or the U.S. Government for the purpose of counterintelligence activities authorized by U.S. law or Executive Order or for the purpose of enforcing laws that protect the national security of the United States. </P>
                                    </APPENDIX>
                                    <APPENDIX>
                                        <PRTPAGE P="18785"/>
                                        <HD SOURCE="HED">Appendix D to Part 310—Provisions of the Privacy Act From Which a General or Specific Exemption May Be Claimed </HD>
                                        <FP>(See paragraph (d) of § 310.26 ) </FP>
                                        <GPOTABLE COLS="03" OPTS="L2,tp0,i1" CDEF="xs60,xs60,r100">
                                            <TTITLE> </TTITLE>
                                            <BOXHD>
                                                <CHED H="1">Exemptions</CHED>
                                                <CHED H="2">(j)(2)</CHED>
                                                <CHED H="2">(k) (1-7)</CHED>
                                                <CHED H="1">Section of the Privacy Act</CHED>
                                            </BOXHD>
                                            <ROW>
                                                <ENT I="01">No</ENT>
                                                <ENT>No</ENT>
                                                <ENT>(b)(1) Disclosures within the Department of Defense.</ENT>
                                            </ROW>
                                            <ROW>
                                                <ENT I="01">No</ENT>
                                                <ENT>No</ENT>
                                                <ENT>(2) Disclosures to the public.</ENT>
                                            </ROW>
                                            <ROW>
                                                <ENT I="01">No</ENT>
                                                <ENT>No</ENT>
                                                <ENT>(3) Disclosures for a “Routine Use.”</ENT>
                                            </ROW>
                                            <ROW>
                                                <ENT I="01">No</ENT>
                                                <ENT>No</ENT>
                                                <ENT>(4) Disclosures to the Bureau of Census.</ENT>
                                            </ROW>
                                            <ROW>
                                                <ENT I="01">No</ENT>
                                                <ENT>No</ENT>
                                                <ENT>(5) Disclosures for statistical research and reporting.</ENT>
                                            </ROW>
                                            <ROW>
                                                <ENT I="01">No</ENT>
                                                <ENT>No</ENT>
                                                <ENT>(6) Disclosures to the NARA.</ENT>
                                            </ROW>
                                            <ROW>
                                                <ENT I="01">No</ENT>
                                                <ENT>No</ENT>
                                                <ENT>(7) Disclosures for law enforcement purposes.</ENT>
                                            </ROW>
                                            <ROW>
                                                <ENT I="01">No</ENT>
                                                <ENT>No</ENT>
                                                <ENT>(8) Disclosures under emergency circumstances.</ENT>
                                            </ROW>
                                            <ROW>
                                                <ENT I="01">No</ENT>
                                                <ENT>No</ENT>
                                                <ENT>(9) Disclosures to the Congress.</ENT>
                                            </ROW>
                                            <ROW>
                                                <ENT I="01">No</ENT>
                                                <ENT>No</ENT>
                                                <ENT>(10) Disclosures to the GAO.</ENT>
                                            </ROW>
                                            <ROW>
                                                <ENT I="01">No</ENT>
                                                <ENT>No</ENT>
                                                <ENT>(11) Disclosures pursuant to court orders.</ENT>
                                            </ROW>
                                            <ROW>
                                                <ENT I="01">No</ENT>
                                                <ENT>No</ENT>
                                                <ENT>(12) Disclosure to consumer reporting agencies.</ENT>
                                            </ROW>
                                            <ROW>
                                                <ENT I="01">No</ENT>
                                                <ENT>No</ENT>
                                                <ENT>(c)(1) Making disclosure accountings.</ENT>
                                            </ROW>
                                            <ROW>
                                                <ENT I="01">No</ENT>
                                                <ENT>No</ENT>
                                                <ENT>(2) Retaining disclosure accountings.</ENT>
                                            </ROW>
                                            <ROW>
                                                <ENT I="01">Yes</ENT>
                                                <ENT>Yes</ENT>
                                                <ENT>(c)(3) Making disclosure accounting available to the individual.</ENT>
                                            </ROW>
                                            <ROW>
                                                <ENT I="01">Yes</ENT>
                                                <ENT>No</ENT>
                                                <ENT>(c)(4) Informing prior recipients of corrections.</ENT>
                                            </ROW>
                                            <ROW>
                                                <ENT I="01">Yes</ENT>
                                                <ENT>Yes</ENT>
                                                <ENT>(d)(1) Individual access to records.</ENT>
                                            </ROW>
                                            <ROW>
                                                <ENT I="01">Yes</ENT>
                                                <ENT>Yes</ENT>
                                                <ENT>(2) Amending records.</ENT>
                                            </ROW>
                                            <ROW>
                                                <ENT I="01">Yes</ENT>
                                                <ENT>Yes</ENT>
                                                <ENT>(3) Review of the Component's refusal to amend a record.</ENT>
                                            </ROW>
                                            <ROW>
                                                <ENT I="01">Yes</ENT>
                                                <ENT>Yes</ENT>
                                                <ENT>(4) Disclosure of disputed information.</ENT>
                                            </ROW>
                                            <ROW>
                                                <ENT I="01">Yes</ENT>
                                                <ENT>Yes</ENT>
                                                <ENT>(5) Access to information compiled in anticipation of civil action.</ENT>
                                            </ROW>
                                            <ROW>
                                                <ENT I="01">Yes</ENT>
                                                <ENT>Yes</ENT>
                                                <ENT>(e)(1) Restrictions on collecting information.</ENT>
                                            </ROW>
                                            <ROW>
                                                <ENT I="01">Yes</ENT>
                                                <ENT>No</ENT>
                                                <ENT>(e)(2) Collecting directly from the individual.</ENT>
                                            </ROW>
                                            <ROW>
                                                <ENT I="01">Yes</ENT>
                                                <ENT>No</ENT>
                                                <ENT>(3) Informing individuals from whom information is requested.</ENT>
                                            </ROW>
                                            <ROW>
                                                <ENT I="01">No</ENT>
                                                <ENT>No</ENT>
                                                <ENT>(e)(4)(A) Describing the name and location of the system.</ENT>
                                            </ROW>
                                            <ROW>
                                                <ENT I="01">No</ENT>
                                                <ENT>No</ENT>
                                                <ENT>(B) Describing categories of individuals.</ENT>
                                            </ROW>
                                            <ROW>
                                                <ENT I="01">No</ENT>
                                                <ENT>No</ENT>
                                                <ENT>(C) Describing categories of records.</ENT>
                                            </ROW>
                                            <ROW>
                                                <ENT I="01">No</ENT>
                                                <ENT>No</ENT>
                                                <ENT>(D) Describing routine uses.</ENT>
                                            </ROW>
                                            <ROW>
                                                <ENT I="01">No</ENT>
                                                <ENT>No</ENT>
                                                <ENT>(E) Describing records management policies and practices.</ENT>
                                            </ROW>
                                            <ROW>
                                                <ENT I="01">No</ENT>
                                                <ENT>No</ENT>
                                                <ENT>(F) Identifying responsible officials.</ENT>
                                            </ROW>
                                            <ROW>
                                                <ENT I="01">Yes</ENT>
                                                <ENT>Yes</ENT>
                                                <ENT>(e)(4)(G) Procedures for determining if a system contains a record on an individual.</ENT>
                                            </ROW>
                                            <ROW>
                                                <ENT I="01">Yes</ENT>
                                                <ENT>Yes</ENT>
                                                <ENT>(H) Procedures for gaining access.</ENT>
                                            </ROW>
                                            <ROW>
                                                <ENT I="01">Yes</ENT>
                                                <ENT>Yes</ENT>
                                                <ENT>(I) Describing categories of information sources.</ENT>
                                            </ROW>
                                            <ROW>
                                                <ENT I="01">Yes</ENT>
                                                <ENT>No</ENT>
                                                <ENT>(e)(5) Standards of accuracy.</ENT>
                                            </ROW>
                                            <ROW>
                                                <ENT I="01">No</ENT>
                                                <ENT>No</ENT>
                                                <ENT>(e)(6) Validating records before disclosure.</ENT>
                                            </ROW>
                                            <ROW>
                                                <ENT I="01">No</ENT>
                                                <ENT>No</ENT>
                                                <ENT>(e)(7) Records of First Amendment activities.</ENT>
                                            </ROW>
                                            <ROW>
                                                <ENT I="01">No</ENT>
                                                <ENT>No</ENT>
                                                <ENT>(e)(8) Notification of disclosure under compulsory legal process.</ENT>
                                            </ROW>
                                            <ROW>
                                                <ENT I="01">No</ENT>
                                                <ENT>No</ENT>
                                                <ENT>(e)(9) Rules of conduct.</ENT>
                                            </ROW>
                                            <ROW>
                                                <ENT I="01">No</ENT>
                                                <ENT>No</ENT>
                                                <ENT>(e)(10) Administrative, technical, and physical safeguards.</ENT>
                                            </ROW>
                                            <ROW>
                                                <ENT I="01">No</ENT>
                                                <ENT>No</ENT>
                                                <ENT>(11) Notice for new and revised routine uses.</ENT>
                                            </ROW>
                                            <ROW>
                                                <ENT I="01">Yes</ENT>
                                                <ENT>Yes</ENT>
                                                <ENT>(f)(1) Rules for determining if an individual is subject of a record.</ENT>
                                            </ROW>
                                            <ROW>
                                                <ENT I="01">Yes</ENT>
                                                <ENT>Yes</ENT>
                                                <ENT>(f)(2) Rules for handling access requests.</ENT>
                                            </ROW>
                                            <ROW>
                                                <ENT I="01">Yes</ENT>
                                                <ENT>Yes</ENT>
                                                <ENT>(f)(3) Rules for granting access.</ENT>
                                            </ROW>
                                            <ROW>
                                                <ENT I="01">Yes</ENT>
                                                <ENT>Yes</ENT>
                                                <ENT>(f)(4) Rules for amending records.</ENT>
                                            </ROW>
                                            <ROW>
                                                <ENT I="01">Yes</ENT>
                                                <ENT>Yes</ENT>
                                                <ENT>(f)(5) Rules regarding fees.</ENT>
                                            </ROW>
                                            <ROW>
                                                <ENT I="01">Yes</ENT>
                                                <ENT>No</ENT>
                                                <ENT>(g)(1) Basis for civil action.</ENT>
                                            </ROW>
                                            <ROW>
                                                <ENT I="01">Yes</ENT>
                                                <ENT>No</ENT>
                                                <ENT>(g)(2) Basis for judicial review and remedies for refusal to amend.</ENT>
                                            </ROW>
                                            <ROW>
                                                <ENT I="01">Yes</ENT>
                                                <ENT>No</ENT>
                                                <ENT>(g)(3) Basis for judicial review and remedies for denial of access.</ENT>
                                            </ROW>
                                            <ROW>
                                                <ENT I="01">Yes</ENT>
                                                <ENT>No</ENT>
                                                <ENT>(g)(4) Basis for judicial review and remedies for other failure to comply.</ENT>
                                            </ROW>
                                            <ROW>
                                                <ENT I="01">Yes</ENT>
                                                <ENT>No</ENT>
                                                <ENT>(g)(5) Jurisdiction and time limits.</ENT>
                                            </ROW>
                                            <ROW>
                                                <ENT I="01">Yes</ENT>
                                                <ENT>No</ENT>
                                                <ENT>(h) Rights of legal guardians.</ENT>
                                            </ROW>
                                            <ROW>
                                                <ENT I="01">No</ENT>
                                                <ENT>No</ENT>
                                                <ENT>(i)(1) Criminal penalties for unauthorized disclosure.</ENT>
                                            </ROW>
                                            <ROW>
                                                <ENT I="01">No</ENT>
                                                <ENT>No</ENT>
                                                <ENT>(2) Criminal penalties for failure to publish.</ENT>
                                            </ROW>
                                            <ROW>
                                                <ENT I="01">No</ENT>
                                                <ENT>No</ENT>
                                                <ENT>(3) Criminal penalties for obtaining records under false pretenses.</ENT>
                                            </ROW>
                                            <ROW>
                                                <ENT I="01">
                                                    Yes 
                                                    <SU>1</SU>
                                                </ENT>
                                                <ENT>No</ENT>
                                                <ENT>(j) Rulemaking requirement.</ENT>
                                            </ROW>
                                            <ROW>
                                                <ENT I="01">N/A</ENT>
                                                <ENT>No</ENT>
                                                <ENT>(j)(1) General exemption for the Central Intelligence Agency.</ENT>
                                            </ROW>
                                            <ROW>
                                                <ENT I="01">N/A</ENT>
                                                <ENT>No</ENT>
                                                <ENT>(j)(2) General exemption for criminal law enforcement records.</ENT>
                                            </ROW>
                                            <ROW>
                                                <ENT I="01">Yes</ENT>
                                                <ENT>No</ENT>
                                                <ENT>(k)(1) Exemption for classified material.</ENT>
                                            </ROW>
                                            <ROW>
                                                <ENT I="01">N/A</ENT>
                                                <ENT>No</ENT>
                                                <ENT>(k)(2) Exemption for law enforcement material.</ENT>
                                            </ROW>
                                            <ROW>
                                                <ENT I="01">Yes</ENT>
                                                <ENT>N/A</ENT>
                                                <ENT>(k)(3) Exemption for records pertaining to Presidential protection.</ENT>
                                            </ROW>
                                            <ROW>
                                                <ENT I="01">Yes</ENT>
                                                <ENT>N/A</ENT>
                                                <ENT>(k)(4) Exemption for statistical records.</ENT>
                                            </ROW>
                                            <ROW>
                                                <ENT I="01">Yes</ENT>
                                                <ENT>N/A</ENT>
                                                <ENT>(k)(5) Exemption for investigatory material compiled for determining suitability for employment or service.</ENT>
                                            </ROW>
                                            <ROW>
                                                <ENT I="01">Yes</ENT>
                                                <ENT>N/A</ENT>
                                                <ENT>(k)(6) Exemption for testing or examination material.</ENT>
                                            </ROW>
                                            <ROW>
                                                <ENT I="01">Yes</ENT>
                                                <ENT>N/A</ENT>
                                                <ENT>(k)(7) Exemption for promotion evaluation materials used by the Armed Forces.</ENT>
                                            </ROW>
                                            <ROW>
                                                <ENT I="01">Yes</ENT>
                                                <ENT>No</ENT>
                                                <ENT>(l)(1) Records stored in GSA records centers.</ENT>
                                            </ROW>
                                            <ROW>
                                                <ENT I="01">Yes</ENT>
                                                <ENT>No</ENT>
                                                <ENT>(l)(2) Records archived before September 27, 1975.</ENT>
                                            </ROW>
                                            <ROW>
                                                <ENT I="01">Yes</ENT>
                                                <ENT>No</ENT>
                                                <ENT>(l)(3) Records archived on or after September 27, 1975.</ENT>
                                            </ROW>
                                            <ROW>
                                                <PRTPAGE P="18786"/>
                                                <ENT I="01">Yes</ENT>
                                                <ENT>No</ENT>
                                                <ENT>(m) Applicability to Government contractors.</ENT>
                                            </ROW>
                                            <ROW>
                                                <ENT I="01">Yes</ENT>
                                                <ENT>No</ENT>
                                                <ENT>(n) Mailing lists.</ENT>
                                            </ROW>
                                            <ROW>
                                                <ENT I="01">
                                                    Yes 
                                                    <SU>1</SU>
                                                </ENT>
                                                <ENT>No</ENT>
                                                <ENT>(o) Reports on new systems.</ENT>
                                            </ROW>
                                            <ROW>
                                                <ENT I="01">
                                                    Yes 
                                                    <SU>1</SU>
                                                </ENT>
                                                <ENT>No</ENT>
                                                <ENT>(p) Annual report.</ENT>
                                            </ROW>
                                            <TNOTE>
                                                <SU>1</SU>
                                                 See paragraph (d) of § 310.26.
                                            </TNOTE>
                                        </GPOTABLE>
                                    </APPENDIX>
                                    <APPENDIX>
                                        <HD SOURCE="HED">
                                            Appendix E to Part 310—Sample of New or Altered System of Records Notice in 
                                            <E T="04">Federal Register</E>
                                             Format 
                                        </HD>
                                        <FP>(See paragraph (f) of § 310.30)</FP>
                                        <HD SOURCE="HD1">New system of records notice </HD>
                                        <HD SOURCE="HD1">
                                            <E T="0742">DEPARTMENT OF DEFENSE</E>
                                        </HD>
                                        <HD SOURCE="HD1">Office of the Secretary</HD>
                                        <HD SOURCE="HD1">Privacy Act of 1974; System of Records </HD>
                                        <FP>
                                            <E T="02">AGENCY:</E>
                                             Office of the Secretary, DoD. 
                                        </FP>
                                        <FP>
                                            <E T="02">ACTION:</E>
                                             Notice to add a system of records. 
                                        </FP>
                                        <FP>
                                            <E T="02">SUMMARY:</E>
                                             The Office of the Secretary of Defense proposes to add a system of records to its inventory of record systems subject to the Privacy Act of 1974 (5 U.S.C. 552a), as amended. 
                                        </FP>
                                        <FP>
                                            <E T="02">DATES:</E>
                                             The changes will be effective on (insert date thirty days after publication in the 
                                            <E T="04">Federal Register</E>
                                            ) unless comments are received that would result in a contrary determination. 
                                        </FP>
                                        <FP>
                                            <E T="02">ADDRESSES:</E>
                                             Send comments to OSD Privacy Act Coordinator, Records Management Section, Washington Headquarters Services, 1155 Defense Pentagon, Washington, DC 20301-1155. 
                                        </FP>
                                        <FP>
                                            <E T="02">FOR FURTHER INFORMATION CONTACT:</E>
                                             Ms. Mary Smith at (703) 000-0000. 
                                        </FP>
                                        <FP>
                                            <E T="02">SUPPLEMENTARY INFORMATION:</E>
                                             The Office of the Secretary of Defense notices for systems of records subject to the Privacy Act of 1974 (5 U.S.C. 552a), as amended, have been published in the 
                                            <E T="04">Federal Register</E>
                                             and are available from the address above. 
                                        </FP>
                                        <P>The proposed systems reports, as required by 5 U.S.C. 552a(r) of the Privacy Act of 1974, as amended, were submitted on January 20, 2006, to the House Committee on Government Reform, the Senate Committee on Homeland Security and Governmental Affairs, and the Office of Management and Budget (OMB) pursuant to paragraph 4c of Appendix I to OMB Circular No. A-130, “Federal Agency Responsibilities for Maintaining Records About Individuals,” dated February 8, 1996 (February 20, 1996, 61 FR 6427). </P>
                                        <P>Dated: February 1, 2006.</P>
                                        <FP>John Miller,</FP>
                                        <FP>
                                            <E T="03">OSD Federal Register Liaison Officer, Department of Defense.</E>
                                        </FP>
                                        <HD SOURCE="HD1">NSLRB 01 </HD>
                                        <P>
                                            <E T="03">System name:</E>
                                             The National Security Labor Relations Board (NSLRB). 
                                        </P>
                                        <P>
                                            <E T="03">System location:</E>
                                             National Security Labor Relations Board (NSLRB), 1401 Wilson Boulevard, Arlington, VA 22209-2325. 
                                        </P>
                                        <P>
                                            <E T="03">Categories of individuals covered by the system:</E>
                                             Current and former civilian Federal Government employees who have filed unfair labor practice charges, negotiability disputes, exceptions to arbitration awards, and impasses with the National Security Labor Relations Board (NSLRB) pursuant to the National Security Personnel System (NSPS). 
                                        </P>
                                        <P>
                                            <E T="03">Categories of records in the system:</E>
                                             Documents relating to the proceedings before the Board, including the name of the individual initiating NSLRB action, statements of witnesses, reports of interviews and hearings, examiner's findings and recommendations, a copy of the original decision, and related correspondence and exhibits. 
                                        </P>
                                        <P>
                                            <E T="03">Authority for maintenance of the system:</E>
                                             The National Defense Authorization Act for FY 2004, Public Law 108-136, Section 1101; 5 U.S.C. 9902(m), Labor Management Relations in the Department of Defense; and 5 CFR 9901.907, National Security Labor Relations Board. 
                                        </P>
                                        <P>
                                            <E T="03">Purpose(s):</E>
                                             To establish a system of records that will document adjudication of unfair labor practice charges, negotiability disputes, exceptions to arbitration awards, and impasses filed with the National Security Labor Relations Board. 
                                        </P>
                                        <P>
                                            <E T="03">Routine uses of records maintained in the system, including categories of users and the purposes of such uses:</E>
                                             In addition to those disclosures generally permitted under 5 U.S.C. 552a(b) of the Privacy Act, these records or information contained therein may specifically be disclosed outside the DoD as a routine use pursuant to 5 U.S.C. 552a(b)(3) as follows: 
                                        </P>
                                        <P>To the Federal Labor Relations Authority (FLRA) or the Equal Employment Opportunity Commission, when requested, for performance of functions authorized by law. </P>
                                        <P>To disclose, in response to a request for discovery or for appearance of a witness, information that is relevant to the subject matter involved in a pending judicial or administrative proceeding. </P>
                                        <P>To provide information to officials of labor organizations recognized under 5 U.S.C. 71 when relevant and necessary to their duties of exclusive representation concerning personnel policies, practices, and matters affecting work conditions. </P>
                                        <P>The DoD “Blanket Routine Uses” set forth at the beginning of OSD's compilation of systems of records notices apply to this system. </P>
                                        <P>
                                            <E T="03">Policies and practices for storing, retrieving, accessing, retaining, and disposing of records in the system:</E>
                                        </P>
                                        <P>
                                            <E T="03">Storage:</E>
                                             Records are maintained on electronic storage media and paper. 
                                        </P>
                                        <P>
                                            <E T="03">Retrievability:</E>
                                             Records will be retrieved in the system by the following identifiers: assigned case number; individual's name; labor organizations filing the unfair labor practice charges; negotiability disputes; exceptions to arbitration awards; date, month, year or filing; complaint type; and the organizational component from which the complaint arises. 
                                        </P>
                                        <P>
                                            <E T="03">Safeguards:</E>
                                             Records are maintained in a controlled facility. Physical entry is restricted by the use of locks, guards, and is accessible only to authorized personnel. Access to records is limited to person(s) responsible for servicing the record in performance of their official duties and who are properly screened and cleared for need-to-know. Access to computerized data is restricted by passwords, which are changed periodically. 
                                        </P>
                                        <P>
                                            <E T="03">Retention and disposal:</E>
                                             Records are disposed of 5 years after final resolution of case. 
                                        </P>
                                        <P>
                                            <E T="03">System manager(s) and address:</E>
                                             Executive Director, National Security Personnel System, Program Executive Office, 1401 Wilson Boulevard, Arlington, VA 22209-2325. 
                                        </P>
                                        <P>
                                            <E T="03">Notification procedure:</E>
                                             Individuals seeking to determine whether this system of records contains information about themselves should address written inquiries to the Executive Director, National Security Personnel System, Program Executive Office, 1401 Wilson Boulevard, Arlington, VA 22209-2325. 
                                        </P>
                                        <P>Request should contain name; assigned case number; approximate case date (day, month, and year); case type; the names of the individuals and/or labor organizations filed the unfair labor practice charges; negotiability disputes; exceptions to arbitration awards; and impasses. </P>
                                        <P>
                                            <E T="03">Record access procedures:</E>
                                             Individuals seeking access to records about themselves contained in this system of records should address written inquiries to the Executive Director, National Security Personnel System, Program Executive Office, 1401 Wilson Boulevard, Arlington, VA 22209-2325. 
                                        </P>
                                        <P>Request should contain name; assigned case number; approximate case date (day, month, and year); case type; the names of the individuals and/or labor organizations filed the unfair labor practice charges; negotiability disputes; exceptions to arbitration awards; and impasses. </P>
                                        <P>
                                            <E T="03">Contesting record procedures:</E>
                                             The OSD's rules for accessing records, for contesting contents and appealing initial agency determinations are published in OSD Administrative Instruction No. 81; 32 CFR part 311; or may be obtained from the system manager. 
                                        </P>
                                        <P>
                                            <E T="03">Record source categories:</E>
                                             Individual; other officials or employees; and departmental and other records containing information pertinent to the NSLRB action. 
                                        </P>
                                        <P>
                                            <E T="03">Exemptions claimed for the system:</E>
                                             None. 
                                            <PRTPAGE P="18787"/>
                                        </P>
                                        <HD SOURCE="HD1">Altered System of Record Notice </HD>
                                        <HD SOURCE="HD1">
                                            <E T="0742">DEPARTMENT OF DEFENSE</E>
                                        </HD>
                                        <HD SOURCE="HD1">
                                            <E T="0742">Defense Logistics Agency</E>
                                        </HD>
                                        <HD SOURCE="HD1">
                                            <E T="0742">Privacy Act of 1974; Systems of Records</E>
                                        </HD>
                                        <FP>
                                            <E T="02">AGENCY:</E>
                                             Defense Logistics Agency. 
                                        </FP>
                                        <FP>
                                            <E T="02">ACTION:</E>
                                             Notice to alter a system of records. 
                                        </FP>
                                        <FP>
                                            <E T="02">Summary:</E>
                                             The Defense Logistics Agency proposes to alter a system of records notice in its inventory of record systems subject to the Privacy Act of 1974 (5 U.S.C. 552a), as amended.  The alteration adds two routine uses, revises the purpose category, and makes other administrative changes to the system notice. 
                                        </FP>
                                        <FP>
                                            <E T="02">DATES:</E>
                                             This action will be effective without further notice on (insert date thirty days after publication in the 
                                            <E T="04">Federal Register</E>
                                            ) unless comments are received that would result in a contrary determination. 
                                        </FP>
                                        <FP>
                                            <E T="02">ADDRESSES:</E>
                                             Send comments to the Privacy Act Officer, Headquarters, Defense Logistics Agency, ATTN: DSS-B, 8725 John J. Kingman Road, Suite 2533, Fort Belvoir, VA 22060-6221.
                                        </FP>
                                        <FP>
                                            <E T="02">FOR FURTHER INFORMATION CONTACT:</E>
                                             Ms. Mary Smith at (703) 000-0000. 
                                        </FP>
                                        <FP>
                                            <E T="02">SUPPLEMENTARY INFORMATION:</E>
                                             The Defense Logistics Agency notices for systems of records subject to the Privacy Act of 1974 (5 U.S.C. 552a), as amended, have been published in the 
                                            <E T="04">Federal Register</E>
                                             and are available from the address above. 
                                        </FP>
                                        <P>The proposed system report, as required by 5 U.S.C. 552a(r) of the Privacy Act of 1974, as amended, was submitted on January 29, 2004, to the House Committee on Government Reform, the Senate Committee on Governmental Affairs, and the Office of Management and Budget (OMB) pursuant to paragraph 4c of Appendix I to OMB Circular No. A-130, ‘Federal Agency Responsibilities for Maintaining Records About Individuals,’ dated February 8, 1996 (February 20, 1996, 61 FR 6427). </P>
                                        <P>Dated: February 2, 2004. </P>
                                        <FP>John Miller, </FP>
                                        <FP>
                                            <E T="03">Alternate OSD Federal Register Liaison Officer, Department of Defense.</E>
                                        </FP>
                                        <HD SOURCE="HD1">S253.10 DLA-G </HD>
                                        <P>
                                            <E T="03">System name:</E>
                                             Invention Disclosure (February 22, 1993, 58 FR 10854). 
                                        </P>
                                        <P>
                                            <E T="03">Changes:</E>
                                        </P>
                                        <STARS/>
                                        <P>
                                            <E T="03">System identifier:</E>
                                             Replace ‘S253.10 DLA-G’ with ‘S100.70’. 
                                        </P>
                                        <STARS/>
                                        <P>
                                            <E T="03">Categories of individuals covered by the system:</E>
                                             Delete ‘to the DLA General Counsel’ at the end of the sentence and replace with ‘to DLA.’ 
                                        </P>
                                        <STARS/>
                                        <P>
                                            <E T="03">Categories of records in the system:</E>
                                             Delete entry and replace with ‘Inventor’s name, Social Security Number, address, and telephone numbers; descriptions of inventions; designs or drawings, as appropriate; evaluations of patentability; recommendations for employee awards; licensing documents; and similar records. Where patent protection is pursued by DLA, the file may also contain copies of applications, Letters Patent, and related materials.' 
                                        </P>
                                        <STARS/>
                                        <P>
                                            <E T="03">Authority for maintenance of the system:</E>
                                             Delete entry and replace with ‘5 U.S.C. 301, Departmental Regulations; 5 U.S.C. 4502, General provisions; 10 U.S.C. 2320, Rights in technical data; 15 U.S.C. 3710b, Rewards for scientific, engineering, and technical personnel of federal agencies; 15 U.S.C. 3711d, Employee activities; 35 U.S.C. 181-185, Secrecy of Certain Inventions and Filing Applications in Foreign Countries; E.O. 9397 (SSN); and E.O. 10096 (Inventions Made by Government Employees) as amended by E.O. 10930.’ 
                                        </P>
                                        <STARS/>
                                        <P>
                                            <E T="03">Purpose(s):</E>
                                             Delete entry and replace with ‘Data is maintained for making determinations regarding and recording DLA interest in the acquisition of patents; for documenting the patent process; and for documenting any rights of the inventor. The records may also be used in conjunction with the employee award program, where appropriate.’ 
                                        </P>
                                        <STARS/>
                                        <P>
                                            <E T="03">Routine uses of records maintained in the system, including categories of users and the purpose of such uses:</E>
                                             Add two new paragraphs: ‘To the U.S. Patent and Trademark Office for use in processing applications and performing related functions and responsibilities under Title 35 of the U.S. Code. 
                                        </P>
                                        <P>To foreign government patent offices for the purpose of securing foreign patent rights.’ </P>
                                        <STARS/>
                                        <P>
                                            <E T="03">Safeguards:</E>
                                             Delete entry and replace with ‘Access is limited to those individuals who require the records for the performance of their official duties. Paper records are maintained in buildings with controlled or monitored access. During non-duty hours, records are secured in locked or guarded buildings, locked offices, or guarded cabinets. The electronic records systems employ user identification and password or smart card technology protocols.’ 
                                        </P>
                                        <STARS/>
                                        <P>
                                            <E T="03">Retention and disposal:</E>
                                             Delete entry and replace with ‘Records maintained by Headquarters and field Offices of Counsel are destroyed 26 years after file is closed. Records maintained by field level Offices of Counsel where patent applications are not prepared are destroyed 7 years after closure.’ 
                                        </P>
                                        <STARS/>
                                        <P>
                                            <E T="03">Record source categories:</E>
                                             Delete entry and replace with ‘Inventors, reviewers, evaluators, officials of U.S. and foreign patent offices, and other persons having a direct interest in the file.’ 
                                        </P>
                                        <STARS/>
                                        <HD SOURCE="HD1">S100.70 </HD>
                                        <P>
                                            <E T="03">System name:</E>
                                             Invention Disclosure. 
                                        </P>
                                        <P>
                                            <E T="03">System location:</E>
                                             Office of the General Counsel, HQ DLA-DG, 8725 John J. Kingman Road, Stop 2533, Fort Belvoir, VA 22060-6221, and the offices of counsel of the DLA field activities. Official mailing addresses are published as an appendix to DLA's compilation of systems of records notices. 
                                        </P>
                                        <P>
                                            <E T="03">Categories of individuals covered by the system:</E>
                                             Employees and military personnel assigned to DLA who have submitted invention disclosures to DLA. 
                                        </P>
                                        <P>
                                            <E T="03">Categories of records in the system:</E>
                                             Inventor's name, Social Security Number, address, and telephone numbers; descriptions of inventions; designs or drawings, as appropriate; evaluations of patentability; recommendations for employee awards; licensing documents; and similar records. Where patent protection is pursued by DLA, the file may also contain copies of applications, Letters Patent, and related materials. 
                                        </P>
                                        <P>
                                            <E T="03">Authority for maintenance of the system:</E>
                                             5 U.S.C. 301, Departmental Regulations; 5 U.S.C. 4502, General provisions; 10 U.S.C. 2320, Rights in technical data; 15 U.S.C. 3710b, Rewards for scientific, engineering, and technical personnel of federal agencies; 15 U.S.C. 3711d, Employee activities; 35 U.S.C. 181-185, Secrecy of Certain Inventions and Filing Applications in Foreign Countries; E.O. 9397 (SSN); and E.O. 10096 (Inventions Made by Government Employees) as amended by E.O. 10930. 
                                        </P>
                                        <P>
                                            <E T="03">Purpose(s):</E>
                                             Data is maintained for making determinations regarding and recording DLA interest in the acquisition of patents, for documenting the patent process, and for documenting any rights of the inventor. The records may also be used in conjunction with the employee award program, where appropriate. 
                                        </P>
                                        <P>
                                            <E T="03">Routine uses of records maintained in the system, including categories of users and the purposes of such uses:</E>
                                             In addition to those disclosures generally permitted under 5 U.S.C. 552a(b) of the Privacy Act, these records or information contained therein may specifically be disclosed outside the DoD as a routine use pursuant to 5 U.S.C. 552a(b)(3) as follows: 
                                        </P>
                                        <P>To the U.S. Patent and Trademark Office for use in processing applications and performing related functions and responsibilities under Title 35 of the U. S. Code. </P>
                                        <P>To foreign government patent offices for the purpose of securing foreign patent rights. </P>
                                        <P>Information may be referred to other government agencies or to non-government agencies or to non-government personnel (including contractors or prospective contractors) having an identified interest in a particular invention and the Government's rights therein. </P>
                                        <P>The DoD ‘Blanket Routine Uses' set forth at the beginning of DLA's compilation of systems of records notices apply to this system.</P>
                                        <P>
                                            <E T="03">Policies and practices for storing, retrieving, accessing, retaining, and disposing of records in the system:</E>
                                        </P>
                                        <P>
                                            <E T="03">Storage:</E>
                                             Records are maintained in paper and computerized form. 
                                        </P>
                                        <P>
                                            <E T="03">Retrievability:</E>
                                             Filed by names of inventors. 
                                        </P>
                                        <P>
                                            <E T="03">Safeguards:</E>
                                             Access is limited to those individuals who require the records for the performance of their official duties. Paper records are maintained in buildings with controlled or monitored access. During non-duty hours, records are secured in locked or guarded buildings, locked offices, or guarded cabinets. The electronic records systems 
                                            <PRTPAGE P="18788"/>
                                            employ user identification and password or smart card technology protocols. 
                                        </P>
                                        <P>
                                            <E T="03">Retention and disposal:</E>
                                             Records maintain by the HQ and field Offices of Counsel are destroyed 26 years after file is closed. Records maintained by field level Offices of Counsel where patent applications are not prepared are destroyed 7 years after closure. 
                                        </P>
                                        <P>
                                            <E T="03">System manager(s) and address:</E>
                                             Office of the General Counsel, Headquarters, Defense Logistics Agency, ATTN: DG, 8725 John J. Kingman Road, Stop 2533, Fort Belvoir, VA 22060-6221. 
                                        </P>
                                        <P>
                                            <E T="03">Notification procedure:</E>
                                             Individuals seeking to determine whether information about themselves is contained in this system should address written inquiries to the Privacy Officer, Headquarters, Defense Logistics Agency, ATTN: DSS-B, 8725 John J. Kingman Road, Stop 6220, Fort Belvoir, VA 22060-6221, or the Privacy Officers at DLA field activities. Official mailing addresses are published as an appendix to DLA's compilation of systems of records notices. 
                                        </P>
                                        <P>
                                            <E T="03">Record access procedures:</E>
                                             Individuals seeking access to information about themselves contained in this system should address written inquiries to the Privacy Officer, Headquarters, Defense Logistics Agency, ATTN: DSS-B, 8725 John J. Kingman Road, Stop 6220, Fort Belvoir, VA 22060-6221, or the Privacy Officers at the DLA field activities. Official mailing addresses are published as an appendix to DLA's compilation of systems of records notices. 
                                        </P>
                                        <P>Individuals should provide information that contains full name, current address and telephone numbers of requester. </P>
                                        <P>For personal visits, each individual shall provide acceptable identification, e.g., driver's license or identification card. </P>
                                        <P>
                                            <E T="03">Contesting record procedures:</E>
                                             The DLA rules for accessing records, contesting contents, and appealing initial agency determinations are contained in 32 CFR part 323, or may be obtained from the Privacy Act Officer, Headquarters, Defense Logistics Agency, ATTN: DSS-B, 8725 John J. Kingman Road, Stop 6220, Fort Belvoir, VA 22060-6221. 
                                        </P>
                                        <P>
                                            <E T="03">Record source categories:</E>
                                             Inventors, reviewers, evaluators, officials of U.S. and foreign patent offices, and other persons having a direct interest in the file. 
                                        </P>
                                        <P>
                                            <E T="03">Exemptions claimed for the system:</E>
                                             None. 
                                        </P>
                                    </APPENDIX>
                                    <APPENDIX>
                                        <HD SOURCE="HED">Appendix F to Part 310—Format for New or Altered System Report </HD>
                                        <FP>(See paragraph (c) of § 310.33) </FP>
                                        <P>The report on a new or altered system shall consist of a transmittal letter, a narrative statement, and include supporting documentation. </P>
                                        <HD SOURCE="HD1">A. Transmittal Letter </HD>
                                        <P>The transmittal letter shall be prepared by the Defense Privacy Office and shall contain assurances that the new or altered system does not duplicate any existing Component systems, DoD-wide systems or government-wide systems. The narrative statement, and the system notice, shall be attached thereto. </P>
                                        <HD SOURCE="HD1">B. Narrative Statement </HD>
                                        <P>The statement shall include information on the following: </P>
                                        <P>1. System Identifier and name; </P>
                                        <P>2. Responsible official; </P>
                                        <P>3. Purpose of establishing the system [for a new system only] or Nature of the changes proposed for the system [for altered system only]; </P>
                                        <P>4. Authority for maintenance of the System; </P>
                                        <P>5. Probable or potential effects on the privacy of individuals; </P>
                                        <P>6. Is the system, in whole or part, being maintained by a contractor; </P>
                                        <P>7. Steps taken to minimize risk of unauthorized access; </P>
                                        <P>8. Routine use compatibility; </P>
                                        <P>9. OMB information collection requirements; and </P>
                                        <P>10. Supporting documentation. </P>
                                        <HD SOURCE="HD1">Attachment 1—Sample Format for Narrative Statement </HD>
                                        <HD SOURCE="HD1">DEPARTMENT OF DEFENSE </HD>
                                        <HD SOURCE="HD1">[Component Name] </HD>
                                        <HD SOURCE="HD1">Narrative Statement on a [New/Altered] System of Records </HD>
                                        <HD SOURCE="HD1">Under the Privacy Act of 1974 </HD>
                                        <P>
                                            1. 
                                            <E T="03">System Identifier and Name.</E>
                                             This caption sets forth the identification and name of the system (see subparagraphs (b)((c) of § 310.32). 
                                        </P>
                                        <P>
                                            2. 
                                            <E T="03">Responsible Official.</E>
                                             The name, title, address, and telephone number of the official responsible for the report and to whom inquiries and comments about the report may be directed by Congress, the Office of Management and Budget, or the Defense Privacy Office. 
                                        </P>
                                        <P>
                                            3. 
                                            <E T="03">Purpose of establishing the system or nature of the changes proposed for the system:</E>
                                             Describe the purpose of the new system or how an existing system is being changed. 
                                        </P>
                                        <P>
                                            4. 
                                            <E T="03">Authority for maintenance of the system.</E>
                                             See paragraph (g) of § 310.32. 
                                        </P>
                                        <P>
                                            5. 
                                            <E T="03">Probable or potential effects on the privacy of individuals.</E>
                                             What effect, if any, will the new or altered system impact the personal privacy of the affected individuals. 
                                        </P>
                                        <P>
                                            6. 
                                            <E T="03">Is the system, in whole or in part, being maintained by a contractor.</E>
                                             If yes, Components shall ensure that the contract has incorporated the Federal Acquisition privacy clause (see paragraph (a)(1) of § 310.12). 
                                        </P>
                                        <P>
                                            7. 
                                            <E T="03">Steps taken to minimize risk of unauthorized access.</E>
                                             Describe actions taken to reduce the vulnerability of the system to potential threats. See Appendix A to this part. 
                                        </P>
                                        <P>
                                            8. 
                                            <E T="03">Routine use compatibility.</E>
                                             Provide assurances that any records contained in the system that are disclosed outside the DoD shall be for a use that is compatible with the purpose for which the record was collected. Advise whether or not the blanket routine uses apply to this system. 
                                        </P>
                                        <P>
                                            9. 
                                            <E T="03">OMB collection requirements.</E>
                                             If information is to be collected from members of the public, the requirements of reference ( ) apply and OMB must be advised. 
                                        </P>
                                        <P>
                                            10. 
                                            <E T="03">Supporting documentation.</E>
                                             The following are typical enclosures that may be required: 
                                        </P>
                                        <P>a. An advance copy of the system notice for a new or altered system that is proposed for publication. </P>
                                        <P>b. An advance copy of a proposed exemption rule if the new or altered system is to be exempted in accordance with subpart F. </P>
                                        <P>c. Any other supporting documentation that may be pertinent or helpful in understanding the need for the system or clarifying its intended use. </P>
                                        <HD SOURCE="HD1">Attachment 2—SAMPLE NARRATIVE STATEMENT </HD>
                                        <HD SOURCE="HD1">DEPARTMENT OF DEFENSE </HD>
                                        <HD SOURCE="HD1">Office of the Secretary </HD>
                                        <HD SOURCE="HD1">Narrative Statement on a New System of Records </HD>
                                        <HD SOURCE="HD1">Under the Privacy Act of 1974 </HD>
                                        <P>
                                            1. 
                                            <E T="03">System identifier and name:</E>
                                             NSLRB 01, entitled “The National Security Labor Relations Board (NSLRB).”
                                        </P>
                                        <P>
                                            2. 
                                            <E T="03">Responsible official:</E>
                                             Mr. John Miller, National Security Labor Relations Board (NSLRB), 0000 Smith Boulevard, Arlington, VA 22209, Telephone (703) 000-0000. 
                                        </P>
                                        <P>
                                            3. 
                                            <E T="03">Purpose of establishing the system:</E>
                                             The Office of the Secretary of Defense is proposing to establish a system of records that will document adjudication of unfair labor practice charges, negotiability disputes, exceptions to arbitration awards, and impasses filed with the National Security Labor Relations Board. 
                                        </P>
                                        <P>
                                            4. 
                                            <E T="03">Authority for the maintenance of the system:</E>
                                             The National Defense Authorization Act for FY 2004, Pub Law 108-136, Section 1101; 5 U.S.C. 9902(m), Labor Management Relations in the Department of Defense; and 5 CFR 9901.907, National Security Labor Relations Board. 
                                        </P>
                                        <P>
                                            5. 
                                            <E T="03">Probable or potential effects on the privacy of individuals:</E>
                                             None 
                                        </P>
                                        <P>
                                            6. 
                                            <E T="03">Is the system, in whole or in part, being maintained by a contractor?</E>
                                             No 
                                        </P>
                                        <P>
                                            7. 
                                            <E T="03">Steps taken to minimize risk of unauthorized access:</E>
                                             Records are maintained in a controlled facility. Physical entry is restricted by the use of locks, guards, and is accessible only to authorized personnel. Access to records is limited to person(s) responsible for servicing the record in performance of their official duties and who are properly screened and cleared for need-to-know. Access to computerized data is restricted by passwords, which are changed periodically. 
                                        </P>
                                        <P>
                                            8. 
                                            <E T="03">Routine use compatibility:</E>
                                             Any release of information contained in this system of records outside of the DoD will be compatible with purposes for which the information is collected and maintained. The DoD “Blanket Routine Uses” apply to this system of records. 
                                        </P>
                                        <P>
                                            9. 
                                            <E T="03">OMB information collection requirements:</E>
                                             None. 
                                        </P>
                                        <P>
                                            10. 
                                            <E T="03">Supporting documentation:</E>
                                             None. 
                                        </P>
                                    </APPENDIX>
                                    <APPENDIX>
                                        <HD SOURCE="HED">Appendix G to Part 310—Sample Amendments or Deletions to System Notices in Federal Register Format </HD>
                                        <FP>(See § 310.34)</FP>
                                        <PRTPAGE P="18789"/>
                                        <HD SOURCE="HD1">
                                            <E T="0742">Amendment of system notice</E>
                                        </HD>
                                        <HD SOURCE="HD1">
                                            <E T="0742">DEPARTMENT OF DEFENSE</E>
                                        </HD>
                                        <HD SOURCE="HD1">
                                            <E T="0742">Department of the Army</E>
                                        </HD>
                                        <HD SOURCE="HD1">
                                            <E T="0742">Privacy Act of 1974; System of Records</E>
                                        </HD>
                                        <FP>
                                            <E T="02">AGENCY:</E>
                                             Department of the Army, DoD. 
                                        </FP>
                                        <FP>
                                            <E T="02">ACTION:</E>
                                             Notice to Amend a System of Records. 
                                        </FP>
                                        <FP>
                                            <E T="02">SUMMARY:</E>
                                             The Department of the Army is proposing to amend a system of records notice in its existing inventory of records systems subject to the Privacy Act of 1974, (5 U.S.C. 552a), as amended. 
                                        </FP>
                                        <FP>
                                            <E T="02">DATES:</E>
                                             This proposed action will be effective without further notice on (insert date thirty days after publication in Federal Register) unless comments are received which result in a contrary determination. 
                                        </FP>
                                        <FP>
                                            <E T="02">ADDRESSES:</E>
                                             Department of the Army, Freedom of Information/Privacy Division, U.S. Army Records Management and Declassification Agency, ATTN: AHRC-PDD-FPZ, 7701 Telegraph Road, Casey Building, Suite 144, Alexandria, VA 22325-3905. 
                                        </FP>
                                        <FP>
                                            <E T="02">FOR FURTHER INFORMATION CONTACT:</E>
                                             Ms. Mary Smith at (703) 000-0000. 
                                        </FP>
                                        <FP>
                                            <E T="02">SUPPLEMENTARY INFORMATION:</E>
                                             The Department of the Army systems of records notices subject to the Privacy Act of 1974, (5 U.S.C. 552a), as amended, have been published in the Federal Register and are available from the address above. 
                                        </FP>
                                        <P>The specific changes to the records systems being amended are set forth below followed by the notices, as amended, published in their entirety. The proposed amendments are not within the purview of subsection (r) of the Privacy Act of 1974, (5 U.S.C. 552a), as amended, which requires the submission of a new or altered system report.</P>
                                        <P>Dated: February 3, 2006. </P>
                                        <FP>John Miller, </FP>
                                        <FP>
                                            <E T="03">OSD Federal Register Liaison Officer, Department of Defense.</E>
                                        </FP>
                                        <HD SOURCE="HD1">A0055 USEUCOM </HD>
                                        <P>
                                            <E T="03">System name:</E>
                                             Europe Command Travel Clearance Records (August 23, 2004, 69 FR 51817). 
                                        </P>
                                        <P>
                                            <E T="03">Changes:</E>
                                        </P>
                                        <STARS/>
                                        <P>
                                            <E T="03">System name:</E>
                                             Delete system identifier and replace with: “A0055 USEUCOM DoD”. 
                                        </P>
                                        <STARS/>
                                        <HD SOURCE="HD1">A0055 USEUCOM DoD </HD>
                                        <P>
                                            <E T="03">System name:</E>
                                             Europe Command Travel Clearance Records. 
                                        </P>
                                        <P>
                                            <E T="03">System location:</E>
                                             Headquarters, United States European Command, Computer Network Operations Center, Building 2324, P.O. Box 1000, APO AE 09131-1000. 
                                        </P>
                                        <P>
                                            <E T="03">Categories of individuals covered by the system:</E>
                                             Military, DoD civilians, and non-DoD personnel traveling under DoD sponsorship (e.g., contractors, foreign nationals and dependents) and includes temporary travelers within the United States European Command's (USEUCOM) area of responsibility as defined by the DoD Foreign Clearance Guide Program. 
                                        </P>
                                        <P>
                                            <E T="03">Categories of records in the system:</E>
                                             Travel requests, which contain the individual's name; rank/pay grade; Social Security Number; military branch or department; passport number; Visa Number; office address and telephone number, official and personal email address, detailed information on sites to be visited, visitation dates and purpose of visit. 
                                        </P>
                                        <P>
                                            <E T="03">Authority for the maintenance of the system:</E>
                                             10 U.S.C. 3013, Secretary of the Army; 10 U.S.C. 5013, Secretary of the Navy; 10 U.S.C. 8013, Secretary of the Air Force; DoD 4500.54-G, Department of Defense Foreign Clearance Guide; Public Law 99-399, Omnibus Diplomatic Security and Antiterrorism Act of 1986; 22 U.S.C. 4801, 4802, and 4805, Foreign Relations and Intercourse; E.O. 12333, United States Intelligence Activities; Army Regulation 55-46, Travel Overseas; and E.O. 9397 (SSN). 
                                        </P>
                                        <P>
                                            <E T="03">Purpose(s):</E>
                                             To provide the DoD with an automated system to clear and audit travel within the United States European Command's area of responsibility and to ensure compliance with the specific clearance requirements outline in the DoD Foreign Clearance Guide; to provide individual travelers with intelligence and travel warnings; and to provide the Defense Attaché and other DoD authorized officials with information necessary to verify official travel by DoD personnel. 
                                        </P>
                                        <P>
                                            <E T="03">Routine uses of records maintained in the system, including categories of users and the purposes of such uses:</E>
                                             In addition to those disclosures generally permitted under 5 U.S.C. 552a(b) of the Privacy Act, these records or information contained therein may specifically be disclosed outside the DoD as a routine use pursuant to 5 U.S.C. 552a(b)(3) as follows: 
                                        </P>
                                        <P>To the Department of State Regional Security Officer, U.S. Embassy officials, and foreign police for the purpose of coordinating security support for DoD travelers. </P>
                                        <P>The DoD ‘Blanket Routine Uses’ set forth at the beginning of the Army's compilation of systems of records notices also apply to this system. </P>
                                        <P>Policies and practices for storing, retiring, accessing, retaining, and disposing of records. </P>
                                        <P>
                                            <E T="03">Storage:</E>
                                             Electronic storage media. 
                                        </P>
                                        <P>
                                            <E T="03">Retrievability:</E>
                                             Retrieved by individual's surname, Social Security Number and/or passport number. 
                                        </P>
                                        <P>
                                            <E T="03">Safeguards:</E>
                                             Electronic records are located in the United States European Command's Theater Requirements Automated Clearance System (TRACS) computer database with built in safeguards. Computerized records are maintained in controlled areas accessible only to authorized personnel with an official need to know access. In addition, automated files are password protected and in compliance with the applicable laws and regulations. Another built in safeguard of the system is records are access to the data through secure network. 
                                        </P>
                                        <P>
                                            <E T="03">Retention and disposal:</E>
                                             Records are destroyed 3 months after travel is completed. 
                                        </P>
                                        <P>
                                            <E T="03">System manager(s) and address:</E>
                                             Special Assistant for Security Matters, Headquarters, United States European Command, Unit 30400, P.O. Box 1000, APO AE 09131-1000. 
                                        </P>
                                        <P>
                                            <E T="03">Notification procedures:</E>
                                             Individuals seeking to determine whether information about themselves is contained in this system of records should address written inquiries to the Special Assistant for Security Matters, Headquarters, United States European Command, Unit 30400, P.O. Box 1000, APO AE 09131-1000. 
                                        </P>
                                        <P>Requests should contain individual's full name, Social Security Number, and/or passport number. </P>
                                        <P>
                                            <E T="03">Record access procedures:</E>
                                             Individuals seeking to access information about themselves that is contained in this system of records should address written inquiries to the Special Assistant for Security Matters, Headquarters, United States European Command, Unit 30400, P.O. Box 1000, APO AE 09131-1000. 
                                        </P>
                                        <P>Requests should contain individual's full name, Social Security Number, and/or passport number. </P>
                                        <P>
                                            <E T="03">Contesting record procedures:</E>
                                             The Army's rules for accessing records and for contesting contents and appealing initial agency determinations are contained in Army Regulation 340-21; 32 CFR part 505; or may be obtained from the system manager. 
                                        </P>
                                        <P>
                                            <E T="03">Record source categories:</E>
                                             From individuals. 
                                        </P>
                                        <P>
                                            <E T="03">Exemptions claimed for the system:</E>
                                             None. 
                                        </P>
                                        <HD SOURCE="HD1">Deletion of System Notice </HD>
                                        <HD SOURCE="HD1">
                                            <E T="0742">DEPARTMENT OF DEFENSE</E>
                                        </HD>
                                        <HD SOURCE="HD1">
                                            <E T="0742">Office of the Secretary</E>
                                        </HD>
                                        <HD SOURCE="HD1">
                                            <E T="0742">Privacy Act of 1974; System of Records</E>
                                        </HD>
                                        <FP>
                                            <E T="02">AGENCY:</E>
                                             Office of the Secretary, DoD. 
                                        </FP>
                                        <FP>
                                            <E T="02">ACTION:</E>
                                             Notice to delete systems of records. 
                                        </FP>
                                        <FP>
                                            <E T="02">SUMMARY:</E>
                                             The Office of the Secretary of Defense is deleting a system of records notice from its existing inventory of records systems subject to the Privacy Act of 1974, (5 U.S.C. 552a), as amended. 
                                        </FP>
                                        <FP>
                                            <E T="02">DATES:</E>
                                             This proposed action will be effective without further notice on (insert date thirty days after publication in 
                                            <E T="04">Federal Register</E>
                                            ) unless comments are received which result in a contrary determination. 
                                        </FP>
                                        <FP>
                                            <E T="02">ADDRESSES:</E>
                                             OSD Privacy Act Coordinator, Records Management Section, Washington Headquarters Services, 1155 Defense Pentagon, Washington, DC 20301-1155. 
                                        </FP>
                                        <FP>
                                            <E T="02">FOR FURTHER INFORMATION CONTACT:</E>
                                             Ms. Mary Smith at (703) 000-0000. 
                                        </FP>
                                        <FP>
                                            <E T="02">SUPPLEMENTARY INFORMATION:</E>
                                             The Office of the Secretary of Defense systems of records notices subject to the Privacy Act of 1974, (5 U.S.C. 552a), as amended, have been published in the 
                                            <E T="04">Federal Register</E>
                                             and are available from the address above. 
                                        </FP>
                                        <P>The specific changes to the records system being amended are set forth below followed by the notice, as amended, published in its entirety. The proposed amendments are not within the purview of subsection (r) of the Privacy Act of 1974, (5 U.S.C. 552a), as amended, which requires the submission of a new or altered system report.</P>
                                        <P>Dated: April 2, 2006. </P>
                                        <FP>John Miller,</FP>
                                        <FP>
                                            <E T="03">OSD Federal Register Liaison Officer, Department of Defense.</E>
                                            <PRTPAGE P="18790"/>
                                        </FP>
                                        <HD SOURCE="HD1">DODDS 27 </HD>
                                        <FP>
                                            <E T="03">System name:</E>
                                             DoD Domestic and Elementary School Employee File (May 9, 2003, 68 FR 24935). 
                                        </FP>
                                        <FP>
                                            <E T="03">Reason:</E>
                                             The records contained in this system of records are covered by OPM/GOVT-1 (General Personnel Records), a government-wide system notice. 
                                        </FP>
                                    </APPENDIX>
                                    <APPENDIX>
                                        <HD SOURCE="HED">Appendix H to Part 310—Litigation Status Sheet </HD>
                                        <P>(See § 310.49) </P>
                                        <HD SOURCE="HD1">Litigation Status Sheet </HD>
                                        <FP SOURCE="FP-1">
                                            1. Case Number 
                                            <SU>1</SU>
                                            <FTREF/>
                                        </FP>
                                        <FTNT>
                                            <P>
                                                <SU>1</SU>
                                                 Number used by the Component for reference purposes.
                                            </P>
                                        </FTNT>
                                        <FP SOURCE="FP-1">2. Requester </FP>
                                        <FP SOURCE="FP-1">
                                            3. Document Title or Description 
                                            <SU>2</SU>
                                            <FTREF/>
                                        </FP>
                                        <FTNT>
                                            <P>
                                                <SU>2</SU>
                                                 Indicate the nature of the case, such as, “Denial of access,” “Refusal to amend,” “Incorrect records,” or other violations of the Act (specify). 
                                            </P>
                                        </FTNT>
                                        <FP SOURCE="FP-1">4. Litigation </FP>
                                        <FP SOURCE="FP-1">a. Date Complaint Filed </FP>
                                        <FP SOURCE="FP-1">b. Court </FP>
                                        <FP SOURCE="FP-1">
                                            c. Case File Number 
                                            <SU>1</SU>
                                        </FP>
                                        <FP SOURCE="FP-1">5. Defendants (DoD Component and individual) </FP>
                                        <FP SOURCE="FP-1">6. Remarks (brief explanation of what the case is about) </FP>
                                        <FP SOURCE="FP-1">7. Court Action </FP>
                                        <FP SOURCE="FP-1">a. Court's Finding </FP>
                                        <FP SOURCE="FP-1">b. Disciplinary Action (as appropriate) </FP>
                                        <FP SOURCE="FP-1">8. Appeal (as appropriate) </FP>
                                        <FP SOURCE="FP-1">a. Date Complaint Filed </FP>
                                        <FP SOURCE="FP-1">b. Court </FP>
                                        <FP SOURCE="FP-1">c. Case File Number </FP>
                                        <FP SOURCE="FP-1">d. Court's Finding </FP>
                                        <FP SOURCE="FP-1">e. Disciplinary Action (as appropriate) </FP>
                                    </APPENDIX>
                                </SECTION>
                            </SUBPART>
                        </PART>
                    </REGTEXT>
                    <SIG>
                        <DATED>Dated: March 28, 2007. </DATED>
                        <NAME>L.M. Bynum, </NAME>
                        <TITLE>Alternate OSD Federal Register Liaison Officer, DoD. </TITLE>
                    </SIG>
                </SUPLINF>
                <FRDOC> [FR Doc. E7-6118 Filed 4-12-07; 8:45 am] </FRDOC>
                <BILCOD>BILLING CODE 5001-06-P </BILCOD>
            </RULE>
        </RULES>
    </NEWPART>
    <VOL>72</VOL>
    <NO>71</NO>
    <DATE>Friday, April 13, 2007</DATE>
    <UNITNAME>Proposed Rules</UNITNAME>
    <NEWPART>
        <PTITLE>
            <PRTPAGE P="18791"/>
            <PARTNO>Part III </PARTNO>
            <AGENCY TYPE="P">Department of Labor</AGENCY>
            <SUBAGY>Occupational Safety and Health Administration</SUBAGY>
            <HRULE/>
            <CFR>29 CFR Part 1910</CFR>
            <TITLE>Explosives; Proposed Rule</TITLE>
        </PTITLE>
        <PRORULES>
            <PRORULE>
                <PREAMB>
                    <PRTPAGE P="18792"/>
                    <AGENCY TYPE="S">DEPARTMENT OF LABOR </AGENCY>
                    <SUBAGY>Occupational Safety and Health Administration </SUBAGY>
                    <CFR>29 CFR Part 1910 </CFR>
                    <DEPDOC>[Docket No. OSHA-2007-0032 (formerly Docket No. OSHA-S031-2006-0665] </DEPDOC>
                    <RIN>RIN 1218-AC09 </RIN>
                    <SUBJECT>Explosives </SUBJECT>
                    <AGY>
                        <HD SOURCE="HED">AGENCY:</HD>
                        <P>Occupational Safety and Health Administration (OSHA), Department of Labor. </P>
                    </AGY>
                    <ACT>
                        <HD SOURCE="HED">ACTION:</HD>
                        <P>Proposed rule. </P>
                    </ACT>
                    <SUM>
                        <HD SOURCE="HED">SUMMARY:</HD>
                        <P>OSHA proposes to revise the explosives and blasting agents standard in subpart H of part 1910. This revision of § 1910.109 is intended to enhance the protections provided to employees engaged in the manufacture, storage, sale, transportation, handling, and use of explosives. The proposal updates and clarifies the regulatory language, addresses regulatory inconsistencies between OSHA and other Federal agencies, incorporates updated consensus standards, and provides the regulated community with greater compliance flexibility. </P>
                    </SUM>
                    <EFFDATE>
                        <HD SOURCE="HED">DATES:</HD>
                        <P>Written comments and hearing requests must be submitted by the following dates: </P>
                        <P>
                            <E T="03">Hard copy:</E>
                             Comments and hearing requests must be submitted (postmarked or sent) by July 12, 2007. 
                        </P>
                        <P>
                            <E T="03">Facsimile and electronic transmissions:</E>
                             Comments and hearing requests must be sent by July 12, 2007. 
                        </P>
                    </EFFDATE>
                    <ADD>
                        <HD SOURCE="HED">ADDRESSES:</HD>
                        <P>You may submit comments, identified by Docket No. OSHA-2007-0032, by any of the following methods: </P>
                        <P>
                            <E T="03">Electronically:</E>
                             You may submit comments and attachments electronically at 
                            <E T="03">http://www.regulations.gov</E>
                            , which is the Federal eRulemaking Portal. Follow the instructions on-line for making electronic submissions. 
                        </P>
                        <P>
                            <E T="03">Fax:</E>
                             If your comments, including attachments, do not exceed 10 pages, you may fax them to the OSHA Docket Office at (202) 693-1648. 
                        </P>
                        <P>
                            <E T="03">Mail, hand delivery, express mail, messenger or courier service:</E>
                             You must submit three copies of your comments and attachments to the OSHA Docket Office, Docket No. OSHA-2007-0032, U.S. Department of Labor, Room N-2625, 200 Constitution Avenue, NW., Washington, DC 20210. Deliveries (hand, express mail, messenger and courier service) are accepted during the Department of Labor's and Docket Office's normal business hours, 8:15 a.m.-4:45 p.m., e.t. 
                        </P>
                        <P>
                            <E T="03">Instructions:</E>
                             All submissions must include the Agency name and the docket number for this rulemaking (Docket No. OSHA-2007-0032). All comments, including any personal information you provide, are placed in the public docket without change and may be made available online at 
                            <E T="03">http://www.regulations.gov.</E>
                             Therefore, OSHA cautions you about submitting personal information such as social security numbers and birthdates. For further information on submitting comments, plus additional information on the rulemaking process, see the “Public Participation” heading in the 
                            <E T="02">SUPPLEMENTARY INFORMATION</E>
                             section of this document. 
                        </P>
                        <P>
                            <E T="03">Docket:</E>
                             To read or download comments and materials submitted in response to this 
                            <E T="04">Federal Register</E>
                             notice, go to Docket No. OSHA-2007-0032 at 
                            <E T="03">http://www.regulations.gov</E>
                             or at the OSHA Docket Office at the address above. All comments and submissions are listed in the 
                            <E T="03">http://www.regulations.gov</E>
                             index, however, some information (e.g., copyrighted material) is not publicly available to read or download through that Web page. All comments and submissions, including copyrighted material, are available for inspection and copying at the OSHA Docket Office. 
                        </P>
                        <P>
                            For information on accessing exhibits referenced in this 
                            <E T="04">Federal Register</E>
                             notice, see the “References and Exhibits” and “Public Participation” headings in the 
                            <E T="02">SUPPLEMENTARY INFORMATION</E>
                             section of this document. 
                        </P>
                        <P>
                            Electronic copies of this 
                            <E T="04">Federal Register</E>
                             document are available at 
                            <E T="03">http://regulations.gov.</E>
                             Copies also are available from the OSHA Office of Publications, Room N-3101, U.S. Department of Labor, 200 Constitution Avenue, NW., Washington DC 20210; telephone (202) 693-1888. This document, as well as news releases and other relevant information, also are available at OSHA's Web page at 
                            <E T="03">http://www.osha.gov.</E>
                        </P>
                    </ADD>
                    <FURINF>
                        <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                        <P>For general information and press inquiries, contact Mr. Kevin Ropp, Office of Communications, Room N-3647, OSHA, U.S. Department of Labor, 200 Constitution Avenue, NW., Washington, DC 20210; telephone (202) 693-1999. For technical inquiries, contact Donald Pittenger, Directorate of Standards and Guidance, Room N-3609, OSHA, U.S. Department of Labor, 200 Constitution Avenue, NW., Washington, DC 20210; telephone (202) 693-2255 or fax (202) 693-1663. </P>
                    </FURINF>
                </PREAMB>
                <SUPLINF>
                    <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                    <HD SOURCE="HD1">References and Exhibits </HD>
                    <P>
                        In this 
                        <E T="04">Federal Register</E>
                         notice, OSHA references a number of supporting materials. References to these materials are given as “Ex.” followed by the number of the document. The referenced materials are posted in both Docket No. OSHA-S031-2006-0665 (which is available at 
                        <E T="03">http://www.regulations.osha.gov</E>
                        ) and OSHA Docket No. S-031 (which is available at 
                        <E T="03">http://dockets.osha.gov</E>
                        ). The documents are also available at the OSHA Docket Office (see 
                        <E T="02">ADDRESSES</E>
                         section). For further information about accessing exhibits referenced in this 
                        <E T="04">Federal Register</E>
                         notice, see the “Public Participation” heading in the 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                         section of this document. 
                    </P>
                    <EXTRACT>
                        <HD SOURCE="HD1">Table of Contents </HD>
                        <FP SOURCE="FP-2">I. Background </FP>
                        <FP SOURCE="FP-2">II. Legal Considerations </FP>
                        <FP SOURCE="FP-2">III. Summary and Explanation of the Proposed Rule </FP>
                        <FP SOURCE="FP-2">IV. Preliminary Economic and Regulatory Screening Analysis </FP>
                        <FP SOURCE="FP-2">V. Environmental Impact Analysis </FP>
                        <FP SOURCE="FP-2">VI. Paperwork Reduction Act </FP>
                        <FP SOURCE="FP-2">VII. Federalism </FP>
                        <FP SOURCE="FP-2">VIII. State Plan Standards </FP>
                        <FP SOURCE="FP-2">IX. Unfunded Mandates </FP>
                        <FP SOURCE="FP-2">X. Public Participation </FP>
                        <FP SOURCE="FP-2">XI. List of Subjects in 29 CFR part 1910 </FP>
                        <FP SOURCE="FP-2">XII. Authority and Signature </FP>
                        <FP SOURCE="FP-2">XIII. Amendments to Standards</FP>
                    </EXTRACT>
                    <HD SOURCE="HD1">I. Background </HD>
                    <HD SOURCE="HD2">History of the Standard </HD>
                    <P>
                        In 1970, Congress enacted the Occupational Safety and Health Act (29 U.S.C. 651 
                        <E T="03">et seq.</E>
                        ) (the Act or the OSH Act) directing OSHA to promulgate safety and health standards to assure, as far as possible, safe and healthful working conditions for every employee in the Nation. To expedite OSHA's mission, Congress directed the Secretary of Labor through section 6(a) of the Act (29 U.S.C. 655(a)) to promulgate safety and health standards within the first two years of the Act's enactment by summarily adopting existing national consensus and established Federal standards, without requiring the Agency to go through the rulemaking procedures detailed in section 6 of the Act. 
                    </P>
                    <P>
                        On May 29, 1971, pursuant to section 6(a) of the Act, OSHA promulgated its explosives and blasting agents standard at 29 CFR 1910.109 (36 FR 10553-10562). The standard was based on two national consensus standards—the National Fire Protection Association (NFPA) 495-1970 
                        <E T="03">
                            Code for the Manufacture, Transportation, Storage, and Use of Explosives and Blasting 
                            <PRTPAGE P="18793"/>
                            Agents
                        </E>
                        , and NFPA 490-1970 
                        <E T="03">Code for the Storage of Ammonium Nitrate</E>
                        . 
                    </P>
                    <P>The explosives and blasting agents standard promulgated in 1971 was similar to the current standard found at § 1910.109 and included provisions on the storage of explosives, blasting agents, and ammonium nitrate; the transportation of explosives; and the use of explosives and blasting agents. Few significant changes have been made to the standard since its promulgation. On March 31, 1972, OSHA amended the standard by adding paragraph (j) “Small arms ammunition, small arms primers, and small arms propellants” (37 FR 6577). It also added paragraph (k) “Scope,” which stated in part that: “This section applies to the manufacture, keeping, having, storage, sale, transportation, and use of explosives, blasting agents, and pyrotechnics” 37 FR 6577. </P>
                    <P>On February 24, 1992, OSHA issued a new standard at § 1910.119 “Process Safety Management” (PSM) covering working conditions during the manufacture of highly hazardous chemicals (57 FR 6356). Both the manufacture of explosives (excluding blasting agents) and the manufacture of pyrotechnics must meet the requirements contained in the PSM standard. 57 FR 6356. The PSM final rule revised the scope provision in the explosives and blasting agents standard by adding § 1910.109(k)(2) which states that the manufacture of explosives must meet the requirements contained in § 1910.119 and by adding § 1910.109(k)(3) which states that the manufacture of pyrotechnics must meet the requirements in § 1910.119. 57 FR 6356. </P>
                    <P>The most recent revisions made to § 1910.109 were on June 18, 1998 (63 FR 33450) in which OSHA amended two provisions to make them consistent with Department of Transportation (DOT) regulations. The revisions now allow blasting caps to be transported on the same vehicle with other explosives (§ 1910.109(d)(1)(iv)) and allow the re-use of containers and packaging materials that have previously contained explosives provided that such re-use is performed in accordance with DOT regulations at 49 CFR 173.28 (§ 1910.109(e)(2)(i)). </P>
                    <HD SOURCE="HD2">The Petition </HD>
                    <P>On July 29, 2002, OSHA received a petition (the Petition) from the Institute of Makers of Explosives (IME) and the Sporting Arms and Ammunition Manufacturers' Institute (SAAMI) to revise the standard. A copy of the Petition can be found at Docket No. OSHA-S031-2006-0665 (Ex. 2-1). IME is an association of manufacturers of high explosives and other companies that distribute explosives or provide other related services and the SAAMI is an association of manufacturers of sporting firearms, ammunition, and related components. The Petition claimed that § 1910.109 does not reflect significant technological and safety advances made by the explosives industry since the standard was promulgated. It further contended that the standard contains outdated references, classifications, and jurisdiction-related provisions that do not accurately represent the current regulatory environment. </P>
                    <P>The Petition requested OSHA to make a number of changes to the standard, including the following, and provided draft regulatory language: </P>
                    <P>• Exclude the manufacture of explosives from the PSM requirements of § 1910.119 and incorporate revised PSM requirements for the manufacture of explosives into § 1910.109; </P>
                    <P>• Replace references to outdated DOT explosives classifications with the current DOT classification system; </P>
                    <P>• Eliminate the provisions in § 1910.109 covering the storage of explosives and the construction of magazines because they are regulated by the Bureau of Alcohol, Tobacco, Firearms, and Explosives (ATF); </P>
                    <P>• Eliminate provisions in § 1910.109 applicable to the transportation of explosives on public highways because such transportation is regulated by DOT; </P>
                    <P>• Update provisions for guarding against accidental initiation by sources of extraneous electricity; </P>
                    <P>• Include provisions governing the intra-plant transportation of explosives; </P>
                    <P>• Include provisions for the use of nonelectric detonation systems; </P>
                    <P>• Revise provisions regarding the crimping of detonators to safety fuse; </P>
                    <P>• Update provisions for clearing the blasting area of unauthorized personnel; and </P>
                    <P>• Update the provisions for the design of bulk delivery and mixing vehicles and of mixing equipment. </P>
                    <P>In response to the Petition, OSHA carefully reviewed the requirements of the current standard and other related OSHA standards. It analyzed the recommendations as well as the draft regulatory language provided in the Petition. OSHA also examined the regulations of other federal agencies relating to explosives and consulted with interested parties about the need to revise the standard. Apart from IME and SAAMI, these interested parties included the International Society of Explosives Engineers (ISEE), the American Pyrotechnics Association (APA), the United Steel Workers of America (USWA), and the Paper, Allied-Industrial, Chemical and Energy Workers International (PACE). In addition, OSHA consulted with other Federal agencies about their explosives regulations and procedures. These Federal agencies included the DOT, ATF, the Interagency Committee on Explosives (ICE), the Department of Defense Explosives Safety Board (DDESB), the Consumer Product Safety Commission (CPSC), and the Mine Safety and Health Administration. </P>
                    <P>Based upon its review of the Petition and the standard, OSHA has concluded that the following actions are appropriate. These actions are discussed in greater detail in the summary and explanation section of the proposed rule (see section III). </P>
                    <HD SOURCE="HD3">A. Update the Standard </HD>
                    <P>Workplace hazards associated with explosives activities pose significant risks to employees. OSHA has determined that the existing standard needs to be updated to adequately protect employees from these risks. Each year, over 5 billion pounds of explosives are manufactured or imported into the U.S.A. These explosives are used on a daily basis in many different ways. The manufacture, storage, transportation, sale, and use of explosives present significant risks not only to the employees who work directly with them but to the many other employees who may work in the immediate vicinity of the explosives. </P>
                    <P>
                        Explosives are, by their nature and design, inherently dangerous and their safe handling, storage, and use are critical to the safety of those working with or near them. There have been many incidents in the past of injuries and deaths resulting from the accidental detonation of explosives. One of the most famous examples, the Texas City Disaster, did not actually involve explosives but ammonium nitrate, one of the ingredients used to make a type of explosive called blasting agents. On April 16, 1947, a ship named the SS Grandcamp was docked at the port of Texas City, Texas. Its cargo hold was full of ammonium nitrate. Shortly after a small fire was detected in the hold, the ammonium nitrate detonated. The explosion killed at least 581 people, injured over 5,000 others, destroyed the port, and severely damaged the town. The shockwave from the explosion shattered windows in Houston, over 40 miles away. Only three years earlier, another ship docked at Port Chicago, California, exploded when its cargo of explosives detonated. The explosion 
                        <PRTPAGE P="18794"/>
                        killed 320 sailors and civilians and injured over 400 others. 
                    </P>
                    <P>A review of accidents involving explosives indicates that such incidents are most often caused by unsafe work practices or faulty equipment. These factors are frequently exacerbated by the failure to properly train not only the employees handling and using the explosives but also the employees in the vicinity of the explosives in question. In many cases, the initial incident, while serious, triggers even greater loss of life and property by spreading to nearby facilities or causing serious injury to employees trying to fight the resulting fire. </P>
                    <P>The existing standard has undergone few significant revisions since it was promulgated over 35 years ago and many of its requirements do not accurately reflect current working conditions in the explosives industry. Over the last 35 years, the explosives industry has changed significantly. New forms of explosives have been developed (e.g., emulsions), new kinds of detonators have been introduced (e.g., electronic detonators), and substantial changes have been made in the processes and equipment employed to create, handle and use explosives (e.g., new kinds of bulk delivery vehicles). OSHA has concluded that the existing standard must be updated to reflect these changes and to adequately protect employees from the significant risks involved in working with or near explosives. To update the standard, OSHA has consulted with other federal agencies and with interested parties about new technologies, products, and procedures used by the explosives industry and has incorporated these developments into the proposed rule. It has also updated all references in the standard to current national consensus standards. </P>
                    <HD SOURCE="HD3">B. Increase the Clarity and Focus of the Standard </HD>
                    <P>Many of the existing requirements in § 1910.109 are difficult to understand, repetitive, and internally inconsistent. In addition, some of these existing requirements address issues, such as general public safety, that go beyond OSHA's authority to regulate. When the standard was promulgated in 1971 through section 6(a) of the Act, OSHA adopted much of the language contained in the national consensus standards upon which it was based (i.e., NFPA 495 and NFPA 490). These national consensus standards were not written in language well suited for a Federal regulation and had broader coverage (e.g., public safety) than needed by OSHA to cover working conditions in the explosives industry. </P>
                    <P>To make the standard more “user-friendly,” the proposal has been rewritten in plain language. Internal inconsistencies and duplicative requirements have been eliminated. In addition, it has been rewritten to eliminate references to public safety that are beyond OSHA's authority to regulate. </P>
                    <HD SOURCE="HD3">C. Increase the Regulatory Consistency of the Standard </HD>
                    <P>There are inconsistencies between the explosives regulations of different Federal agencies. For example, OSHA classifies explosives in its current standard as Class A, Class B, and Class C explosives. ATF classifies explosives in terms of high explosives, low explosives, and blasting agents (27 CFR 555.202). DOT has adopted the United Nations Globally Harmonized System of Classification and Labelling of Chemicals (GHS) (Ex. 2-2). The GHS is intended to harmonize existing communication systems on chemicals in order to develop a single, worldwide harmonized system to address classification of chemicals according to their hazards, and communicate the related information through labels and safety data sheets. Based on the GHS, DOT classifies all explosives as Class 1 chemicals and further subdivides them into Division 1.1 through 1.6 explosives (49 CFR 173.50). </P>
                    <P>Magazines (structures used for the storage of explosives) are also classified differently by different Federal agencies. For example, OSHA classifies magazines as Class I and Class II (§ 1910.109(c)(1)) but ATF classifies them as Type 1 through Type 5 (27 CFR 555.203). </P>
                    <P>One of OSHA's major goals in this proposed rulemaking is to increase regulatory consistency with other Federal agencies involved in regulating the explosives industry and to eliminate confusion within the regulated community. To achieve this goal, OSHA proposes to adopt the GHS definitional classification system for “explosives.” This will make OSHA's classification system consistent with the one used by DOT, which is also based on the GHS. </P>
                    <HD SOURCE="HD3">D. Increase the Regulatory Flexibility of the Standard </HD>
                    <P>To provide the regulated community with greater regulatory flexibility, OSHA has endeavored to use general performance-oriented language in the proposed standard. This allows OSHA to draft a requirement in terms of a goal and it allows the employer greater choice on how to achieve that goal. </P>
                    <HD SOURCE="HD3">E. Resolve Authority Issues in the Standard </HD>
                    <P>There is some confusion in the regulated community over the boundaries of OSHA's authority to regulate working conditions in the explosives industry. One of OSHA's goals in this rulemaking is to clarify the extent of its authority to regulate working conditions in the explosives industry. In particular, OSHA discusses the boundaries of its authority to regulate working conditions during the storage of explosives and during the transportation of explosives. </P>
                    <HD SOURCE="HD1">II. Legal Considerations </HD>
                    <P>The purpose of the OSH Act is “to assure so far as possible every working man and woman in the Nation safe and healthful working conditions and to preserve our human resources.” 29 U.S.C. 651(b). To achieve this goal, Congress authorized the Secretary of Labor to promulgate and enforce occupational safety and health standards (see 29 U.S.C. 655(a) authorizing summary adoption of existing consensus and federal standards within two years of Act's enactment, 655(b) authorizing promulgation of standards pursuant to notice and comment, and 654(b) requiring employers to comply with OSHA standards). </P>
                    <P>A safety or health standard is a standard “which requires conditions, or the adoption or use of one or more practices, means, methods, operations, or processes, reasonably necessary or appropriate to provide safe or healthful employment” (29 U.S.C. 652(8)). </P>
                    <P>A standard is reasonably necessary or appropriate within the meaning of Section 652(8) if it substantially reduces or eliminates significant risk, and is economically feasible, technologically feasible, and cost effective, and is consistent with prior Agency action or is a justified departure, is supported by substantial evidence, and is better able to effectuate the Act's purposes than any national consensus standard it supersedes. See 58 FR 16612-16616 (March 30, 1993). </P>
                    <P>
                        A standard is technologically feasible if the protective measures it requires already exist, can be brought into existence with available technology, or can be created with technology that can reasonably be expected to be developed. 
                        <E T="03">American Textile Mfrs. Institute</E>
                         v. 
                        <E T="03">OSHA</E>
                        , 452 U.S. 490, 513 (1981) (
                        <E T="03">ATMI</E>
                        ); 
                        <E T="03">American Iron and Steel Institute</E>
                         v. 
                        <E T="03">OSHA</E>
                        , 939 F.2d 975, 980 (D.C. Cir. 1991) (
                        <E T="03">AISI</E>
                        ). 
                    </P>
                    <P>
                        A standard is economically feasible if industry can absorb or pass on the costs 
                        <PRTPAGE P="18795"/>
                        of compliance without threatening its long-term profitability or competitive structure. See 
                        <E T="03">ATMI</E>
                        , 452 U.S. at 530 n. 55; 
                        <E T="03">AISI</E>
                        , 939 F.2d at 980. A standard is cost effective if the protective measures it requires are the least costly of the available alternatives that achieve the same level of protection. 
                        <E T="03">ATMI</E>
                        , 452 U.S. at 514 n. 32; 
                        <E T="03">International Union, UAW</E>
                         v. 
                        <E T="03">OSHA</E>
                        , 37 F.3d 665, 668 (D.C. Cir. 1994) (
                        <E T="03">LOTO II</E>
                        ). 
                    </P>
                    <P>Section 6(b)(7) authorizes OSHA to include among a standard's requirements labeling, monitoring, medical testing and other information gathering and transmittal provisions. 29 U.S.C. 655(b)(7). </P>
                    <P>
                        All standards must be highly protective. See 58 FR at 16614-16615; 
                        <E T="03">LOTO II</E>
                        , 37 F.3d at 668-669. Finally, whenever practical, standards shall “be expressed in terms of objective criteria and of the performance desired.” 29 U.S.C. 655(b)(5). 
                    </P>
                    <HD SOURCE="HD1">III. Summary and Explanation of the Proposed Rule </HD>
                    <HD SOURCE="HD2">OSHA's Authority To Regulate </HD>
                    <P>
                        The purpose of the following discussion is to clarify the degree to which OSHA has authority to regulate working conditions relating to explosives. A number of Federal agencies have authority to regulate explosives. For example, the OSH Act grants OSHA authority to create and enforce standards covering workplace safety and health. As part of its mission, OSHA currently regulates working conditions in the storage, sale, transportation, manufacture, and use of explosives (29 CFR 1910.109 and 1910.119 and part 1926 subpart U). The Mine Safety and Health Administration is responsible for regulating the transportation, storage, and use of explosives at mining facilities subject to the Federal Mine Safety and Health Act of 1977. Its relevant regulations can be found at 30 CFR 56.6000 to 56.6905, 57.6000 to 57.6960, 75.1300 to 75.1328, and 77.1300 to 77.1304. The United States Department of Transportation (DOT), under the Hazardous Materials Transportation Act (49 U.S.C. 5101 
                        <E T="03">et seq.</E>
                        ), is responsible for regulating the safe transportation of explosives in intrastate, interstate, and foreign commerce. Its regulations cover not only the movement of explosives in commerce but also the loading, unloading, and storage of explosives incidental to that movement (49 CFR parts 171 to 180 and 397). 
                    </P>
                    <P>The Bureau of Alcohol, Tobacco, Firearms and Explosives (ATF) regulations cover the import, manufacture, distribution, and storage of explosives (27 CFR part 555). Its regulations require all manufacturers, importers, and dealers in explosives to obtain a Federal license from ATF and require certain users of explosives to obtain a Federal permit from ATF. The Agency also regulates the safe and secure storage of explosives at approved facilities. The United States Coast Guard has regulations covering the loading, transportation, unloading, and stowage of explosives on vessels and at related land-side facilities (33 CFR part 126, 46 CFR part 194, 49 CFR parts 171 to 173 and 176). </P>
                    <P>
                        The Consumer Product Safety Commission regulates consumer fireworks as part of its mission to protect the public from unreasonable risks of serious injury or death from consumer products (16 CFR parts 1500 and 1507). Its regulations contain construction, performance, and labeling requirements for consumer fireworks. The Environmental Protection Agency, under such statutes as the Resource Conservation and Recovery Act (42 U.S.C. 6901 
                        <E T="03">et seq.</E>
                        ), the Clean Water Act (33 U.S.C. 1251 
                        <E T="03">et seq.</E>
                        ), and the Clean Air Act (42 U.S.C. 7401 
                        <E T="03">et seq.</E>
                        ), regulates releases and wastes involved in the manufacture, use, and disposal of explosives. The United States Department of the Interior's Office of Surface Mining is responsible for regulating blast effects, such as flyrock and ground vibration, near surface mines (30 CFR 816, 817, and 850). 
                    </P>
                    <P>Given that there are multiple federal agencies that have authority to regulate explosives and that there are several different aspects to the regulation of explosives, areas can develop where federal agency authorities overlap. OSHA recognizes that there is the potential for overlap between provisions of this NPRM and a recent Department of Homeland Security (DHS) proposed regulation. Pursuant to the DHS Appropriations Act of 2007, Public Law 109-295 (October 4, 2006), DHS has authority to regulate the security of chemical facilities. DHS published an Advance Notice of Rulemaking titled Chemical Facility Anti-terrorism Standards (71 FR 78276) (December 28, 2006) and will publish an implementing interim final rule on the matter. The DHS Advance Notice proposes to require high-risk chemical facilities to develop and implement “Site Security Plans” with measures that address their security vulnerabilities (as determined through a “Vulnerability Assessment”) and that address the DHS risk-based performance standards for security at chemical facilities. To the extent that any overlapping issues develop, OSHA and DHS will work to resolve those issues. </P>
                    <P>The above description is not a complete listing of all the Federal agencies that regulate explosives. With so many agencies involved, confusion has occurred in the regulated community over the regulatory boundaries between some agencies. One issue that has arisen concerns the degree of overlap in OSHA and ATF regulations covering the storage of explosives. Another issue involves whether OSHA has the authority to regulate working conditions during the transportation of explosives when DOT and the United States Coast Guard also regulates such transportation. The following is a discussion of these two issues. </P>
                    <P>
                        <E T="03">OSHA's Authority to Regulate the Storage of Explosives.</E>
                         The OSH Act gives OSHA broad authority to promulgate and enforce standards to promote workplace safety and health. 29 U.S.C. 651. The courts have supported this broad interpretation of OSHA's authority. 
                        <E T="03">Southern Railway Co.</E>
                         v. 
                        <E T="03">OSHRC</E>
                        , 539 F.2d 335, 338 (4th Cir. 1976) 
                        <E T="03">cert. denied</E>
                        , 429 U.S. 999 (1976) (“OSHA was enacted in response to an appalling record of death and disability in our industrial environment, and it was the clear intent of Congress to meet the problem with broad and, hopefully, effective legislation.”). However, OSHA's authority to regulate working conditions is restricted by section 4(b)(1) of the OSH Act (29 U.S.C. 653(b)(1)), which states that: 
                    </P>
                    <EXTRACT>
                        <P>Nothing in this Act shall apply to working conditions of employees with respect to which other Federal agencies * * * exercise statutory authority to prescribe or enforce standards or regulations affecting occupational safety or health.</P>
                    </EXTRACT>
                      
                    <P>
                        Congress enacted this provision, called the “preemption provision,” to avoid duplicative regulatory coverage between OSHA and other Federal agencies in the area of workplace safety and health. 
                        <E T="03">Organized Migrants in Community Action</E>
                         v. 
                        <E T="03">Brennan</E>
                        , 520 F.2d 1161, 1161 (D.C. Cir. 1975). The preemption provision prevents OSHA from regulating working conditions when another Federal agency exercises its statutory authority to prescribe or enforce standards or regulations covering those working conditions. 
                        <E T="03">Chao</E>
                         v. 
                        <E T="03">Mallard Bay Drilling, Inc.</E>
                        , 524 U.S. 235, 241 (2002). OSHA is not preempted if another Federal agency has statutory authority but has not exercised that authority. 524 U.S. at 241. 
                    </P>
                    <P>
                        Is OSHA preempted by ATF under the preemption provision of the OSH Act from regulating working conditions 
                        <PRTPAGE P="18796"/>
                        relating to the storage of explosives? To answer this question, the following questions must be answered. Does ATF have statutory authority to regulate the storage of explosives? If so, is ATF exercising that authority? If so, to what extent do ATF's requirements cover the same working conditions as OSHA's requirements? 
                    </P>
                    <P>Title XI of the Organized Crime Control Act of 1970, Pub.L. No. 91-452, 84 Stat. 922, gives ATF, through the Secretary of the Treasury, the statutory authority to regulate the storage of explosives. Section 1101 of Title XI states that “[t]he Congress hereby declares that the purpose of this title is to protect interstate and foreign commerce against interference and interruption by reducing the hazard to persons and property arising from misuse and unsafe or insecure storage of explosive materials.” 84 Stat. 952. Thus, Congress gave ATF the statutory authority to issue and enforce regulations to protect persons (including employees) from the unsafe storage of explosives. ATF has exercised this authority by promulgating and enforcing regulations covering the storage of explosives (see 27 CFR part 555). </P>
                    <P>ATF's explosive storage regulations are very similar to OSHA's requirements for working conditions involved in the storage of explosives. Many of ATF's requirements affect the same types of working conditions as OSHA's requirements. The following table shows the overlap between ATF's regulations and OSHA's requirements for the storage of explosives. </P>
                    <GPOTABLE COLS="2" OPTS="L2,tp0,i1" CDEF="s50,r50">
                        <TTITLE> </TTITLE>
                        <BOXHD>
                            <CHED H="1">ATF's requirements </CHED>
                            <CHED H="1">OSHA's requirements</CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">27 CFR 555.203 Types of magazines </ENT>
                            <ENT>29 CFR 1910.109(c)(1)(iv) and (v). </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">27 CFR 555.206 Location of magazines </ENT>
                            <ENT>29 CFR 1910.109(c)(1)(vi), (vii) and (viii). </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">27 CFR 555.207 to .211 Construction of magazines </ENT>
                            <ENT>29 CFR 1910.109(c)(2), (3) and (4). </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">27 CFR 555.212 Smoking and open flames </ENT>
                            <ENT>29 CFR 1910.109(c)(5)(vii). </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">27 CFR 555.213 Quantity and storage restrictions </ENT>
                            <ENT>29 CFR 1910.109(c)(1)(ii). </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">27 CFR 555.214 Storage within magazines </ENT>
                            <ENT>29 CFR 1910.109(c)(5). </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">27 CFR 555.215 Housekeeping </ENT>
                            <ENT>29 CFR 1910.109(c)(5)(iv) and (v). </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">27 CFR 555.216 Repair of magazines </ENT>
                            <ENT>29 CFR 1910.109(c)(5)(vi). </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">27 CFR 555.217 Lighting </ENT>
                            <ENT>29 CFR 1910.109(c)(2)(vi). </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">27 CFR 555.218 to .220 Tables of distances for storage of explosive materials </ENT>
                            <ENT>
                                29 CFR 1910.109(c)(1) Table H-21. 
                                <LI>29 CFR 1910.109(g)(4) Table H-22. </LI>
                            </ENT>
                        </ROW>
                    </GPOTABLE>
                    <P>ATF's regulations for the storage of explosives apply to the same kinds of working conditions as OSHA's requirements for the storage of explosives. Although ATF's regulations do not always contain the same or similar requirements as OSHA's requirements, they cover the same general working conditions. In some cases, ATF's regulations include working conditions not covered as extensively by OSHA's requirements. For example, unlike OSHA's requirements, ATF's regulations contain separate requirements for the storage of display fireworks, pyrotechnic compositions, and explosive materials used in assembling fireworks (see 27 CFR 555.221 to .224). </P>
                    <P>In summary, ATF has statutory authority to regulate the storage of explosives and it exercises this statutory authority through its promulgation and enforcement of regulations covering explosives storage. Its storage regulations affect the same kinds of working conditions as those covered by OSHA's requirements in § 1910.109. Therefore, OSHA has concluded that its storage requirements for explosives in § 1910.109(c) are preempted under section 4(b)(1) of the OSH Act by ATF's regulations at 27 CFR part 555 subpart K. As a consequence, OSHA is proposing in this rulemaking to eliminate the provisions in § 1910.109 that deal with the storage of explosives. </P>
                    <P>OSHA is proposing to retain the provisions in § 1910.109(i) that cover the storage of ammonium nitrate. These provisions are not pre-empted by ATF's explosive storage regulations in 27 CFR part 555 subpart K because, although ammonium nitrate is a component of certain explosives such as ANFO, by itself, it is not an explosive. Therefore, it is not regulated by these ATF regulations. In addition, OSHA is also proposing to retain the provisions in § 1910.109(j) that cover the storage of small arms ammunition and components of small arms ammunition. Although small arms ammunition and components of small arms ammunition, such as small arms primers and smokeless propellants, are explosives, ATF's explosives storage regulations do not apply to the storage of ammunition as defined in 27 CFR 555.11 (see 27 CFR 555.141(a)(4)). Thus, OSHA's existing § 1910.109(j) covering the storage of small arms ammunition and components of small arms ammunition are not preempted by ATF's regulations. </P>
                    <P>Furthermore, ATF's explosives regulations (see 27 CFR 555.141(a)(7)) do not apply to consumer fireworks as defined in 27 CFR 555.11. These items are generally classified as UN0336, UN0337, UN0431, and UN0432 by DOT at 49 CFR 172.101, and generally known as consumer fireworks or articles pyrotechnic. These fireworks are classified as Class 1 Division 1.4 explosives by DOT at 40 CFR 172.101. Because ATF does not regulate the storage of these types of fireworks, OSHA retains authority to regulate their storage. At this time, however, OSHA is not proposing to regulate the storage of these types of fireworks in the proposed standard but plans to deal with them in a future rulemaking on pyrotechnics. </P>
                    <P>
                        <E T="03">Issue #1:</E>
                         As discussed above, OSHA is proposing to withdraw its requirements in § 1910.109 covering the storage of explosives. OSHA is seeking comments on the following issue. Apart from small arms ammunition and related components, are there any explosives that are currently covered by the storage requirements in § 1910.109 that are not covered by ATF's storage regulations? 
                    </P>
                    <P>
                        <E T="03">OSHA's Authority to Regulate the Transportation of Explosives.</E>
                         Do DOT and the United States Coast Guard preempt OSHA from regulating working conditions during the transportation of explosives? DOT regulates the transportation of hazardous materials, including explosives, by statutory authority granted to it by the Hazardous Materials Transportation Act (the Hazmat Act) enacted in 1975 (49 U.S.C. 1801 
                        <E T="03">et seq.</E>
                        ). DOT has exercised this statutory authority by promulgating and enforcing regulations covering the transportation of hazardous materials (49 CFR parts 171 to 180). The United States Coast Guard is called to enforce these authorities during the transportation of hazardous materials on vessels upon the navigable waters of the United States. In addition, the United States Coast Guard is authorized to regulate the handling of dangerous cargo, including explosives, at waterfront facilities under 33 CFR part 126. 
                    </P>
                    <P>In 1990, Congress amended the Hazmat Act (Pub. L. 101-615, § 2936, Nov. 16, 1990, 104 Stat. 3244) and added the following reverse preemption language in § 1805(b)(3): </P>
                    <EXTRACT>
                        <P>
                            For purposes of section 4(b)(1) of the Occupational Safety and Health Act of 1970 (29 U.S.C. 653(b)(1)), no action taken by the [DOT] Secretary pursuant to this section shall 
                            <PRTPAGE P="18797"/>
                            be deemed to be an exercise of statutory authority to prescribe or enforce standards or regulations affecting occupational safety or health.
                        </P>
                    </EXTRACT>
                      
                    <P>The section in the Hazmat Act referred to in the reverse preemption language was § 1805 “Handling of hazardous materials.” Section 1805(a) covered the number, training, and qualifications of personnel involved in handling hazardous materials; the type and frequency of inspections; the equipment used to detect, warn, and control the risks posed by hazardous materials; the use of equipment and facilities employed in the handling and transportation of hazardous materials; and systems for monitoring the safety assurance procedures for transporting hazardous materials. Section 1805(b) included training criteria for the safe handling and transportation of hazardous materials. The remaining provisions in § 1805 covered the registration, filing, and permit requirements for transporters of hazardous materials. </P>
                    <P>The reverse preemption language in § 1805(b)(3) of the Hazmat Act nullified any effect of the OSH Act's 4(b)(1) preemption provision over matters covered by § 1805 of the Hazmat Act. Because § 1805 covered such things as the training, equipment and facilities used during the handling and transportation of hazardous materials, OSHA could regulate working conditions associated with these aspects of the handling and transportation of hazardous materials. </P>
                    <P>
                        In 1994, Congress amended and recodified the Hazmat Act to its current form as 49 U.S.C. chapter 51—Transportation of Hazardous Material, § 5101 
                        <E T="03">et seq.</E>
                         (Pub. L. 103-272, July 5, 1994, 108 Stat. 745). Although the reverse preemption language was altered and recodified at § 5107(f)(2), its meaning and coverage remained the same. Section 5107(f)(2) states: 
                    </P>
                    <EXTRACT>
                        <HD SOURCE="HD1">§ 5107 Hazmat employee training requirements and grants </HD>
                        <STARS/>
                        <P>(f) Relationship to other laws. </P>
                        <STARS/>
                        <P>(2) An action of the Secretary of Transportation under subsections (a)-(d) of this section and sections 5106, 5108(a)-(g)(1) and (h), and 5109 of this title is not an exercise, under section 4(b)(1) of the Occupational Safety and Health Act of 1970 (29 U.S.C. 653(b)(1)), of statutory authority to prescribe or enforce standards or regulations affecting occupational safety and health. </P>
                    </EXTRACT>
                    <P>Section 5106 involves criteria for the handling of hazardous materials and includes the following: </P>
                    <EXTRACT>
                        <P>The Secretary of Transportation may prescribe criteria for handling hazardous material, including: </P>
                        <P>(1) a minimum number of personnel; </P>
                        <P>(2) minimum levels of training and qualifications for personnel; </P>
                        <P>(3) the kind and frequency of inspections; </P>
                        <P>(4) equipment for detecting, warning of, and controlling risks posed by the hazardous material; </P>
                        <P>(5) specifications for the use of equipment and facilities used in handling and transporting the hazardous material; and </P>
                        <P>(6) a system of monitoring safety procedures for transporting the hazardous material.</P>
                    </EXTRACT>
                    <P>Section 5107(a) to (d) covers training requirements for employees working with hazardous materials. Section 5108(a) to (g)(1) and (h) involves registration requirements for transporting hazardous materials and § 5109 covers safety permits for motor carriers transporting hazardous materials. </P>
                    <P>Similar to the reverse preemption language in the 1990 amendments to the Hazmat Act, § 5107(f)(2) of the 1994 amendments to the Hazmat Act nullifies any effect of the OSH Act's 4(b)(1) preemption provision over matters covered by §§ 5106, 5107(a) to (d), 5108(a) to (g)(1) and (h), and 5109. This allows OSHA to regulate working conditions relating to these matters, which include “the use of equipment and facilities used in handling and transporting the hazardous material” (49 U.S.C. 5106(5)). Accordingly, OSHA has the authority to not only regulate working conditions at facilities involved in the transportation of hazardous materials but also when equipment is used during the transportation of hazardous materials. It is noteworthy that the reverse preemption language in the 1994 amendments to the Hazmat Act does not exclude DOT from also regulating the areas covered by §§ 5106, 5107(a) to (d), 5108(a) to (g)(1) and (h), and 5109. </P>
                    <P>
                        The Occupational Safety and Health Review Commission examined the reverse preemption language in 
                        <E T="03">Yellow Freight Systems, Inc.</E>
                        , 17 BNA OSHC 1699, 1995-97 CCH OSHD ¶ 31,105 (No. 93-3292, 1996). In that case, the operator of a freight terminal argued that OSHA's citations against it were invalid because OSHA was preempted from regulating working conditions at the terminal by DOT under the 4(b)(1) preemption provision of the OSH Act. The Commission disagreed with the operator and concluded that when Congress amended § 1805(b)(3) in the 1990 amendments to the Hazmat Act, it “intended to nullify the preemptive effect of DOT actions taken under section 1805.” 
                        <E T="03">Id</E>
                        . at 1701. It also made the equivalent finding about the reverse preemption language in the 1994 amendments to the Hazmat Act. 
                        <E T="03">Id</E>
                        . At the invitation of the Commission, DOT submitted its interpretation of § 1805(b)(3) in the 
                        <E T="03">Yellow Freight</E>
                         case. DOT stated that the reverse preemption language “found in § 1805(b)(3) * * * referred to the entirety of § 1805.” 
                        <E T="03">Id</E>
                        . Thus, DOT agreed that OSHA was not preempted from regulating working conditions in those aspects of the transportation of hazardous materials covered by § 1805. 
                    </P>
                    <P>
                        On October 30, 2003, DOT issued a final rule clarifying the application of its hazardous materials regulations to the loading, unloading, and storage of hazardous materials incidental to movement in commerce (68 FR 61906). DOT's hazardous materials regulations cover pre-transportation functions involving the preparation of hazardous materials for transportation in commerce. 
                        <E T="03">Id</E>
                        . at 61906, 61908. They also cover transportation functions involving the actual movement of hazardous materials in commerce, including the loading, unloading, and storage of hazardous materials that is incidental to that movement. 
                        <E T="03">Id</E>
                        . at 61906, 61914. 
                    </P>
                    <P>
                        In the preamble to the final rule, DOT noted the reverse preemption language at § 5107(f)(2) in the 1994 amendments to the Hazmat Act and stated that: “Such ‘reverse preemption language’ functions to nullify any effect the OSH Act's 4(b)(1) provision might otherwise have and thus ensures that OSHA's standards remain applicable (68 FR 61926).” DOT further stated that it “neither affirmatively regulate[s] the working conditions at facilities where pre-transportation and transportation functions are performed, nor assert[s] comprehensive regulatory jurisdiction over the working conditions at these facilities. * * * This final rule makes clear that [DOT does] not intend to exercise [its] statutory authority in a manner that precludes OSHA from regulating at facilities where pre-transportation and transportation functions are performed.” 
                        <E T="03">Id</E>
                        . Thus, DOT recognizes that, through the reverse preemption language of the Hazmat Law, OSHA has the statutory authority to regulate working conditions at facilities where pre-transportation and transportation functions are performed. 
                    </P>
                    <P>
                        In its final rule, DOT did not directly address whether OSHA has statutory authority to regulate working conditions during the actual movement of hazardous materials in commerce. However, it stated that DOT “has developed a special expertise that 
                        <PRTPAGE P="18798"/>
                        makes the Department uniquely qualified to play the primary Federal regulatory role in the protection of employees who operate motor vehicles, trains, aircraft, and vessels used to transport hazardous materials.” 
                        <E T="03">Id</E>
                        . at 61927. 
                    </P>
                    <P>OSHA agrees that DOT has the unique expertise to play a lead role in the protection of employees during the transportation of hazardous materials. However, OSHA also recognizes that, through the reverse preemption language of § 5107(f)(2) in the 1994 amendments to the Hazmat Act, Congress has granted OSHA statutory authority to regulate working conditions during the handling and transportation of hazardous materials. The Agency views this statutory authority to include working conditions during the actual movement of hazardous material in commerce, as well as during the preparation of hazardous materials prior to movement, and the loading, unloading, and temporary storage of hazardous material incidental to movement. </P>
                    <P>Although OSHA has the statutory authority to regulate working conditions at each stage in the transportation of hazardous materials, the Agency is not required to exercise that authority. OSHA recognizes DOT and the United States Coast Guard's extensive regulatory expertise and coverage in the area of the safe transportation of hazardous materials. The Agency also believes it is important to avoid duplicative or conflicting regulatory requirements between federal agencies. As a result, OSHA has no current plans to expand its regulation of working conditions during the transportation of hazardous materials. </P>
                    <P>The following preamble discussion explains significant changes made in the proposal to the existing standard. The proposed standard changes the title of 29 CFR 1910.109 from “Explosives and Blasting Agents” to “Explosives.” Since the proposal includes blasting agents in the definition of explosives (discussed below), it is no longer appropriate for the title of the section to include both terms. </P>
                    <P>This proposed rule contains a complete revision and re-organization of existing § 1910.109. In addition to requesting comments on any of the requirements in the proposed standard, OSHA has identified issues throughout the preamble and has requested comments on these issues. </P>
                    <P>OSHA's development of the proposed rule was based in part on the 2001 edition of NFPA 495—Explosive Materials Code. NFPA has recently issued a 2006 edition of this code. OSHA has compared the differences between the 2001 and 2006 editions. Any significant changes relevant to the proposed rule in the 2006 edition compared to the 2001 edition are discussed at the appropriate location in the preamble. OSHA is interested in comments on whether there are any requirements in the 2006 edition of NFPA 495 that should be in the proposed rule but have not been included. </P>
                    <P>The proposed rule references DOT regulations in several provisions. OSHA has included these references to DOT regulations to ensure that the proposed rule is consistent with DOT's regulations. However, OSHA is interested in comments on whether such DOT references should be retained, excluded, or replaced with an alternative in the final rule. If you think some or all of the references to DOT regulations should be replaced with an alternative, please provide the alternative language for the affected provisions in the proposed rule. </P>
                    <P>As an aid to understanding the changes in the proposed rule, a table, “Proposed Reorganization of Existing Requirements,” has been placed in the docket (Ex. 2-22) listing the requirements in the existing standard and identifying where they are located in the proposed rule. In addition, a second table, “New Requirements in Proposed Rule,” has been placed in the docket (Ex. 2-23) listing all the new provisions in the proposed rule that are not in the existing standard. </P>
                    <P>
                        <E T="03">Paragraph (a) Scope</E>
                        . Proposed paragraph (a) defines the applicability of § 1910.109, and has been moved from existing paragraph (k), at the end of the standard, to the beginning of the proposed standard. This change enables a reader to quickly determine the applicability of the standard. 
                    </P>
                    <P>Proposed paragraph (a)(1) would apply this section to the manufacture, storage, sale, transportation, handling, and use of explosives, including blasting agents and pyrotechnics. The proposed paragraph is similar to existing paragraph (k)(1) except in three ways. First, for ease of compliance, each of the multiple requirements in existing paragraph (k)(1) has been moved to a separate proposed paragraph. As a result, the requirement in existing paragraph (k)(1) on the applicability of the standard to the use of explosives in medicines and medicinal agents has been moved to proposed paragraph (a)(3)(ii). The requirement in existing paragraph (k)(1) on the applicability of the standard to the sale and use of pyrotechnics has been moved to proposed paragraph (a)(3)(iii). </P>
                    <P>Second, proposed paragraph (a)(1) has been rewritten for clarity. For example, ambiguous terms such as “keeping” and “having” in existing paragraph (k)(1) have been removed in proposed paragraph (a)(1). OSHA believes the proposed language is clearer and more concise than the existing language, and will enhance compliance. </P>
                    <P>
                        Third, the application of this section to storage has been removed. The reason for this is explained in the 
                        <E T="03">OSHA's Authority to Regulate</E>
                         discussion above. 
                    </P>
                    <P>Proposed paragraph (a)(2) requires the employer to comply with § 1910.119, Process Safety Management (PSM), for operations involving the manufacture of explosives, as defined in proposed paragraph (b). The proposed paragraph revises the requirements in existing paragraph (k)(2), which requires the manufacture of explosives, as defined in existing paragraph (a)(3), to comply with the requirements of § 1910.119. </P>
                    <P>The proposal deletes existing paragraph (k)(3) which requires the manufacture of pyrotechnics, as defined in existing paragraph (a)(10), to comply with the requirements of § 1910.119. Paragraph (b) of the proposed standard defines pyrotechnics as explosives (see discussion below on proposed paragraph (b)). Thus, it is no longer necessary to have one provision requiring that the manufacture of explosives comply with § 1910.119 and another provision requiring that the manufacture of pyrotechnics comply with § 1910.119. Proposed paragraph (a)(2) requiring that the manufacture of explosives comply with § 1910.119 covers all explosives as defined in proposed paragraph (b), including pyrotechnics. </P>
                    <P>Under both the existing standard (existing paragraph (k)) and the proposed standard (proposed paragraph (a)(2)), the manufacture of blasting agents does not have to comply with the PSM standard at § 1910.119. The existing standard does not define blasting agents as explosives but the proposed standard classifies them as Class 1 Division 1.5 explosives (see discussion below on proposed paragraph (b)). Even though the proposed standard includes blasting agents as explosives and requires that the manufacture of explosives comply with § 1910.119, OSHA in proposed paragraph (a)(2) is specifically excluding blasting agents from the requirements of § 1910.119. This exclusion includes water gels, slurries, and emulsions classified as Class 1 Division 1.5 explosives. </P>
                    <P>
                        The PSM standard was developed to safeguard employees from catastrophic releases of toxic, reactive, flammable, or 
                        <PRTPAGE P="18799"/>
                        explosive chemicals (see § 1910.119 
                        <E T="03">Purpose</E>
                        ). Blasting agents, as Class 1 Division 1.5 explosives, are very insensitive and have a very low probability of causing an unintended mass explosion. For this reason, OSHA has concluded that blasting agents, unlike Division 1.1 to 1.4 explosives, do not pose the potential catastrophic consequences to employees required of chemicals subject to § 1910.119 and should be excluded from the PSM standard. However, if one or more ingredients of a blasting agent is otherwise classified as an explosive (i.e., as a Division 1.1, 1.2, 1.3, or 1.4 explosive), then the manufacturing process for that blasting agent would be required to comply with § 1910.119. Although the manufacture of blasting agents is not subject to the PSM standard, both the existing standard at § 1910.109(g) and (h) and the proposed standard at § 1910.109(c) and (g) have requirements covering the safe manufacture of blasting agents. 
                    </P>
                    <P>Proposed paragraph (a)(3)(i) clarifies that § 1910.109, as a general industry standard, does not apply to construction work covered by 29 CFR part 1926. This paragraph is new but does not change the scope of the existing standard because the existing standard also does not apply to construction work. Subpart U of 29 CFR part 1926 specifically addresses blasting and the use of explosives in the construction industry. OSHA believes the proposed language clarifies the scope of the proposed standard and addresses some confusion on the issue that was revealed during discussions with stakeholders. </P>
                    <P>
                        Proposed paragraph (a)(3)(ii) states that this section does not apply to the use of explosives in medicines and medicinal agents in the forms prescribed by the official 
                        <E T="03">United States Pharmacopeia and the National Formulary</E>
                         (USP-NF). The USP-NF is available from the United States Pharmacopeial Convention, Inc., 12601 Twinbrook Parkway, Rockville, MD, 20852. The proposal continues the existing standard's exclusion of medicines and medical agents containing explosives from the standard's requirements. For ease of compliance, this exclusion was separated from other requirements within existing paragraph (k)(1) and made into a separate proposed paragraph (a)(3)(ii). The proposed language is similar to the existing exclusion, and was modified to be consistent with paragraph 1.1.7 of the 2001 edition of NFPA 495 (Ex. 2-5). 
                    </P>
                    <P>Proposed paragraph (a)(3)(iii) states that the section does not apply to the use or sale of both public display and consumer pyrotechnics. For ease of compliance, this requirement was separated from other requirements within existing paragraph (k)(1) and is proposed as paragraph (a)(3)(iii). The application of the proposed paragraph has not changed from that of existing (k)(1). However, OSHA has revised the paragraph to clarify that the proposed standard does not apply to the use or sale of both public display and consumer fireworks. Note that, although they are not covered by the existing or proposed § 1910.109 standard, OSHA has the authority to regulate the use of public display fireworks and the sale of public display and consumer fireworks. However, the use of consumer fireworks by the public does not fall within OSHA's authority to regulate workplace safety and health. OSHA believes the proposed language is clearer than the existing language in paragraph (k)(1). </P>
                    <P>Since the initial publication of § 1910.109, NFPA has published three codes for the use and sale of pyrotechnics: (1) NFPA 1123-2000—Code for Fireworks Display; (2) NFPA 1124-2003—Code for the Manufacture, Storage, and Retail Sales of Fireworks and Pyrotechnic Articles; and (3) NFPA 1126-2001—Standard for the use of Pyrotechnics before a Proximate Audience. In the future, OSHA intends to conduct further rulemaking based upon these NFPA codes and at that time will modify the scope of § 1910.109 to include the sale of both public display pyrotechnics and consumer fireworks and the use of pyrotechnics at public displays. Unless otherwise stated, the provisions of the proposed rule, like those in the current rule, apply to pyrotechnics as well as to other types of explosives. In addition, the proposal continues to apply OSHA's PSM regulations to the manufacture of pyrotechnics as discussed in proposed paragraph (a)(2) above. However, OSHA has decided, because of time and resource constraints, to address additional issues regarding pyrotechnics in a separate rulemaking. OSHA believes that trying to expand pyrotechnics coverage in the current rulemaking would result in significant delay in providing needed protection from explosives hazards. Proposed paragraph (i) is being reserved for this future pyrotechnics rulemaking. </P>
                    <P>
                        <E T="03">Paragraph (b) Definitions applicable to this section</E>
                        . Paragraph (b) lists and defines all major terms used in the proposed standard. Some of the proposed definitions are the same as those in the existing standard, while others have been reworded. Some definitions are new and some have not been retained from the existing standard. 
                    </P>
                    <HD SOURCE="HD2">New Definitions </HD>
                    <P>Upon consideration of technological developments in the explosives field, the plain language initiative, inconsistencies in definitions among Federal agencies, and definitions used in relation to public safety versus employee safety, OSHA proposes the following new definitions: </P>
                    <P>
                        <E T="03">Blast area</E>
                        . OSHA is proposing to define this term to mean the area of a blast within the influence of flying rock or other debris, gases, and concussion. This term is commonly used in the explosives industry and is being added to the proposal to clarify its safety requirements for blasting operations. The use of the term in the proposal is consistent with its use in the 2001 edition of NFPA 495 (Ex. 2-5). 
                    </P>
                    <P>
                        <E T="03">Blast site</E>
                        . This term would be defined to mean the area where explosives are handled during the preparation and loading of drill holes, including 50 feet (15.2 m) in all directions from the perimeter formed by loaded holes. The 50-foot distance requirement, applies in all directions along the full depth of the drill hole and the blast site exists until the explosives are detonated. This term is commonly used in the explosives industry and is being added to the proposal to clarify its safety requirements for blasting operations. The use of the term in the proposal is consistent with its use in the 2001 edition of NFPA 495 (Ex. 2-5). 
                    </P>
                    <P>
                        <E T="03">Issue #2:</E>
                         In subsequent discussions with the Institute of Makers of Explosives (IME) following their submission of the Petition, they recommended that OSHA revise the definition of blast site to decrease the 50-foot requirement to 30 feet if “the perimeter of loaded holes is marked and separated from non-blast site areas by a barrier.” IME would define a barrier as a “material object or objects that separates, keeps apart, or demarcates in a conspicuous manner such as cones or a warning sign or tape.” OSHA, however, is concerned that simply installing a barrier, as defined by IME, at a blast site may not provide the degree of safety needed to allow employees to be as close as 30 feet to explosion hazards. OSHA requests specific comments on the IME recommendation. 
                    </P>
                    <P>
                        <E T="03">Blaster-in-charge</E>
                        . OSHA would define this term to mean the person in charge of the handling, loading, and firing of explosives within the blast site and blast area. This term is intended to identify a person designated by the employer to be in charge of the 
                        <PRTPAGE P="18800"/>
                        handling, loading, and firing of explosives. 
                    </P>
                    <P>The 2001 edition of NFPA 495 (Ex. 2-5) does not use the term “blaster-in-charge” but uses the term “blaster” as a person “qualified to be in charge of and responsible for the loading and firing of a blast.” While NFPA 495 does not specifically require one person to be in charge of the blast area, the definition of blaster-in-charge in the proposed standard requires that one person is in charge of the blast area and the blast site. This is being done to enhance safety by centralizing control in one person. The proposed term “blaster-in-charge” is based upon a recommendation in the Petition (Ex. 2-1). </P>
                    <P>
                        <E T="03">Bulk delivery vehicle</E>
                        . This term would be defined to mean any vehicle that transports blasting agents or their ingredients, in bulk form. Bulk delivery vehicles may also be capable of mixing ingredients to form blasting agents and loading blasting agents directly into drill holes. For example, bulk delivery vehicles may contain ammonium nitrate and a fuel oil in separate compartments and mix the two to form a blasting agent just before the blasting agent is transferred into the drill hole. The bulk delivery vehicle may also be capable of adding an emulsion to the mixture. The bulk delivery vehicle will either auger or pump the blasting agent into the drill hole. This definition is intended to provide clarity and reflects technological advancements in bulk blasting agent delivery methods. 
                    </P>
                    <P>
                        <E T="03">Competent person</E>
                        . This term would be defined by OSHA to mean an employee designated by the employer who, by way of training and/or experience, is knowledgeable of applicable standards, is capable of identifying workplace hazards relating to explosives, and has authority to take appropriate corrective actions to control such hazards. Although not defined, this term is used in the existing standard at (c)(5)(viii), (c)(5)(ix), (d)(2)(iii)(b), and (g)(5)(vii). Defining the term in the proposed standard enhances safety by clearly stating the required qualifications of the competent person. 
                    </P>
                    <P>
                        <E T="03">Detonator</E>
                        . OSHA is proposing to define this term to mean any device containing an initiating or primary explosive that is used for initiating detonation in another explosive material. A detonator may not contain more than .35 ounces (10 grams) of total explosives by weight, excluding ignition or delay charges. The term includes, but is not limited to, electric blasting caps of instantaneous and delay types, electronic detonators, blasting caps for use with safety fuse, detonating cord delay connectors, and nonelectric instantaneous and delay blasting caps which use detonating cord, shock tube, or any other replacement for electric leg wires. Although the term is used in the existing standard in paragraph (e)(1)(ii), it is not defined. The proposed standard defines the term to enhance regulatory clarity and to reflect recent technological advances in detonation methods. 
                    </P>
                    <P>
                        <E T="03">Electric detonator</E>
                        . OSHA is proposing that this term be defined as a detonator designed for, and capable of, initiation by means of an electric current. This term is reflective of recent technological advancements in detonation methods. 
                    </P>
                    <P>
                        <E T="03">Electronic detonator</E>
                        . OSHA would define this term to mean a detonator that utilizes stored electrical energy as a means of powering an electronic timing delay element/module and that provides initiation energy for firing the base charge. This term is reflective of recent technological advancements in detonation methods. 
                    </P>
                    <P>
                        <E T="03">Emulsion</E>
                        . This term would be defined to mean an explosive that either contains substantial amounts of oxidizer dissolved in water droplets that are surrounded by an immiscible fuel, or contains droplets of an immiscible fuel that are surrounded by water containing substantial amounts of oxidizer. Emulsions, depending on their properties, are classified as Division 1.1 explosives or Division 1.5 blasting agents. This term has been added due to the development and routine use of emulsions by the industry, and is based upon a recommendation in the Petition (Ex. 2-1). 
                    </P>
                    <P>
                        <E T="03">Hot work</E>
                        . OSHA is proposing to define this term to mean any work involving electric or gas welding, cutting, brazing, or similar flame or spark-producing operations. This term is consistent with the definition in the PSM standard (§ 1910.119(b)). 
                    </P>
                    <P>
                        <E T="03">Vehicle</E>
                        . This term would be defined by OSHA to mean any motor vehicle, machine, tractor, trailer, or semi-trailer propelled or drawn by mechanical power and used in the transportation of explosives. This replaces the existing definition of “motor vehicle.” Unlike the existing definition of “motor vehicle,” the proposed definition does not contain the word “highway” because the proposed standard covers vehicles that are used both on and off the highway. The term “self-propelled” in the existing definition would be replaced by the phrase “propelled or drawn by mechanical power” to be consistent with the DOT definition of motor vehicle at 49 CFR 171.8 and recommendations of the Petition (Ex. 2-1). 
                    </P>
                    <HD SOURCE="HD2">Revised Definitions </HD>
                    <P>OSHA is proposing the following revisions to existing definitions in § 1910.109: </P>
                    <P>
                        <E T="03">Blasting agent</E>
                        . OSHA is proposing that this term be defined as any material or mixture intended for blasting that is classified as a Division 1.5 explosive. This is different from the definition in existing paragraph (a)(1) that reads: 
                    </P>
                    <EXTRACT>
                        <P>Blasting agent—any material or mixture, consisting of a fuel and oxidizer, intended for blasting, not otherwise classified as an explosive and in which none of the ingredients are classified as an explosive, provided that the finished product, as mixed and packaged for use or shipment, cannot be detonated by means of a No. 8 test blasting cap when unconfined.</P>
                    </EXTRACT>
                    <P>OSHA has changed the definition of “blasting agent” in the proposed standard to update it and make it consistent with the definition used by the DOT and the United Nations' Globally Harmonized System of Classification and Labeling of Chemicals (see discussion below) explosives classification system. The changes were also recommended by the Petition (Ex. 2-1). </P>
                    <P>
                        <E T="03">Explosive</E>
                        . This term would be defined to mean any device, or liquid or solid chemical compound or mixture, the primary or common purpose of which is to function by explosion. The term “explosive” would be defined to include all material included as a Class 1 explosive by DOT in accordance with 49 CFR chapter I. The term would include, but would not be limited to, dynamite, black powder, pellet powders, detonators, blasting agents, initiating explosives, blasting caps, safety fuse, fuse lighters, fuse igniters, squibs, cordeau detonant fuse, instantaneous fuse, igniter cord, igniters, pyrotechnics, special industrial explosive materials, small arms ammunition, small arms ammunition primers, smokeless propellant, cartridges for propellant-actuated power devices, and cartridges for industrial guns. 
                    </P>
                    <P>In the proposed standard, OSHA would classify explosives using the same classification system as DOT (see 49 CFR 173.50). Explosives would be classified using the following divisions: </P>
                    <P>(i) Division 1.1 consists of explosives that have a mass explosion hazard. A mass explosion is one which affects almost the entire load instantaneously. </P>
                    <P>(ii) Division 1.2 consists of explosives that have a projection hazard but not a mass explosion hazard. </P>
                    <P>
                        (iii) Division 1.3 consists of explosives that have a fire hazard and either a minor blast hazard or a minor 
                        <PRTPAGE P="18801"/>
                        projection hazard or both, but not a mass explosion hazard. 
                    </P>
                    <P>(iv) Division 1.4 consists of explosives that present a minor explosion hazard. The explosive effects are largely confined to the package and no projection of fragments of appreciable size or range is to be expected. An external fire must not cause virtually instantaneous explosion of almost the entire contents of the package. </P>
                    <P>(v) Division 1.5 consists of very insensitive explosives. This division is comprised of substances which have a mass explosion hazard but are so insensitive that there is very little probability of initiation or of transition from burning to detonation under normal conditions. (The probability of transition from burning to detonation is greater when large quantities are involved.) </P>
                    <P>(vi) Division 1.6 consists of extremely insensitive articles which do not have a mass explosive hazard. This division is comprised of articles which contain only extremely insensitive detonating substances and which demonstrate a negligible probability of accidental initiation or propagation. (The risk from articles of Division 1.6 is limited to the explosion of a single article.) </P>
                    <P>These definitions are different from the existing paragraph (a)(3) that reads: </P>
                    <EXTRACT>
                        <P>Explosive—any chemical compound, mixture, or device, the primary or common purpose of which is to function by explosion, i.e., with substantially instantaneous release of gas and heat, unless such compound, mixture, or device is otherwise specifically classified by the U.S. Department of Transportation; see 49 CFR chapter I. The term “explosives” shall include all material which is classified as Class A, Class B, and Class C explosives by the U.S. Department of Transportation, and includes, but is not limited to dynamite, black powder, pellet powders, initiating explosives, blasting caps, electric blasting caps, safety fuse, fuse lighters, fuse igniters, squibs, cordeau detonant fuse, instantaneous fuse, igniter cord, igniters, small arms ammunition, small arms ammunition primers, smokeless propellant, cartridges for propellant-actuated power devices, and cartridges for industrial guns. Commercial explosives are those explosives which are intended to be used in commercial or industrial operations. </P>
                        <NOTE>
                            <HD SOURCE="HED">Note 1:</HD>
                            <P>Classification of explosives is described by the U.S. Department of Transportation as follows (see 49 CFR chapter I):</P>
                            <P>(i) Class A explosives. Possessing, detonating, or otherwise maximum hazard; such as dynamite, nitroglycerin, picric acid, lead azide, fulminate of mercury, black powder, blasting caps, and detonating primers. </P>
                            <P>(ii) Class B explosives. Possessing flammable hazard, such as propellant explosives (including some smokeless propellants), photographic flash powders, and some special fireworks. </P>
                            <P>(iii) Class C explosives. Includes certain types of manufactured articles which contain Class A or Class B explosives, or both, as components but in restricted quantities. </P>
                            <P>(iv) Forbidden or not acceptable explosives. Explosives which are forbidden or not acceptable for transportation by common carriers by rail freight, rail express, highway, or water in accordance with the regulations of the U.S. Department of Transportation, 49 CFR chapter I.</P>
                        </NOTE>
                    </EXTRACT>
                    <P>The term “explosive” in the proposed standard has been modified to be more consistent with the definition currently used by DOT. When § 1910.109 was originally promulgated in 1971, OSHA defined explosives in terms of Class A, Class B, and Class C explosives. Blasting agents were considered separately from explosives. At that time, DOT classified explosives in the same way. While OSHA continues to use this classification system in the existing standard, DOT has revised its explosive classification system. </P>
                    <P>On December 21, 1990, DOT issued a final rule that revised the “Hazardous Materials Regulations” contained in 49 CFR chapter I that cover the classification, packaging and shipping of explosives (including blasting agents), oxidizers, and flammable liquids and solids. Essentially, the revisions adopted the United Nations (UN) Recommendations on the Transport of Dangerous Goods (Ex. 2-18), standardizing the testing, classification, packaging, labeling, placarding, and handling of explosives, thereby reducing regulatory inconsistencies that existed between the United States and other countries for purposes of transport of dangerous goods. </P>
                    <P>The revision of DOT's classification system eliminated Classes A, B, C, and blasting agents, and adopted the UN classification system that assigns all explosives to Class 1. This UN classification system is called the Globally Harmonized System of Classification and Labeling of Chemicals (GHS) (Ex. 2-2). The system further categorizes Class 1 explosives into Divisions 1.1, 1.2, 1.3, 1.4, 1.5, and 1.6. This classification system includes blasting agents defined as explosives, and assigns them to Division 1.5. </P>
                    <P>ATF's classification of explosive materials at 27 CFR 555.202 is different from both the former and current DOT classification systems and places explosive materials in three categories: high, low, and blasting agents. In addition, a list of explosive materials is to be published at least annually by ATF (see 27 CFR 555.23). </P>
                    <P>The use of different explosives classification systems by DOT, ATF, and OSHA is confusing and burdensome for the regulated community. Therefore, OSHA is proposing to adopt the DOT UN-based classification system as part of the definition of explosives as applied in § 1910.109(b). The use of this globally-harmonized system enhances clarity and reduces confusion, thereby resulting in greater understanding and increased safety in the use of explosives. Stakeholders have indicated the desire that other departments and agencies should also consider adoption of the DOT UN-based classification system to reduce the burden for and misunderstanding within the industry. </P>
                    <P>Another change in the definition of explosives in the proposed standard is the specific inclusion of blasting agents and pyrotechnics. Since blasting agents and pyrotechnics are considered explosives by DOT and are listed in the ATF list of explosive materials, they should be included in the OSHA definition of explosives. There is no significant impact expected from this change since, in both the existing and proposed standards, the manufacture of blasting agents is excluded and the manufacture of pyrotechnics is covered by the PSM requirements (see existing standard §§ 1910.109(k)(2) and (3) and proposed standard §§ 1910.109(a)(2) and (b)). </P>
                    <P>The following conversion table has been developed to illustrate the differences between the existing (labeled “Current OSHA Classification”) and the proposed (labeled “Proposed OSHA/Current DOT Classification”) classification systems and a similar table would be inserted at the end of the proposed definition of “explosives”. </P>
                    <GPOTABLE COLS="02" OPTS="L2,i1" CDEF="s50,r50">
                        <TTITLE>Classification Conversion Table</TTITLE>
                        <BOXHD>
                            <CHED H="1">
                                Proposed OSHA/
                                <LI>current DOT classification</LI>
                            </CHED>
                            <CHED H="1">
                                Current OSHA 
                                <LI>classification</LI>
                            </CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">Division 1.1</ENT>
                            <ENT>Class A explosives.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Division 1.2</ENT>
                            <ENT>Class A or Class B explosives.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Division 1.3</ENT>
                            <ENT>Class B explosives.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Division 1.4</ENT>
                            <ENT>Class C explosives.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Division 1.5</ENT>
                            <ENT> Blasting agents.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Division 1.6</ENT>
                            <ENT>No applicable hazard class.</ENT>
                        </ROW>
                    </GPOTABLE>
                    <P>
                        <E T="03">Pyrotechnics.</E>
                         OSHA would define this term to mean any combustible or explosive compositions or manufactured articles designed and prepared for the purpose of producing audible or visible effects by combustion, deflagration, or detonation, which are commonly referred to as fireworks. This proposed definition is the same as the 
                        <PRTPAGE P="18802"/>
                        existing definition in (a)(10) except that it includes the additional words “by combustion, deflagration, or detonation.” These words have been added to the proposed definition to make it consistent with the definitions used by ATF and NFPA for fireworks. 
                    </P>
                    <P>
                        ATF defines fireworks in 27 CFR 555.11 (Ex. 2-4) as “any composition or device designed to produce a visible or an audible effect by combustion, deflagration, or detonation, and which meets the definition of ‘consumer fireworks' or ‘display fireworks' as defined by this section.” NFPA similarly defines fireworks in paragraph 3.3.30 in the 2003 edition of NFPA 1124 (Ex. 2-19) as “any composition or device for the purpose of producing a visible or an audible effect by combustion, deflagration, or detonation, and that meets the definition of 
                        <E T="03">consumer fireworks</E>
                         or 
                        <E T="03">display fireworks</E>
                         as set forth in this code.” 
                    </P>
                    <P>The DOT regulations do not explicitly define fireworks. However, like the proposed standard, fireworks may be classified under the DOT regulations (49 CFR 172.101) as Division 1.1, 1.2, 1.3, or 1.4 explosives, depending on the properties of the composition. </P>
                    <P>
                        <E T="03">Semiconductive hose.</E>
                         OSHA is proposing to define this term to mean a hose with an electrical resistance high enough to limit flow of stray electric currents to safe levels, yet not so high as to prevent drainage of static electric charges to ground; or a hose of not more than two megohms resistance over its entire length and of not less than 1,000 ohms per foot. This definition has been modified from the existing requirement in paragraph (a)(12) which states: “Semiconductive hose—a hose with an electrical resistance high enough to limit flow of stray electric currents to safe levels, yet not so high as to prevent drainage of static electric charges to ground; hose of not more than 2 megohms resistance over its entire length and of not less than 5,000 ohms per foot meets the requirement.” The modification of the existing text requirement of “not less than 5,000 ohms per foot resistance” to the proposed text of “not less than 1,000 ohms per foot resistance” is recommended in the Petition (Ex. 2-1) and is also in accordance with the 2001 edition of NFPA 495 (Ex. 2-5) definition. In addition, after further discussion on this issue, IME maintained that the use of 1,000 ohms has become the accepted practice in the industry and it is a better balance in terms of safety to ensure the hose does not become electrically charged and create a source of static electricity. A resistance that is too high can cause the hose to become electrically charged and become a dangerous source of static electricity. The proposed reduction in resistance to 1,000 ohms creates a safer work environment by eliminating the possibility of a static charge that can create a spark at the blast hole. At the same time, anything less than 1,000 ohms may be conductive, which could create a current path from the vehicle directly to the drill hole. 
                    </P>
                    <P>
                        <E T="03">Smokeless propellants.</E>
                         This term would be defined by OSHA to mean solid propellants, commonly called smokeless powders, used in small arms ammunition, cannon, rockets, and propellant-actuated power devices. This proposed definition is essentially the same as the existing definition in paragraph (a)(15). However, the phrase “in the trade” immediately after the phrase “commonly called smokeless propellants” in the existing definition has been eliminated in the proposed definition because it is unnecessary. 
                    </P>
                    <P>
                        <E T="03">Water gels or slurries.</E>
                         OSHA is proposing that this term be defined as explosives that contain substantial proportions of water, oxidizers, and fuel with a cross-linking agent, a gelling, or a thickening agent added. Water gels or slurries, depending on their properties, are classified as Division 1.1 explosives or Division 1.5 blasting agents. This definition is a plain language rewrite of the existing definition in (a)(18) with no substantive change. The proposed change is consistent with the definition of water gel in paragraph 3.3.58 of the 2001 edition of NFPA 495 (Ex. 2-5), and is based upon a recommendation in the Petition (Ex. 2-1). 
                    </P>
                    <P>The definitions in the existing standard for the following terms have not been included in the proposed standard because the terms are not used in the proposed standard: Explosive-actuated power devices, highway, special industrial explosive devices, and DOT specifications. </P>
                    <P>Existing paragraph (a)(7), which reads: “Motor vehicle—any self-propelled vehicle, truck, tractor, semitrailer, or truck-full trailers used for the transportation of freight over public highways,” has not been retained in the proposal and has been replaced with the term “vehicle” as part of the plain language rewrite to eliminate the confusion created in the existing standard which uses several different terms to describe a vehicle. </P>
                    <P>The definitions of the following terms have remained the same in the proposed standard as in the existing standard: Magazine, propellant-actuated power device, small arms ammunition, small arms ammunition primers, and special industrial explosive materials. </P>
                    <P>
                        <E T="03">Paragraph (c) General provisions.</E>
                         As OSHA reviewed the existing standard, it appeared that many of the provisions contained in other paragraphs of existing § 1910.109 were more suitably placed under the general provisions in proposed paragraph (c) since they have broad applicability. As a result, proposed paragraph (c) contains general provisions that apply to all explosives activities, including a number of provisions that were previously located in other paragraphs in the existing rule. 
                    </P>
                    <P>
                        Paragraph (c)(1) of the proposal addresses explosive hazards. Paragraph (c)(1)(i) would require the employer to ensure that explosives are manufactured, transported, sold, handled, and used in a safe manner. This requirement is essentially the same as and replaces existing paragraph (b)(1) except that, unlike the existing paragraph, the requirements for safe manufacture and sale of explosives are included in the proposed paragraph to be consistent with the scope of the standard in proposed paragraph (a), as described earlier. In addition, the proposed paragraph (c)(1)(i) will not apply to storage of explosives. The reason for this is explained in the 
                        <E T="03">OSHA's Authority to Regulate</E>
                         discussion above. 
                    </P>
                    <P>Paragraph (c)(1)(ii) would require the employer to ensure that only persons trained in accordance with paragraph (j) of this section handle or use explosives. Loading and unloading of explosives are examples of handling, and blasting of slag pockets is an example of the use of explosives. This is a new requirement that reinforces the importance of training for all employees engaged in the handling and use of explosives. This proposed paragraph is based on a recommendation in the Petition (Ex. 2-1). </P>
                    <P>
                        Paragraph (c)(1)(iii) would require the employer to ensure that blasting equipment or explosives that are unsafe due to deterioration, damage, or other causes are not used, and are disposed of by a person experienced in the safe disposal of such materials as soon as possible in accordance with manufacturers' recommendations. This paragraph is derived from and replaces existing paragraph (c)(5)(v) which deals with disposal of deteriorated explosives in storage and (e)(2)(iii) which prohibits the use of deteriorated or damaged explosives or blasting equipment. The two existing requirements were combined into one requirement in the proposal covering explosives that may have deteriorated or been damaged to the point where they have become unstable and may be unsafe. This requirement is also consistent with 
                        <PRTPAGE P="18803"/>
                        paragraph 9.6.3 of the 2001 edition of NFPA 495 (Ex. 2-5) for the disposal of explosive materials. 
                    </P>
                    <P>Paragraph (c)(1)(iv) addresses housekeeping and would require the employer to ensure that proper housekeeping is performed to prevent hazardous accumulations of explosives, oxidizers, or fuels and other sensitizers in, on, or in close proximity to facilities and equipment containing explosives. This would include any amount of accumulation that could potentially create a hazardous situation resulting in a fire or explosion. This is a new requirement and was recommended by the Petition (Ex. 2-1) to ensure that proper housekeeping is maintained to prevent an explosion. </P>
                    <P>Paragraph (c)(1)(v) would require the employer to ensure that all equipment is maintained in good working condition. In addition, paragraph (c)(1)(vi) would require a program of systematic maintenance of equipment be conducted on a regular schedule. Proposed paragraphs (c)(1)(v) and (vi) contain similar requirements as existing paragraph (h)(3)(v)(b). However, while the requirements in existing paragraph (h)(3)(v)(b) only apply to water gels, the requirements in proposed paragraphs (c)(1)(v) and (vi) would apply to all explosives covered by the proposed standard. OSHA believes it is important for employee safety that equipment involved with any explosives, not just water gels, is maintained in good working condition. The proposed paragraphs have also been re-written in clearer and more concise language. In addition, the proposed requirements are generally consistent with the requirements in paragraph 6.3.5(2) of the 2001 edition of NFPA 495 (Ex. 2-5) for explosives mixing facilities. </P>
                    <P>Paragraph (c)(1)(vii) would require the employer to ensure that no person is allowed to enter facilities containing explosives, or to transport, handle, or use explosives while under the influence of intoxicating liquors, narcotics, or other drugs that may cause the person to act in an unsafe manner in the workplace. Due to safety considerations, OSHA is proposing that such persons be completely restricted from access to a facility where explosives are manufactured or stored as well as restricting them from the handling and transportation of explosives. This requirement is a result of combining and replacing requirements in existing paragraphs (e)(1)(i) and (g)(6)(iv) that deal with hazards associated with intoxicating liquors, narcotics, or other dangerous drugs. This is another example of where OSHA is proposing to combine two similar requirements into one clearer, more concise requirement. Since this proposed requirement applies to all explosives activities, OSHA is proposing to relocate it in the general requirements paragraph. Existing paragraph (e)(1)(i) also addresses the hazards of smoking, matches, and flame near explosives but these issues are dealt with in proposed paragraph (c)(3). </P>
                    <P>Paragraph (c)(1)(viii) would require the employer to ensure that no person enters a facility containing explosives or a blast site unless authorized by the employer to enter the facility. This is a new requirement that was recommended by the Petition (Ex. 2-1) and is intended to prevent unnecessary entrance of employees into areas where explosives are present. Due to the nature of explosives, it is imperative that only employees necessary to perform required work are allowed to enter the facility or area containing explosives. In addition, in the event of an accidental explosion, this requirement would limit the number of persons exposed to the hazard. The proposal recognizes the fact that there may be occasions where other persons have a legitimate need to be in these areas and the proposed wording gives the employer sufficient flexibility to allow others to enter when necessary. Such situations may occur when an employer needs to conduct an environmental site tour, a customer or regulator site tour, an internal contractor audit, a senior management safety inspection, or other similar circumstances. </P>
                    <P>Paragraph (c)(1)(ix) would require the employer to ensure that no flammable cleaning solvents are present in facilities containing explosives except where authorized by the employer and where their presence does not endanger the safety of employees. This is a new requirement and is based on a recommendation in the Petition (Ex. 2-1). Due to their potential to create a fire and thus cause an explosion, it is generally not safe to have flammable cleaning solvents in facilities containing explosives. There are a number of situations, however, where the use of such substances may be appropriate. For example, isopropyl alcohol is used in some instances to clean articles. For storage magazines, ATF requirements in 27 CFR 555.215 (Ex. 2-4) require volatile materials be kept at least 50 feet from outdoor magazines. </P>
                    <P>The requirements in paragraph (c)(2) of the proposed standard address the electrical hazards associated with explosives. Requirements for electrical protection are scattered throughout the existing § 1910.109 standard. Those requirements have been consolidated into one set of requirements in paragraph (c)(2) of the proposed standard. This will more clearly identify to employers the requirements that must be followed to prevent fires or explosions due to electrical hazards. OSHA notes that the requirements in proposed paragraph (c)(2) supplement the general electrical requirements of 29 CFR part 1910 Subpart S. Employers must, therefore, follow both the Subpart S requirements for all explosives facilities and the additional requirements proposed in paragraph (c)(2). </P>
                    <P>Paragraph (c)(2)(i) would require the employer to ensure that the primary electrical supply to any part of the facility (e.g., building, loading dock, etc.) containing explosives can be disconnected at a safe remote location away from that part of the facility. A safe remote location from a part of the facility containing explosives is a location far enough away to ensure that, if all the explosives in that part of the facility detonated, a person at the remote location would not be injured by the explosion. In determining what a safe remote location is, the employer will need to consider factors such as the type and amount of explosives present. </P>
                    <P>This is a new requirement that was recommended by the Petition (Ex. 2-1). It is consistent with the requirements in § 1910.308(c) for special electrical systems and would require a remote, electrical power shut-off switch to each part of a facility containing explosives. It is important that, in the event of an evacuation due to a fire or explosion in part of a facility, the electrical power to that part of the facility can be turned off remotely to prevent any further problems caused by energized circuits such as an electrical short circuit. A “part of a facility containing explosives” would include any building on a site where explosives are manufactured, handled or stored. </P>
                    <P>
                        Proposed paragraph (c)(2)(ii) deals with safety hazards caused by electrical storms. During the approach and progress of an electrical storm, paragraph (c)(2)(ii)(A) would require the employer to ensure that all explosive manufacturing and blasting operations are suspended, and paragraph (c)(2)(ii)(B) would require the employer to ensure that employees located in or near facilities containing explosives, or in blast sites, are withdrawn immediately to a safe remote location. A safe remote location in this case would be a location far enough away from all the explosives in the facility or blast site so that a person would not be injured if there were an explosion. These proposed requirements are based on the 
                        <PRTPAGE P="18804"/>
                        requirements in existing paragraph (e)(1)(vii)(a) which requires employers to remove employees from the blasting area during the approach and progress of an electrical storm. However, proposed paragraph (c)(2)(ii)(A) has been expanded to require the suspension of explosive manufacturing operations and proposed paragraph (c)(2)(ii)(B) also requires the immediate withdrawal of employees located near explosives. This reduces the time the employees are exposed to a potential hazard. The expansion of the existing requirement is in recognition that an electrical storm may be hazardous to employees at facilities and blast sites containing explosives and that employees need to be kept a safe distance away from a potential explosion. This is standard practice in the industry and is consistent with a recommendation in the Petition (Ex. 2-1). 
                    </P>
                    <P>Static electricity as a potential source of ignition is probably the single greatest concern for facilities and blast sites containing explosives. The Petition (Ex. 2-1) recommends new requirements for static electricity protection that would require any new static electricity protection system to comply with NFPA 77, Static Electricity (Ex. 2-7). However, it recommended limiting the application of the requirements only to systems installed after the effective date of the new standard and would not require an existing manufacturing facility to install a new system or modify an existing system to meet the requirements of NFPA 77. IME informed OSHA that certain explosives are not static-sensitive and do not require protection. IME further argues that, since explosives manufacturing is subject to the requirements of OSHA's PSM standard at § 1910.119, areas in an explosives manufacturing facility where static electricity protection systems may be needed should already have been identified through the process hazard analysis requirements of the PSM standard, and adequate safeguards should have been instituted in accordance with the PSM standard. </P>
                    <P>OSHA believes that static electricity protection systems can be important safety features for facilities containing explosives. The Agency considered proposing a requirement in paragraph (c) that would require the employer to ensure that all facilities containing explosives have appropriate and effective static electricity protection systems, with suggested methods of compliance found in NFPA 77. The Agency decided not to propose such language because it lacked sufficient data and information on the types and effectiveness of static electricity protection systems. OSHA is seeking additional information on these issues through public comments. </P>
                    <P>
                        <E T="03">Issue #3:</E>
                         Do some or all types of facilities containing explosives require static electricity protection systems? If you think such protection systems are necessary, please explain when and why they are necessary. Should different kinds of protection systems be used in different circumstances, such as in different kinds of facilities, explosives, or geographic locations? What would be the costs associated with requiring static electricity protection systems? To what extent are such protection systems currently being used? What benefit in employee safety, if any, would be gained from using such protection systems? Are there any disadvantages to requiring facilities covered by this standard to install static electricity protection systems? 
                    </P>
                    <P>Proposed paragraph (c)(3) contains requirements that address fire and explosion hazards. Some of the requirements in paragraph (c)(3) are new and others are requirements from existing § 1910.109 that have been consolidated, clarified, and moved to this general fire and explosion prevention paragraph. The purpose of this consolidation is to make it easier for users of the standard to know what fire and explosion prevention regulations are required by combining them into one paragraph. </P>
                    <P>Paragraph (c)(3)(i) would require the employer to ensure that explosives are handled in a manner that minimizes the spillage and jarring, the generation of explosive dust, and the creation of friction in or in close proximity to explosives. This is a new requirement that is based on a recommendation in the Petition (Ex. 2-1) and OSHA believes it is an important precaution for handling and moving shock and friction sensitive explosive materials. </P>
                    <P>Paragraph (c)(3)(ii)(A) would require the employer to ensure that when a fire is in imminent danger of contact with explosives, employees do not fight the fire. In addition, paragraphs (c)(3)(ii)(B) and (C) would require that all employees be moved to a safe area and the fire be guarded against intruders. These are new requirements based on a recommendation in the Petition (Ex. 2-1) and are consistent with the language in paragraph 9.1.6 of the 2001 edition of NFPA 495 (Ex. 2-5). OSHA considers these to be widely accepted practices within the industry when dealing with fires near explosive materials. If the fire is past the point where it can be prevented from reaching explosive materials, the requirements in proposed paragraph (c)(3)(ii) would help to ensure that employees are safely away from the explosives in the event that the fire causes them to detonate. </P>
                    <P>The hazards of flame, matches, and spark producing devices are dealt with in proposed paragraph (c)(3)(iii)(A) by requiring the employer to ensure that no open flames, matches, or spark producing devices are located within 50 feet of explosives or facilities containing explosives. As mentioned earlier, “facilities containing explosives” refers to any building on a site where explosives are manufactured, handled or stored. This requirement is a consolidation of four requirements in the existing standard that have been combined into one general requirement and clarified in the proposed rule. Existing paragraphs (c)(5)(vii), (e)(1)(i), (g)(2)(vi)(d), and (g)(5)(iii) deal with open flames, matches, or spark producing devices around magazines, near explosives, near buildings or facilities used to mix blasting agents, and near blasting agent storage warehouses. The term “facilities containing explosives” used in proposed paragraph (c)(1)(vii) covers all these situations. The 50-foot prohibition is consistent throughout this proposed rule and, in general, is considered to be an acceptable safe distance. </P>
                    <P>
                        <E T="03">Issue #4:</E>
                         OSHA seeks specific comments on the impact proposed paragraph (c)(3)(iii) would have on the storage and retail sale of small arms ammunition, small arms primers, and smokeless propellants. Do open flames, matches, or spark producing devices create a hazard when located within 50 feet of small arms ammunition, small arms primers, or smokeless propellants, or facilities containing these products? Can employers involved in the storage or retail sale of small arms ammunition, small arms primers, or smokeless propellants prevent all open flames, matches, or spark producing devices from coming within 50 feet of these products or facilities containing these products? If not, why not? Should proposed paragraph (c)(3)(iii) use a protective distance other than 50 feet and, if so, what distance should it be and why? Should OSHA exclude small arms ammunition, small arms primers, and smokeless propellants from the requirements of proposed paragraph (c)(3)(iii)? 
                    </P>
                    <P>
                        Existing paragraphs (c)(5)(vii), (g)(2)(vi)(d), and (g)(5)(iii) also deal with smoking and the hazards of firearms near storage magazines and blasting agent mixing plants. The proposed standard separates these two concepts and deals with them as individual requirements in proposed paragraphs 
                        <PRTPAGE P="18805"/>
                        (c)(3)(iii)(B) and (C). Proposed paragraph (c)(3)(iii)(B) would require the employer to ensure that smoking is only permitted in authorized smoking areas. This requirement is a change from the existing requirements that allow smoking as long as it is done more than 50 feet away from particular activities or operations. Under the proposed requirement, the employer would have to ensure that smoking areas are a safe distance from explosives. 
                    </P>
                    <P>Proposed paragraph (c)(3)(iii)(C) would require the employer to ensure that no person carries firearms, ammunition, or similar articles in facilities containing explosives or blast sites except as required for work duties. This proposed requirement is different from the existing requirements which prohibit firearms within 50 feet of storage magazines and blasting agent mixing plants. The proposed requirement would prohibit firearms at facilities containing explosives and at blast sites. In addition, as recommended by the Petition (Ex. 2-1), the proposed requirement would prohibit ammunition and similar articles along with firearms. The requirement would allow firearms, ammunition, or similar articles to be carried by guards as needed to perform their work duties. </P>
                    <P>Paragraph (c)(3)(iii)(D) would require the employer to ensure that vehicles are not refueled within 50 feet of a facility containing explosives or a blast site. This is a new requirement based on a recommendation in the Petition (Ex. 2-1). A fire or explosion caused by refueling a vehicle could in turn cause explosives to explode if they are too near to the refueling vehicle. Proposed paragraph (c)(3)(iii)(D) addresses this hazard by requiring a safe 50-foot distance between explosives and refueling vehicles. </P>
                    <P>Proposed paragraph (c)(4) covers general maintenance and repairs. These requirements deal with the possibility of maintenance or repair work being a potential cause of an explosion. Paragraph (c)(4)(i) would require the employer to ensure that, before any maintenance or repairs are started in or in close proximity to any facility containing explosives or a blast site, the immediate area surrounding the maintenance or repair work is free of explosives, including residues and dusts containing explosives. The removal of explosives and the cleaning of the surrounding area is a basic precaution necessary to prevent an explosion. Maintenance and repair work may create sparking and may require the use of welding equipment. Such activities could be a source of ignition for explosives and their remnants, including residues and dusts. This proposed safety requirement is based on a recommendation in the Petition (Ex. 2-1). OSHA also believes such cleaning around maintenance or repair work to be standard industry practice. </P>
                    <P>The proposal does not specify a distance around the maintenance or repair work that must be cleaned. The employer must make the determination of what distance is safe based on the situation. For hot work operations, whether done for maintenance, repair, or for any other reason, the employer must also comply with proposed paragraph (c)(4)(ii), which requires the employer to ensure that the fire prevention and protection requirements in § 1910.252(a) and proposed paragraph (c)(3)(iii) of this section are implemented prior to beginning hot work operations. The requirements in § 1910.252(a) provide general rules for welding operations. In addition, proposed paragraph (c)(3)(iii) would require that any hot work operations, since they are fire hazards, be performed 50 feet or more away from explosives or facilities containing explosives. Therefore, hot work operations may not be performed inside or within 50 feet of facilities containing explosives. </P>
                    <P>One area that continues to create confusion in the explosives industry is labeling requirements. The existing § 1910.109 standard does not contain labeling requirements. However, labels are required by the Department of Transportation (DOT) for the transportation of packages or containment devices that contain hazardous materials meeting one or more of DOT's hazard class definitions (see 49 CFR part 172, subpart E) (Ex. 2-8). In addition, OSHA's Hazard Communication Standard, 29 CFR 1910.1200, requires labels for hazardous chemicals. Specifically, § 1910.1200(f)(1) requires the chemical manufacturer, importer, or distributor to ensure that each container of hazardous chemicals is labeled, tagged, or marked prior to leaving the workplace. The information must contain the identity of the hazardous chemical(s), appropriate hazard warnings, and the name and address of the chemical manufacturer, importer, or other responsible party. In addition, § 1910.1200(f)(5) requires the employer to ensure that each container of hazardous chemicals in the workplace is labeled, tagged, or marked with information about the identity and hazards of the chemicals in the containers. In both cases, the requirements are performance-oriented and do not specify the design or appearance of the label. </P>
                    <P>In an effort to clarify the labeling requirements for explosives, OSHA is clarifying in proposed paragraph (c)(5)(i) that the employer must communicate hazards associated with explosives in accordance with the requirements of the Hazard Communication Standard, § 1910.1200. This simply clarifies that packages of explosives are required to be labeled in accordance with § 1901.1200. In addition, the proposed requirement specifies that, where labeling of explosives is required under § 1910.1200, Globally Harmonized System of Classification and Labeling of Chemicals (GHS) (Ex. 2-2) labels must be used for the different divisions of explosives. This makes the labeling requirements in the proposed standard more consistent with the DOT labeling requirements. To make it easier to comply with the proposed label requirements, in addition to describing the contents of the labels, OSHA has proposed to include pictures of the required GHS labels. The labels would have a signal word, a hazard statement, and either a division designation or a pictogram. The pictogram would be black on a white background with a red frame sufficiently large to be clearly visible. </P>
                    <P>In practical terms, the label required by the proposed standard depends on the status of the container, package, box, or bag. For transport containers, a GHS label would not be required where a DOT label is used (see GHS document paragraph 1.4.10.5.1) (Ex. 2-2). Thus, a truck containing explosives would be placarded on the outside according to DOT requirements, and all transport containers inside the truck would need to be provided with a DOT label. Any packages, boxes, or bags within the transport containers in the truck would require labels in accordance with OSHA's Hazard Communication standard (§ 1910.1200) and proposed paragraph (c)(5)(i) would require the labels to be GHS. In addition, all in-plant containers, packages, boxes, or bags would be required to follow § 1910.1200 requirements and thus would be required to have the GHS labels required by proposed paragraph (c)(5)(i). </P>
                    <P>In effect, proposed paragraph (c)(5)(i) is not adding a label requirement, but merely specifying the type of label that must be present for compliance with § 1910.1200. Labels required for compliance with § 1910.1200 and those required by DOT will still be necessary. </P>
                    <P>
                        <E T="03">Issue #5:</E>
                         This proposed paragraph does not contain a phase-in period of time for compliance with the GHS label requirements. The Agency seeks input 
                        <PRTPAGE P="18806"/>
                        on whether employers need a phase-in period to comply with the new requirement of proposed paragraph (c)(5)(i) that requires labels be GHS labels? If so, how long should the phase-in period be to allow employers sufficient time to become familiar with and have the capability to provide these labels on containers? 
                    </P>
                    <P>In addition, OSHA is aware that a United Nations Sub-Committee is considering adding unstable explosives to the GHS on the classification of explosives. They claim that even though unstable explosives are precluded from transport, they may occur in the workplace and need to be classified so that they can be regulated. The Agency seeks information on unstable explosives in the commercial explosives industry, where these unstable explosives occur, and what the hazards are? Are there hazards from unstable explosives that OSHA should regulate? </P>
                    <P>Proposed paragraph (c)(5)(ii) incorporates the already existing requirement that the employer ensure that DOT markings, placards, and labels are retained in accordance with § 1910.1201. The purpose of proposed paragraph (c)(5)(ii) is to clarify employer requirements concerning the use of DOT markings, placards and labels on packages, vehicles, and freight cars or containers containing explosives. Under § 1910.1201, any employer who receives a package of explosives which is required to be marked, labeled, or placarded in accordance with DOT's hazardous materials regulations (49 CFR parts 171 through 180) must retain those markings, labels, and placards on the package until the packaging is sufficiently cleaned of residue and purged of vapors to remove any potential hazards. Section 1910.1201 also requires that any employer who receives a vehicle, freight car, or container that is required to be marked or placarded in accordance with DOT's hazardous materials regulations must retain those markings and placards on the vehicle, freight car, or container until the explosives that require the marking or placarding are sufficiently removed to prevent any potential hazards. However, note that under § 1910.1201(d), for non-bulk packages containing explosives that will not be reshipped, the requirements of § 1910.1201 are met if a label or other acceptable marking is affixed in accordance with the Hazard Communication standard (see § 1910.1201(d)). Under § 1910.1201(e), non-bulk packaging is defined at 49 CFR 171.8 as packaging which has: (1) a maximum capacity of 119 gallons (450 L) or less as a receptacle for a liquid; (2) a maximum net mass of 882 pounds (400 kg) or less and a maximum capacity of 119 gallons (450 L) or less as a receptacle for a solid; or (3) a water capacity of 1000 pounds (454 kg) or less as a receptacle for a gas as defined in 49 CFR 173.115. </P>
                    <P>
                        <E T="03">Paragraph (d) Storage of ammonium nitrate.</E>
                         As discussed in the preamble above, “OSHA's Authority to Regulate,” OSHA is proposing to withdraw the provisions in existing paragraph (c) for the storage of explosives because they are preempted by ATF's regulations covering the storage of explosives (see 27 CFR part 555). In the proposed standard, OSHA proposes to continue to regulate the storage of ammonium nitrate (which is not an explosive) and the storage of small arms ammunition, primers, and smokeless propellants (which are not preempted by ATF's regulations). 
                    </P>
                    <P>Proposed paragraph (d) sets forth requirements for the storage of ammonium nitrate. The existing requirements for ammonium nitrate storage in § 1910.109(i) are based on the 1970 edition of NFPA 490. The proposed requirements are based on the 2002 edition of NFPA 490 (Ex. 2-6). The Petition (Ex. 2-1) did not recommend any changes to the existing requirements for the storage of ammonium nitrate. </P>
                    <P>OSHA is proposing to remove requirements from existing paragraph (i)(1) that are either unnecessary or outdated. Specifically, the requirements in existing paragraphs (i)(1)(i)(b) and (c) would be removed. Existing paragraph (i)(1)(i)(b) states that the regulations addressing the storage of ammonium nitrate do not apply to the transportation of ammonium nitrate. OSHA has concluded that this requirement is inappropriate because provisions covering the storage of ammonium nitrate are clearly different from provisions covering the transportation of ammonium nitrate. </P>
                    <P>Existing paragraph (i)(1)(c) states that paragraph (i) covering the storage of ammonium nitrate does not apply to the storage of ammonium nitrate under the jurisdiction of and in compliance with the regulations of the U.S. Coast Guard at 46 CFR parts 146 to 149. OSHA proposes to eliminate this requirement from the proposed standard because it is inaccurate and not related to the storage of ammonium nitrate. Parts 146 and 149 of the U.S. Coast Guard regulations are reserved parts that do not contain any regulations. Parts 147 and 148 contain regulations covering the transportation of hazardous materials on ships. In particular, 46 CFR 148.03-11 and 33 CFR 126.28 describes stowage requirements for Ammonium Nitrate onboard vessels and facilities respectively. Stowage is the general term used for “storage” onboard ships and waterfront facilities under the regulations found in 46 CFR part 148 and 33 CFR part 126. </P>
                    <P>Existing paragraph (i)(1)(ii)(b) states that the standards for ammonium nitrate (nitrous oxide grade) are those found in the “Specifications, Properties, and Recommendations for Packaging, Transportation, Storage, and Use of Ammonium Nitrate,” available from the Compressed Gas Association, Inc., which is incorporated by reference as specified in § 1910.6. The purpose and intent of the requirement is not clear. First, this existing paragraph merely references a document containing standards for nitrous oxide grade ammonium nitrate. It does not explain how such standards should be applied. Second, nitrous oxide grade ammonium nitrate is not used in the manufacture of explosives. It is not necessary to provide references in § 1910.109 for grades of ammonium nitrate that are not used in the explosives industry. Since this requirement is both unnecessary and confusing, OSHA proposes to eliminate it and its associated incorporation by reference in the proposed standard. </P>
                    <P>Proposed paragraph (d)(1) sets out the applicability of the requirements for the storage of ammonium nitrate. Proposed paragraph (d)(1)(i) states that proposed paragraph (d) applies to the storage of ammonium nitrate in quantities of 1,000 pounds (454 kg) or more to be used in the manufacture of explosives. Proposed paragraph (d)(1)(i) replaces existing paragraph (i)(2)(i) with a plain-language re-write to clarify that OSHA intends the requirements to apply to ammonium nitrate that will be used in the manufacture of explosives and that the requirements apply specifically to the storage of ammonium nitrate. OSHA is retaining the 1,000 pounds or more quantity for inclusion in proposed paragraph (d)(1)(i). Ammonium nitrate in quantities of 1,000 pounds or more must be stored according to proposed paragraph (d). This designated limit is consistent with paragraph 1.3 of the 2002 edition of NFPA 490 (Ex. 2-6) and is considered an acceptable threshold in the explosives industry. </P>
                    <P>
                        <E T="03">Issue #6:</E>
                         OSHA seeks specific comments on whether the storage requirements for ammonium nitrate should be triggered by specific quantities. If so, please explain what those quantities should be and why. 
                    </P>
                    <P>
                        Proposed paragraph (d)(1)(ii) revises existing paragraph (i)(1)(i)(a) to clarify that paragraph (d) does not apply to ammonium nitrate that can be classified 
                        <PRTPAGE P="18807"/>
                        as an explosive. As discussed earlier, the storage of ammonium nitrate that can be classified as an explosive would be covered by the storage requirements for explosives in ATF's regulations (27 CFR part 555). 
                    </P>
                    <P>Proposed paragraph (d)(2) addresses ammonium nitrate stored in buildings. Most of the requirements in the paragraph are consistent with paragraphs in the existing standard and are also consistent with the 2002 edition of NFPA 490. Any proposed requirements that differ from the existing requirements are discussed below. </P>
                    <P>Paragraph (d)(2)(i) states that buildings or structures constructed and used to store ammonium nitrate since before August 27, 1971, and that do not meet the requirements of proposed paragraph (d)(2), are deemed to be acceptable for the continued storage of ammonium nitrate, provided such use does not endanger the safety of employees. To fall within this exception, the building or structure must have been used to store ammonium nitrate from before August 27, 1971, until the effective date of this proposed standard. This proposed paragraph is consistent with and would replace existing paragraph (i)(2)(iii)(e) which allows continued use of buildings or structures built and used to store ammonium nitrate prior to the August 27, 1971 effective date of the existing standard (36 FR 10466), provided that such use does not endanger the safety of employees. </P>
                    <P>Paragraph (d)(2)(ii)(A) would require the employer to ensure that ammonium nitrate is stored in a manner that minimizes as far as possible fire and explosion hazards, including exposure to toxic vapors from burning or decomposing ammonium nitrate. This proposed requirement is similar to existing paragraph (i)(2)(ii) except that it covers all quantities of ammonium nitrate of 1,000 pounds or more stored in a building, whereas existing (i)(2)(ii) and paragraph 4.1.4 of the 2002 edition of NFPA 490 limit the requirement to “large quantity storage” of ammonium nitrate. </P>
                    <P>It is not clear what amount of ammonium nitrate would be considered a large quantity. Since “large quantity” is undefined in NFPA 490, OSHA believes it is necessary and appropriate to propose a more finite quantity to assure adequate employee protection. As a result, OSHA is proposing to apply this requirement to all quantities of ammonium nitrate covered by proposed paragraph (d). Other minor revisions have been added that are consistent with the plain language re-write and do not change the intent of the existing standard. </P>
                    <P>Paragraphs (d)(2)(ii)(B) and (d)(2)(ii)(C) would require the employer to ensure that storage buildings are not over one story in height above ground level and storage buildings do not have basements unless the basements are open on at least one side. These proposed requirements are the same as and replace the requirements in existing paragraph (i)(2)(iii)(a). To be consistent with maintaining one requirement per paragraph, the proposal replaces the requirements in existing paragraph (i)(2)(iii)(a) with two separate paragraphs. Both of these proposed requirements are similar to paragraph 4.2.1 of the 2002 edition of NFPA 490 (Ex. 2-6). </P>
                    <P>Paragraph (d)(2)(ii)(D) would require the employer to ensure that storage buildings are adequately ventilated to prevent unsafe heat or fume accumulations. This is essentially the same as existing paragraph (i)(2)(iii)(b), and paragraph 4.2.2 of the 2002 edition of NFPA 490 (Ex. 2-6) except that it does not contain the option that the building be constructed to be self-ventilating in the event of a fire. The purpose of the self-ventilation requirement in existing paragraph (i)(2)(iii)(b) is unclear. OSHA understands “self-ventilating” to mean the building is equipped with automatic (smoke or heat operated) roof vents, presumably to operate prior to fire department arrival. Use of these types of vents, however, has been somewhat controversial over the years for general commodity storage. Existing paragraph (i)(4)(i)(a) also deals with ventilation for warehouses that store bulk ammonium nitrate. In OSHA's continued effort in this proposed rule to combine duplicate requirements in the existing standard, OSHA is combining existing paragraphs (i)(2)(iii)(b) and (i)(4)(i)(a) in proposed paragraph (d)(2)(ii)(D). </P>
                    <P>
                        <E T="03">Issue #7:</E>
                         In proposed paragraph (d)(2), OSHA is requiring that the ventilation in storage buildings should prevent the accumulation of heat or fumes that could cause a fire rather than be designed to ventilate the storage building once a fire has started. OSHA requests specific comments on this issue, including the proposed approach emphasizing pre-fire safety rather than safety during a fire, and whether self-ventilation should be required for buildings or structures that store ammonium nitrate. 
                    </P>
                    <P>Paragraph (d)(2)(ii)(E) would require the employer to ensure that storage building walls are constructed to meet a four-hour fire resistant rating whenever they face and are within 50 feet of a combustible building, forest, pile of combustible materials, or other similar hazards. This proposed paragraph also would allow that, in lieu of a four-hour fire resistant wall, other equivalent means of exposure protection may be used. This proposed requirement is essentially the same as and replaces requirements in existing paragraph (i)(2)(iii)(c) except that “fire-resistive construction” was changed to “four-hour fire resistant rating” to be consistent with the 2002 edition of NFPA 490. The term “four-hour fire resistant rating” is derived from paragraph 4.2.3 in NFPA 490-2002, which requires a Type I wall for the exposed storage wall, and references NFPA 220, Standard on Types of Building Construction (Ex. 2-20), for a description of the wall to be used. Based on Table 3-1 of NFPA 220, OSHA has determined that the appropriate and most protective wall to be used is a four-hour fire resistant wall for protection against combustible materials. </P>
                    <P>
                        Paragraph (d)(2)(ii)(F) would require the employer to ensure that roof coverings of buildings or structures used to store ammonium nitrate, at a minimum, afford a light degree of fire protection to the roof deck, do not slip from position, and do not present a flying brand hazard. This proposed requirement is equivalent to and replaces the similar requirement in existing paragraph (i)(2)(iii)(c) except that OSHA proposes to delete the reference to the NFPA standard contained in existing paragraph (i)(2)(iii)(c) and include a more performance based requirement instead.
                        <SU>1</SU>
                        <FTREF/>
                         Circumstances may differ from facility to facility. OSHA has considered the relevant NFPA standards and has determined that a Class C (as defined in NFPA 256-2003) or better roof would meet the requirements of this proposed provision. 
                    </P>
                    <FTNT>
                        <P>
                            <SU>1</SU>
                             Existing paragraph (i)(2)(iii)(c) references NFPA 203M-1970 (Ex. 2-14) to determine whether the roof meets a rating of Class C or better. This is an incorrect reference since NFPA 203M-1970 does not define a Class C roof covering. NFPA 256 actually provides the test methods to determine the rating of a roof. The 2000 edition of NFPA 203 (NFPA 203M was re-designated as NFPA 203) (Ex. 2-15) references paragraphs 3.1.1 and 3.1.5 in NFPA 256 for the test methods to determine the classification of roof coverings.
                        </P>
                    </FTNT>
                    <P>
                        <E T="03">Issue #8:</E>
                         Does paragraph (d)(2)(ii)(F) as proposed provide adequate guidance for employers to follow in providing a safe roof for buildings or structures used to store ammonium nitrate? 
                    </P>
                    <P>
                        Proposed paragraph (d)(2)(ii)(G) would require the employer to ensure that storage buildings do not exceed a height of 40 feet unless constructed of noncombustible material or adequate 
                        <PRTPAGE P="18808"/>
                        facilities for fighting a roof fire are available. This proposed requirement is the same as and replaces existing paragraph (i)(4)(i)(b) except that the proposed requirement covers the storage of bulk ammonium nitrate and the storage of ammonium nitrate in bags, drums or other containers whereas the existing requirement only covers the storage of bulk ammonium nitrate. The proposed paragraph has also been re-written in clearer language. In addition, it is consistent with paragraph 6.1.2 of the 2002 edition of NFPA 490 (Ex. 2-6). 
                    </P>
                    <P>Paragraph (d)(2)(ii)(H) would require the employer to ensure that all flooring is of noncombustible material. Paragraph (d)(2)(ii)(I) would require the employer to ensure that all flooring is protected against impregnation by ammonium nitrate. Paragraph (d)(2)(ii)(J) would require the employer to ensure that no flooring has drains or piping into which any molten ammonium nitrate could flow and be confined in the event of fire. These proposed requirements are the same as and replace existing paragraph (i)(2)(iii)(d) except that they have been separated into individual provisions and re-written in clearer and more concise language. The proposed requirements are also consistent with paragraph 4.2.4 of the 2002 edition of NFPA 490 (Ex. 2-6). </P>
                    <P>Paragraph (d)(2)(ii)(K) would require the employer to ensure that storage buildings are dry and free from water seepage. This proposed requirement has been re-written in clearer and more concise language and replaces existing paragraph (i)(2)(iii)(f). Proposed paragraph (d)(2)(ii)(K) is also consistent with paragraph 4.2.6 of the 2002 edition of NFPA 490 (Ex. 2-6). </P>
                    <P>Paragraph (d)(2)(ii)(L) would require the employer to ensure that unauthorized persons do not enter an ammonium nitrate storage area. This proposed requirement is the same as and replaces existing paragraph (i)(6)(iii) except that it has been re-written in more succinct and understandable language. </P>
                    <P>Paragraph (d)(2)(ii)(M) would require the employer to ensure that ammonium nitrate and storage buildings containing ammonium nitrate are located at a safe distance from readily combustible fuels. This proposed requirement is the same as and replaces existing paragraph (g)(5)(v) except that it has been re-written in clearer language. The proposed paragraph is also consistent with paragraph 5.5.2 of the 2001 edition of NFPA 495 (Ex. 2-5). OSHA believes that it is important for employee safety to keep combustible fuels away from all ammonium nitrate, not just piles of ammonium nitrate (as in the existing requirement). </P>
                    <P>
                        Paragraph (d)(2)(ii)(N) would require the employer to ensure that in areas where lightning storms are prevalent, lightning protection systems are provided. Lightning protection systems meeting the safety requirements found in Appendix K of National Fire Protection Association (NFPA) 780-2004, 
                        <E T="03">Standard for the Installation of Lightning Protection Systems</E>
                        ), or other equally protective criteria would meet the requirements of this provision. 
                    </P>
                    <P>This proposed requirement is similar to and replaces existing paragraph (i)(6)(ii) except that the reference to NFPA has been updated, as discussed below, and compliance options broadened. </P>
                    <P>
                        OSHA found the requirement in existing paragraph (i)(6)(ii) may be confusing and difficult for employers to comply with for two reasons. First, the phrase “in areas where lightning storms are prevalent” is somewhat vague. Without clarification of where these areas are, the Agency believes this requirement may be difficult to comply with and difficult for OSHA to enforce. Second, the existing requirement also refers to NFPA 78-1968, 
                        <E T="03">Lightning Protection Code</E>
                         (Ex. 2-11), which appears to be problematic as well as outdated. When reviewing this NFPA document, OSHA found it difficult to determine how lightning protection for explosives is covered by NFPA 78-1968. In the NFPA 78-1968 document, Section 20, paragraph 2001 states that the code does not apply to “explosives manufacturing buildings and magazines.” 
                    </P>
                    <P>The current Lightning Protection Code, NFPA 780-2004 (Ex. 2-10) (in 1992 the numerical designation of the code was changed from NFPA 78 to NFPA 780), is similarly confusing in its application to explosives. The scope of NFPA 780-2004 states in paragraph 1.1.2(1) that the document does not cover lightning protection system installation requirements for explosives manufacturing buildings and magazines. However, in an explanatory note, the reason given for the exclusion is that these structures need special consideration because the contents of the structures are sensitive to arc or spark ignition. The note goes on to direct the reader to Appendix K of NFPA 780-2004 for guidance on protection of such structures. Based on this, it appears that NFPA made a determination to add guidance for lightning protection for explosives facilities after 1968 and those guidelines were placed in an Appendix K to NFPA 780-2004. It also appears that even though the scope of NFPA 780-2004 excludes explosives facilities, the standard does contain requirements for lightning protection at explosives facilities in its Appendix K. </P>
                    <P>Therefore, proposed paragraph (d)(2)(ii)(N) specifically indicates that Appendix K of NFPA 780-2004 or other equally protective criteria can be used for guidance on installing a lightning protection system. OSHA believes this will clarify the applicability of NFPA 780-2004. However, the systems identified in NFPA 780-2004 Appendix K are not the only systems that can be used. They are identified for purposes of providing guidance to employers on possible systems that meet the requirements of the proposed standard and employers are free to employ any protective systems that would afford equivalent protection. </P>
                    <P>OSHA did not change the requirement that lightning protection be provided only in areas where lightning storms are prevalent and did not change the applicability to storage of ammonium nitrate. To make the proposed lightning protection requirement easier to understand and comply with, OSHA considered revising the language to eliminate the restriction to “areas where lightning storms are prevalent.” In addition, OSHA considered expanding the requirement's application to all facilities containing explosives. This would mean that any existing facility without a lightning protection system would need to be retrofitted with a system. </P>
                    <P>These changes have not been included in this proposed rule because OSHA believes that additional information is needed in order to fully evaluate the potential impact of such changes on affected facilities. The Agency is seeking specific comments as described below. </P>
                    <P>
                        <E T="03">Issue #9:</E>
                         Should OSHA require lightning protection systems for any facility that contains ammonium nitrate or explosives? What would these systems cost? What would it cost to install lightning protection systems at facilities that currently do not have them? Is the meaning of the words “in areas where lightning storms are prevalent” in proposed paragraph (d)(2)(ii)(N) clear? If not, is there any language OSHA should consider using to clarify the meaning of the proposed provision? Should OSHA require lightning protection systems in all areas since lightning storms can occur anywhere? Is it appropriate for OSHA to refer in proposed paragraph (d)(2)(ii)(N) to NFPA 780-2004 Appendix K for recommended methods of compliance for buildings storing ammonium nitrate? 
                        <PRTPAGE P="18809"/>
                    </P>
                    <P>Proposed paragraph (d)(3) addresses the storage of ammonium nitrate in bags and containers and is similar to existing paragraph (i)(3). In proposed paragraph (d)(3), OSHA uses the term “containers” to mean any container used for the storage of ammonium nitrate (including drums). Although existing paragraph (i)(3) includes the term “drums,” the term is not used in any of the requirements that follow existing paragraph (i)(3). OSHA believes this could lead to confusion and has proposed, for clarity purposes, that drums be treated the same as other containers used to store ammonium nitrate. OSHA believes this is the intent of both existing paragraph (i)(3) and Chapter 5 of the 2002 edition of NFPA 490. </P>
                    <P>Paragraph (d)(3)(i)(A) would require the employer to ensure that bags and containers used for ammonium nitrate storage are constructed in accordance with DOT regulations (49 CFR chapter I). Paragraph (d)(3)(i)(B) would require the employer to ensure that bags and containers used for ammonium nitrate storage are labeled in accordance with DOT regulations (49 CFR chapter I) or § 1910.1200 regulations, as applicable. The proposed requirements in (d)(3)(i) (A) and (B) are similar to and replace existing paragraph (i)(3)(i)(a) except that they have been re-written in clearer language using the terms and references consistent with those used throughout this proposed rule. They are also consistent with paragraph 5.1 of the 2002 edition of NFPA 490 (Ex. 2-6). In addition, for ease of compliance, the proposed requirements were revised into two separate subparagraphs, one covering the construction of the bags and containers used for ammonium nitrate storage and the other for the labeling of the bags and containers. This clarifies that the referenced DOT regulations include both construction and labeling criteria and, to be consistent with proposed paragraph (c)(5)(i), the labeling requirements in proposed paragraph (d)(3)(i)(B) include compliance with § 1910.1200, as applicable. </P>
                    <P>Proposed paragraphs (d)(3)(i)(A) and (d)(3)(i)(B) are not intended to cover bags or containers used for the temporary holding of ammonium nitrate during the manufacture of explosives. If a bag or container is used to temporarily hold ammonium nitrate during the manufacturing of explosives, it is not considered storage. Since the temporary holding of material during the manufacturing process is not considered storage, OSHA is proposing not to retain existing paragraph (i)(3)(i)(b) which excludes containers used in the actual manufacturing of explosives from compliance with existing paragraph (i)(3)(i)(a). </P>
                    <P>Paragraph (d)(3)(ii) would require the employer to ensure that bags and containers of ammonium nitrate are not placed into storage when the temperature of the ammonium nitrate exceeds 130 °F. This proposed requirement is essentially the same as and replaces existing paragraph (i)(3)(ii)(a) except that it has been rewritten in clearer language using terms consistent with the proposed rule. In addition, unlike the existing requirement that only applies to containers, the proposed requirement applies to both bags and containers since they are treated the same in the proposed standard. Proposed paragraph (d)(3)(ii) is also consistent with paragraph 5.2.1 of the 2002 edition of NFPA 490 (Ex. 2-6). </P>
                    <P>Paragraph (d)(3)(iii) would require the employer to ensure that bags and containers of ammonium nitrate are not stored within 30 inches of storage building walls and partitions. This proposed requirement is the same as and replaces existing paragraph (i)(3)(ii)(b) except that it also includes containers to be consistent with other requirements in proposed paragraph (d)(3). Proposed paragraph (d)(3)(iii) is also slightly different than paragraph 5.2.2 of the 2002 edition of NFPA 490 (Ex. 2-6) which only addresses bags. However, as stated earlier, OSHA is treating bags and containers in the same way in this proposed standard. </P>
                    <P>Paragraph (d)(3)(iv) would require the employer to ensure that stacks of bags or containers of ammonium nitrate do not exceed 20 feet in height or 20 feet in width. Proposed paragraph (d)(3)(v) would require the employer to ensure that stacks of bags or containers of ammonium nitrate are limited to 50 feet in length unless located in a building of non-combustible construction or protected by an automatic sprinkler system. Proposed paragraph (d)(3)(vi) would require the employer to ensure that bags or containers of ammonium nitrate are not stacked within 36 inches of the roof or overhead supporting structure of the storage building. These three requirements are the same as and replace those in existing paragraph (i)(3)(ii)(c) except that the proposed requirements use the terms “stacks of bags or containers” whereas existing paragraph (i)(3)(ii)(c) uses the term “piles.” Proposed paragraphs (d)(3)(iv), (v), and (vi) are also consistent with paragraphs 5.2.3 and 5.2.4 of the 2002 edition of NFPA 490 (Ex. 2-6). </P>
                    <P>Paragraph (d)(3)(vii) would require the employer to ensure that aisles at least 3-feet wide are provided to separate stacks of bags or containers of ammonium nitrate and paragraph (d)(3)(viii) would require the employer to ensure that at least one main aisle separating stacks of bags or containers of ammonium nitrate in the storage area is at least 4-feet wide. The purpose of this wider aisle requirement is to facilitate egress in case of an emergency. These proposed requirements are the same as and replace the requirements in existing paragraph (i)(3)(ii)(d) except that they have been rewritten in clearer language. In addition, the term “piles” in existing paragraph (i)(3)(ii)(d) has been replaced in proposed paragraph (d)(3)(vii) and (viii) with the phrase “stacks of bags or containers.” The proposed requirements are also consistent with those in paragraph 5.2.5 of the 2002 edition of NFPA 490 (Ex. 2-6). </P>
                    <P>Proposed paragraph (d)(4) addresses storage of bulk ammonium nitrate. Paragraph (d)(4)(i) would require the employer to ensure that bulk storage bins used to store ammonium nitrate are clean and free of materials which may contaminate the ammonium nitrate. The proposed requirement is essentially the same as and replaces existing paragraph (i)(4)(ii)(a) except that the proposed language uses the term “bulk storage bins” instead of just “bins.” OSHA believes the term “bulk storage bins” better describes the bins that are regulated. Proposed paragraph (d)(4)(i) is also consistent with paragraph 6.2.1 of the 2002 edition of NFPA 490 (Ex. 2-6). </P>
                    <P>
                        Paragraph (d)(4)(ii) would require the employer to ensure that, to avoid contamination of the ammonium nitrate, galvanized iron, copper, lead, and zinc are not used in the construction of ammonium nitrate bulk storage bins unless suitably protected against the corrosive and reactive properties of the ammonium nitrate. Proposed paragraph (d)(4)(iii) would require the employer to ensure that aluminum and wooden bulk storage bins used to store ammonium nitrate are protected against ammonium nitrate impregnation. Proposed paragraph (d)(4)(iv) would require the employer to ensure that the partitions dividing stored ammonium nitrate from other products are constructed to prevent contamination of the ammonium nitrate with these other products. All three of these proposed requirements are essentially the same as and replace the requirements in existing paragraph (i)(4)(ii)(b). They are also consistent with paragraphs 6.2.2 and 6.2.3 of the 2002 edition of NFPA 490 (Ex. 2-6). To be consistent with the goal of specifying one requirement per paragraph, the proposal simply splits 
                        <PRTPAGE P="18810"/>
                        the requirements in existing paragraph (i)(4)(ii)(b) into three separate paragraphs. Each of the three proposed requirements has been re-written in clearer language without changing the intent of the existing requirements. 
                    </P>
                    <P>Paragraph (d)(4)(v) would require the employer to ensure that ammonium nitrate bulk storage bins or piles are clearly identified by signs reading “Ammonium Nitrate” with letters at least 2-inches high. This proposed requirement is the same as existing paragraph (i)(4)(ii)(c) except that the proposed requirement uses the term “bulk storage bins,” as discussed earlier. It is also consistent with paragraph 6.2.4 of the 2002 edition of NFPA 490 (Ex. 2-6). </P>
                    <P>Paragraph (d)(4)(vi) would require the employer to ensure that bulk ammonium nitrate in piles or in bulk storage bins is loosened or moved periodically to minimize caking. This proposed requirement is the same as and replaces existing paragraph (i)(4)(iii)(a) except that it has been rewritten in clearer, more concise language. The word “loosened” was added to provide a better description of what OSHA intends the standard to require to prevent caking. The proposed paragraph is also consistent with paragraph 6.3.1 of the 2002 edition of NFPA 490 (Ex. 2-6). </P>
                    <P>Paragraph (d)(4)(vii) would require the employer to ensure that explosives are not used to break up or loosen caked ammonium nitrate. This proposed requirement is essentially the same as and replaces existing paragraph (i)(4)(iii)(d) except that it has been rewritten in clearer language using terms consistent with those defined in this proposed standard. The proposed requirement is also consistent with paragraph 6.3.4 of the 2002 edition of NFPA 490 (Ex. 2-6). </P>
                    <P>Paragraph (d)(4)(viii) would require the employer to ensure that the top of a bulk ammonium nitrate pile is no closer than 36 inches below the roof or supporting structure of the storage building. This proposed requirement is a change from existing paragraph (i)(4)(iii)(b) and paragraph 6.3.2 of the 2002 edition of NFPA 490 (Ex. 2-6). The existing requirement states that: “Height or depth of piles shall be limited by the pressure-setting tendency of the product.” Because this sentence is more of an informative statement and is not a safety requirement, OSHA is not retaining it in proposed paragraph (d)(4)(viii). Aside from the elimination of this sentence, the proposed paragraph has been rewritten in clearer language. </P>
                    <P>Paragraph (d)(4)(ix) would require the employer to ensure that bulk ammonium nitrate is not placed into storage when its temperature exceeds 130 °F. This proposed requirement is the same as and replaces existing paragraph (i)(4)(iii)(c) except that it has been re-written to be consistent with the similar requirement for storage of bags and containers in proposed paragraph (d)(3)(ii). Proposed paragraph (d)(4)(ix) is also consistent with paragraph 6.3.3 of the 2002 edition of NFPA 490 (Ex. 2-6). </P>
                    <P>
                        Proposed paragraph (d)(5) contains requirements that address ammonium nitrate contaminants. Paragraph (d)(5)(i) would require the employer to ensure that ammonium nitrate is kept in its own building, or is separated from flammable, combustible, corrosive, explosive, or contaminating materials or processes by a wall with at least a 1-hour fire-resistant rating. The separation wall would have to extend at least to the underside of the roof. In lieu of separation walls, ammonium nitrate may be separated from these materials or processes by a space of at least 30 feet with means to prevent mixing, such as sills or curbs. This proposed requirement is a combination of requirements in existing paragraphs (i)(5)(i)(a) and (i)(5)(i)(b). For purposes of clarity and ease of compliance, OSHA proposes to replace the list of items 
                        <SU>2</SU>
                        <FTREF/>
                         in existing paragraph (i)(5)(i)(a) that ammonium nitrate should be separated from with a description of the types of materials from which ammonium nitrate should be separated. OSHA believes flammable, combustible, corrosive, explosive, or contaminating materials or processes covers all items in the list in existing paragraph (i)(5)(i)(a) and would allow for any other materials or newly developed materials to be covered where the existing list might not include them due to its more restrictive scope. OSHA is concerned that a hazardous material not contained in the existing list could be misconstrued as being safe to store with ammonium nitrate. Also the alternate means to prevent mixing of materials (a 30-foot or more separation) contained in existing paragraph (i)(5)(i)(b) was included in proposed paragraph (d)(5)(i) to make the requirement self-contained for ease of compliance. The addition of a means to prevent mixing by use of sills or curbs was added to proposed paragraph (d)(5)(i) to be consistent with paragraph 7.1.3 of the 2002 edition of NFPA 490 (Ex. 2-6). 
                    </P>
                    <FTNT>
                        <P>
                            <SU>2</SU>
                             Existing paragraph 1910.109(i)(5)(i)(a) states that: “Ammonium nitrate shall be in a separate building or shall be separated by approved type firewalls of not less than 1 hour fire-resistance rating from storage of organic chemicals, acids, or other corrosive materials, materials that may require blasting during processing or handling, compressed flammable gases, flammable and combustible materials or other contaminating substances, including but not limited to animal fats, baled cotton, baled rags, baled scrap paper, bleaching powder, burlap or cotton bags, caustic soda, coal, coke, charcoal, cork, camphor, excelsior, fibers of any kind, fish oils, fish meal, foam rubber, hay, lubricating oil, linseed oil, or other oxidizable or drying oils, naphthalene, oakum, oiled clothing, oiled paper, oiled textiles, paint, straw, sawdust, wood shavings, or vegetable oils. Walls referred to in this subdivision need extend only to the underside of the roof.” 
                        </P>
                    </FTNT>
                    <P>Paragraph (d)(5)(ii) would require the employer to ensure that flammable liquids are not placed or stored in buildings used for the storage of ammonium nitrate except where permitted by § 1910.106 and proposed paragraph (d)(5)(i) of § 1910.109. Section 1910.106 contains OSHA's general requirements for flammable and combustible liquids. Proposed paragraph (d)(5)(ii) is essentially the same as and replaces existing paragraph (i)(5)(i)(c) except that it has been rewritten in clearer language with redundancies and extraneous words removed. The proposed paragraph is also consistent with paragraph 7.1.4 of the 2002 edition of NFPA 490 (Ex. 2-6). In addition, proposed paragraph (d)(5)(ii) applies to the placement as well as the storage of flammable liquids in buildings used to store ammonium nitrate. OSHA is convinced that even short term placement of flammable liquids in such buildings can be hazardous unless adequate precautions are taken. </P>
                    <P>Paragraph (d)(5)(iii) would require the employer to ensure that no liquefied petroleum gas is placed or stored in a building used to store ammonium nitrate except in accordance with § 1910.110. Section 1910.110 contains OSHA's general requirements for storage and handling of liquefied petroleum gases. The proposed requirement is essentially the same as and replaces existing paragraph (i)(5)(i)(d). Proposed paragraph (d)(5)(iii) is also consistent with paragraph 7.1.5 of the 2002 edition of NFPA 490 (Ex. 2-6). </P>
                    <P>Paragraph (d)(5)(iv) would require the employer to ensure that sulfur and finely divided metals are not stored in the same building with ammonium nitrate. This proposed requirement is the same as and replaces existing paragraph (i)(5)(ii)(a) except that it has been rewritten in clearer language. Sulfur and finely divided metals can create a fire hazard and should be kept in a separate building from the ammonium nitrate building. The proposed paragraph is also consistent with paragraph 7.2.1 of the 2002 edition of NFPA 490 (Ex. 2-6). </P>
                    <P>
                        OSHA is not retaining paragraphs (i)(5)(ii)(b) through (i)(5)(ii)(d) in the 
                        <PRTPAGE P="18811"/>
                        existing standard because they focus on the storage of explosives (including blasting agents) rather than the storage of ammonium nitrate. As discussed earlier, the storage of explosives (including blasting agents) is covered by ATF regulations. 
                    </P>
                    <P>The final topic addressing the storage of ammonium nitrate deals with fire protection. Proposed paragraph (d)(6)(i) would require the employer to ensure that buildings in which greater than 2500 tons of ammonium nitrate is stored are equipped with an automatic sprinkler system that complies with § 1910.159. The proposed requirement is similar to and replaces existing paragraph (i)(7)(i). It is also consistent with paragraph 9.1.1 of the 2002 edition of NFPA 490 (Ex. 2-6). </P>
                    <P>
                        <E T="03">Issue #10:</E>
                         OSHA requests comments on the issue of automatic sprinkler systems for the storage of ammonium nitrate. In terms of employee safety, is it appropriate to only require an automatic sprinkler system for the storage of ammonium nitrate in quantities exceeding 2,500 tons? Should the storage of ammonium nitrate in quantities less than 2,500 tons, e.g. 1,000 tons, require an automatic sprinkler system? Should the storage of ammonium nitrate, regardless of quantity, always require an automatic sprinkler system? Alternatively, should OSHA consider eliminating the requirement for automatic sprinkler systems for ammonium nitrate storage? What evidence would support the elimination of this requirement? 
                    </P>
                    <P>Paragraph (d)(6)(ii) would require the employer to ensure that all fire protection equipment and systems in ammonium nitrate storage buildings meet the requirements of Subpart L, Fire Protection, of this part. This proposed requirement replaces existing paragraphs (i)(7)(ii)(a) and (i)(7)(ii)(b) and requires the use of the more updated and specific OSHA regulations for fire protection equipment and systems contained in subpart L. </P>
                    <P>
                        <E T="03">Paragraph (e) Transportation of explosives.</E>
                         As discussed earlier in the Authority to Regulate section of the preamble, OSHA has authority to regulate working conditions during the transportation of explosives. Unless otherwise specified, all the requirements in proposed paragraph (e) apply to the transportation of explosives both within and outside private facilities and worksites. 
                    </P>
                    <P>Proposed paragraph (e)(1) addresses general provisions associated with the transportation of explosives. Proposed paragraph (e)(1)(i) would require the employer to ensure that no employee smokes, carries matches or any other flame-producing device, or carries any firearms or cartridges (except firearms and cartridges required to be carried by guards) while in, or within 25 feet (7.63m) of, a vehicle containing explosives. This proposed requirement replaces a comparable requirement in existing paragraph (d)(1)(i) except this proposed paragraph includes an exception for firearms and cartridges required to be carried by guards. It is also consistent with paragraph 7.1.4 of the 2001 edition of NFPA 495 (Ex. 2-5). </P>
                    <P>
                        Existing paragraph (d)(1)(i) states that: “No employee shall be allowed to smoke, carry matches or any other flame-producing device, or carry any firearms or loaded cartridges while in or 
                        <E T="03">near</E>
                         a motor vehicle transporting explosives” (emphasis added). To eliminate confusion over the meaning of the term “near” as used in existing paragraph (d)(1)(i), OSHA specifies in proposed paragraph (e)(1)(i) that such items and activities must remain at least 25 feet away from the vehicle. The proposed 25-foot requirement is also consistent with the Federal Motor Carrier Safety Administration requirements in 49 CFR 397.13. 
                    </P>
                    <P>Proposed paragraph (e)(1)(i), along with many others in this proposed transportation paragraph, uses the term “vehicle.” As discussed in the definitions section of this preamble, OSHA has defined the term “vehicle” in this proposal, as described in the preamble above when discussing definitions. The reason for defining and using the term “vehicle” is to eliminate any confusion created in the existing standard which uses several different terms, such as a motor vehicle, semitrailer, truck, and van, to describe a vehicle. </P>
                    <P>Paragraph (e)(1)(ii) would require the employer to ensure that no employee drives, loads, or unloads a vehicle containing explosives in an unsafe manner. This proposed requirement is essentially the same as and replaces a requirement in existing paragraph (d)(1)(i) except that it has been re-written in clearer language. It is also consistent with paragraph 7.1.5 of the 2001 edition of NFPA 495 (Ex. 2-5). To achieve the goal of specifying one requirement per paragraph, OSHA has split the requirements in existing paragraph (d)(1)(i) into two separate proposed paragraphs (e)(1)(i) and (e)(1)(ii). </P>
                    <P>Paragraph (e)(1)(iii) would require the employer to ensure that explosives are not transferred from one vehicle to another without informing local fire and police departments. This will help to ensure that the transfer is performed in a safe manner. In addition, a competent person must supervise the transfer of explosives. This is applicable to all transfer work whether it is done within private facilities or on public highways. A competent person is defined in proposed paragraph (b) as an employee designated by the employer who, by way of training and/or experience, is knowledgeable about applicable standards, is capable of identifying workplace hazards relating to explosives, and has authority to take appropriate corrective actions to control such hazards. Proposed paragraph (e)(1)(iii) would also require the employer to ensure that in the event of breakdown or collision, the local fire and police departments are promptly notified. Informing such local authorities will help to ensure that the breakdown or collision is handled in a safe manner. Proposed paragraph (e)(1)(iii) differs from existing paragraph (d)(1)(iii), but is compatible with paragraph 7.1.7 of the 2001 edition of NFPA 495 (Ex. 2-5). The existing requirement only requires a competent person when the transfer involves a disabled vehicle, whereas the proposal would require the supervision of a competent person whenever a transfer of explosives occurs between two vehicles, whether or not the transfer is caused by the breakdown of one of the vehicles. OSHA recognizes the risks involved in the transfer of explosives and proposes to ensure that this activity is always done under the supervision of a competent person as defined in paragraph (b). </P>
                    <P>Paragraph (e)(1)(iv) would require the employer to ensure that no repair work, other than emergency repairs that do not present a source of ignition, is performed on a vehicle containing explosives. This is a new requirement based on a recommendation in the Petition (Ex. 2-1). OSHA agrees with the Petition that there are risks involved in making vehicle repairs near explosives since certain repair work could be a source of ignition for the explosives in the vehicle. As a result, OSHA is only permitting such repair work in emergency situations when the work can be performed safely. The proposed paragraph is consistent with requirements in proposed paragraph (c)(4) discussed above. </P>
                    <P>
                        Paragraph (e)(1)(v) would require the employer to ensure that detonators are not transported with other explosives in the same vehicle, unless packaged, segregated, and transported in accordance with the regulations of DOT (49 CFR chapter I) (Ex. 2-8). This proposed requirement replaces existing paragraph (d)(1)(iv) except that, instead of using the terms “blasting caps” and 
                        <PRTPAGE P="18812"/>
                        “electric blasting caps” as in the existing paragraph, OSHA is proposing to use the term “detonators” (which includes blasting caps and electric blasting caps) to be consistent with the industry use of this term. The proposed paragraph is also consistent with paragraph 7.1.8 of the 2001 edition of NFPA 495 (Ex. 2-5). 
                    </P>
                    <P>Paragraph (e)(1)(vi) would require the employer to ensure that when explosives are transported on a railway car utilizing private railroad tracks, the car, its contents, and method of loading are in accordance with the regulations of DOT (49 CFR chapter I) (Ex. 2-8). This proposed requirement replaces existing paragraph (f)(1). While DOT regulations cover railway cars on public railroad tracks, the proposed requirement covers such cars on private railroad tracks. OSHA's intent here is to ensure that employees are provided the same level of safety when the railway car is on private tracks as compared to public railway tracks. The proposed language is also consistent with paragraph 11.1.1 of the 2001 edition of NFPA 495 (Ex. 2-5). </P>
                    <P>Paragraph (e)(1)(vii) would require the employer to ensure that explosives at a railway facility, truck terminal, pier, harbor facility, or airport terminal, whether for delivery to a consignee or forwarded to some other destination, are kept in a manner that minimizes risk to employees. This proposed requirement is changed somewhat from existing paragraph (f)(4) and paragraph 11.1.4 of the 2001 edition of NFPA 495 (Ex. 2-5). Compared to the existing requirement and the NFPA standard, the proposed paragraph places more emphasis on employee safety to ensure that risk to employees is minimized. </P>
                    <P>Paragraph (e)(1)(viii) would require the driver or other employee attending the vehicle be knowledgeable about the nature and hazards of the explosives contained in the vehicle and the procedures for handling emergency situations. This proposed requirement replaces a requirement in existing paragraph (d)(3)(iii) except that it has been updated and rewritten in clearer and more concise language. OSHA has eliminated the language in existing paragraph (d)(3)(iii) that refers to public safety because such issues are outside of OSHA's authority to regulate. </P>
                    <P>Proposed paragraph (e)(2) addresses vehicles used in the transportation of explosives. Paragraphs (e)(2)(i)(A) through (C) would require the employer to ensure that any vehicle used to carry explosives is able to safely carry the designated load, has close-fitting floors, and has wood or other non-sparking materials covering any exposed spark-producing metal on the inside of the vehicle body. Proposed paragraph (e)(2)(i) rewrites and simplifies the requirements in existing paragraph (d)(2)(i), putting the revised requirements into three separate proposed paragraphs, (e)(2)(i)(A) through (C). The proposed requirements are also consistent with paragraphs 7.2.1, 7.2.3, and 7.2.4 of the 2001 edition of NFPA 495 (Ex. 2-5). </P>
                    <P>
                        <E T="03">Issue #11:</E>
                         Existing paragraph (d)(2)(i) and proposed paragraph (e)(2)(i)(C) require the employer to ensure that any vehicle used to carry explosives has wood or other non-sparking materials covering any exposed spark-producing metal on the inside of the vehicle body. This is not consistent with paragraph 8.2.3 of the 2006 edition of NFPA 495 (Ex. 2-21) which requires: “Vehicles used for transporting frictional spark-sensitive explosive materials such as Black Powder and primary explosives shall have no exposed spark-producing surface inside of the cargo body.” Should the requirements in proposed paragraph (e)(2)(i)(C) only apply to frictional spark-sensitive explosives? Would such a limitation in proposed paragraph (e)(2)(i)(C) reduce the cost of transporting non-frictional spark-sensitive explosives? 
                    </P>
                    <P>Paragraph (e)(2)(ii) would require the employer to ensure that any vehicle containing explosives or oxidizers located at a private facility or blast site has exterior markings or placards designed and displayed in accordance with the regulations of DOT (49 CFR chapter I) (Ex. 2-8). This proposed requirement is a change from and replaces existing paragraph (d)(2)(ii)(a) which contains a table of required OSHA markings and placards. Since DOT already addresses vehicle markings and placards, and compliance with DOT regulations during the transportation of explosives outside of private facilities is required throughout the explosives industry, OSHA proposes to adopt DOT regulations and apply them to vehicles containing explosives or oxidizers in private facilities rather than continue to require a separate set of placards and markings. OSHA believes this proposed language will make it easier for employers to comply with placarding and marking requirements and will increase safety by eliminating any possible confusion created by different OSHA and DOT requirements for the similar activities. Since DOT placarding and marking regulations already cover transportation outside of private facilities, this proposed paragraph applies the same requirements to vehicles on private facilities. </P>
                    <P>Because OSHA proposes to reference DOT regulations for placarding and marking of vehicles, the placarding and marking requirements in existing paragraphs (d)(2)(ii)(c), (d), and (e) are no longer necessary and are not included in the proposed standard. </P>
                    <P>Proposed paragraph (e)(2)(iii) addresses open-bodied vehicles. Proposed paragraph (e)(3)(iii)(A) would require the employer to ensure that any explosives on an open-bodied vehicle are protected with a flameproof and moisture-proof tarpaulin or other effective means of protection from fire, sparks, and moisture. This proposed requirement is essentially the same as and replaces a requirement in existing paragraph (d)(2)(i) except that it has been re-written in clearer language and the proposed paragraph includes protection from fire as well as sparks and moisture. A similar requirement was contained in paragraph 421 of the 1970 version of NFPA 495 (Ex. 2-13). It is not, however, in the current 2001 edition of NFPA 495. While OSHA is not sure why this requirement was eliminated from the 2001 edition, it believes that this type of protection is still important for employee protection and proposes to retain this requirement in the proposed standard. </P>
                    <P>Paragraph (e)(2)(iii)(B) would require the employer to ensure that the explosives in open-bodied vehicles are not loaded above the sides of the vehicle. This proposed requirement is the same as and replaces a requirement in existing paragraph (d)(2)(i). This requirement was also in paragraph 421 of the 1970 version of NFPA 495 (Ex. 2-13) but is not in the 2001 edition. However, OSHA believes this to be an important requirement for employee protection and is proposing to retain it in this proposed standard. As discussed earlier, existing paragraph (d)(2)(i) is a very long requirement containing many separate requirements. To encourage better understanding, OSHA is proposing to split existing paragraph (d)(2)(i) into several paragraphs, each containing an individual requirement. </P>
                    <P>
                        Proposed paragraph (e)(2)(iv) addresses the necessity for fire extinguishers in vehicles used to carry explosives. Paragraph (e)(2)(iv)(A) would require the employer to ensure that each vehicle used to carry explosives is equipped with at least two fire extinguishers filled and in good working order, each having a rating of at least 4-A:40-B:C. This proposed requirement is essentially the same as existing paragraph (d)(2)(iii) except that the required fire extinguishers have been upgraded to meet the standards in paragraph 8.2.6 of the 2006 edition of 
                        <PRTPAGE P="18813"/>
                        NFPA 495 (Ex. 2-21). In addition, the changes in the proposed requirement were recommended by the Petition (Ex. 2-1). 
                    </P>
                    <P>Paragraph (e)(2)(iv)(B) would require the employer to ensure that each vehicle used to carry explosives has one fire extinguisher located in close proximity to the driver's seat. This proposed requirement is derived from existing paragraph (d)(2)(iii)(b) and paragraph 7.2.6 of the 2001 edition of NFPA 495 (Ex. 2-5). The extinguisher filling and examination requirements contained in existing paragraph (d)(2)(iii)(b) are addressed in proposed paragraph (e)(2)(v)(A), as discussed below. The multiple requirements contained in existing paragraph (d)(2)(iii)(b) have been split up in the proposed standard. OSHA believes this will make the proposed requirements easier to comply with and more understandable. In addition, the proposed requirement substitutes the term “in close proximity” for “near” which is used in the existing standard to describe the required location of the extinguisher in relation to the driver's seat. OSHA believes “in close proximity” is a more definitive term than “near” the driver's seat and is intended to convey the requirement that the vehicle driver have quick access to a fire extinguisher in the event of an emergency. </P>
                    <P>Paragraph (e)(2)(iv)(C) would require the employer to ensure that each vehicle used to carry explosives is equipped only with fire extinguishers listed or approved by a nationally recognized testing laboratory. The proposed requirement also refers to § 1910.155(c)(3)(iv)(A) for a definition of listed fire extinguishers and § 1910.7 for nationally recognized testing laboratories. This proposed requirement is essentially the same as and replaces existing paragraph (d)(2)(iii)(a). It is also consistent with paragraph 7.2.6.1 of the 2001 edition of NFPA 495 (Ex. 2-5). </P>
                    <P>Proposed paragraph (e)(2)(v) contains additional requirements for vehicles used for carrying explosives. Paragraph (e)(2)(v)(A) would require the employer to ensure that the fire extinguishers required in proposed paragraph (e)(2)(iv)(C) above are used, maintained, and tested in accordance with § 1910.157. This proposed requirement is changed from existing paragraph (d)(2)(iv)(a) in that the existing provision simply requires that extinguishers be filled and in working order without specifying how this should be done. Since OSHA has standards for portable fire extinguishers in § 1910.157, the Agency wants to emphasize in the proposed requirement that portable fire extinguishers in vehicles used for carrying explosives must comply with § 1910.157 requirements in addition to the requirements in this proposed standard. </P>
                    <P>Paragraph (e)(2)(v)(B) would require the employer to ensure that the use of fire extinguishers is restricted to fighting non-explosive fires involving tires, batteries, engines, cabs, etc., where the fire is not in imminent danger of reaching the explosive cargo. OSHA believes it is important to clarify that the fire extinguishers should not be used to fight explosives fires or fires that have the potential to rapidly reach the explosives. Portable extinguishers are not effective enough to sufficiently protect the safety of employees fighting such dangerous fires. The proposed language was recommended by the Petition (Ex. 2-1). This is a new requirement which is consistent with proposed paragraph (c)(3)(ii)(A) which requires employers to ensure that employees do not fight fires if they are in imminent danger of contact with explosives. </P>
                    <P>Paragraph (e)(2)(v)(C) would require the employer to ensure that the explosive cargo cannot shift, spill, or become damaged during transit. This is a new requirement based on a recommendation in the Petition (Ex. 2-1). OSHA believes that spillage and damage to containers can create a potential explosion hazard and should be eliminated. This requirement would simply require that the explosive cargo be secured to ensure that no spillage or damage occurs to the containers. </P>
                    <P>Paragraph (e)(2)(vi) would require the employer to ensure that any vehicle containing explosives is maintained in good and safe working condition. This is a change from existing paragraph (d)(2)(iv) which contains a detailed list of items to be inspected on the vehicle and paragraph 7.2.7 of the 2001 edition of NFPA 495 (Ex. 2-5) which contains the same list of inspection items. OSHA is adopting a more performance oriented approach and is proposing to simplify and replace the existing detailed, but not necessarily all inclusive, requirements by requiring the employer to ensure that the vehicle is in proper working order. OSHA does not want to limit the inspection to a specific set of items to ensure the vehicle is in safe working condition. Some common items that should be checked during an inspection include but are not limited to fire extinguishers; electrical wiring; fuel tank and feedline; brakes; lights; horn; windshield wipers; steering apparatus; and tires. While the proposal does not require an inspection prior to each use of the vehicle, it does require the employer to ensure that the vehicle is kept properly maintained at all times. </P>
                    <P>Proposed paragraph (e)(3) addresses the operation of vehicles containing explosives. Paragraph (e)(3)(i)(A) would require the employer to ensure that only employees designated by the employer are permitted to ride in or drive a vehicle containing explosives. This is a new requirement proposed by the Petition (Ex. 2-1). OSHA agrees that it is important to workplace safety that only employees given permission to do so by the employer should operate or ride in vehicles containing explosives. Paragraph (e)(3)(i)(B) would require the employer to ensure that vehicles containing explosives are only driven by and are in the charge of a driver who is familiar with relevant traffic regulations and the provisions of this section, and possesses a valid driver's license appropriate for the vehicle being driven. This proposed requirement is similar to and replaces existing paragraphs (d)(3)(i) and (g)(6)(ii) which address general explosive transportation and specific transportation for blasting agents, respectively. Since blasting agents are defined as explosives in this proposed standard, OSHA is combining these two existing requirements into one general proposed requirement for driving a vehicle containing explosives. OSHA believes the proposed language is a simpler, more concise way to describe the responsibilities of the driver. </P>
                    <P>
                        <E T="03">Issue #12:</E>
                         OSHA requests comments on the appropriateness of proposed paragraph (e)(3)(i)(B) for the on-site transportation of explosives at private facilities. The proposal would require that employees have a valid driver's license appropriate for the vehicle being driven. In certain situations, employees who transport explosives or blasting agents on the employer's premises may be required to obtain a commercial driver's license (CDL) and hazardous materials endorsement. Even drivers whose activities are limited to tasks such as moving a loaded vehicle from the loading dock to an onsite transportation staging area, or backing a vehicle up to a loading dock would need a valid driver's license appropriate for the vehicle being driven and, depending on the vehicle type, that may require a CDL. OSHA is seeking specific comments on whether it is appropriate for safety reasons to require a valid driver's license for on-site transportation. 
                    </P>
                    <P>
                        Paragraph (e)(3)(i)(C) would require the employer to ensure that, except under emergency conditions, no vehicle containing explosives is parked before reaching its destination on any public street adjacent to or in close proximity 
                        <PRTPAGE P="18814"/>
                        to any place of employment. The proposed requirement is similar to existing paragraph (d)(3)(ii). It is also consistent with paragraph 7.3.3 of the 2001 edition of NFPA 495 (Ex. 2-5). 
                    </P>
                    <P>Paragraph (e)(3)(i)(D) would require the employer to ensure that no spark-producing metal, spark-producing tools, oils, matches, firearms, electric storage batteries, flammable substances, acids, oxidizers, or corrosive compounds are carried in the body of any vehicle containing explosives, unless the carrying of such dangerous articles and the explosives comply with DOT regulations (49 CFR chapter I) (Ex. 2-8). The body of the vehicle is intended to mean the cargo-carrying body that contains the explosives and not the cab portion or engine compartment of the vehicle. The proposed requirement is a combination of existing paragraphs (d)(3)(iv) and (g)(6)(iii), which address general explosives transportation and specific transportation for blasting agents, respectively. Since blasting agents are defined as explosives in the proposed rule, OSHA is combining these two existing requirements into one general proposed requirement for driving a vehicle containing explosives. </P>
                    <P>Paragraph (e)(3)(i)(E) would require the employer to ensure that deliveries of explosives are only received by employees authorized by the employer to receive such explosives. This proposed requirement is based on existing paragraph (d)(3)(vi) which addresses both the delivery of explosives and the storage of the delivered explosives. The proposed paragraph is also consistent with paragraph 7.3.8 of the 2001 edition of NFPA 495 (Ex. 2-5). Because the storage of delivered explosives is already covered by ATF's regulations at 27 CFR part 555, the proposed paragraph (e)(3)(i)(E) only covers the delivery of explosives to authorized employees. </P>
                    <P>Paragraph (e)(3)(ii) would require the employer to ensure that every vehicle containing Division 1.1, 1.2, or 1.3 explosives at the employer's worksite or facility is attended at all times by the driver or other responsible person authorized by the employer. This proposed requirement is similar to a requirement contained in existing paragraph (d)(3)(iii) except that it has been rewritten in clearer language and revised to be consistent with the proposed explosives classification system discussed earlier. The proposed paragraph is also consistent with paragraph 7.3.4 of the 2001 edition of NFPA 495 (Ex. 2-5) except that the proposed paragraph only applies to vehicles at an employer's worksite or facility. The term “transporting” in existing paragraph (d)(3)(iii) has been replaced with the term “containing” in the proposed paragraph to clarify that the provision applies to stationary as well as moving vehicles. OSHA is restricting proposed paragraph (e)(3)(ii) to employers' worksites and facilities because DOT already has attendant requirements for vehicles containing explosives on public highways at 49 CFR 397.5. </P>
                    <P>Proposed paragraph (e)(3)(ii)(A) clarifies that the vehicle containing explosives is considered “attended” only when the driver or another responsible person authorized by the employer is physically on or in the vehicle, or can see and reach the vehicle quickly without any interference. In addition, this proposed paragraph states that “attended” also means that the driver or other responsible authorized person is awake, alert, and not engaged in other duties or activities which may divert his or her attention from the vehicle. If the driver needs to leave the vehicle to obtain food or drink or to use a restroom, a second authorized responsible employee should remain with the vehicle. Proposed paragraph (e)(3)(ii)(A) replaces existing paragraph (d)(3)(iii)(a) except that the exception in the existing paragraph for communication or to obtain food or physical comfort has not been retained in the proposed paragraph. The Agency believes that vehicles containing explosives should not be left unattended for any period of time. Any exception to this would directly conflict with the requirements in proposed paragraph (e)(3)(ii), discussed above, which requires that vehicles be attended at all times. Proposed paragraph (e)(3)(ii)(A) is similar to paragraph 7.3.5 of the 2001 edition of NFPA 495 (Ex. 2-5) but the NFPA standard has an exception for communication and to obtain food or physical comfort. </P>
                    <P>Paragraph (e)(3)(ii)(B) would require the driver or other employee attending the vehicle to be authorized, capable, and have the necessary means to safely drive the assigned vehicle. This proposed requirement replaces a requirement in existing paragraph (d)(3)(iii) except that it has been rewritten in clearer and more concise language. </P>
                    <P>Two requirements in existing paragraph (d)(3) covering the transportation of explosives have not been retained in the proposed standard. Existing paragraph (d)(3)(iii)(b) allows the unattended parking of a vehicle containing Class A or B explosives if it is parked within a securely fenced or walled area with all gates or entrances locked or if it is at a magazine site established solely for the purpose of storing explosives. OSHA has not included these requirements in the proposed standard because similar provisions are already required by the Federal Motor Carrier Safety regulations at 49 CFR 397.5. OSHA does not want to unnecessarily duplicate the regulations of other federal agencies. </P>
                    <P>Existing paragraph (d)(3)(v) requires that vehicles transporting explosives avoid congested areas and heavy traffic. Since equivalent requirements are already contained in the Federal Motor Carrier Safety Administration regulations at 49 CFR 397.67, OSHA is not retaining this requirement in the proposed rule to avoid duplicating the requirements of other Federal agencies. </P>
                    <P>
                        <E T="03">Paragraph (f) Use of explosives for blasting.</E>
                         Proposed paragraph (f) addresses the use of explosives for blasting. Most explosives in the United States are used for blasting purposes in the construction and mining industries. These blasting operations are not covered by § 1910.109 but are covered by OSHA's construction regulations (29 CFR part 1926 subpart U) and MSHA's blasting regulations (30 CFR part 56 subpart E, 30 CFR part 57 subpart E, 30 CFR part 75 subpart N, and 30 CFR part 77 subpart N). However, § 1910.109 does cover the use of explosives by general industry. These general industry uses, when not part of construction or mining activities, include the blasting of rocks, slag pockets, and beaver dams, as well as blasting associated with metal hardening, stump removal, pond creation, and avalanche control, and various types of blasting used to create art sculptures. Compared to the use of explosives by the mining and construction industries, these general industry uses do not require large amounts of explosives and are performed relatively infrequently. 
                    </P>
                    <P>
                        Paragraph (f)(1) of the proposed standard sets out the general requirements for blasting. Proposed paragraphs (f)(1)(i)(A) through (f)(1)(i)(E) are new requirements that prescribe the duties and responsibilities of the blaster-in-charge to ensure the blast site and blast area are safe at all times. Paragraph (f)(1)(i)(A) would require the employer to ensure that the blaster-in-charge is trained, knowledgeable, and experienced in the storage, transportation, handling, and use of explosives. This new requirement is intended to ensure that the blaster-in-charge has the necessary training and experience in all relevant aspects of explosives. Throughout this proposed paragraph, the blaster-in-charge is given the authority by the employer to control the blast site and the blast area. In 
                        <PRTPAGE P="18815"/>
                        addition to training and experience, proposed paragraph (f)(1)(i)(B) requires the employer to ensure that the blaster-in-charge is knowledgeable about relevant federal, state, and local regulations pertaining to explosives. These include all applicable OSHA regulations and any other Federal regulations that apply, including ATF and DOT requirements. In addition, the blaster-in-charge must be aware of any state and local regulations that may impact the blast site and blast area. OSHA believes that without the prescribed training, knowledge, and experience, the blaster-in-charge will be unable to satisfactorily do his or her job and that the employer will be unable to ensure employee safety during workplace blasting operations. 
                    </P>
                    <P>Paragraph (f)(1)(i)(C) would require the employer to ensure that the blaster-in-charge is trained, knowledgeable, and experienced in the use of each type of blasting method being used. Since every blast site is unique and the methods used may vary from one blast site to another, it is important that the blaster-in-charge have the training, knowledge, and experience in the particular method to be used to ensure a safe blast site. </P>
                    <P>Paragraph (f)(1)(i)(D) would require the employer to ensure that the blaster-in-charge is in control of the blasting operations, blast site, and blast area. This new proposed requirement ensures that the blaster-in-charge has overall control of the blast site and blasting operations, including control over the employees entering the blast site, as well as all the safety and security requirements before, during, and after the blast is fired. This is a general requirement that includes all aspects of the blasting operations from setting the blast site and blast area dimensions to giving the all-clear signal after the blast has been completed. </P>
                    <P>Paragraph (f)(1)(i)(E) would require the employer to ensure that the blaster-in-charge evaluates each blast site and blast area and implements the measures that will ensure the safety of employees and the security of each blast site and blast area. This requires the blaster-in-charge to evaluate each unique blast site and blast area, using his or her knowledge, training, and experience to determine proper procedures during the set-up and firing of the blast and during the post-blast operations to ensure that the blast site and blast area are safe and secure for all employees. </P>
                    <P>Although proposed paragraphs (f)(1)(i)(A) through (E) require the employer to place significant duties on the blaster-in-charge, it is ultimately the responsibility of the employer to designate a blaster-in-charge and to ensure that he or she has the proper knowledge, training, and experience to be qualified as a blaster-in-charge and that all requirements in proposed paragraphs (f)(1)(i)(A) through (E) are met. </P>
                    <P>The requirements in proposed paragraph (f)(1)(i) were recommended by the Petition (Ex. 2-1). It recommended that only one person at the blast site should control all the activities of the site and be in charge of the safety and security of the blast site and blast area. OSHA agrees that these duties should be handled by one person, the blaster-in-charge, who is highly trained, knowledgeable, and experienced in blasting operations. Proposed paragraph (f)(1)(i) replaces existing paragraph (e)(1)(iv) with a much more complete set of responsibilities for the newly defined blaster-in-charge. OSHA believes the requirements in proposed paragraph (f)(1)(i) are clearer and more precise than the existing requirements and will allow for easier compliance with the proposed requirement. The concept of a “blaster-in-charge” is evident in existing paragraph (e) and in Chapter 9 of NFPA 495-2001 which contain descriptions of the duties of the person in charge of blasting operations. Since the term “blaster-in-charge” is commonly used in the explosives industry to describe the duties of this person, OSHA believes the use of this term is appropriate in the proposed standard. </P>
                    <P>Paragraph (f)(1)(ii)(A) would require the employer to ensure that explosives are used in accordance with manufacturers' recommendations. This is a new requirement recommended by the Petition (Ex. 2-1). OSHA agrees with the Petition that it is important for employee safety during blasting operations to follow manufacturers' recommendations and proposes to include this requirement in the proposed standard. </P>
                    <P>Paragraph (f)(1)(ii)(B) would require the employer to ensure that all employees involved in blasting operations work only under the supervision of the blaster-in-charge. This is a new requirement which OSHA believes is essential for employee safety during blasting operations. It ensures that the blaster-in-charge has the overall control of the blasting operations. </P>
                    <P>Paragraph (f)(1)(ii)(C) would require the employer to ensure that only Type 3 magazines or the original containers are used to transport detonators and other explosives from magazines to the blast site. “Original container” here means the containers in which the detonators were originally transported from the detonator manufacturer. Proposed paragraph (f)(1)(ii)(C) is similar to existing paragraph (e)(1)(ii) except that it has been modified by updating the type of magazine that can be used for the transportation of the explosives. Existing paragraph (e)(1)(ii) requires a Class II magazine whereas proposed paragraph (f)(1)(ii)(c) requires a Type 3 magazine. A Type 3 magazine, as defined by ATF at 27 CFR 555.203(c) (Ex. 2-4), is a portable outdoor magazine for the temporary storage of high explosives. To be consistent with the newer ATF magazine types, the proposed paragraph references a Type 3 magazine which is classified as a class II magazine under the existing standard. Type 3 magazines containing explosives must never be left unattended (27 CFR 555.209). A Type 3 magazine is commonly called a “day box”. </P>
                    <P>Paragraph (f)(1)(ii)(D) would require the employer to ensure that employees are protected from flying fragments produced during blasting operations by removing employees to a safe distance, using protective barricades, or utilizing other equivalent means to protect employees. This proposed requirement is loosely based on existing paragraph (e)(1)(iii) and has been modified to improve employee safety. The existing requirement addresses adjacent structure damage and, presumably, pedestrian protection in congested areas near the blasting operations. In the proposed standard, the protective measures have changed to focus on employee safety and include removal of employees to safe locations or the use of other equivalent means to protect employees. </P>
                    <P>
                        Paragraph (f)(1)(ii)(E) would require the employer to ensure that adequate precautions are taken to prevent sources of induced current, such as lightning, adjacent power lines, dust storms, snow storms, radar, radio transmitters, cellular phones, or other sources of extraneous electricity, from causing the accidental detonation of electric blasting caps. This proposed paragraph replaces a similar requirement in existing paragraph (e)(1)(vii) except that it has been revised to include snow storms and cellular phones. Both snow storms and cellular phones can generate extraneous electricity and be potential sources of accidental ignition. The addition of snow storms is consistent with the requirements in paragraph 9.1.16 of the 2001 edition of NFPA 495 (Ex. 2-5). In addition, due to the increasing use of cellular phones and their potential to be a source of ignition, OSHA proposes to add cellular phones to the list of items to be controlled. This addition was based on a 
                        <PRTPAGE P="18816"/>
                        recommendation in the Petition (Ex. 2-1). 
                    </P>
                    <P>Paragraph (f)(1)(ii)(F) would require the employer to post signs warning against the use of mobile radio transmitters or cellular phones on all roads within 350 feet of the blasting operations. This is similar to existing paragraph (e)(1)(vii)(b), except that cellular phones have been added to the proposed language. Cellular phones have been included because of their increased use and potential to be a source of ignition for electric blasting caps. Unlike existing paragraph (e)(1)(vii)(b), proposed paragraph (f)(1)(ii)(F) identifies the specific warning language to be displayed on the signs: </P>
                    <HD SOURCE="HD3">WARNING </HD>
                    <HD SOURCE="HD3">EXPLOSIVES HAZARD </HD>
                    <HD SOURCE="HD3">DO NOT USE MOBILE RADIO TRANSMITTERS OR CELLULAR PHONES</HD>
                    <P>Proposed paragraph (f)(1)(iii) deals with certain types of blasting operations. Paragraph (f)(1)(iii)(A) would require the employer to ensure that all surface blasting operations are conducted only during daylight hours. This proposed language is similar to and replaces existing paragraph (e)(1)(v), except that the existing requirement applies to “blasting operations” whereas the proposed language limits the requirement to “surface blasting operations.” The proposed language is the same as paragraph 9.1.14 of the 2001 edition of NFPA 495 (Ex. 2-5). Surface blasting operations rely on natural light whereas underground blasting operations are illuminated with artificial light. Therefore, OSHA proposes to limit (f)(1)(iii)(A) to surface blasting operations because it believes it is unnecessary for the purposes of employee safety to restrict underground blasting operations to daylight hours. </P>
                    <P>Proposed paragraph (f)(1)(iii)(B) provides a limited exception to proposed paragraph (f)(1)(iii)(A). It allows unusual blasting operations associated with industrial processes, such as blasting slag pockets and dustcatchers, to be performed at any time of the day, provided they are performed indoors and a minimum illumination density of 20 lumens per square foot is provided within a 5-foot (1.5 m) radius of locations where explosives are being assembled, placed, or attached to detonators. This is a new requirement but it is consistent with OSHA policy contained in OSHA Instruction STD 1-5.12, dated October 30, 1978 (Ex. 2-3). In that directive, OSHA identified several necessary revisions it planned to make to § 1910.109, including a revision to allow unusual blasting operations associated with industrial processes to occur at any time of day, provided proper illumination and other appropriate requirements were met. Proposed paragraph (f)(1)(iii)(B) is intended to implement the Agency's stated intention. </P>
                    <P>Paragraph (f)(1)(iv) would require that whenever blasting operations are being conducted in close proximity to gas, electric, water, telephone, or other similar utilities, the employer shall not commence such blasting operations until receiving and documenting approval from the appropriate utility representatives. This proposed paragraph replaces existing paragraph (e)(1)(vi). The existing standard only requires notification of the affected utility 24 hours in advance of blasting. It does not require a response from the utility prior to the employer beginning blasting. Thus, the employer may have already begun or even completed the blasting operation before a utility has had adequate time to identify a potential problem with the blasting operation and communicate this fact to the employer. The Agency believes this is a flaw in the existing standard and could lead to the endangerment of employees working in blasting operations near utility lines. Obtaining and documenting approval from the utility prior to blasting is important to employee safety. The approval process will vary by locality depending on already established procedures and may, in fact, often take less than 24 hours. Documentation may be in the form of a fax, e-mail, or record of a conversation. </P>
                    <P>Proposed paragraph (f)(2) addresses the handling and storage of explosives at blast sites. Proposed paragraph (f)(2)(i) would require the employer to ensure that empty containers and paper and fiber packing materials which previously contained explosives are disposed of in a safe manner, or reused in accordance with DOT regulations (49 CFR chapter I) (Ex. 2-8). This proposed requirement is the same as existing paragraph (e)(2)(i) except that it has been re-written in clearer language. The proposed requirement is also consistent with paragraph 9.6.1 of the 2001 edition of NFPA 495 (Ex. 2-5). </P>
                    <P>Paragraph (f)(2)(ii) would require the employer to ensure that only non-sparking tools are used to open containers of explosives. This proposed requirement is consistent with the requirement in existing paragraph (e)(2)(ii) which allows the use of non-sparking metallic slitters for opening fiberboard cases. However, this proposed paragraph differs from paragraph 9.1.10 of the 2001 edition of NFPA 495 (Ex. 2-5) which does not require that metal slitters used for opening fiberboard containers be non-sparking. OSHA believes the requirement to use non-sparking slitters is needed to reduce the potential for introducing any material that can create sparks into areas where explosives are located. The Agency does not believe the exception for fiberboard containers is necessary and is concerned that it may actually create a hazard by allowing a sparking tool in the area of explosives. If permitted, the tool could potentially be mistakenly used for a task other than opening fiberboard containers. As a general approach, this proposed rule requires the consistent use of only non-sparking tools and materials when working with explosives. </P>
                    <P>Paragraph (f)(2)(iii) would require the employer to ensure that no explosives are abandoned. This proposed requirement is the same as and replaces existing paragraph (e)(2)(iv) and is consistent with paragraph 9.1.2 of the 2001 edition of NFPA 495 (Ex. 2-5) and ensures that abandoned explosives are not accidentally detonated. </P>
                    <P>Paragraph (f)(2)(iv) would require the employer to ensure that all unused explosives are returned immediately to appropriate magazines. This proposed requirement is similar to a requirement in existing paragraph (e)(3)(iv) except that it has been moved to proposed paragraph (f)(2) which addresses the storage of explosives at blast sites. The proposed paragraph is intended to address safety and security by ensuring that no unused explosives are left behind after a blast and are returned immediately to the proper storage magazine if not used. Proposed paragraph (f)(2)(iv) is consistent with paragraph 9.2.6 of the 2001 edition of NFPA 495 (Ex. 2-5) which requires that all excess explosive materials be removed from the area and returned to the proper storage facilities. </P>
                    <P>The requirement in existing paragraph (e)(2)(ii) that containers of explosives not be opened in any magazine or within 50 feet of any magazine has not been retained in the proposed rule because it is already covered by ATF at 27 CFR 555.214(c) and OSHA does not want to duplicate the regulations of other federal agencies. In addition, the language in existing paragraph (e)(2)(ii) addressing the opening of kegs and wooden cases is not in the proposed rule since these types of containers are no longer used in the industry. </P>
                    <P>
                        Paragraph (f)(3) in the proposal addresses the loading of explosives in 
                        <PRTPAGE P="18817"/>
                        drill holes. Paragraph (f)(3)(i) would require the employer to ensure that all drill holes are of sufficient size to permit the free insertion of explosives. Attempting to force explosives into a drill hole that is too small for the size of the explosives may in some circumstances cause the explosives to detonate. This proposed requirement replaces existing paragraph (e)(3)(i) except that it has been re-written in clearer language. The proposed language is also consistent with the requirement in paragraph 9.2.2 of the 2001 edition of NFPA 495 (Ex. 2-5). 
                    </P>
                    <P>Proposed paragraph (f)(3)(ii) addresses safe procedures for tamping explosives. Paragraph (f)(3)(ii)(A) would require the employer to ensure that tamping of explosives is performed only with non-sparking tools. This proposed requirement replaces a requirement in existing paragraph (e)(3)(ii) except that it has been rewritten to simplify the requirement by only allowing the use of non-sparking tools. The existing requirement limits the tool to be used for tamping to wood rods. Rather than specifying the type of tamping rods used, OSHA is using performance language to allow any non-sparking tool to be used. In this way, an employer may elect to use a non-wood tamping rod provided it is only comprised of non-sparking material. OSHA's intent is that no part of the rod, including any connectors, can be made of a sparking material. </P>
                    <P>Paragraph (f)(3)(ii)(B) would require the employer to ensure that tamping of explosives is performed in a manner that does not degrade, or otherwise damage the explosives or cause the explosives to detonate. This proposed requirement is consistent with a requirement in existing paragraph (e)(3)(ii) except that it has been revised to better clarify the meaning of violent tamping. Both existing paragraph (e)(3)(ii) and paragraph 9.2.5.1 of the 2001 edition of NFPA 495 (Ex. 2-5) require that violent tamping be avoided. Initiation of explosives by impact or friction could result from severe or violent tamping, especially if a detonator is involved. In the proposal, OSHA more clearly expresses the intent of the requirement by using performance language and stating that tamping must be done in a manner that does not degrade or damage the explosives or cause the explosives to detonate. The Agency believes this better describes the intent of the existing requirement and the meaning of the term “violent tamping,” and will aid in compliance with the regulation. </P>
                    <P>Proposed paragraph (f)(3)(iii) would require the employer to ensure that certain requirements are followed when performing pneumatic loading of explosives into drill holes primed with electric detonators or other static electricity-sensitive initiation systems. For example, paragraph (f)(3)(iii)(A) would require the employer to ensure that the equipment is bonded and grounded, paragraph (f)(3)(iii)(B) would require the employer to ensure that a semi-conductive hose is used, and paragraph (f)(3)(iii)(C) would require the employer to ensure that the blaster-in-charge evaluates all systems to assure that they will safely dissipate static electricity under potential field conditions. These proposed requirements are essentially the same as and replace existing § 1910.109(e)(3)(iii) and (g)(3)(iv)(c). The only modification to the language in the proposed rule is an update to include drill holes primed with electric detonators or other static electricity-sensitive initiation systems. The existing language in (e)(3)(iii) only addresses electric blasting caps. This modification reflects current industry practice and is consistent with the paragraph 9.2.4 of the 2001 edition of NFPA 495 (Ex. 2-5). </P>
                    <P>Paragraph (f)(3)(iv) would require the employer to ensure that no employee drills into explosives or any portion of a hole that at any time contained explosives. This proposed requirement modifies existing paragraph (e)(3)(vi), which prohibits the deepening of drill holes that have previously contained explosives. The proposed language increases employee safety by expanding the coverage of existing paragraph (e)(3)(vi) to prohibit drilling into explosives or any portion of a hole that at any time contained explosives. This includes drilling through a cross-section of a drill hole that once contained explosives. This proposed language was recommended by the Petition (Ex. 2-1). </P>
                    <P>Paragraph (f)(3)(v) would require the employer to ensure that, after the drill hole loading process is completed but before detonation, all remaining explosives, including detonators, are immediately returned to the appropriate magazines. This ensures that none of the remaining explosives are unintentionally left near the loaded drill holes and detonated when the loaded drill holes are detonated. The proposed requirement replaces existing paragraph (e)(3)(vii) except that, without changing the intent of the requirement, it has been rewritten in clearer language using terms more consistent with those used in other parts of the proposed standard. Unlike the existing requirement, the proposed version explicitly states that all the remaining explosives must be immediately returned to the appropriate magazines before the loaded explosives are detonated. This proposed requirement is also consistent with paragraph 9.2.6 of the 2001 edition of NFPA 495 (Ex. 2-5) which addresses storage of excess explosive materials. </P>
                    <P>Paragraph (f)(3)(vi) would require the employer to ensure that, during the time that drill holes are loaded or are being loaded, only personnel who are engaged in drilling or loading operations, or are otherwise authorized by the employer, may enter the blast site. The time when the drill holes are loaded or being loaded is a period of increased risk of accidental detonation of the explosives. The proposed provision reduces the risk to employees by ensuring that only essential employees are in the blast site during this time. This is a new requirement recommended by the Petition (Ex. 2-1). The Agency agrees that this is an important consideration for the safety and security of the blast site and should be addressed in the proposed rule. This proposed requirement is also consistent with paragraph 9.2.1 of the 2001 edition of NFPA 495 (Ex. 2-5) which addresses unauthorized personnel entering the blast site during loading operations. </P>
                    <P>Paragraph (f)(3)(vii)(A) would require the employer to ensure that, after the loaded drill holes are connected but prior to them being connected to a source of initiation, the blast area is barricaded and posted, guarded, or both. If the blast area is barricaded and posted, the posted sign must contain sufficient language, such as “DANGER—EXPLOSIVES HAZARD—DO NOT ENTER,” to ensure that employees are aware of the hazards involved within the blast area. In addition, paragraph (f)(3)(vii)(B) would require all personnel to be removed from the blast area. These proposed requirements are new and were recommended by the Petition (Ex. 2-1). The Agency agrees with the Petition that it is necessary to ensure that all employees are removed from the blast area for their safety during this stage of the blasting operations. These proposed requirements are also consistent with paragraph 9.2.7 of the 2001 edition of NFPA 495 (Ex. 2-5) which addresses personnel in the blast area during pre-blast and post-blast operations. </P>
                    <P>
                        Proposed paragraph (f)(4) continues with the blasting operation sequence and addresses the initiation of the explosives. Paragraph (f)(4)(i) would require the employer to ensure that, where sources of extraneous electricity in excess of fifty (50) milliamperes (flowing through a one-ohm resistor) are present, electric detonators are used only after sufficient measures are taken 
                        <PRTPAGE P="18818"/>
                        to ensure that the detonators will not inadvertently activate. This is a new requirement based on a recommendation in the Petition (Ex. 2-1) and is consistent with paragraph 9.3.3 of the 2001 edition of NFPA 495 (Ex. 2-5). This determination about whether to use electric detonators would need to be made by the blaster-in-charge on a case-by-case basis. As discussed earlier in proposed paragraph (f)(1)(ii)(E), certain sources of electrical current can cause accidental ignitions of electric detonators and paragraph (f)(4)(i) is being proposed to ensure that appropriate steps are taken so that electric detonators do not activate accidentally. 
                    </P>
                    <P>Paragraph (f)(4)(ii) would require the employer to ensure that the blaster-in-charge supervises selection and installation of the blast initiation system. This is a new requirement based on a recommendation in the Petition (Ex. 2-1) and is consistent with paragraph 9.3.6.4(1) of the 2001 edition of NFPA 495 (Ex. 2-5). The purpose of this requirement is to ensure that the proper initiation system is selected and installed depending on the particular blast to be performed. </P>
                    <P>Paragraph (f)(4)(iii) would require the employer to ensure that the initiation system is used in accordance with the manufacturer's recommendations. This is a new requirement based on a recommendation in the Petition (Ex. 2-1) and is consistent with paragraph 9.3.6.4(2) of the 2001 edition of NFPA 495 (Ex. 2-5). This proposed requirement applies to both electric and electronic detonators and OSHA believes it would increase employee safety in the use of initiation systems. </P>
                    <P>Proposed paragraphs (f)(4)(iv), (f)(4)(v), and (f)(4)(vi) address requirements that are specific to non-electric initiation systems, including electronic initiation systems. The proposal also contains similar (where applicable) requirements specific to electric initiation systems below in proposed paragraphs (f)(4)(xi) and (f)(4)(xii). Paragraph (f)(4)(iv) would require the employer to ensure that the blaster-in-charge checks the initiation system visually after the blast hookup. This is a new requirement based on a recommendation in the Petition (Ex. 2-1) and is consistent with paragraph 9.3.6.4(3) of the 2001 edition of NFPA 495 (Ex. 2-5). The purpose of this requirement is to visually ensure the connections in the initiation system were made properly in order to prevent misfires. Paragraph (f)(4)(v) would require the employer to ensure that the blaster-in-charge tests the blast layout for continuity as recommended by the manufacturer. This is a new requirement based on a recommendation in the Petition (Ex. 2-1) and is consistent with paragraph 9.3.6.4(4) of the 2001 edition of NFPA 495 (Ex. 2-5). OSHA believes this new requirement will enhance employee safety during blasting operations by reducing the chance of misfires due to improper connections. </P>
                    <P>Paragraph (f)(4)(vi) would require the employer to ensure that where deemed necessary by the blaster-in-charge, a double trunk line or closed-loop hookup is used in the initiation system. This is a new requirement based on a recommendation in the Petition (Ex. 2-1) and is consistent with paragraph 9.3.6.4(5) of the 2001 edition of NFPA 495 (Ex. 2-5). OSHA believes this proposed requirement would increase employee safety by reducing misfires through the use, where necessary, of double trunk lines or closed-loop hookups. </P>
                    <P>Proposed paragraph (f)(4)(vii) would require the employer to ensure that when a safety fuse is used, only a crimper approved by the detonator manufacturer or the safety fuse manufacturer is used to connect the detonator to the safety fuse. This requirement replaces a requirement in existing paragraph (e)(4)(ii) that, when a fuse is used, the blasting cap must be securely attached to the safety fuse with a standard-ring type cap crimper. Compared to the existing requirement, the new language enhances employee safety by ensuring that the appropriate type of crimper is used to connect the detonator to the safety fuse. This new requirement was recommended by the Petition (Ex. 2-1). </P>
                    <P>
                        <E T="03">Issue #13:</E>
                         Paragraph 10.3.2 of the 2006 edition of NFPA 495 (Ex. 2-21) includes a requirement that when a safety fuse is used, “in no case shall fuse lengths of less than 3 ft or with a burn time of less than 120 seconds be used.” The proposed standard does not contain this requirement. Should it be included in the standard? If so, are the fuse length and burn time restrictions adequate to protect the safety of employees? 
                    </P>
                    <P>Paragraph (f)(4)(viii) would require the employer to ensure that all primers are assembled at least 50 feet (15.25 m) away from any magazine. This proposed requirement replaces a similar requirement in existing paragraph (e)(4)(ii). It is also consistent with a requirement in paragraph 9.3.6.1 of the 2001 edition of NFPA 495 (Ex. 2-5). </P>
                    <P>
                        <E T="03">Issue #14:</E>
                         After further discussions with IME concerning the Petition, IME suggested an exception to proposed paragraph (f)(4)(viii) to allow primers to be assembled within 50 feet of a Type 3 “day box” magazine. IME argued that worksite conditions and space restrictions may make it impractical or impossible to keep the Type 3 magazine, in which detonators are located, at a distance of 50 feet or more from the place where the primer is being assembled. IME asserted that such situations may occur when blasting is taking place in an underground or other confined area. IME argued that the 50 foot restriction in the proposed paragraph requires the blaster-in-charge to transport only one detonator at a time from the Type 3 magazine which could potentially leave the primers unattended and could result in the magazine being located in an area out of the sight and physical control of the blaster-in-charge. OSHA requests comments on whether proposed paragraph (f)(4)(viii) should apply to all magazines including Type 3 magazines? Alternatively, when warranted by work conditions, should primers be allowed to be assembled within 50 feet of a Type 3 magazine? If so, what kinds of work conditions would warrant such an exception? If an exception is made for Type 3 magazines, how close to such a magazine can primers be assembled safely? 
                    </P>
                    <P>Paragraph (f)(4)(ix) would require the employer to ensure that primers are made up only as needed for immediate use. This proposed requirement is the same as and replaces existing paragraph (e)(4)(iii) except that it has been rewritten in clearer language without changing the intent of the requirement. In addition, the proposed requirement is consistent with a requirement in paragraph 9.3.6.1 of the 2001 edition of NFPA 495 (Ex. 2-5). </P>
                    <P>
                        Paragraph (f)(4)(x) would require the employer to ensure that when an explosives cartridge that does not have a detonator well is used as a primer, a hole large enough to accommodate the detonator is made in the cartridge with a spark-resistant powder punch approved either by the explosives manufacturer or by the blaster-in-charge. This proposed paragraph is based on and replaces existing paragraph (e)(4)(iv) but has been revised to reflect current industry practice. The revised language also clarifies the kind of powder punch that can be used to make a well for the detonator. The proposed requirement allows the use of a spark-resistant cap crimper for this purpose since it is a form of a powder punch. The purpose of this requirement is to ensure that, for safe use, the detonator well is made in the correct manner and is the correct size to accommodate the detonator. For safety 
                        <PRTPAGE P="18819"/>
                        reasons, the employer should never use a cast primer or booster if the hole for the detonator is too small. Further, the employer should never enlarge a hole in a cast primer or booster to accept a detonator or force or attempt to force a detonator into explosive material. The revisions in the proposed paragraph were recommended by the Petition (Ex. 2-1) and are consistent with the requirements contained in paragraph 9.3.6 of the 2001 edition of NFPA 495 (Ex. 2-5). 
                    </P>
                    <P>Paragraph (f)(4)(xi) would require the employer to ensure that, when testing electric circuits that connect loaded drill holes, only blasting galvanometers or other instruments specifically designed for this purpose are used. This proposed requirement is similar to existing paragraph (e)(4)(vii) except that it has been updated to be consistent with paragraph 9.3.5 of the 2001 edition of NFPA 495 (Ex. 2-5) which allows other test instruments to be used as long as they are designed for that purpose. </P>
                    <P>Proposed paragraph (f)(4)(xii) addresses requirements for electrical firing of blasts. Paragraph (f)(4)(xii)(A) would require the employer to ensure that only the person making the lead-line connections or the blaster-in-charge fires the shot. This paragraph is essentially the same as a requirement in existing paragraph (e)(4)(viii) but has been revised to allow the blaster-in-charge the authority to fire the shot in addition to the person making the lead-line connections. The change was made to be consistent with the responsibilities given to the blaster-in-charge in this proposed rule and to be consistent with paragraph 9.3.7 of the 2001 edition of NFPA 495 (Ex. 2-5), which allows the blaster-in-charge to fire the shot. In some cases, the blaster-in-charge may need to delegate the responsibility of firing the shot to the person who made the lead-line connections. This is the only other person the blaster-in-charge may delegate to perform this duty. </P>
                    <P>Proposed paragraph (f)(4)(xii)(B) would require the employer to ensure that blasting lead lines remain shunted (shorted) and not connected to the blasting machine or other source of current until the charge is to be fired. This proposed requirement is the same as and replaces a requirement in existing paragraph (e)(4)(viii) except that the term “shunted” has been added to clarify the intent of the requirement and to be consistent with paragraph 9.3.7 of the 2001 edition of NFPA 495 (Ex. 2-5). </P>
                    <P>
                        <E T="03">Issue #15:</E>
                         The proposed rule does not address static sensitive detonators. OSHA would like specific comments on whether there is a potential hazard associated with static electricity setting off electric detonators. If there is a hazard, should OSHA address this hazard in § 1910.109 by requiring all electric detonators be tested for electrostatic sensitivity? If so, what testing procedures should be used? Is it technically and economically feasible to require detonator manufacturers to test for static sensitivity? Are there procedures employees can take to eliminate an electrostatic hazard such as using rubber gloves or friction tape when working with electric detonators? 
                    </P>
                    <P>Proposed paragraph (f)(5) addresses the need for a warning signal prior to firing a blast. Paragraph (f)(5) would require the employer to ensure that, before a blast is fired, all persons and vehicles are at a safe distance outside the blast area or under sufficient cover, and that an adequate warning signal is given. This proposed requirement is essentially the same as and replaces existing paragraph (e)(5) except that it has been rewritten in clearer language. Unlike the existing paragraph, the proposed paragraph does not include a requirement that surplus explosives be in a safe place because this requirement is already addressed in proposed paragraphs (f)(2)(iv) and (f)(3)(v) which require that unused explosives and detonators be immediately returned to the appropriate magazines. The purpose of the warning signal, usually a siren, is to ensure that all employees are a safe distance away from the blast when fired. Typically, the blast area is cleared by the blaster-in-charge well before the siren sounds. The siren is used to warn of an imminent blast (the siren usually sounds up to a minute before the blast). If anyone is still in the blast area, it provides them with adequate time to get out safely. Also, the warning siren allows anyone outside the blast area a chance to move behind a barrier or use necessary hearing protection. Proposed paragraph (f)(5) is consistent with paragraph 9.3.8 of the 2001 edition of NFPA 495 (Ex. 2-5). </P>
                    <P>Paragraph (f)(6) in the proposal addresses post blast procedures. Paragraph (f)(6)(i) would require the employer to ensure that, after a blast, no other person enters the blast area until it is inspected by the blaster-in-charge and found to be free of misfires and other safety hazards and the blaster-in-charge has given an all-clear signal. This is a new requirement that requires the blaster-in-charge to conduct a search for safety hazards and to prevent all persons from entering the blast area until the blaster-in-charge determines it is safe. It is also consistent with paragraphs 9.4.1 and 9.4.3 of the 2001 edition of NFPA 495 (Ex. 2-5). </P>
                    <P>Paragraph (f)(6)(ii) would require the employer to ensure that the blaster-in-charge does not enter the blast site until sufficient time has passed to allow smoke and fumes to dissipate and dust to settle. This is a new requirement intended to prevent the blaster-in-charge from entering the blast site before it is safe to conduct the inspection of the blast site. It is also consistent with paragraph 9.4.2 of the 2001 edition of NFPA 495 (Ex. 2-5). </P>
                    <P>Paragraph (f)(7) in the proposal addresses misfires. It is a consolidation of many paragraphs scattered throughout the existing standard concerning misfires. OSHA felt it would be easier for employers to understand the requirements involving misfires if they were located in the same paragraph. </P>
                    <P>Paragraph (f)(7)(i) would require the employer to ensure that, whenever there is a misfire while using blasting cap and fuse or electronic detonators, all employees remain outside the blast area for at least 1 hour. If electric detonators or non-electric detonators are used and a misfire occurs, this waiting period may be reduced to 30 minutes. This proposed requirement is essentially the same as existing paragraph (e)(4)(vi) and paragraphs 9.5.4 and 9.5.5 of the 2001 edition of NFPA 495 (Ex. 2-5). The only changes are that, compared to the existing requirement, the proposed requirement has been rewritten for clarity and electronic detonators have been added. Since electronic detonators are relatively new technology, the existing standard does not contain requirements that address a waiting period following a misfire involving electronic detonators. </P>
                    <P>
                        <E T="03">Issue #16:</E>
                         OSHA is seeking comments on what is an appropriate waiting period after misfires. The Agency is proposing a misfire waiting period of at least 1 hour if a blasting cap and fuse or an electronic detonator was used and a misfire waiting period of at least 30 minutes if an electric or non-electric (other than blasting cap and fuse) detonator was used. OSHA's construction standard at § 1926.911(d) requires a waiting period of at least one hour if there is a misfire while using cap and fuse. On the other hand, MSHA's regulations at 30 CFR §§ 56.6310 and 57.6310 require persons to wait 30 minutes if a safety fuse and blasting caps are used and 15 minutes if any other type of detonator is used. These MSHA requirements apply to surface metal and nonmetal mines and to underground metal and nonmetal mines. Paragraphs 9.5.4 and 9.5.5 of the 2001 edition of NFPA 495 require a 1-hour waiting period after a misfire using 
                        <PRTPAGE P="18820"/>
                        cap and fuse and a 30 minute waiting period after a misfire using an electric or non-electric detonator (other than cap and fuse). However, the 2006 edition of NFPA 495 (Ex. 2-21) has reduced the waiting periods to 30 minutes when using electronic or cap and fuse initiation and 15 minutes for all others. 
                    </P>
                    <P>OSHA is seeking comment on whether the waiting periods for misfires in its proposed standard are appropriate for employee safety. Should the Agency consider the waiting periods in the 2006 edition of NFPA 495 or other alternative waiting periods and, if so, why? What is the general industry practice for waiting periods after misfires? </P>
                    <P>Paragraph (f)(7)(ii) would require the employer to ensure that, whenever explosives remain in a misfired hole, a new primer is inserted and the hole is reblasted. Where reblasting presents a hazard, the remaining explosives shall be washed out with water, or, where the misfire is underwater, blown out with air.  This proposed requirement is similar to and replaces existing paragraph (e)(4)(v) and has been rewritten in clearer language. Unlike the existing requirement, when reblasting presents a hazard, the proposed paragraph allows the explosive to be extracted using water or, where the misfire is underwater, using air. This is consistent with the requirements in paragraph 9.5.3 of the 2001 edition of NFPA 495 (Ex. 2-5) and provides for misfire situations where reblasting may be unsafe. </P>
                    <P>Paragraph (f)(7)(iii) would require the employer to ensure that misfires are handled under the direction of the blaster-in-charge and all initiation paths are carefully traced and a thorough search made for unexploded charges. This proposed requirement is essentially the same as and replaces requirements in existing paragraph (e)(4)(vi) except that the blaster-in-charge is specifically assigned the duty to direct the handling misfires. This proposed requirement is also consistent with paragraphs 9.5.6 and 9.5.7 of the 2001 edition of NFPA 495 (Ex. 2-5) which address the employer's responsibility concerning misfires and the need to conduct a search for unexploded charges. </P>
                    <P>Paragraph (f)(7)(iv) would require the employer to ensure that explosives recovered from blasting misfires are placed in a magazine that is used only for the storage of misfired explosives and are then disposed of as soon as possible in accordance with the manufacturers' recommendations. This would be a new requirement and is consistent with the requirements in paragraph 8.8.4 of the 2001 edition of NFPA 495 (Ex. 2-5). The proposed paragraph is intended to protect employee safety by requiring possibly dangerous and unstable misfired explosives to be isolated in magazines and to be kept away from other explosives. </P>
                    <P>Paragraph (f)(7)(v) would require the employer to ensure that detonators recovered from blasting misfires are not reused and are disposed of as soon as possible in accordance with the manufacturers' recommendations. Proposed paragraphs (f)(7)(iv) and (v) are essentially the same as and replace those in existing paragraph (c)(5)(ix) and are also consistent with the requirements in paragraph 8.8.4 of the 2001 edition of NFPA 495 (Ex. 2-5). </P>
                    <P>
                        <E T="03">Paragraph (g) Blasting agents, water gels, slurries, and emulsions.</E>
                         In paragraph (g), OSHA is proposing specific requirements for blasting agents, water gels, slurries, and emulsions. Existing paragraph (g) covers blasting agents and existing paragraph (h) covers water gels and slurries. OSHA has determined that these two paragraphs contain many duplicative requirements. Therefore, OSHA is proposing to combine these two existing paragraphs into one proposed paragraph (g) to cover blasting agents, water gels, slurries, and emulsions. Most of the requirements in proposed paragraph (g) would cover blasting agents, water gels, slurries, and emulsions, but some would only cover water gels, slurries, and emulsions. 
                    </P>
                    <P>Existing paragraph (h) addresses water gels and slurries but does not address emulsions. Emulsions are similar to water gels and slurries but are a relatively new product which did not exist when the current § 1910.109 standard was promulgated. They are being included with blasting agents, water gels, and slurries in proposed paragraph (g). </P>
                    <P>Proposed paragraph (g)(1)(i)(A) would require that, unless otherwise specified in proposed paragraph (g), blasting agents, water gels, slurries, and emulsions shall be stored, transported, handled, and used in the same manner as other explosives. The revised requirement is essentially the same as existing paragraph (g)(1) and (h)(1). </P>
                    <P>Proposed paragraph (g)(1)(i)(B) would require that, unless otherwise specified in proposed paragraph (g), water gels, slurries, and emulsions classified as Division 1.1 or Division 1.5 must meet the same requirements as blasting agents in paragraph (g). As mentioned above in the preamble, there is a large overlap between existing paragraph (g) covering blasting agents and existing paragraph (h) covering water gels and slurries. To avoid unnecessary duplication, these two existing paragraphs are being combined in proposed paragraph (g), which would apply to blasting agents, water gels, slurries, and emulsions. In addition, proposed paragraph (g)(1)(i)(B) states that the manufacture of water gels, slurries, and emulsions that can be classified as Division 1.1 explosives must also comply with § 1910.119 Process Safety Management. However, unless specified in the proposed standard, water gels, slurries, and emulsions that can be classified as Division 1.5 explosives are subject to the same requirements in the proposed standard that apply to other kinds of blasting agents. This includes the requirements in the proposed standard covering the manufacture of such Division 1.5 water gels, slurries, and emulsions. </P>
                    <GPOTABLE COLS="03" OPTS="L2,i1" CDEF="s45,r45,r45">
                        <TTITLE>Consolidation of Requirements in Existing Paragraphs (g) and (h) Into Proposed Paragraph (g)</TTITLE>
                        <BOXHD>
                            <CHED H="1">
                                Existing paragraph (g)
                                <LI>blasting agents</LI>
                            </CHED>
                            <CHED H="1">
                                Existing paragraph (h)
                                <LI>water gels</LI>
                            </CHED>
                            <CHED H="1">
                                Proposed paragraph (g)
                                <LI>blasting agents, water gels, slurries, and emulsions</LI>
                            </CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">(g)(2)(ii)(a)</ENT>
                            <ENT>(h)(3)(ii)(a)</ENT>
                            <ENT>(g)(2)(i)(A).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(g)(2)(ii)(b)</ENT>
                            <ENT>(h)(3)(ii)(b)</ENT>
                            <ENT>(g)(2)(i)(B).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(g)(2)(ii)(d)</ENT>
                            <ENT>(h)(3)(ii)(d)</ENT>
                            <ENT>(g)(2)(i)(C).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(g)(2)(ii)(e)</ENT>
                            <ENT>(h)(3)(ii)(e)</ENT>
                            <ENT>(g)(2)(i)(D)-(F).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(g)(2)(ii)(f)</ENT>
                            <ENT>(h)(3)(ii)(f)</ENT>
                            <ENT>(g)(2)(i)(G) and (H).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(g)(2)(ii)(c)</ENT>
                            <ENT>(h)(3)(ii)(c)</ENT>
                            <ENT>(g)(2)(i)(J).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(g)(2)(iii)(a)</ENT>
                            <ENT>(h)(3)(iv)(a)</ENT>
                            <ENT>(g)(2)(ii)(A).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(g)(3)(iii)(a)</ENT>
                            <ENT>(h)(4)(ii)(b)</ENT>
                            <ENT>(g)(3)(iii)(A) and (B).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(g)(3)(iii)(c)</ENT>
                            <ENT>(h)(4)(ii)(d)</ENT>
                            <ENT>(g)(3)(iii)(C).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(g)(3)(iii)(d)</ENT>
                            <ENT>(h)(4)(ii)(e)</ENT>
                            <ENT>(g)(3)(iii)(E).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(g)(3)(iii)(e)</ENT>
                            <ENT>(h)(4)(ii)(f)</ENT>
                            <ENT>(g)(3)(iii)(G).</ENT>
                        </ROW>
                    </GPOTABLE>
                    <P>Paragraph (g)(1)(ii)(A) would require the employer to ensure that caked oxidizers, either in bags or in bulk, are not loosened by blasting. The provision is the same as existing (g)(5)(vi) and consistent with paragraph 5.5.3 of the 2001 edition of NFPA 495 (Ex. 2-5). </P>
                    <P>Paragraph (g)(1)(ii)(B) would require the employer to ensure that equipment used for mixing and packaging blasting agents is constructed of materials compatible with the blasting agent composition. The proposed paragraph is phrased in performance language but is consistent with existing paragraph (g)(2)(iii)(b) and with paragraph 5.2.4.2 of the 2001 edition of NFPA 495 (Ex. 2-5). </P>
                    <P>
                        Paragraph (g)(1)(ii)(C) would require the employer to ensure that spills or leaks which may contaminate 
                        <PRTPAGE P="18821"/>
                        combustible materials are cleaned up immediately. The provision is equivalent to and replaces existing paragraph (h)(3)(iii)(b) with the exception that the proposed requirement does not retain the statement that: “Nitrate-water solutions may be stored in tank cars, tank trucks, or fixed tanks without quantity or distance limitations.” OSHA has omitted this statement from the proposal because it is merely advisory and does not improve employee safety. In addition, the proposed paragraph extends the coverage of the existing paragraph to cover not only water gels, slurries, and emulsions but also blasting agents in general. OSHA believes that the expansion of the existing requirement to blasting agents in general will enhance employee safety. 
                    </P>
                    <P>Paragraph (g)(1)(ii)(D) would require the employer to ensure that ingredients are not kept with incompatible materials that may endanger the safety of employees if the ingredients and incompatible materials are commingled. This proposed requirement is essentially the same as and replaces the corresponding existing provision (h)(3)(iii)(d) and is consistent with paragraph 6.3.3(4) of the 2001 edition of NFPA 495 (Ex. 2-5). While the existing paragraph only applies to water gels, slurries, and emulsions, the proposed paragraph also applies to blasting agents in general. OSHA believes that it is important for employee safety that ingredients of blasting agents in general, and not only those of water gels, slurries, and emulsions, be kept away from incompatible materials. </P>
                    <P>Paragraph (g)(1)(ii)(E) would require the employer to ensure that water gels, slurries, and emulsions maintain their liquid or water content. This is a new requirement based on a recommendation in the Petition (Ex. 2-1). OSHA believes the requirement is needed because, according to IME, when water gels, slurries, and emulsions lose their liquid or water content, their stability decreases and the possibility of unintentional detonation increases. Therefore, maintaining the water content of water gels, slurries, and emulsions helps to maintain their stability and avoid unintentional deteriorations. </P>
                    <P>Proposed paragraph (g)(1)(iii) would apply where a Type 5 magazine is used as a bulk storage container for blasting agents and would require the employer to ensure that any electrically-driven conveyor used for loading or unloading the magazine be designed to minimize damage from corrosion. This proposed provision is consistent with the requirements of existing (g)(4)(iv) and with paragraph 5.4.5 of NFPA 495-2001 (Ex. 2-5). One minor change is that OSHA has not retained the language in existing paragraph (g)(4)(iv) that specifically requires electrically driven conveyors to conform to subpart S (Electrical) because the obligation is already imposed in subpart S and, therefore, there is no need to restate that requirement. </P>
                    <P>Existing paragraphs (g)(4)(i) through (iii), covering explosives storage, are not being retained in the proposed standard because they are preempted by ATF's explosives storage regulations at 27 CFR part 555. See the discussion above at “OSHA's Authority to Regulate” on how ATF's explosives storage regulations preempt OSHA's explosives storage regulations in § 1910.109. </P>
                    <P>Proposed paragraph (g)(2) sets forth a number of requirements related to fixed location mixing of blasting agents. The requirements are essentially the same as existing requirements except for editorial revisions to make the provisions easier to understand. The proposed requirements are also consistent with the 2001 edition of NFPA 495. </P>
                    <P>Proposed paragraph (g)(2)(i)(A) would require the employer to ensure that buildings used for the mixing of blasting agents are of noncombustible construction or constructed of sheet metal on wood studs. The provision is equivalent to existing (g)(2)(ii)(a) and (h)(3)(ii)(a) and is consistent with paragraphs 5.2.3.1 and 6.3.2(1) of the 2001 edition of NFPA 495 (Ex. 2-5). </P>
                    <P>Proposed paragraph (g)(2)(i)(B) would require the employer to ensure that the floors of any building used for mixing blasting agents are constructed of concrete or other minimally absorbent material and have no drains or piping into which molten materials could flow and be confined during a fire. Apart from minor revisions, the provision is equivalent to existing paragraphs (g)(2)(ii)(b), (g)(2)(vi)(a), and (h)(3)(ii)(b) and is consistent with paragraphs 5.2.3.2 and 6.3.2(2) of the 2001 edition of NFPA 495 (Ex. 2-5). Specifically, the word “nonabsorbent” in the existing provision has been changed to “minimally absorbent” to reflect that concrete floors can allow some liquid to penetrate their surface. Concrete floors are common in fixed location mixing buildings, and the “nonabsorbent” language of the existing provision has caused some concern about the use of concrete. Therefore, the purpose of the revision is to clarify the requirements of the proposed provision. OSHA believes this minor change will have no negative effect on employee safety. </P>
                    <P>Proposed paragraph (g)(2)(i)(C) would require the employer to ensure that the building is ventilated to prevent unsafe heat or fume accumulations. The provision is equivalent to and replaces existing paragraphs (g)(2)(ii)(d) and (h)(3)(ii)(d) and is consistent with 5.2.3.4 and 6.3.2(4) of the 2001 edition of NFPA 495 (Ex. 2-5) . However, existing paragraphs (g)(2)(ii)(d) and (h)(3)(ii)(d) and paragraphs 5.2.3.4 and 6.3.2(4) of the 2001 edition of NFPA 495 use the phrase “well ventilated.” The proposed paragraph uses the phrase “ventilated to prevent unsafe heat or fume accumulations.” OSHA believes the proposed language more clearly expresses the intent of the requirement. </P>
                    <P>Proposed paragraph (g)(2)(i)(D) would require the employer to ensure that heating, if supplied for the building, is provided in a manner that does not create a fire or ignition hazard. Proposed paragraph (g)(2)(i)(E) would further require that all direct sources of indoor heat be provided exclusively from units located outside the building. For example, if heat is pumped into the building, the heating element must be located outside the building to eliminate the ignition source from within the building. Proposed paragraph (g)(2)(i)(F) would clarify that heating units may be used in the building if they do not depend on combustion processes, such as electric heaters, and do not create a fire or ignition hazard. Examples of unacceptable heating units are those that use kerosene or propane. The provisions replace requirements in existing paragraphs (g)(2)(ii)(e) and (h)(3)(ii)(e) and are consistent with paragraphs 5.2.3.5 and 6.3.2(5) of the 2001 edition of NFPA (Ex. 2-5). </P>
                    <P>Proposed paragraph (g)(2)(i)(G) would require the employer to ensure that all internal combustion engines are located outside the building, or that they are safely ventilated and isolated by a fire barrier wall with at least a 1-hour rating. Proposed paragraph (g)(2)(i)(H) would require the employer to ensure that the exhaust systems on all internal-combustion engines are located so that no sparks or other ignition sources create a hazard to any materials in or in close proximity to the building. These requirements are essentially the same as and replace those in existing paragraphs (g)(2)(ii)(f) and (h)(3)(ii)(f) and are consistent with paragraphs 5.2.3.6 and 6.3.2(6) of the 2001 edition of NFPA 495 (Ex. 2-5). </P>
                    <P>
                        Proposed paragraph (g)(2)(i)(I) would require the employer to ensure that all electric equipment located in the mixing room meets the requirements in subpart S of this part for Class II, Division 2 locations. The proposed provision is 
                        <PRTPAGE P="18822"/>
                        equivalent to and replaces existing paragraph (g)(2)(v) and is consistent with paragraph 5.2.6 of the 2001 edition of NFPA 495 (Ex. 2-5). 
                    </P>
                    <P>Paragraph (g)(2)(i)(J) would require the employer to ensure that all fuel-oil storage facilities are separated from the mixing building and located in such a manner that in case of tank rupture, the oil will drain away from the mixing building and other facilities containing explosives or employees. Alternatively, tanks may be diked in a manner that will contain the entire tank contents in case of rupture. The proposed provision replaces existing paragraphs (g)(2)(ii)(c) and (h)(3)(ii)(c) except that OSHA has made two changes in the proposed paragraph compared to the existing paragraphs. First, in the proposed paragraph, OSHA has added the alternative method of diking tanks. This addition is based on a recommendation in the Petition (Ex. 2-1). OSHA believes this alternative method is as safe as allowing the oil to drain away from the mixing building. Second, the existing paragraphs only require the oil from a ruptured tank to drain away from the mixing building, whereas the proposed paragraph requires such oil to drain away from all buildings and other facilities containing explosives or employees. OSHA believes this expansion increases safety for employees at the workplace by ensuring that oil from a ruptured tank is diverted away from buildings and other facilities where employees may be located. Except for these two additions, the proposed paragraph is consistent with paragraphs 5.2.3.3 and 6.3.2(3) of the 2001 edition of NFPA 495 (Ex. 2-5). </P>
                    <P>Proposed paragraph (g)(2)(i)(K) would require the employer to ensure that the land surrounding blasting agent mixing plants be kept clear of all combustible materials for a distance of at least 25 feet. This proposed paragraph is the same as and replaces existing paragraph (g)(2)(vi)(e) and is consistent with paragraph 5.2.8(5) in the 2001 edition of NFP A 495. Note that under § 1910.119(e)(3)(v), the employer must already identify and control any hazards, such as nearby combustible materials, relating to the siting of a facility at which Division 1.1 to 1.4 explosives are manufactured, that could initiate a catastrophic release within the manufacturing process. </P>
                    <P>Proposed paragraph (g)(2)(ii) sets forth requirements for equipment used for mixing of blasting agents at fixed locations. Like the requirements of proposed paragraph (g)(2)(i), the requirements in proposed paragraph (g)(2)(ii) are essentially the same as those in the existing standard and in paragraph 5.2 of NFPA 495 except that they have been reorganized into separate provisions so they are easier to understand. </P>
                    <P>Proposed paragraph (g)(2)(ii)(A) would require the employer to ensure that the mixing equipment minimizes the possibility of frictional heating, compaction, and confinement of the explosives present. The provision is equivalent to and replaces corresponding requirements in existing paragraphs (g)(2)(iii)(a) and (h)(3)(iv)(a) and is consistent with paragraphs 5.2.4.1 and 6.3.4(1) of the 2001 edition of NFPA 495 (Ex. 2-5). </P>
                    <P>Proposed paragraph (g)(2)(ii)(B) would require the employer to ensure that all surfaces of the mixing equipment are accessible for cleaning. The provision is equivalent to and replaces the corresponding requirement in existing paragraph (g)(2)(iii)(a) and is consistent with paragraph 5.2.4.1 of the 2001 edition of NFPA 495 (Ex. 2-5). </P>
                    <P>Proposed paragraph (g)(2)(ii)(C) would require the employer to ensure that all bearings and drive assemblies are mounted outside the mixer and are protected against dust accumulation. The provision is equivalent to and replaces the corresponding requirement of existing paragraph (g)(2)(iii)(a) and is consistent with paragraph 5.2.4.1 of the 2001 edition of NFPA 495 (Ex. 2-5). </P>
                    <P>Proposed paragraph (g)(2)(ii)(D) would require the employer to ensure that fuel oil is prevented from flowing to the mixer in case of fire. It further requires that in gravity-flow systems, an automatic spring-loaded shutoff valve with a fusible link be installed. The provision is equivalent to and replaces the corresponding requirement of existing paragraph (g)(2)(iii)(c) and is consistent with paragraph 5.2.4.3 of the 2001 edition of NFPA 495 (Ex. 2-5). </P>
                    <P>Proposed paragraph (g)(2)(ii)(E) would require the employer to ensure that both the equipment and handling procedures prevent the inadvertent introduction of foreign objects or materials into the mixing process. The provision is equivalent to and replaces existing paragraph (h)(3)(iv)(b) and is consistent with paragraph 6.3.4(2) of the 2001 edition of NFPA 495 (Ex. 2-5). </P>
                    <P>Proposed paragraph (g)(2)(ii)(F) would require the employer to ensure that mixers, pumps, valves, and related equipment are regularly and periodically flushed, cleaned, dismantled, and inspected. The provision is equivalent to and replaces existing paragraph (h)(3)(iv)(c) and is consistent with paragraph 6.3.4(3) of the 2001 edition of NFPA 495 (Ex. 2-5). In the existing standard, the requirements in paragraphs (h)(3)(iv)(b) and (c) apply only to water gels and slurries whereas proposed paragraphs (g)(2)(ii)(E) and (F) are applying these requirements to all blasting agents, including water gels, slurries, and emulsions. OSHA believes that the regular and periodic flushing, cleaning, dismantling, and inspection of these types of equipment help to prevent the malfunction of the equipment. Such malfunctions could lead to a potential explosion hazard and endanger the safety of employees. OSHA further believes that these safety provisions should cover the manufacture of all blasting agents and not just water gels and slurries. </P>
                    <P>Proposed paragraph (g)(2)(iii) sets forth requirements for blasting agent compositions in fixed mixing locations. Paragraph (g)(2)(iii)(A) would require the employer to ensure that oxidizers of small particle size, such as crushed ammonium nitrate prills or fines, which may be more sensitive than coarser products, are handled with additional care compared to the coarser products. These oxidizers of small particle size may be more sensitive and more likely to be accidentally ignited or initiated if care is not taken in their handling. The provision is equivalent to and replaces the requirement of existing paragraph (g)(2)(iv)(b) and is consistent with paragraph 5.2.5.1 of the 2001 edition of NFPA 495 (Ex. 2-5). </P>
                    <P>Proposed paragraph (g)(2)(iii)(B) would require the employer to ensure that no hydrocarbon liquid fuel with a flashpoint lower than 125 °F (51.7 °C) is used in the manufacture of blasting agents except at ambient air temperatures below 45 °F (7.2 °C) where fuel oils with flashpoints as low as 100 °F (37.8 °C) are used. The requirement replaces existing paragraph (g)(2)(iv)(c) and has been updated to be consistent with paragraph 5.2.5.2 of the 2001 edition of NFPA 495 (Ex. 2-5). </P>
                    <P>Proposed paragraph (g)(2)(iii)(C) would require the employer to ensure that crude oil and crankcase oil are not used as blasting agent ingredients. This requirement is the same as and replaces existing paragraph (g)(2)(iv)(d). </P>
                    <P>
                        Proposed paragraph (g)(2)(iii)(D) would require the employer to ensure that metal powders such as aluminum are kept dry and stored in moisture-resistant or weather-tight containers. Proposed paragraph (g)(2)(iii)(E) would require that solid fuels be used in a manner that minimizes dust explosion hazards as far as possible. These requirements are essentially the same as and replace those in existing paragraph (g)(2)(iv)(e) and are consistent with paragraph 5.2.5.4 of the 2001 edition of NFPA 495 (Ex. 2-5). 
                        <PRTPAGE P="18823"/>
                    </P>
                    <P>Proposed paragraph (g)(2)(iii)(F) would prohibit the use of peroxides and chlorates in mixing blasting agents. The provision is equivalent to and replaces existing paragraph (g)(2)(iv)(f) and is consistent with paragraph 5.2.5.5 of the 2001 edition of NFPA 495 (Ex. 2-5) . </P>
                    <P>Proposed paragraph (g)(2)(iv) sets forth requirements for mixing operations for blasting agents and water gels, slurries, and emulsions classified as Division 1.5 blasting agents. However, water gels, slurries, and emulsions classified as Division 1.1 explosives must meet the requirements of § 1910.119. Paragraph (g)(2)(iv)(A) would require the employer to ensure that empty ammonium nitrate bags are disposed of daily in a safe manner. The provision is equivalent to existing paragraph (g)(2)(vi)(f) and is consistent with paragraph 5.2.8(6) of the 2001 edition of NFPA 495 (Ex. 2-5). </P>
                    <P>Proposed paragraph (g)(2)(iv)(B) would require the employer to ensure that no hot work or open flame is permitted in or around the mixing building unless the equipment and surrounding area have been completely washed down and all oxidizers and fuels removed. This provision is similar to existing paragraph (g)(2)(vi)(g) except the more general term “hot work” has been substituted in the proposal for the term “welding” in the existing standard. As discussed above in Definitions, proposed paragraph (b), “hot work” means any work involving electric or gas welding, cutting, brazing, or similar flame or spark-producing operations. Hot work in general, including welding, can be a hazard in the presence of explosives. The proposed language is consistent with § 1910.119, the process safety management standard, and was recommended by the Petition (Ex. 2-1). </P>
                    <P>Proposed paragraph (g)(2)(iv)(C) would require the employer to ensure that, before welding or repairing hollow shafts of mixing equipment, all blasting agents and their ingredients are removed from the outside and inside of the shaft, and the shaft is vented through an opening at least one-half inch in diameter. This provision is equivalent to and replaces existing paragraph (g)(2)(vi)(h) and is consistent with paragraph 5.2.8(8) of the 2001 edition of NFPA 495 (Ex. 2-5). </P>
                    <P>Proposed paragraph (g)(2)(iv)(D) would require the employer to ensure that no explosives other than blasting agents (Class 1, Division 1.5 explosives) are located inside or within 50 feet (15.25 m) of any building used for the mixing of blasting agents. The provision is equivalent to and replaces existing paragraph (g)(2)(vi)(i) and is consistent with paragraph 5.2.8(9) of the 2001 edition of NFPA 495 (Ex. 2-5). </P>
                    <P>Proposed paragraph (g)(3) sets forth requirements for bulk delivery vehicles transporting blasting agents and their ingredients. Proposed paragraph (g)(3)(i) would require that, in addition to the provisions of proposed paragraph (g)(3), bulk delivery vehicles also meet the requirements of proposed paragraph (e) Transportation of explosives. OSHA has added the new language to make it clear that bulk delivery vehicles transporting blasting agents or their ingredients in bulk form are subject to both proposed paragraph (e) and (g)(3). </P>
                    <P>Proposed paragraph (g)(3)(ii) sets forth requirements for the construction of bulk delivery vehicles. Proposed paragraph (g)(3)(ii)(A) would require the employer to ensure that the vehicle body is constructed of noncombustible materials. Proposed paragraph (g)(3)(ii)(B) would require the employer to ensure that bulk delivery vehicles have enclosed bodies. Proposed paragraph (g)(3)(ii)(C) would require the employer to ensure that all moving parts of the mixing system are designed to prevent heat buildup. Proposed paragraph (g)(3)(ii)(D) would require the employer to ensure that shafts or axles which contact the blasting agent or blasting agent ingredients have outboard bearings with a 1-inch (2.54 cm) minimum clearance between the bearings and outside of the product container. The requirements in proposed paragraph (g)(3)(ii) replace those in existing paragraph (g)(3)(ii)(a) through (c) and are consistent with paragraph 5.3.2(1) through 5.3.2(3) of the 2001 edition of NFPA 495 (Ex. 2-5). The proposal does not retain the portion of existing paragraph (g)(3)(ii)(c) that requires the employer to give particular attention to clearances on moving parts. The intent of the provision is unclear, the issue of clearance is covered in part by proposed paragraphs (g)(3)(ii)(A), (C), and (D), and the provision would be difficult to enforce </P>
                    <P>Proposed paragraph (g)(3)(ii)(E) would require the employer to ensure that when electrical power is supplied by a self-contained generator located on the vehicle, the generator is located where it will not create a fire or ignition hazard. The requirement is similar to and replaces existing paragraph (h)(4)(i)(b) and is consistent with paragraph 6.4.1(2) of the 2001 edition of NFPA 495 (Ex. 2-5), except that the existing requirement and the NFPA provision only apply to vehicles used to deliver water gels. OSHA is proposing to revise the requirement to apply to vehicles used to deliver all types of blasting agents, not just water gels. This change is based on a recommendation in the Petition (Ex. 2-1) and OSHA believes it will improve employee safety by ensuring that the location of the generator will not create a fire or ignition hazard on bulk delivery vehicles transporting all types of blasting agents. The proposed requirement also differs from the existing requirement and the NFPA provision in that they only require a generator to be at a point separate from the where the water gel is discharged, whereas the proposed requirement contains performance language and requires that the generator be located so that it does not create a fire or ignition hazard. </P>
                    <P>Proposed paragraph (g)(3)(ii)(F) would require the employer to ensure that the vehicle is able to safely carry the designated load. This requirement is equivalent to a requirement in existing paragraph (g)(3)(ii)(d) and is consistent with paragraph 5.3.2(4) of the 2001 edition of NFPA 495 (Ex. 2-5). </P>
                    <P>Proposed paragraph (g)(3)(ii)(G) would require the employer to ensure that the vehicle's processing equipment, including its mixing and conveying equipment, is compatible with the relative sensitivity of the materials being handled and does not create a risk of accidental ignition or detonation of the materials. The provision is equivalent to and replaces the corresponding requirement of existing (h)(4)(i)(c) (which refers to existing paragraph (h)(3)(iv)(a)) and consistent with paragraph 6.4.1(3) of the 2001 edition of NFPA 495 (Ex. 2-5) except the existing requirement only applies to vehicles used to deliver water gels. The proposed requirement would apply to vehicles used to deliver all types of blasting agents, not just water gels. OSHA believes that this application is reasonable, is important for employee safety, and reflects current industry practice. </P>
                    <P>
                        Proposed paragraph (g)(3)(ii)(H) would require the employer to ensure that all hollow shafts in the vehicle's processing equipment are constructed to permit venting through an opening at least one-half inch in diameter. Although this is a new requirement, it is already implicitly contained in existing paragraph (g)(3)(v)(b) which requires that, before welding or making repairs to a hollow shaft on bulk delivery and mixing vehicles, the shaft must be vented through a minimum one-half-inch diameter opening. The new requirement was recommended by the Petition (Ex. 2-1) and is consistent with paragraph 5.3.5(2) of the 2001 edition of NFPA 495 (Ex. 2-5) which requires that all oxidizing material be 
                        <PRTPAGE P="18824"/>
                        removed from the outside and inside of the shaft and the shaft is vented with an opening at least one-half inch in diameter. Proposed paragraph (g)(3)(ii)(H) is also consistent with proposed paragraph (g)(3)(v)(B) which requires the employer to ensure that, before welding or repairing a hollow shaft on bulk delivery vehicles, the shaft must be vented with an opening at least one-half inch in diameter. 
                    </P>
                    <P>Proposed paragraph (g)(3)(ii)(I) would require the employer to ensure that suitable means are provided to prevent the flow of fuel oil to the mixer in case of fire. The proposed requirement would also require that, in a gravity-flow system, an automatic spring-loaded shutoff valve with a fusible link be installed. This proposed requirement is the same as existing paragraph (g)(2)(iii)(c) and proposed paragraph (g)(2)(ii)(D) for fixed location mixing of blasting agents. The requirement is being proposed for the construction of bulk delivery vehicles since the hazard of fire is the same as in fixed location mixing of blasting agents. The Petition (Ex. 2-1) also recommended extending this requirement to cover the construction of bulk delivery vehicles. </P>
                    <P>Proposed paragraph (g)(3)(iii) sets forth requirements for the operation of bulk delivery vehicles. Proposed paragraph (g)(3)(iii)(A) would require the employer to ensure that the driver of the vehicle is trained and capable of safely operating the vehicle. Proposed paragraph (g)(3)(iii)(B) would require the employer to ensure that the operator, whether the driver or another employee, is trained and capable of safely operating the mixing, conveying, and related equipment on the vehicle. As described above in the preamble on definitions, proposed paragraph (b), some bulk delivery vehicles only transport blasting agents or their ingredients but have no mixing, conveying or related equipment. Other bulk delivery vehicles include such additional equipment. On these vehicles, this additional equipment may be operated by the driver or by one or more additional employees. Proposed paragraph (g)(3)(iii)(B) requires the employer to ensure that, whoever is the operator of the mixing, conveying and related equipment, they must be trained and capable of operating the equipment in a safe manner. Proposed paragraphs (g)(3)(iii)(A) and (B) are equivalent to and replace requirements in existing paragraphs (g)(3)(iii)(a) and (h)(4)(ii)(b), and are consistent with paragraphs 5.3.3(2) and 6.4.2(1) of the 2001 edition of NFPA 495 (Ex. 2-5). </P>
                    <P>Proposed paragraph (g)(3)(iii)(C) would prohibit smoking, matches, open flames, spark-producing devices, and firearms (except firearms required to be carried by guards) within 25 feet (7.63 m) of bulk delivery vehicles. The proposed paragraph differs from the existing provisions in paragraphs (g)(3)(iii)(c) and (h)(4)(ii)(d) as well as paragraphs 5.3.3(5) and 6.4.2(2) of the 2001 edition of NFPA 495 (Ex. 2-5). The proposal sets a distance of 25 feet (7.63 m) from the vehicle where smoking, matches, open flames, spark producing devices, and firearms are not permitted whereas the existing requirements in paragraphs (g)(3)(iii)(c) and (h)(4)(ii)(d) use the phrase “in or about bulk vehicles” and the NFPA standard uses the phrase “in or around bulk vehicles” to describe the distance or area in which smoking, carrying matches, etc., is not permitted. The proposed change is based on a recommendation from the Petition (Ex. 2-1). OSHA believes the language in the existing requirements is too vague and should be replaced with the more concise restriction of 25 feet. </P>
                    <P>A similar 25-foot restriction is imposed by the Federal Motor Carrier Safety Administration (FMCSA) in its transportation of hazardous materials regulations. At 49 CFR 397.13, FMCSA requires that “[n]o person may smoke or carry a lighted cigarette, cigar, or pipe on or within 25 feet of (a) A motor vehicle which contains Class 1 materials.” However, this FMCSA regulation only applies to motor vehicles on public highways whereas paragraph (g)(3)(iii)(C) in the proposal applies at all times to bulk delivery vehicles, whether or not they are at private facilities or worksites or on public highways. </P>
                    <P>Proposed paragraph (g)(3)(iii)(D) would require the employer to ensure that the transfer of blasting agents or their ingredients from one bulk delivery vehicle to another vehicle is performed at a safe distance away from any blast site where drill holes are loaded or in the process of being loaded. This proposed requirement is similar to existing paragraph (h)(4)(ii)(g) except the existing requirement only applies to vehicles used to deliver water gels whereas the proposed requirement applies to vehicles used to deliver all types of blasting agents. The proposed paragraph is also consistent with paragraph 6.4.2(5) of the 2001 edition of NFPA 495 (Ex. 2-5). OSHA believes that this proposed language is reasonable, necessary to minimize the risk of accidental detonation, and reflects current industry practice. </P>
                    <P>Proposed paragraph (g)(3)(iii)(E) would require the employer to ensure that while the bulk delivery vehicle is in a blast site, caution is exercised to avoid driving the vehicle over hoses or dragging hoses over firing lines, detonating cords, detonator wires or tubes, or explosives. Proposed paragraph (g)(3)(iii)(F) would require the employer to ensure that the driver has the assistance of a second person to act as a guide to ensure the safe movement of the bulk delivery vehicle in the blast site. These provisions are equivalent to and replace the requirements in existing paragraphs (g)(3)(iii)(d) and (h)(4)(ii)(e) and are consistent with paragraphs 5.3.3(6) and 6.4.2(3) of the 2001 edition of NFPA 495 (Ex. 2-5). </P>
                    <P>Proposed paragraph (g)(3)(iii)(G) would prohibit the mixing of blasting agent ingredients while the bulk delivery vehicle is in transit. This proposed requirement is equivalent to and replaces existing paragraphs (g)(3)(iii)(e) and (h)(4)(ii)(f) and is consistent with paragraphs 5.3.3(7) and 6.4.2(4) of the 2001 edition of NFPA 495 (Ex. 2-5). </P>
                    <P>Proposed paragraph (g)(3)(iii)(H) would require the employer to ensure that a positive action parking brake, which sets the wheel brakes on at least one axle, is used during bulk delivery operations. Proposed paragraph (g)(3)(iii)(I) would require the employer to ensure that at least two wheels are chocked whenever necessary to prevent vehicle movement. These provisions are similar to existing paragraph (h)(4)(i)(d) and are consistent with paragraph 6.4.1(4) of the 2001 edition of NFPA 495 (Ex. 2-5). However, unlike the existing requirement, the proposed requirement applies to vehicles used to deliver all types of blasting agents, not just water gels. OSHA believes that this proposed requirement will increase employee safety compared to the existing requirement and reflects current industry practice. </P>
                    <P>Proposed paragraph (g)(3)(iii)(J) would require the employer to ensure that the vehicle is maintained in good mechanical condition. This requirement is equivalent to and replaces corresponding requirements in existing paragraphs (g)(3)(ii)(d) and (g)(6)(vi). The proposed paragraph is also consistent with paragraphs 5.3.2(4), 5.3.3(4), and 5.6.6 of the 2001 edition of NFPA 495 (Ex. 2-5). </P>
                    <P>
                        Proposed paragraph (g)(3)(iv) sets forth requirements for drill holes, primed with electric detonators or other static-electricity sensitive systems that are being pneumatically loaded from bulk delivery vehicles. Paragraph (g)(3)(iv)(A) would require the employer to ensure that the blaster-in-charge evaluates all such systems to determine that they adequately dissipate static 
                        <PRTPAGE P="18825"/>
                        electricity under potential field conditions. The proposed provision substitutes “blaster-in-charge” for the term “qualified person” used in existing paragraph (g)(3)(iv)(c) and is consistent with paragraph 5.3.4(3) of the 2001 edition of NFPA 495 (Ex. 2-5). 
                    </P>
                    <P>Proposed paragraph (g)(3)(iv)(B) would require the employer to ensure that a grounding device is used to prevent the accumulation of static electricity. This provision is equivalent to and replaces existing paragraph (g)(3)(iv)(a) and is consistent with paragraph 5.3.4(1) of the 2001 edition of NFPA 495 (Ex. 2-5). </P>
                    <P>Proposed paragraph (g)(3)(iv)(C) would require the employer to ensure that the discharge hose used has a resistance range sufficient to prevent conducting stray currents, yet is conductive enough to bleed off static electricity buildup. The provision is equivalent to and replaces existing paragraph (g)(3)(iv)(b) and is consistent with paragraph 5.3.4(2) of the 2001 edition of NFPA 495 (Ex. 2-5). </P>
                    <P>Proposed paragraph (g)(3)(v) proposes requirements for repairs to bulk delivery vehicles. Paragraph (g)(3)(v)(A) would prohibit hot work from being performed, or open flames used, on or around any part of the bulk delivery vehicle until all blasting agents and their ingredients have been removed and the vehicle has been completely washed down. This provision is similar to existing paragraph (g)(3)(v)(a) and paragraph 5.3.5(1) of the 2001 edition of NFPA 495 (Ex. 2-5) except in two areas. First, the existing paragraph and the NFPA standard use the term “welding” whereas the proposed paragraph uses the term “hot work.” As discussed above in the explanation of proposed paragraph (b), “hot work” means any work involving electric or gas welding, cutting, brazing, or similar flame or spark-producing operations. Thus, “hot work” includes welding but is a more general term. Use of the term “hot work” in the proposed paragraph broadens the protective scope of the provision and is consistent with the use of the term in other parts of the proposed standard. Second, the existing language requires that welding must not be performed unless “all oxidizer material” has been removed. The proposed language is more general in that it requires “all blasting agents and their ingredients” be removed before hot work is performed. Again, the language of the proposed paragraph broadens the protective scope of the provision. OSHA believes that the broader language in proposed paragraph (g)(3)(v)(A) provides greater safety for employees. Similar language for this proposed provision was recommended by the Petition (Ex. 2-1). </P>
                    <P>Proposed paragraph (g)(3)(v)(B) would require the employer to ensure that before welding or repairing hollow shafts of equipment, all blasting agents and their ingredients are removed from the outside and inside of the shaft and the shaft is vented through an opening at least one-half inch in diameter. The proposed language is similar to and replaces existing paragraph (g)(3)(v)(b) and is consistent with paragraph 5.3.5(2) of the 2001 edition of NFPA 495 (Ex. 2-5). However, the proposed language is more specific than the existing language by requiring that “all blasting agents and their ingredients be removed.” The existing language only requires that the shaft be thoroughly cleaned but does not specify what is to be removed. OSHA believes the proposed language is more understandable and increases workplace safety by explicitly requiring that all blasting agents and their ingredients must be removed before such welding or repair work. </P>
                    <P>Existing paragraphs (g)(4)(v), (g)(4)(vi), and (g)(5) (except for (g)(5)(v) and (vi)) are not retained in the proposed standard because they deal with issues covered by ATF regulations at 27 CFR part 555 subpart K (see preamble discussion above on preemption of storage requirements in § 1910.109 by ATF's regulations). Existing paragraphs (g)(5)(v) and (vi) are retained in the proposed standard in proposed paragraphs (d)(2)(ii)(B) and (g)(1)(i)(B), respectively (see the preamble discussion above on these two proposed paragraphs for a detailed explanation). </P>
                    <P>Existing paragraph (g)(7) requires persons using blasting agents to comply with all applicable provisions of existing paragraph (e), Use of explosives and blasting agents. With the redefining of explosives in the proposed standard to include blasting agents, existing paragraph (g)(7) becomes redundant and therefore is not retained in the proposed rule. </P>
                    <P>
                        <E T="03">Paragraph (h) Small arms ammunition, small arms primers, and smokeless propellants.</E>
                         The requirements of proposed paragraph (h) are very similar to the requirements in existing paragraph (j). Most of the revisions have been made to make proposed paragraph (h) consistent with the 2001 edition of NFPA 495. 
                    </P>
                    <P>Small arms ammunitions are finished consumer products that pose lesser hazards to employees when compared with most other forms of explosives. There are very small quantities of explosive matter sealed in the ammunition shells which, when inadvertently detonated (except when confined as in the firing chamber of a weapon), do not constitute a substantial projection or mass explosion hazard. Therefore, the safe storage and transportation requirements for small arms ammunition are different from other explosives. </P>
                    <P>Proposed paragraph (h)(1) states that proposed paragraph (h) does not apply to in-process temporary storage during the manufacture of small arms ammunition, small arms primers, and smokeless propellants. This is similar to and replaces existing paragraph (j)(1) except that the proposed language uses the phrase “temporary in-process storage” whereas the existing language only uses the phrase “in-process storage.” The term “temporary” has been added to emphasize that in-process storage is limited to storage which is temporary in nature and is an integral and indispensable part of the manufacturing process. However, proposed paragraph (h) does apply to the non-temporary storage of small arms ammunition, small arms primers, and smokeless propellants. In addition, existing paragraph (j)(1) states that existing paragraph (j) does not apply to the intraplant transportation during the manufacture of small arms ammunition, small arms primers, and smokeless propellants. This provision has not been retained in the proposed paragraph because none of the requirements in proposed paragraph (h) apply to such intraplant transportation. </P>
                    <P>Existing paragraph (j)(2)(i) contains a requirement that states: “No quantity limitations are imposed on the storage of small arms ammunition in warehouses, retail stores, and other general occupancy facilities, except those imposed by limitations of storage facilities.” This statement has not been included in proposed paragraph (h) because it is not mandatory in the existing paragraph and does not improve employee safety. </P>
                    <P>
                        Proposed paragraph (h)(2) would require the employer to ensure that small arms ammunition is separated from flammable liquids, flammable solids, and oxidizing materials by a fire barrier wall with at least a 1-hour fire resistance rating or by a distance of at least 25 feet. The proposed requirement replaces the existing paragraph (j)(2)(ii). The existing provision defines “flammable solid” in terms of the classification used by DOT. The proposed rule has dropped the reference to DOT's classification because “flammable solid” is defined in OSHA's Hazard Communication standard at § 1910.1200. 
                        <PRTPAGE P="18826"/>
                    </P>
                    <P>
                        <E T="03">Issue #17:</E>
                         Although proposed paragraph (h)(2) is consistent with paragraph 923 of the 1970 edition of NFPA 495 (Ex. 2-13), it is not consistent with paragraph 13.2.3 of the 2001 edition of NFPA 495 (Ex. 2-5). In the 2001 edition, NFPA has reduced the separation distance from 25 to 15 feet. This reduction in distance may reduce employee protection. OSHA requests specific comments on whether the minimum separation distance between small arms ammunition and flammable liquids, flammable solids, and oxidizing materials should remain 25 feet, be reduced to 15 feet, or be changed to some other distance. 
                    </P>
                    <P>Existing paragraph (j)(2)(iii), which addresses small arms ammunition storage with Class A and Class B explosives, has not been retained in the proposed rule because it is already covered by ATF storage regulations (27 CFR part 555 subpart K) and OSHA does not want to duplicate the regulations of other federal agencies. </P>
                    <P>Proposed paragraph (h)(3) sets forth requirements for smokeless propellants. Paragraph (h)(3)(i)(A) would require the employer to ensure that all smokeless propellants be stored in shipping containers in accordance with DOT regulations at 49 CFR part 173 for smokeless propellants. The proposed provision is consistent with paragraph 13.3.6 of the 2001 edition of NFPA 495 (Ex. 2-5) and substantially the same as existing paragraph (j)(3)(i). </P>
                    <P>Paragraph (h)(3)(i)(B) would require the employer to ensure that no more than 20 pounds of smokeless propellants, in containers not to exceed 1 pound, are displayed in a commercial establishment. The existing standard does not have any provisions restricting the quantity of smokeless propellants that may be displayed in commercial establishments. On March 31, 1972, OSHA revised § 1910.109 to include the following language: “Not more than 20 pounds of smokeless propellants, in containers of 1 pound maximum capacity, shall be displayed in commercial establishments” (37 FR 6577). This is identical to the intent of proposed paragraph (h)(3)(i)(B). However, on October 24, 1978, OSHA removed this language from the explosives standard because it believed it addressed public safety requirements that are subject to the control of local building and fire code officials (43 FR 49726). While OSHA agrees that the provision did cover a public safety issue, it now believes that it also addressed an employee safety issue because employees in commercial establishments that display smokeless propellants are often in close proximity to the propellants. OSHA believes that having no restriction on the quantity of smokeless propellants that can be displayed in commercial establishments is contrary to employee safety. Therefore, OSHA is reinstating this provision in the proposed standard as paragraph (h)(3)(i)(B). </P>
                    <P>
                        <E T="03">Issue #18:</E>
                         Although proposed paragraph (h)(3)(i)(B) is consistent with paragraph 937 of the 1970 edition of NFPA 495 (Ex. 2-13), it is not consistent with paragraph 13.3.8 of the 2001 edition of NFPA 495 (Ex. 2-5), which allows not more than 50 pounds of smokeless propellants to be displayed in a commercial establishment. The 1970 edition appears to provide greater employee safety. OSHA requests specific comments on whether there should be a weight restriction for the display of smokeless propellants in commercial establishments and, if so, whether the maximum weight limit should be 20 pounds, 50 pounds, or some other quantity. 
                    </P>
                    <P>Proposed paragraph (h)(3)(ii) sets forth storage requirements for commercial stocks of smokeless propellants. Proposed paragraph (h)(3)(ii)(A) would require the employer to ensure that quantities of smokeless propellants over 20 pounds and not exceeding 100 pounds be stored in portable wooden boxes having walls at least 1 inch thick. </P>
                    <P>
                        <E T="03">Issue #19:</E>
                         Proposed paragraph (h)(3)(ii)(A) is not consistent with paragraph 13.3.9(1) of the 2001 edition of NFPA 495 (Ex. 2-5) which requires commercial stocks of smokeless propellants exceeding 50 pounds but not over 100 pounds to be stored in portable wooden boxes having walls at least 1 inch thick. The weight restrictions in proposed paragraph (h)(3)(ii)(A) are the same as in paragraph 937 of the 1970 edition of NFPA 495 (Ex. 2-13) and in existing paragraph (j)(3)(iii) (i.e., over 20 pounds but not over 100 pounds). Thus they appear to provide better employee protection than the 2001 edition of NFPA 495. OSHA requests comments on whether the weight restrictions should be over 20 pounds but not over 100 pounds, over 50 pounds but not over 100 pounds, or some other range of weights. In addition, OSHA seeks comments on whether it should allow storage of quantities of 20 to 100 pounds in either portable wooden containers or non-portable cabinets. 
                    </P>
                    <P>
                        Paragraph (h)(3)(ii)(B) would require the employer to ensure that quantities of smokeless propellants over 100 pounds and not exceeding 750 pounds are stored in non-portable cabinets having walls at least 1 inch thick. Paragraph (h)(3)(ii)(B)(
                        <E T="03">1</E>
                        ) would require that not more than 400 pounds be permitted to be stored in any one non-portable cabinet, and paragraph (h)(3)(ii)(B)(
                        <E T="03">2</E>
                        ) would require non-portable cabinets be separated by a distance of at least 25 feet or by a fire barrier wall with at least a 1-hour fire resistance rating. Proposed paragraphs (h)(3)(ii)(B) and (h)(3)(ii)(B)(
                        <E T="03">1</E>
                        ) are similar to existing paragraph (j)(3)(iv). Proposed paragraph (h)(3)(ii)(B)(
                        <E T="03">2</E>
                        ) is a new requirement that OSHA believes would increase employee safety and is contained in paragraph 13.3.9(2) of the 2001 edition of NFPA 495 (Ex. 2-5). 
                    </P>
                    <P>
                        <E T="03">Issue #20:</E>
                         Proposed paragraph (h)(3)(ii)(B) is not consistent with paragraph 13.3.9(2) of the 2001 edition of NFPA 495 (Ex. 2-5), insofar as the NFPA provision requires commercial stocks of smokeless propellants exceeding 100 pounds but not over 800 pounds to be stored in nonportable storage cabinets having walls at least 1 inch thick. The weight restrictions in proposed paragraph (h)(3)(ii)(B) (over 100 pounds but not over 750 pounds) are the same as in paragraph 937 of the 1970 edition of NFPA 495 (Ex. 2-13). Thus they appear to provide better employee protection than the 2001 edition of NFPA 495. OSHA requests comments on whether the weight restrictions for the storage of commercial stocks of smokeless propellants should be over 100 pounds but not over 750 pounds, over 100 pounds but not over 800 pounds, or some other range of weights. 
                    </P>
                    <P>
                        Paragraph (h)(3)(ii)(C) would require the employer to ensure that quantities of smokeless propellants over 750 pounds and not exceeding 5,000 pounds are stored in a building only if the requirements in proposed provisions (h)(3)(ii)(C)(
                        <E T="03">1</E>
                        ) through (h)(3)(ii)(C)(
                        <E T="03">7</E>
                        ) are met. These proposed provisions are new and offer an alternate means of compliance to existing paragraph (j)(3)(v) for commercial stocks of smokeless propellants over 750 pounds but less than 5,000 pounds. If the quantity of smokeless propellants is greater than 750 pounds, and the provisions in proposed paragraph (h)(3)(ii)(C)(
                        <E T="03">1</E>
                        ) through (
                        <E T="03">7</E>
                        ) are not met, storage in accordance with the proposed (h)(3)(iii) is required. If the quantity of smokeless propellants is over 5000 pounds, then the storage requirements in proposed paragraph (h)(3)(iii) must be met. 
                    </P>
                    <P>
                        Paragraph (h)(3)(ii)(C)(
                        <E T="03">1</E>
                        ) would require that the warehouse or storage room not be accessible to unauthorized personnel. Paragraph (h)(3)(ii)(C)(
                        <E T="03">2</E>
                        ) would require that smokeless propellants be stored in nonportable 
                        <PRTPAGE P="18827"/>
                        storage cabinets having wood walls at least 1 inch thick and having shelves with no more than 3 feet of separation between shelves. Paragraph (h)(3)(ii)(C)(
                        <E T="03">3</E>
                        ) would require that no more than 400 pounds be stored in any one cabinet. Paragraph (h)(3)(ii)(C)(
                        <E T="03">4</E>
                        ) would require that cabinets be located against the walls of the storage room or warehouse. Paragraph (h)(3)(ii)(C)(
                        <E T="03">5</E>
                        ) would require the cabinets to be at least 40 feet apart. It further allows that the separation between cabinets shall be permitted to be reduced to 20 feet where barricades twice the height of the cabinets are attached to the wall midway between each cabinet and the barricades extend at least 10 feet outward, and are constructed of either 1/4-inch boiler plate, 2-inch thick wood, brick, or concrete block. Paragraph (h)(3)(ii)(C)(
                        <E T="03">6</E>
                        ) would require that smokeless propellants be separated from flammable liquids, flammable solids, and oxidizing materials by a distance of at least 25 feet or by a fire barrier wall with at least a 1-hour fire resistance rating. Paragraph (h)(3)(ii)(C)(
                        <E T="03">7</E>
                        ) would require that the building be protected by an automatic sprinkler system installed in accordance with § 1910.159. Proposed paragraphs (h)(3)(ii)(C)(
                        <E T="03">1</E>
                        ) to (
                        <E T="03">7</E>
                        ) are based on paragraphs 13.3.9(3)(a) to (g) of the 2001 edition of NFPA 495 (Ex. 2-5). OSHA believes that the level of safety provided by these requirements in proposed paragraph (h)(3)(ii)(C) would provide an equivalent level of employee safety to existing paragraph (j)(3)(v). 
                    </P>
                    <P>Paragraph (h)(3)(iii) would require the employer to ensure that smokeless propellants exceeding 5,000 pounds or not stored in accordance with proposed paragraphs (h)(3)(ii)(A) through (C) of this section are stored in a Type 4 magazine in accordance with ATF regulations for the storage of explosives (27 CFR 555.203 and 555.210). Proposed paragraph (h)(3)(iii) is equivalent to existing paragraph (j)(3)(v) except that it also covers the new requirements in proposed paragraph (h)(3)(ii)(C) for quantities over 750 pounds but not exceeding 5,000 pounds. </P>
                    <P>Proposed paragraph (h)(4) sets forth requirements for small arms ammunition primers. Paragraph (h)(4)(i)(A) would require the employer to ensure that small arms ammunition primers be stored in shipping containers in accordance with the applicable regulations of DOT (49 CFR chapter I) (Ex. 2-8). This is substantially the same as existing paragraph (j)(4)(i). </P>
                    <P>Paragraph (h)(4)(i)(B) would require the employer to ensure that small arms ammunition primers be separated from flammable liquids, flammable solids, and oxidizing materials by a fire barrier wall with at least a 1-hour fire resistance rating or by a distance of at least 25 feet. The proposed requirement is similar to existing paragraph (j)(4)(iii) and is consistent with paragraph 13.5.6(2)(f) of the 2001 edition of NFPA 495 (Ex. 2-5). The existing provision defines “flammable solid” in terms of the classification used by DOT. The proposed rule has dropped the reference to DOT's classification because “flammable solid” is defined in OSHA's Hazard Communication standard at § 1910.1200. </P>
                    <P>
                        Paragraph (h)(4)(i)(C) would require the employer to ensure that no more than 10,000 small arms primers be displayed in a commercial establishment. This requirement is in accordance with paragraph 13.5.5 of the 2001 edition of NFPA 495 (Ex. 2-5). In a notice published in the 
                        <E T="04">Federal Register</E>
                         on October 24, 1978 (43 FR 49726), OSHA revoked a similar provision that it believed addressed public safety requirements subject to the control of local building and fire code officials. As with proposed paragraph (h)(3)(i)(B) discussed above, OSHA agrees that this is a public safety issue but believes that it is also an employee safety issue because employees, as well as the public, can be near primers in a commercial establishment that displays them. Limiting display quantities of small arms primers protects such employees. Therefore, a display limitation is included in proposed paragraph (h)(4)(i)(C). 
                    </P>
                    <P>
                        <E T="03">Issue #21:</E>
                         Proposed paragraphs (h)(3)(i)(B) and (h)(4)(i)(C) place restrictions on the quantity of smokeless propellants and small arms primers, respectively, that can be displayed in commercial establishments. Should OSHA further clarify the quantity limitations for smokeless propellants and small arms primers to allow multiple displays in commercial establishments? If so, what quantities should be allowed and should the quantities be based on the size of the commercial establishment? Should there be a minimum distance between displays to ensure employee safety? Should the same limitations placed on commercial establishments also apply to gun shows? 
                    </P>
                    <P>
                        Proposed paragraph (h)(4)(ii) sets forth requirements for commercial stocks of small arms primers. Paragraph (h)(4)(ii)(A)(
                        <E T="03">1</E>
                        ) and (
                        <E T="03">2</E>
                        ) would require the employer to ensure that, when quantities of 750,000 or less are stored in a building, not more than 100,000 are stored in any one pile and the piles are at least 15 feet (4.6 m) apart. The proposed provisions are equivalent to and replace existing paragraph (j)(4)(iv) and are in accordance with paragraph 13.5.6(1) of the 2001 edition of NFPA 495 (Ex. 2-5). 
                    </P>
                    <P>
                        Paragraph (h)(4)(ii)(B) would require the employer to ensure that quantities of small arms ammunition primers in excess of 750,000 are  stored in a building only if it meets the requirements in proposed paragraphs (h)(4)(ii)(B)(
                        <E T="03">1</E>
                        ) through (h)(4)(ii)(B)(
                        <E T="03">7</E>
                        ). 
                    </P>
                    <P>
                        Paragraph (h)(4)(ii)(B)(
                        <E T="03">1</E>
                        ) would require that the warehouse or storage room not be accessible to unauthorized personnel. Paragraph (h)(4)(ii)(B)(
                        <E T="03">2</E>
                        ) would require primers to be stored in cabinets with no more than 200,000 primers stored in any one cabinet. Paragraph (h)(4)(ii)(B)(
                        <E T="03">3</E>
                        ) would require that shelves in cabinets have a vertical separation of at least 2 feet. Paragraph (h)(4)(ii)(B)(
                        <E T="03">4</E>
                        ) would require cabinets to be located against the walls of the warehouse or storage room. Paragraph (h)(4)(ii)(B)(
                        <E T="03">5</E>
                        ) would require the cabinets be at least 40 feet apart. It further allows that the separation between cabinets may be reduced to 20 feet where barricades twice the height of the cabinets are firmly attached to the wall midway between each cabinet and the barricades extend at least 10 feet outward and are constructed of either 
                        <FR>1/4</FR>
                        -inch boiler plate, 2-inch thick wood, brick, or concrete block. Paragraph (h)(4)(ii)(B)(
                        <E T="03">6</E>
                        ) would require primers to be separated from materials classified by DOT as flammable liquids, flammable solids, and oxidizing materials by a distance of at least 25 feet or by a fire barrier wall with at least a 1-hour fire resistance rating. Paragraph (h)(4)(ii)(B)(
                        <E T="03">7</E>
                        ) would require the building to be protected by an automatic sprinkler system installed in accordance with § 1910.159. Proposed paragraphs (h)(4)(ii)(B)(
                        <E T="03">1</E>
                        ) to (
                        <E T="03">7</E>
                        ) are based on paragraph 13.5.6(2) of the 2001 edition of NFPA 495 (Ex. 2-5). These proposed paragraphs are all new and offer an alternate means of compliance to existing paragraph (j)(4)(v), which requires primers in excess of 750,000 to be stored in magazines. OSHA believes that the level of safety provided by these alternative requirements would provide an equivalent level of employee safety as the existing paragraphs (j)(4)(iv) and (j)(4)(v). 
                    </P>
                    <P>Proposed paragraph (h)(4)(iii) would require the employer to ensure that small arms ammunition primers that are not stored in accordance with proposed paragraph (h)(4)(ii) be stored in a magazine in accordance with ATF regulations for the storage of explosives (27 CFR 555.203 and 555.210). </P>
                    <P>
                        <E T="03">Issue #22:</E>
                         Paragraph 14.1.6 of the 2006 edition of NFPA 495 (Ex. 2-21) 
                        <PRTPAGE P="18828"/>
                        requires that: “The bulk repackaging of small arms ammunition, primers, smokeless propellants, or Black Powder propellants shall not be performed in retail stores.” The proposed standard does not contain this requirement. Should it be included in the standard to protect the safety of employees and, if so, why? 
                    </P>
                    <P>
                        <E T="03">Paragraph (i) Pyrotechnics.</E>
                         Proposed paragraph (i) is reserved for the future development of pyrotechnic regulations. The existing standard has no separate requirements for pyrotechnics, although they are covered, where applicable, by the general explosives provisions of the proposed standard as well as other existing OSHA standards, such as § 1910.119, Process safety management. 
                    </P>
                    <P>
                        <E T="03">Paragraph (j) Training.</E>
                         Proposed paragraph (j) is new and contains proposed training requirements for employees in the explosives industry. OSHA believes that the proposed training requirements will enhance the workplace safety benefits resulting from the proposal's safety provisions. This paragraph has been written to clearly state what training is required and to avoid overlapping training requirements with other standards. 
                    </P>
                    <P>Paragraph (j)(1) would require the employer to provide information and training on safe work practices for each employee prior to or at the time of the employee's initial job assignment involving the manufacture, storage, sale, transportation, handling, or use of explosives, including repair or maintenance of related facilities and equipment. An equivalent training requirement is contained in OSHA's hazard communication standard at § 1910.1200(h)(1). </P>
                    <P>Paragraph (j)(2) would require the employer to ensure that the training provided under proposed paragraph (j) is specific to each employee's unique work duties. It is not the intent of OSHA that each employee should be trained in all aspects of an operation. However, every employee needs to be trained to do his or her specific job safely. </P>
                    <P>Paragraph (j)(3) would reinforce the training requirements in § 1910.1200, the Hazard Communication standard, and further requires the employer to inform each employee of the requirements in § 1910.109 that apply to the employee's work duties. Employers must also make available to employees a copy of the § 1910.109 standard. This will help employees to be better informed about workplace hazards involving explosives. </P>
                    <P>Paragraph (j)(4) would require employers to train employees in safety practices, including applicable emergency procedures, that relate to their work involving explosives and are necessary for their safety. OSHA is proposing this paragraph because it believes that training in safety practices, including applicable emergency procedures, enhances workplace safety. </P>
                    <P>Paragraph (j)(5) would require the employer to retrain employees as necessary to ensure that each employee has the requisite proficiency in the relevant safe work practices whenever there are workplace changes, such as the institution of new or modified procedures or products. Workplace changes can create new safety hazards to employees. OSHA believes that, when such changes create new workplace hazards, retraining is necessary to ensure employee safety and health. </P>
                    <P>Paragraph (j)(6) would require the employer to conduct retraining whenever the employer has reason to believe that there are inadequacies in the employee's knowledge or performance of safe work practices. These reasons may include, but are not limited to, observation of unsafe work practices and errors in operating procedures. Considering the potential catastrophic impact of unsafe work practices in the explosives industry, such unsafe work practices or habits need to be detected and corrected as soon as possible before a tragedy occurs. </P>
                    <P>Paragraph (j)(7) would require the employer to provide information and training in a manner that is understandable to each employee. Differences in language, reading capabilities, and physical challenges may create communication issues in a workplace. It is essential that employers adapt their training methods so that individual employees comprehend the information and training provided. </P>
                    <P>Paragraph (j)(8) would require the employer to determine that each employee has demonstrated proficiency in all aspects of the required training. Such demonstrations help to identify comprehension deficiencies or training failures so they can be corrected in a prompt manner. </P>
                    <P>Paragraph (j)(9) would state that an employer is deemed to be in compliance with a training provision in proposed paragraph (j) of this section for an employee if an identical training provision has been satisfied for that employee under § 1910.1200, Hazard Communication or DOT training requirements (49 CFR part 172) (Ex. 2-8). This provision is consistent with OSHA's goal that duplicative training efforts are not required. </P>
                    <P>All existing “reserved” paragraphs in § 1910.109 would be eliminated in the proposed standard. These existing paragraphs are: (a)(5), (a)(9), (a)(11), (c)(3)(viii), (d)(1)(ii), (d)(2)(ii)(b), (e)(4)(i), (g)(2)(i), (g)(6)(v), (h)(3)(i), (i)(1)(ii)(a), (j)(3)(ii), and (j)(4)(ii). </P>
                    <P>OSHA is proposing to revise the definition of explosives in OSHA's hazard communication standard at § 1910.1200 by replacing it with the definition of explosives in paragraph (b) of the proposed standard. This revision of the definition of explosives in the hazard communication standard would not only make the definition consistent with the one used in the proposed standard, it would also make it consistent with the definition of explosives used by DOT. As discussed earlier, the definition in the proposed standard incorporates the Globally Harmonized System of Classification and Labeling of Chemicals (GHS). Thus, the revised definition of explosives in the hazard communication standard would also incorporate the GHS. </P>
                    <HD SOURCE="HD1">IV. Preliminary Economic and Regulatory Screening Analysis </HD>
                    <HD SOURCE="HD2">Overview </HD>
                    <P>The proposed rule would revise and update the provisions contained in § 1910.109 of the existing Subpart H standards. OSHA has determined that this action is not a significant regulatory action within the meaning of Executive Order 12866. In sum, the proposed rule is anticipated to generate a maximum of $1.5 million in regulatory costs annually. These costs will be at least partially, if not fully, offset by cost savings that may be attributed to the de-regulatory aspects of the proposed revision. </P>
                    <P>The proposed requirements primarily update and clarify regulatory language and address regulatory inconsistencies between OSHA and other Federal agencies. A number of the new requirements are deregulatory in nature, and will yield cost-savings relative to the existing standards. For example, in cases where there is overlap between OSHA and other agencies, the result of this action could potentially be a reduction in regulatory burden as covered employers will no longer have to track and comply with multiple sets of Federal regulations for explosives. </P>
                    <P>
                        OSHA has conducted detailed comparisons of the existing and proposed rules in order to determine which provisions are expected to increase compliance costs, which are expected to be neutral with respect to costs, and which are expected to reduce employers' regulatory burden. Generally, the cost-neutral changes to the existing standard are changes that fall into two categories: (1) Clarifications 
                        <PRTPAGE P="18829"/>
                        to the scope of the standard and (2) some of the overlaps with other OSHA or Federal standards that have precedence over § 1910.109. As an example of the first category, proposed § 1910.109(a)(3)(i) explicitly excludes the construction industry, which is consistent with the OSHA convention that a specific OSHA standard supersedes the more general applicable standard. Activities occurring during construction or demolition would be covered under the part 1926 construction standards rather than the part 1910 general industry standards for explosives and blasting agents. While the explicit exclusion of construction improves clarity, it does not represent any change in regulatory burden. 
                    </P>
                    <P>Several provisions represent changes with deregulatory or cost-saving features. For example, proposed paragraph (b) adds the definition of a “competent person,” which is applied in proposed paragraph (e)(1)(iii), replacing existing paragraph (d)(1)(iii). This existing requirement states that “proper and qualified supervision” needs to be provided for transferring explosives from one vehicle to another, which tends to infer that a supervisor may be required for such a transfer. In the proposed standard, the competent person needed to perform these duties need not be a supervisor, so there will be a cost savings due to differential wage rates associated with the new wording. These cost savings are estimated below. As a second example, the labeling criteria for explosives in proposed paragraph (c)(5), by recognizing the globally harmonized system criteria, may provide a cost savings as these are the same criteria that DOT is using for the transportation of explosives. This will help remove the need for having two different sets of labeling for shipments overseas or within the United States. The proposed rule also eliminates storage requirements. Currently, the employer must follow the storage requirements for explosives in § 1910.109 and ATF's storage regulations in 27 CFR part 555. Under the proposed rule, the employer would only have to comply with the ATF regulations. This reduction in overlapping regulations should result in cost savings for the employer. </P>
                    <HD SOURCE="HD2">Compliance Cost Estimates </HD>
                    <P>There are a few provisions in the proposed standard that may potentially result in cost increases for affected employers. Specifically, these relate to new general provisions in paragraph (c) and new training provisions in paragraph (j), as described below. OSHA estimates that the costs associated with complying with the provisions in paragraph (c) would be $549,375 annually and the training provisions in paragraph (j) would be $908,354 annually. OSHA believes that the cost estimates presented below represent upper bound estimates since the overwhelming majority of employers in the explosives industry are subject to other explosives regulations in addition to § 1910.109. </P>
                    <P>
                        In addition, provisions in current paragraphs (h)(3)(iv)(
                        <E T="03">b</E>
                        ) and (
                        <E T="03">c</E>
                        ) that now apply only to water gels will apply to all blasting agents in proposed paragraphs (g)(2)(ii)(E) and (F). OSHA believes that employers are currently meeting the proposed requirements that both equipment and handling procedures be designed to prevent the introduction of foreign objects or materials and that mixers, pumps, valves, and related equipment be designed to permit regular and periodic flushing, cleaning, dismantling, and inspection. Thus, employers will not incur new costs. OSHA welcomes comments on this assumption. 
                    </P>
                    <HD SOURCE="HD2">New General Provisions in Paragraph (c) </HD>
                    <P>The manufacturers of blasting agents may be affected by new provisions that are contained in proposed paragraph (c). Specifically, the provisions with potential cost implications are: </P>
                    <P>• Requiring that the primary electrical supply to a facility containing explosives be able to be disconnected from a safe remote location [proposed paragraph (c)(2)(i)]; </P>
                    <P>• requiring the removal of explosive materials, prior to the conduct of maintenance or repair activities, from the immediate area where such activities are to take place [proposed paragraph (c)(4)(i)]. </P>
                    <P>These new provisions affect only areas where blasting agents (explosives classified as Division 1.5 explosives) are manufactured or loaded. Since the manufacturing of Division 1.1-1.4 explosives must follow the Process Safety Management (PSM) standard requirements (which already include these types of requirements), manufacturers of blasting agents, who in general also manufacture other explosives, are already likely to be in compliance with the proposed paragraph (c) provisions. </P>
                    <P>
                        Manufacturers of blasting agents are classified in the North American Industry Classification System (NAICS) as code 325920, Explosives Manufacturing. This classification includes all types of explosives manufacturing, not just blasting agent manufacturing. According to the U.S. Department of Commerce's (USDOC, 2003) 
                        <E T="03">2001 County Business Patterns</E>
                         (CBP) database and as shown in Table 1, there are 100 establishments with a total of 7,325 employees in NAICS 325920. These include all types of explosives manufacturing, not just blasting agents. 
                    </P>
                    <P>OSHA estimates that the costs to comply with the above requirements are a function of the size of the establishment. Larger establishments typically: (1) Require a greater investment for disconnecting the primary electrical supply to a facility from a remote location and (2) have larger amounts of maintenance and repair activities where the removal of explosive materials would be required. Thus, to account for the size of the establishment, the compliance costs were expressed on a per-employee basis. </P>
                    <P>
                        In OSHA's professional judgment, a reasonable estimate of the annualized expenses associated with complying with these provisions is $75 per employee. Thus, with 7,325 employees affected by the new general provisions in paragraph (c), the aggregate annual costs of complying with the provisions in (c) are estimated to be $549,375 for all affected facilities. OSHA estimates that providing a remote way to disconnect electricity to a facility would be about $25 per employee or $250 for a facility with 10 employees. Other costs, such as labor costs to remove explosive materials during maintenance and repair activities are estimated to be $50 per employee. For a facility with 10 employees, $500 translates into roughly 25 hours per year (or 2 hours per month) at a wage rate of $20.44 for production and maintenance workers.
                        <SU>3</SU>
                        <FTREF/>
                         This seemed reasonable for maintenance activities that occur during the year. OSHA requests comments on these estimates. 
                    </P>
                    <FTNT>
                        <P>
                            <SU>3</SU>
                             The hourly wage rate (including fringe benefits) is based on the average hourly wage data for 2002 reported in the Bureau of Labor Statistics (BLS) National Industry-Specific Occupational Employment and Wage Estimates (BLS, 2003). The BLS wage data are discussed in greater detail in estimating the costs associated with new training requirements. 
                        </P>
                    </FTNT>
                    <P>
                        These figures are considered to represent upper bound estimates for several reasons. First, the above estimates assume that all explosive manufacturers produce blasting agents, which is not likely to be the case. Second, not all employees at all facilities are involved in making blasting agents. Third, many manufacturers of blasting agents also manufacture other explosives and are already likely to be in compliance with these new requirements in the buildings where the other explosives are handled, since they are subject to PSM 
                        <PRTPAGE P="18830"/>
                        requirements. Finally, the above requirements represent IME or NFPA recommended practices, which many manufacturers follow voluntarily. 
                    </P>
                    <HD SOURCE="HD2">New Training Provisions in Paragraph (j) </HD>
                    <P>The new training requirements include the following: </P>
                    <P>• Providing information and training on safe work practices for each employee prior to or at the time of the employee's initial job assignment involving the manufacture, storage, sale, transportation, handling, or use of explosives, including repair or maintenance of facilities and related equipment; </P>
                    <P>• ensuring that the training provided is specific to each employee's unique work duties; </P>
                    <P>• in addition to the information and training requirements of § 1910.1200, Hazard Communication, informing each employee of the requirements of this section that apply to the employee's work duties and making a copy of the standard available to the employee; </P>
                    <P>• training employees in any safety practices, including applicable emergency procedures that relate to their work and are necessary for their safety; </P>
                    <P>• whenever there are workplace changes, such as the institution of new or modified procedures or products, retraining employees, as necessary, to ensure that each employee has the requisite proficiency in the relevant safe work practices; </P>
                    <P>• retraining employees whenever the employer has reason to believe that there are inadequacies in the employees' knowledge of or performance of safe work practices; </P>
                    <P>• providing information and training in a manner that is understandable to each employee; and </P>
                    <P>• determining that each employee has demonstrated proficiency in all aspects of the required training. </P>
                    <P>The proposed training requirements also state that an employer will be deemed to be in compliance with the training requirements for an employee if an identical training provision has been satisfied for that employee under Section 1910.1200, Hazard Communication, or the DOT training requirements (in 49 CFR part 172). </P>
                    <P>
                        The proposed training requirements could primarily affect employees who come into contact with explosive materials during the manufacturing of explosives, including blasting agents (NAICS 325920) and small arms ammunition (NAICS 332992). In particular, these employees primarily include production employees, as well as installation/maintenance/repair employees and transportation/material moving employees. Some transportation workers (
                        <E T="03">i.e.</E>
                        , truck drivers, packers, and packagers), as well as shipping clerks and order fillers, must already be trained in accordance with DOT requirements, so their employers would already be in compliance with the training required by proposed paragraph (j). In addition, the ATF requirements described earlier will apply to persons involved with handling, storing, and using explosives and pyrotechnics. The ATF requirements have training and qualification criteria and Hazcom training requirements are applicable (so these persons, too, would already have training meeting the requirements of proposed paragraph (j)). 
                    </P>
                    <P>
                        Table 1 presents summary data for the manufacturing of explosives, including blasting agents (NAICS 325920) and small arms ammunition (NAICS 332992). According to the U.S. Department of Commerce's (USDOC, 2003) 2001 
                        <E T="03">County Business Patterns</E>
                         (CBP) database, there are 100 establishments with 7,325 employees in NAICS 325920. An estimated 58 percent are installation/maintenance/repair, production, and transportation/material moving workers (excluding truck drivers, packers, and packagers), based on the Bureau of Labor Statistics (BLS, 2003) 
                        <E T="03">Occupational Employment Statistics (OES) Survey</E>
                         data for 2002 for NAICS 3259. Similarly, 
                        <E T="03">the 2001 CBP</E>
                         database (USDOC, 2003) indicates that there are 111 establishments with 6,717 employees in NAICS 332992. An estimated 66 percent are installation/maintenance/repair, production, and transportation/material moving workers (excluding truck drivers, packers, and packagers) based on the BLS (2003) 
                        <E T="03">OES Survey</E>
                         data for 2002 for NAICS 3329. Thus, combined, there are, after rounding, approximately 8,700 employees who potentially will need training in accordance with proposed paragraph (j). 
                    </P>
                    <P>The estimation of the compliance costs associated with providing the necessary training to these employees has been determined based on: (1) An assessment of the risks faced by each employee given each employee's unique work duties; (2) the provision of training courses to employees that satisfy the hazard communication requirements tailored to explosive chemicals; and (3) the allowance for some additional time to go over emergency evacuation procedures with each employee. The number of chemicals that an employee will be using and exposed to in making blasting agents will be limited in number. Therefore, the training can be more targeted to the chemicals being used, rather than to more general training on all types of chemicals. </P>
                    <P>The compliance cost estimates for the risk assessment are based on the amount of supervisor time (15 minutes per employee) and clerical support time (3 minutes per employee) required to determine the risk of exposure and the appropriate training level for each employee (given each employee's unique work duties), coupled with supervisor and clerical wages. </P>
                    <P>
                        The cost estimates for the necessary training materials are based upon two alternative approaches: (1) Using a self-paced on-line training course (example at 
                        <E T="03">http://www.hazmatschool.com</E>
                        ) or (2) using a self-paced interactive training course available on CD-ROM (example at 
                        <E T="03">http://www.jjkeller.com</E>
                        ). With each of the training approaches, approximately two hours of employee time is expected to be required to complete the course, including time to demonstrate a proficiency with the material learned to a supervisor. Thus, the compliance cost estimates associated with the hazard communication training are calculated based on estimates of the average cost of the training course (about $50 per employee), the amount of training time required for each employee to take the course, clerical support time (3 minutes per employee) to document that the training was taken and successfully completed, coupled with employee and clerical wages. 
                    </P>
                    <P>Finally, the compliance cost estimates associated with explaining the emergency evacuation procedures to each employee are based on the amount of supervisor time (5 minutes per employee) and employee time (5 minutes per employee) required, coupled with supervisor and employee wages. </P>
                    <P>
                        The hourly wage rates for the above employees are based on the average hourly wage data for 2002 and were obtained from the Bureau of Labor Statistics (BLS) 
                        <E T="03">National Industry-Specific Occupational Employment and Wage Estimates</E>
                         (BLS, 2003) for those occupational categories and affected industry sectors where explosives (including blasting agents) and small arms ammunition are manufactured. For benefits data, the March 2000 edition of 
                        <E T="03">Employer Costs for Employee Compensation</E>
                         (BLS, 2000) was used, which indicates a fringe benefits rate of 37 percent of the hourly wage rate. Specifically, average hourly wage rates (including fringe benefits) of $31.34, $20.42, and $16.40 were used for supervisors, employees, and clerical support, respectively, within NAICS 3259 and NAICS 3329. 
                        <PRTPAGE P="18831"/>
                    </P>
                    <P>Combining the training course cost with the labor hour estimates and the hourly wage rates produces a total training cost of approximately $105 per employee. This consists of $9 per employee for the risk assessment, $92 per employee for the training itself, and $4 per employee for the review of the evacuation procedures. For the 8,682 employees that require training, the annual training cost is estimated to be $908,354. Again, these figures are considered to represent upper bound estimates in that most explosives and small arms ammunition manufacturers are believed to be in compliance with these new training requirements since they represent current industry recommended practices, as well as overlap with other OSHA, DOT, and ATF regulations. </P>
                    <P>As described earlier in the Summary and Explanation section of this Notice, for blasting operations conducted near gas, electric, water, telephone, or other similar utilities, proposed paragraph (f)(1)(iv) would require that, prior to the start of blasting operations, employers document the approval given by utility representatives. The current standard, at paragraph (e)(1)(vi), specifies that employers are to notify utility representatives in writing at least 24 hours in advance of the blasting operations. The 2001 edition of NFPA 495 (Ex. 2-5) contains provisions for written notification of utilities that are nearly identical to OSHA's current requirement. </P>
                    <P>Based on a review of the consensus standard indicated above and discussions with industry experts, OSHA believes that most employers maintain a written record of communication with utilities prior to blasting operations. However, even if that were not the case, the incremental employer burden associated with the documentation of approval given by utilities would in all likelihood be modest, representing, at most, three minutes of a clerical employee's time to document and maintain a written record that the utility representative has approved the blasting operation. By applying a conservative estimate that as many as 1,000 blasting operations could be affected by this provision, total costs would equal $820 (1,000 operations × 3 minutes × $16.40/hour). With costs for the other requirements in the proposed standard totaling $1.5 million, the costs for documenting approval of blasting operations near utilities would increase total costs by 0.06 percent and would therefore not present economic feasibility concerns. OSHA requests public comment on this cost issue. </P>
                    <HD SOURCE="HD2">Technological and Economic Feasibility </HD>
                    <P>The proposed requirements primarily update and clarify regulatory language and address regulatory inconsistencies between OSHA standards and those of other Federal agencies. A number of the new requirements are deregulatory in nature, and will yield cost-savings relative to the existing standard. The new requirements that potentially generate costs are consistent with OSHA standards that apply in similar industries. Moreover, OSHA believes that most explosives and small arms ammunition manufacturers are already in compliance with the proposed training requirements since they represent current industry recommended practices, as well as overlap with OSHA's PSM requirements and with the requirements of DOT and ATF regulations. High levels of current compliance with the proposed rule clearly demonstrate that the proposed rule is both technologically and economically feasible. OSHA anticipates that there will be no technological barriers for employers to achieve compliance with the proposed standard. </P>
                    <P>OSHA estimated the cost to employers of the proposed standard and considered whether it would be economically feasible. This analysis is presented in Table 2. For NAICS 325920 and 332992, estimated upper bound compliance costs are significantly less than one percent of revenue, and 2.6 percent and 1.9 percent of profits respectively. Therefore, OSHA has determined that the proposed standard is economically feasible. </P>
                    <HD SOURCE="HD2">Regulatory Flexibility Screening Analysis </HD>
                    <P>In order to determine whether a regulatory flexibility analysis is required under the Regulatory Flexibility Act, OSHA has evaluated the potential economic impacts of this action on small entities. Table 3 and Table 4 present the data used in this analysis to determine whether this standard would have a significant impact on a substantial number of small entities. For purposes of this analysis, OSHA used the Small Business Administration (SBA) definition of a small firm. For NAICS 325920 and NAICS 332992, SBA uses an employment based standard of 500 and 1,000 employees, respectively. </P>
                    <P>OSHA derived estimates of profits and revenues using data from the U.S. Census Bureau and Dun and Bradstreet. As shown in Table 4, upper bound gross compliance costs represent 0.07 percent of the revenues for NAICS 325920 and 0.08 percent of the revenues for NAICS 332992. Upper bound gross compliance costs constitute 1.7 percent of profits for NAICS 325920 and 2.4 percent of profits for NAICS 332992. Based on this evaluation, OSHA certifies that this proposed regulation will not have a significant economic impact on a substantial number of small entities. </P>
                    <HD SOURCE="HD2">Benefits </HD>
                    <P>
                        <E T="03">De-Regulatory Benefits.</E>
                         Several provisions in the proposed standard potentially reduce compliance costs. As noted above, one area of cost savings is in the change in definition of competent person. In the proposed standard, a competent person need not be a supervisor, so there are some cost savings due to differential wage rates. 
                    </P>
                    <P>These cost savings will accrue primarily to employers involved in the manufacturing of explosives, including blasting agents (NAICS 325920) and small arms ammunition (NAICS 332992). The U.S. Department of Commerce's (USDOC, 2003) 2001 County Business Patterns (CBP) database reports that there are 100 establishments with 7,325 employees in NAICS 325920 and 111 establishments with 6,717 employees in NAICS 332992. An estimated 4.1 percent of the employees in NAICS 325920 and 3.9 percent of the employees in NAICS 332992 (based on the Bureau of Labor Statistics (BLS, 2003) Occupational Employment Statistics (OES) Survey data for 2002 for NAICS 3259 and NAICS 3329, respectively) are supervisory personnel responsible for the production and transport of explosive materials. Thus, combined, there are an estimated 561 supervisory employees. </P>
                    <P>The hourly wage rates (including fringe benefits) for all production and transportation personnel and for all production and transportation supervisory personnel are estimated to be $19.85 and $30.88, respectively, for NAICS 3259 and NAICS 3329 combined. These estimates are based on average hourly wage data for 2002, which were obtained from the Bureau of Labor Statistics (BLS) National Industry-Specific Occupational Employment and Wage Estimates (BLS, 2003) for these occupational categories for the affected industry sectors (NAICS 3259 and NAICS 3329) where explosives and small arms ammunition are manufactured. For benefits data, the March 2000 edition of Employer Costs for Employee Compensation (BLS, 2000) was used, which indicates a fringe benefits rate of 37 percent of the hourly wage rate. </P>
                    <P>
                        To the extent that certain responsibilities under the proposal can 
                        <PRTPAGE P="18832"/>
                        be handled by a trained competent person rather than by a supervisor, a savings in labor costs of about $11 per hour can be realized. Depending on the amount of time devoted to these activities, the cost-savings could be quite significant. For example, if each of the 561 supervisors delegate to competent persons the responsibilities of enforcing safety requirements and precautions related to the transferring of explosives from one vehicle to another for approximately 80 hours per year (equivalent to 2 weeks), then the total labor savings would be equal to $0.5 million per year. 
                    </P>
                    <P>The above cost savings estimate applies only to the competent person requirement. OSHA believes that the proposed rule offers many other opportunities for cost savings. For example, while the existing standard covers the storage of explosives (including small arms ammunition, primers, and smokeless propellants), the proposed standard would only cover the storage of small arms ammunition, primers, and smokeless propellants, but not other explosives. OSHA is proposing this change because ATF regulates the storage of explosives (but not the storage of small arms ammunition, primers, and smokeless propellants designed for use in small arms). OSHA has determined that its authority to regulate the storage of these explosives is preempted by ATF's regulations. Therefore, currently an employer must comply with both OSHA and ATF regulations for the storage of explosives while under the proposed standard, the employer would only have to comply with the ATF regulations. This reduction in regulatory burden would likely lead to cost reductions. Another example relates to the exterior markings or placards on vehicles that transport explosives. Currently employers must comply with OSHA's marking and placarding requirements and with those of the DOT. Under the proposed standard, employers would only have to use the markings and placards required by DOT. Again, this reduction in regulatory burden should lead to cost savings by employers. </P>
                    <P>The proposal's elimination of overlapping (and sometimes conflicting) regulatory requirements should save some time each year in assuring compliance with the standard. For example, if the revised standard can save, on average, four hours of review by a lawyer, as well as four hours of review by a health or safety engineer for each establishment, the potential cost savings would equal $108,200. This estimate is based on an hourly wage rate of $87.51 for lawyers and $40.73 for health or safety engineers, which includes 37 percent for fringe benefits applied to the 211 establishments in NAICS 325920 and NAICS 332992 (BLS, Employer Costs for Employee Compensation, 2000; and National Industry-Specific Occupational Employment and Wage Estimates, 2003). </P>
                    <P>
                        <E T="03">Safety Benefits.</E>
                         The potential safety benefits of the proposed standard include a reduction in the number of injuries and deaths associated with accidents involving explosives. In addition, significant property damage often occurs during these accidents. Unlike injury and fatality data, OSHA does not systematically collect data on the amount of property damage which is incurred during workplace accidents. Consequently, OSHA did not attempt to estimate benefits associated with reduced property damage. 
                    </P>
                    <P>To determine the extent to which the proposed standard may reduce the number of deaths and injuries attributable to explosive accidents, OSHA examined its accident investigation reports. The most recent and complete reports cover 1992-2002, and provide detailed information regarding accidents involving explosive materials. During 1992-2002, there were 39 accidents, including 18 that were fatal. </P>
                    <P>As noted above, the proposed standard primarily affects explosive manufacturing that is not covered under PSM. Upon review of the accident reports, OSHA found that seven of the 39 accidents occurred during the manufacture of explosives. Seven fatalities and five hospitalizations occurred as a consequence of these accidents during 1992-2002. Upon further review, OSHA found that at least one of these accidents, which involved two fatalities, could have potentially been prevented through compliance with the new training requirements. Specifically, in this particular accident, the employer did not assure that the employees were wearing appropriate protective clothing or that spark producing devices were not taken into explosive processing areas. </P>
                    <P>
                        Focusing only on this single accident, the proposed standard would have produced $12.6 million in total benefits or $1.3 million annually if it were 100 percent effective at preventing these deaths.
                        <SU>4</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>4</SU>
                             Based on EPA's estimate of a value of $6.1 million for  a statistical life, updated to $6.3 million for inflation (See EPA's Guidelines for Preparing Economic Analyses, EPA 240-R-00-003, September 2000).
                        </P>
                    </FTNT>
                    <GPOTABLE COLS="06" OPTS="L2,i1" CDEF="s40,16,12,12,12,16">
                        <TTITLE>Table 1.—Summary of Explosives Manufacturing and Small Arms Ammunition Manufacturing Industries</TTITLE>
                        <BOXHD>
                            <CHED H="1">NAICS code</CHED>
                            <CHED H="1">
                                Number of establishments 
                                <SU>1</SU>
                            </CHED>
                            <CHED H="1">
                                Number of firms 
                                <SU>1</SU>
                            </CHED>
                            <CHED H="1">
                                Employment 
                                <SU>1</SU>
                            </CHED>
                            <CHED H="1">Total compliance costs</CHED>
                            <CHED H="1">
                                Compliance cost
                                <LI>per firm</LI>
                            </CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">325920</ENT>
                            <ENT>100</ENT>
                            <ENT>63</ENT>
                            <ENT>7,325</ENT>
                            <ENT>$993,888</ENT>
                            <ENT>$15,776</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">332992</ENT>
                            <ENT>111</ENT>
                            <ENT>105</ENT>
                            <ENT>6,717</ENT>
                            <ENT>463,840</ENT>
                            <ENT>4,418</ENT>
                        </ROW>
                        <TNOTE>
                            <SU>1</SU>
                             U.S. Census Bureau, Statistics of U.S. Businesses, 2001.
                        </TNOTE>
                    </GPOTABLE>
                    <GPOTABLE COLS="08" OPTS="L2,i1" CDEF="s40,11,11,11,11,11,11,11">
                        <TTITLE>Table 2.—Economic Feasibility Analysis</TTITLE>
                        <BOXHD>
                            <CHED H="1">NAICS code</CHED>
                            <CHED H="1">
                                Number 
                                <LI>
                                    of firms 
                                    <SU>1</SU>
                                </LI>
                            </CHED>
                            <CHED H="1">
                                Total revenue
                                <LI>
                                    ($1,000) 
                                    <SU>2</SU>
                                </LI>
                            </CHED>
                            <CHED H="1">
                                Profit rate 
                                <SU>3</SU>
                                <LI>(percent)</LI>
                            </CHED>
                            <CHED H="1">
                                Revenue 
                                <LI>per firm</LI>
                                <LI>($1,000)</LI>
                            </CHED>
                            <CHED H="1">
                                Profit 
                                <LI>per firm</LI>
                                <LI>($1,000)</LI>
                            </CHED>
                            <CHED H="1">
                                Compliance 
                                <LI>cost as a</LI>
                                <LI>percent of </LI>
                                <LI>revenue</LI>
                            </CHED>
                            <CHED H="1">
                                Compliance
                                <LI>cost as a</LI>
                                <LI>percent of</LI>
                                <LI>profit</LI>
                            </CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">325920</ENT>
                            <ENT>63</ENT>
                            <ENT>1,582,333</ENT>
                            <ENT>2.45</ENT>
                            <ENT>25,116</ENT>
                            <ENT>615,352</ENT>
                            <ENT>0.06</ENT>
                            <ENT>2.56</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">332992</ENT>
                            <ENT>105</ENT>
                            <ENT>1,051,301</ENT>
                            <ENT>2.28</ENT>
                            <ENT>10,012</ENT>
                            <ENT>228,282</ENT>
                            <ENT>0.04</ENT>
                            <ENT>1.94</ENT>
                        </ROW>
                        <TNOTE>
                            <SU>1</SU>
                             U.S. Census Bureau, Statistics of U.S. Businesses, 2001.
                        </TNOTE>
                        <TNOTE>
                            <SU>2</SU>
                             U.S. Census Bureau, Statistics of U.S. Businesses, 1997, updated to 2002 dollars using the GDP implicit price deflator (NAICS 325920 maps to SIC 2892 and NAICS 332992 maps to SIC 3482)
                            <PRTPAGE P="18833"/>
                        </TNOTE>
                        <TNOTE>
                            <SU>3</SU>
                             Dun &amp; Bradstreet, Industry Norms and Key Business Ratios, 2000/2001. An alternative source of profit data is the IRS Corporation Source Book of Statistics of Income, which suggests profit rates of 5.05 percent and 7.09 percent, respectively. OSHA chose the lower rates reported in Dun &amp; Bradstreet to keep the analysis conservative.
                        </TNOTE>
                    </GPOTABLE>
                    <GPOTABLE COLS="06" OPTS="L2,i1" CDEF="s40,12,16,12,12,16">
                        <TTITLE>Table 3.—Summary of Employment Data and Compliance Cost Estimates for Small Explosives and Small Arms Ammunition Manufacturing Firms</TTITLE>
                        <BOXHD>
                            <CHED H="1">NAICS code</CHED>
                            <CHED H="1">SBA employment size standard</CHED>
                            <CHED H="1">
                                Number of SBA establishments 
                                <SU>1</SU>
                            </CHED>
                            <CHED H="1">
                                Number of 
                                <LI>
                                    SBA firms 
                                    <SU>1</SU>
                                </LI>
                            </CHED>
                            <CHED H="1">Total compliance costs for SBA firms</CHED>
                            <CHED H="1">
                                Compliance cost
                                <LI>per firm</LI>
                            </CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">325920</ENT>
                            <ENT>500</ENT>
                            <ENT>59</ENT>
                            <ENT>52</ENT>
                            <ENT>$269,062</ENT>
                            <ENT>$5,174</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">332992</ENT>
                            <ENT>1,000</ENT>
                            <ENT>101</ENT>
                            <ENT>99</ENT>
                            <ENT>84,178</ENT>
                            <ENT>850</ENT>
                        </ROW>
                        <TNOTE>
                            <SU>1</SU>
                             U.S. Census Bureau, Statistics of U.S. Businesses, 2001.
                        </TNOTE>
                    </GPOTABLE>
                    <NOTE>
                        <HD SOURCE="HED">Note:</HD>
                        <P>The published data for NAICS 332992 (SIC 3482) does not provide information for the &lt; 1,000 employment size class, so the analysis was based on the &lt; 500 size class. Because the overwhelming majority of establishments/firms fall into the &lt; 500 category, OSHA believes the approach is reasonable. Comments are welcome.</P>
                    </NOTE>
                    <GPOTABLE COLS="08" OPTS="L2,i1" CDEF="s40,10,10,10,10,10,16,16">
                        <TTITLE>Table 4.—Screening Analysis for Small Firms Affected by the Rule </TTITLE>
                        <BOXHD>
                            <CHED H="1">NAICS code</CHED>
                            <CHED H="1">
                                Number of
                                <LI>
                                    SBA firms 
                                    <SU>1</SU>
                                </LI>
                            </CHED>
                            <CHED H="1">
                                Total SBA revenue ($1,000) 
                                <SU>2</SU>
                            </CHED>
                            <CHED H="1">
                                Profit rate 
                                <SU>3</SU>
                                <LI>(percent)</LI>
                            </CHED>
                            <CHED H="1">Revenue per firm</CHED>
                            <CHED H="1">Profit per firm</CHED>
                            <CHED H="1">
                                Compliance cost
                                <LI>as a percent</LI>
                                <LI>of revenue</LI>
                            </CHED>
                            <CHED H="1">
                                Compliance cost
                                <LI>as a percent</LI>
                                <LI>of profit</LI>
                            </CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">325920</ENT>
                            <ENT>52</ENT>
                            <ENT>383,261</ENT>
                            <ENT>4.16</ENT>
                            <ENT>$7,370,406</ENT>
                            <ENT>$306,609</ENT>
                            <ENT>0.07</ENT>
                            <ENT>1.69</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">332992</ENT>
                            <ENT>99</ENT>
                            <ENT>105,296</ENT>
                            <ENT>3.31</ENT>
                            <ENT>1,063,595</ENT>
                            <ENT>35,205</ENT>
                            <ENT>0.08</ENT>
                            <ENT>2.42</ENT>
                        </ROW>
                        <TNOTE>
                            <SU>1</SU>
                             U.S. Census Bureau, Statistics of U.S. Businesses, 2001.
                        </TNOTE>
                        <TNOTE>
                            <SU>2</SU>
                             U.S. Census Bureau, Statistics of U.S. Businesses, 1997, updated to 2002 dollars using the GDP implicit price deflator (NAICS 325920 maps to SIC 2892 and NAICS 332992 maps to SIC 3482).
                        </TNOTE>
                        <TNOTE>
                            <SU>3</SU>
                             Dun &amp; Bradstreet, Industry Norms and Key Business Ratios, 2000/2001. An alternative source of profit data is the IRS Corporation Source Book of Statistics of Income, which suggests profit rates of 5.05 percent and 7.09 percent, respectively. OSHA chose the lower rates reported in Dun &amp; Bradstreet to keep the analysis conservative.
                        </TNOTE>
                    </GPOTABLE>
                    <NOTE>
                        <HD SOURCE="HED">Note:</HD>
                        <P>The published data for NAICS 332992 (SIC 3482) does not provide information for the &lt; 1,000 employment size class, so the analysis was based on the &lt; 500 size class. Because the overwhelming majority of establishments/firms fall into the &lt; 500 category, OSHA believes the approach is reasonable. Comments are welcome.</P>
                    </NOTE>
                    <HD SOURCE="HD1">V. Environmental Impact Analysis </HD>
                    <P>
                        The proposed standard has been reviewed in accordance with the requirements of the National Environmental Policy Act (NEPA) of 1969 (42 U.S.C. 4321 
                        <E T="03">et seq.</E>
                        ), the regulations of the Council on Environmental Quality (CEQ) (40 CFR part 1500), and DOL NEPA Procedures (29 CFR part 11). The provisions of the proposed standard focus on the reduction and avoidance of employee injuries and deaths during the storage, handling, transportation and use of explosives, including blasting agents and pyrotechnics. OSHA has determined that these proposed provisions will have no significant effect on air, water, or soil quality, plant or animal life, the use of land, or other aspects of the environment. 
                    </P>
                    <HD SOURCE="HD1">VI. Paperwork Reduction Act </HD>
                    <P>
                        After review of the proposed revisions to the Explosives Standard, OSHA has identified one new collection of information (paperwork) requirement and determined other paragraphs are not paperwork requirements or impose no burden hours or costs on employers. Collection of information requirements are subject to review by the Office of Management and Budget (OMB) under the Paperwork Reduction Act of 1995 (PRA95), 44 U.S.C. 3501 
                        <E T="03">et. seq.,</E>
                         and its regulation at 5 CFR part 1320. PRA95 defines a collection of information to mean “the obtaining, causing to be obtained, soliciting, or requiring the disclosure to third parties or the public of facts or opinions by or for an agency regardless of form or format” (44 U.S.C. 3502(3)(A)). 
                    </P>
                    <P>The new paperwork requirement, contained in proposed paragraph (f)(1)(iv), requires employers to document approval from the utility prior to blasting operations that are being conducted in close proximity to gas, electric, water, telephone, or other similar utilities. Documentation may be in the form of a fax, email, or record of a conversation. </P>
                    <P>The title, summary, description of the need for and proposed use of the collection of information requirement, description of respondents, and the frequency of response of the information collection requirement are described below with an estimate of the annual cost and reporting burden as required by § 1320.5(a)(1)(iv) and § 1320.8(d)(2). The reporting burden includes the time for reviewing instructions, gathering and maintaining the data needed, and completing and reviewing the collection of information. </P>
                    <P>OSHA has a particular interest in comments on the following issues: </P>
                    <P>• Whether the proposed collection of information requirement is necessary for the proper performance of the Agency's functions to protect workers, including whether the information is useful; </P>
                    <P>• The accuracy of OSHA's estimate of the burden (time and costs) of the collection of information requirement, including the validity of the methodology and assumptions used; </P>
                    <P>• The quality, utility, and clarity of the information collected; and </P>
                    <P>• Ways to minimize the burden on employers who must comply; for example, by using automated or other technological information-collection and transmission techniques. </P>
                    <P>
                        <E T="03">Title:</E>
                         Explosives (29 CFR 1910.109). 
                    </P>
                    <P>
                        <E T="03">Summary:</E>
                         Proposed paragraph (f)(1)(iv) would require that whenever blasting operations are being conducted in close proximity to gas, electric, water, telephone, or other similar utilities, the employer will not commence such blasting operations until receiving and documenting approval from the appropriate utility representatives. 
                    </P>
                    <P>
                        <E T="03">Description:</E>
                         The current Standard does not require a response from the 
                        <PRTPAGE P="18834"/>
                        utility prior to the employer beginning blasting; this could lead to the endangerment of employees working in blasting operations near utility lines. Obtaining and documenting approval from the utility prior to blasting will better ensure employee safety during these operations. 
                    </P>
                    <P>
                        <E T="03">Respondents:</E>
                         Employers in general industry who conduct blasting operations near utilities. 
                    </P>
                    <P>
                        <E T="03">Frequency:</E>
                         On occasion. Employer will contact the utility prior to blasting near gas, electric, water, telephone, or other utilities. 
                    </P>
                    <P>
                        <E T="03">Average Time per Response:</E>
                         OSHA estimates on average, the employer will spend 3 minutes (.05 hour) to document and maintain written approval that the utility representative has approved the blasting operation. 
                    </P>
                    <P>
                        <E T="03">Total Burden Hours:</E>
                         25. 
                    </P>
                    <P>
                        <E T="03">Costs</E>
                         (purchase of capital/startup costs): None. 
                    </P>
                    <P>The Agency has submitted an information collection request (ICR) for the proposed standard to OMB for review and approval of the collection of information contained in proposed paragraph (f)(1)(iv). </P>
                    <P>Other proposed paragraphs reviewed for paperwork are not new; or, are not collection of information requirements for the following reasons: (1) The paperwork requirements are contained in existing standards; (2) the requirements are exempt from the definition of a collection of information, since the Government provides specific language for signs/labels for public disclosure (5 CFR 1320.3(c)(2)); (3) the requirements are usual and customary business activities that impose no new burden hours or costs on employers (5 CFR 1320.3(b)(2)); and, (4) the training provisions are performance-oriented, and are not considered collections of information. </P>
                    <P>
                        Proposed paragraphs containing paperwork requirements that are in existing standards include: § 1910.109(c)(5) 
                        <E T="03">Labels,</E>
                         § 1910.109(d)(3) 
                        <E T="03">Storage of ammonium nitrate in bags and containers,</E>
                         and § 1910.109(e)(2) 
                        <E T="03">Vehicles.</E>
                         Proposed paragraphs that provide specific language for labels and/or signs include: again, § 1910.109(c)(5) 
                        <E T="03">Labels,</E>
                         § 1910.109(d)(4) 
                        <E T="03">Storage of bulk ammonium nitrate,</E>
                         and § 1910.109(f)(1) and (3) 
                        <E T="03">Use of explosives for blasting.</E>
                         Proposed paragraph § 1910.109(e)(1) 
                        <E T="03">Transportation of explosives,</E>
                         contains a notification requirement that is the same as the notification requirement in paragraph 7.1.7 of the 2001 edition of NFPA 495 (Ex. 2-5). Since employers routinely follow the NFPA Codes, the notification is a usual and customary business practice. Finally, paragraphs § 1910.109(f)(3) 
                        <E T="03">Use of explosives for blasting,</E>
                         § 1910.109(g)(3) 
                        <E T="03">Bulk delivery vehicles,</E>
                         and § 1910.109(j) 
                        <E T="03">Training,</E>
                         contain training requirements that are not counted since these provisions provide the employer a “performance-oriented” approach. 
                    </P>
                    <P>
                        Interested parties who wish to comment on OSHA's ICR seeking OMB approval for paragraph (f)(1)(iv), or OSHA's determination that proposed paragraphs in the preceding paragraph impose no new burden hours or costs on employers must send their written comments to the Office of Information and Regulatory Affairs, Attn: OMB Desk Officer for OSHA, Office of Management and Budget, Room 10235, 726 Jackson Place, NW., Washington, DC 20503. The Agency also encourages commenters to submit their comments on this paperwork determination to OSHA along with their other comments on the proposed rule. To read or download the complete ICR, go to 
                        <E T="03">http://www.regulations.gov</E>
                         (Docket No. OSHA-S031-2006-0665) or 
                        <E T="03">http://dockets.osha.gov</E>
                         (Docket No. S-031). You also may obtain an electronic copy of the complete ICR at 
                        <E T="03">http://www.reginfo.gov.</E>
                         Click on “Inventory of Approved Information Collections, Collections Under Review, Recently Approved/ Expired,” then scroll under “Currently Under Review” to Department of Labor (DOL) to view all of the DOL's ICRs, including those ICRs submitted for proposed rulemakings. To make inquiries, or to request other information, contact Mr. Todd Owen, OSHA, Directorate of Standards and Guidance, Room N-3609, U.S. Department of Labor, 200 Constitution Avenue, NW., Washington, DC 20210; telephone (202) 693-2222. 
                    </P>
                    <HD SOURCE="HD1">VII. Federalism </HD>
                    <P>OSHA has reviewed this proposed rule in accordance with the Executive Order on Federalism (Executive Order 13132, 64 FR 43255, August 10, 1999), which requires that agencies, to the extent possible, refrain from limiting State policy options, consult with States prior to taking any actions that would restrict State policy options, and take such actions only when there is clear constitutional authority and the presence of a problem of national scope. Executive Order 13132 provides for preemption of State law only if there is a clear congressional intent for the Agency to do so. Any such preemption is to be limited to the extent possible. </P>
                    <P>
                        Section 18 of the OSH Act (29 U.S.C. 651 
                        <E T="03">et seq.</E>
                        ) expresses Congress's intent to preempt State laws where OSHA has promulgated occupational safety and health standards. Under the OSH Act, a State can avoid preemption on issues covered by Federal standards only if it submits, and obtains Federal approval of, a plan for the development of such standards and their enforcement (State-Plan State). 29 U.S.C. 667. Occupational safety and health standards developed by such State-Plan States must, among other things, be at least as effective in providing safe and healthful employment and places of employment as the Federal standards. Subject to these requirements, State-Plan States are free to develop and enforce under State law their own requirements for safety and health standards. 
                    </P>
                    <P>This proposed rule complies with Executive Order 13132. As Congress has expressed a clear intent for OSHA standards to preempt State job safety and health rules in areas addressed by OSHA standards in States without OSHA-approved State Plans, this proposed rule would limit State policy options in the same manner as all OSHA standards. In States with OSHA-approved State Plans, this action does not significantly limit State policy options. </P>
                    <P>State comments are invited on this proposal and will be fully considered prior to promulgation of a final rule. </P>
                    <HD SOURCE="HD1">VIII. State Plan Standards </HD>
                    <P>
                        When Federal OSHA promulgates a new standard or more stringent amendment to an existing standard, the 26 States and U.S. Territories with their own OSHA-approved occupational safety and health plans must revise their standards to reflect the new standard or amendment, or show OSHA why there is no need for action, e.g., because an existing State standard covering this area is already “at least as effective” as the new Federal standard or amendment. 29 CFR 1953.5(a). The State standard must be at least as effective as the final Federal rule, must be applicable to both the private and public (State and local government employees) sectors, and must be completed within six months of the publication date of the final Federal rule. When OSHA promulgates a new standard or amendment to a standard which does not impose additional or more stringent requirements than an existing standard, States are not required to revise their standards, although OSHA may encourage them to do so. The 26 States and territories with OSHA-approved State Plans are: Alaska, Arizona, California, Connecticut (plan covers only State and local government employees), Hawaii, Indiana, Iowa, Kentucky, Maryland, Michigan, Minnesota, Nevada, New Mexico, New Jersey (plan covers only State and local 
                        <PRTPAGE P="18835"/>
                        government employees), New York (plan covers only State and local government employees), North Carolina, Oregon, Puerto Rico, South Carolina, Tennessee, Utah, Vermont, Virginia, Virgin Islands (plan covers only State and local government employees), Washington, and Wyoming. 
                    </P>
                    <HD SOURCE="HD1">IX. Unfunded Mandates </HD>
                    <P>
                        OSHA reviewed this proposed rule according to the Unfunded Mandates Reform Act of 1995 (UMRA) (2 U.S.C. 1501 
                        <E T="03">et seq.</E>
                        ) and Executive Order 12875 and determined that this rule does not include any Federal mandate that may result in increased expenditures by State, local, and tribal governments, or increased expenditures by the private sector of more than $100 million in any year. 
                    </P>
                    <HD SOURCE="HD1">X. Public Participation </HD>
                    <HD SOURCE="HD2">Submission of Comments and Access to Docket </HD>
                    <P>OSHA invites comments on all aspects of the proposed rule. Throughout this document OSHA has invited comment on specific issues and requested information and data about practices at your establishment and in your industry. OSHA will carefully review and evaluate these comments, information and data, as well as all other information in the rulemaking record, to determine how to proceed. </P>
                    <P>
                        You may submit comments in response to this document (1) electronically at 
                        <E T="03">http://www.regulations.gov,</E>
                         which is the Federal eRulemaking Portal; (2) by facsimile (FAX); or (3) by hard copy. All comments, attachments and other material must identify the Agency name and the OSHA docket number for this rulemaking (Docket No. OSHA-2007-0032). You may supplement electronic submissions by uploading document files electronically. If, instead, you wish to mail additional materials in reference to an electronic or fax submission, you must submit three copies to the OSHA Docket Office (see 
                        <E T="02">ADDRESSES</E>
                         section). The additional materials must clearly identify your electronic comments by name, date, and docket number so OSHA can attach them to your comments.
                    </P>
                    <P>Because of security-related procedures, the use of regular mail may cause a significant delay in the receipt of comments. For information about security procedures concerning the delivery of materials by hand, express delivery, messenger or courier service, please contact the OSHA Docket Office at (202) 693-2350 (TTY (877) 889-5627). </P>
                    <P>
                        Comments and submissions in response to this 
                        <E T="04">Federal Register</E>
                         notice are posted without change at 
                        <E T="03">http://www.regulations.gov</E>
                         (Docket No. OSHA-2007-0032). Therefore, OSHA cautions commenters about submitting personal information such as social security numbers and date of birth. 
                    </P>
                    <P>
                        Exhibits referenced in this 
                        <E T="04">Federal Register</E>
                         document are posted in both Docket No. OSHA-S031-2006-0665 (which is available at 
                        <E T="03">http://www.regulations.gov</E>
                        ) and OSHA Docket No. S-031 (which is available at 
                        <E T="03">http://dockets.osha.gov.</E>
                    </P>
                    <P>
                        Although all submissions in response to this 
                        <E T="04">Federal Register</E>
                         notice and exhibits referenced in this notice are listed in the 
                        <E T="03">http://www.regulations.gov</E>
                         and 
                        <E T="03">http://dockets.osha.gov</E>
                         indexes, some information (e.g., copyrighted material) is not publicly available to read or download from those Web pages. All submissions and exhibits, including copyrighted material, are available for inspection and copying at the OSHA Docket Office (see 
                        <E T="02">ADDRESSES</E>
                         section). Information on using the 
                        <E T="03">http://www.regulations.gov</E>
                         Web page to submit comments and access dockets is available at the Web page's User Tips link. Contact the OSHA Docket Office for information about materials not available through the Web pages and for assistance in using the internet to locate docket submissions. 
                    </P>
                    <P>
                        Electronic copies of this 
                        <E T="04">Federal Register</E>
                         document are available at 
                        <E T="03">http://regulations.gov.</E>
                         This document, as well as news releases and other relevant information, also are available at OSHA's Web page at 
                        <E T="03">http://www.osha.gov.</E>
                    </P>
                    <HD SOURCE="HD2">Requests for Informal Public Hearings </HD>
                    <P>
                        Under section 6(b)(3) of the OSH Act and 29 CFR 1911.11, members of the public may request an informal hearing by following the instructions under the section of this 
                        <E T="04">Federal Register</E>
                         notice titled 
                        <E T="02">ADDRESSES</E>
                        . These requests must include the objections to the proposal that warrant a hearing. The hearing requests must: 
                    </P>
                    <P>• Include the name and address of the party requesting the hearing; </P>
                    <P>• Ensure that the request is sent or postmarked no later than June 12, 2007; </P>
                    <P>• Number each objection separately; </P>
                    <P>• Specify with particularity the grounds for each objection; </P>
                    <P>• Include a detailed summary of the evidence supporting each objection which the requester plans to offer at the requested hearing. </P>
                    <LSTSUB>
                        <HD SOURCE="HED">XI. List of Subjects in 29 CFR Part 1910 </HD>
                        <P>Blasting agents, Explosives, Health, Occupational safety and health, Pyrotechnics, Safety. </P>
                    </LSTSUB>
                    <HD SOURCE="HD1">XII. Authority and Signature </HD>
                    <P>This document was prepared under the authority of Edwin G. Foulke, Jr., Assistant Secretary of Labor for Occupational Safety and Health, U.S. Department of Labor, 200 Constitution Avenue, NW., Washington, DC 20210. Pursuant to Sections 4, 6, and 8 of the OSH Act of 1970 (29 U.S.C. 653, 655, 657), Secretary of Labor's Order No. 5-2002 (67 FR 65008), and 29 CFR part 1911, it is hereby amending subpart H of 29 CFR part 1910 as set forth below. </P>
                    <SIG>
                        <DATED>Signed at Washington, DC on April 4, 2007. </DATED>
                        <NAME>Edwin G. Foulke, Jr., </NAME>
                        <TITLE>Assistant Secretary of Labor for Occupational Safety and Health. </TITLE>
                    </SIG>
                    <HD SOURCE="HD1">XIII. Amendments to Standards </HD>
                    <P>For the reasons set forth in the preamble, OSHA proposes to amend Part 1910 of Title 29 of the Code of Federal Regulations as follows: </P>
                    <PART>
                        <HD SOURCE="HED">PART 1910—[AMENDED] </HD>
                        <SUBPART>
                            <HD SOURCE="HED">Subpart A—General </HD>
                        </SUBPART>
                        <P>1. The authority citation for Subpart A of part 1910 is revised to read as follows: </P>
                        <AUTH>
                            <HD SOURCE="HED">Authority:</HD>
                            <P>Secs. 4, 6, and 8 of the Occupational Safety and Health Act of 1970 (29 U.S.C. 653, 655, 657); Secretary of Labor's Order No. 12-71 (36 FR 8754), 8-76 (41 FR 25059), 9-83 (48 FR 35736), 1-90 (55 FR 9033), 6-96 (62 FR 111), or 5-2002 (67 FR 65008), as applicable. </P>
                        </AUTH>
                        <EXTRACT>
                            <P>Sections 1910.7 and 1910.8 also issued under 29 CFR part 1911. Section 1910.7(f) also issued under 31 U.S.C. 9701, 29 U.S.C. 9a, 5 U.S.C. 553; Pub. L. 106-113 (113 Stat. 1501A-222); and OMB Circular A-25 (dated July 8, 1993) (58 FR 38142, July 15, 1993). </P>
                        </EXTRACT>
                          
                        <P>2. Section 1910.6 is amended by removing and reserving paragraphs (k)(9), (q)(17), and (q)(25). </P>
                        <SUBPART>
                            <HD SOURCE="HED">Subpart H—Hazardous Materials </HD>
                        </SUBPART>
                        <P>3. The authority citation for subpart H of part 1910 is revised to read as follows: </P>
                        <AUTH>
                            <HD SOURCE="HED">Authority:</HD>
                            <P>Sections 4, 6, and 8 of the Occupational Safety and Health Act of 1970 (29 U.S.C. 653, 655, 657); Secretary of Labor's Order No. 12-71 (36 FR 8754), 8-76 (41 FR 25059), 9-83 (48 FR 35736), 1-90 (55 FR 9033), 6-96 (62 FR 111), 3-2000 (65 FR 50017), or 5-2002 (67 FR 65008), as applicable; and 29 CFR part 1911. </P>
                        </AUTH>
                        <EXTRACT>
                            <P>Sections 1910.103, 1910.106 through 1910.111, and 1910.119, 1910.120, and 1910.122 through 126 also issued under 29 CFR part 1911. </P>
                        </EXTRACT>
                          
                        <PRTPAGE P="18836"/>
                        <P>Section 1910.119 also issued under section 304, Clean Air Act Amendments of 1990 (Pub. L. 101-549), reprinted at 29 U.S.C. 655 Note. </P>
                        <P>Section 1910.120 also issued under section 126, Superfund Amendments and Reauthorization Act of 1986 as amended (29 U.S.C. 655 Note), and 5 U.S.C. 553. </P>
                        <P>4. Section 1910.109 of subpart H is revised to read as follows: </P>
                        <SECTION>
                            <SECTNO>§ 1910.109 </SECTNO>
                            <SUBJECT>Explosives. </SUBJECT>
                            <P>
                                (a) 
                                <E T="03">Scope.</E>
                                 (1) This section applies to the manufacture, storage, sale, transportation, handling, and use of explosives, including blasting agents and pyrotechnics. 
                            </P>
                            <P>(2) The employer also shall comply with § 1910.119, Process Safety Management, for operations involving the manufacture of explosives as defined in paragraph (b) of this section. However, blasting agents as defined in paragraph (b) of this section, including water gels, slurries, and emulsions classified as Division 1.5 explosives, are not covered by § 1910.119. </P>
                            <P>(3) This section does not apply to: </P>
                            <P>(i) Construction work covered by 29 CFR part 1926; </P>
                            <P>
                                (ii) The use of explosives in medicines and medicinal agents in the forms prescribed by the official 
                                <E T="03">United States Pharmacopeia and the National Formulary</E>
                                 (USP-NF); or 
                            </P>
                            <P>(iii) The sale and use of consumer and public display pyrotechnics. </P>
                            <P>
                                (b) 
                                <E T="03">Definitions applicable to this section.</E>
                                  
                                <E T="03">Blast area</E>
                                 means the area of a blast within the influence of flying rock or other debris, gases, and concussion. 
                            </P>
                            <P>
                                <E T="03">Blast site</E>
                                 means the area where explosives are handled during the preparation and loading of drill holes, including 50 feet (15.2 m) in all directions from the perimeter formed by loaded holes. The 50 foot distance requirement applies in all directions along the full depth of the drill hole. 
                            </P>
                            <P>
                                <E T="03">Blaster-in-charge</E>
                                 means the person in charge of the handling, loading, and firing of explosives within the blast site and blast area. 
                            </P>
                            <P>
                                <E T="03">Blasting agent</E>
                                 means any material or mixture intended for blasting that is classified as a Division 1.5 explosive. 
                            </P>
                            <P>
                                <E T="03">Bulk delivery vehicle</E>
                                 means any vehicle that transports blasting agents or their ingredients in bulk form including bulk delivery vehicles that are capable of mixing the ingredients to form blasting agents and loading the blasting agents directly into drill holes. 
                            </P>
                            <P>
                                <E T="03">Competent person</E>
                                 means an employee designated by the employer who, by way of training and experience, is knowledgeable of applicable standards, is capable of identifying workplace hazards relating to explosives, and has authority to take appropriate corrective actions to control such hazards. 
                            </P>
                            <P>
                                <E T="03">Detonator</E>
                                 means any device containing an initiating or primary explosive that is used for initiating detonation in another explosive material. A detonator may not contain more than .35 ounces (10 g) of total explosives by weight, excluding ignition or delay charges. The term includes, but is not limited to, electric blasting caps of instantaneous and delay types, electronic detonators, blasting caps for use with safety fuse, detonating cord delay connectors, and nonelectric instantaneous and delay blasting caps which use detonating cord, shock tube, or any other replacement for electric leg wires. 
                            </P>
                            <P>
                                <E T="03">Electric detonator</E>
                                 means a detonator designed for, and capable of, initiation by means of an electric current. 
                            </P>
                            <P>
                                <E T="03">Electronic detonator</E>
                                 means a detonator that utilizes stored electrical energy as a means of powering an electronic timing delay element/module and that provides initiation energy for firing the base charge. 
                            </P>
                            <P>
                                <E T="03">Emulsion</E>
                                 means an explosive that either contains substantial amounts of oxidizer dissolved in water droplets that are surrounded by an immiscible fuel, or contains droplets of an immiscible fuel that are surrounded by water containing substantial amounts of oxidizer. Emulsions, depending on their properties, are classified as Division 1.1 explosives or Division 1.5 blasting agents. 
                            </P>
                            <P>
                                <E T="03">Explosive</E>
                                 means any device, or liquid or solid chemical compound or mixture, the primary or common purpose of which is to function by explosion. 
                            </P>
                            <P>(i) The term “explosive” includes all material included as a Class 1 explosive by DOT in accordance with 49 CFR chapter I. The term includes, but is not limited to, dynamite, black powder, pellet powders, detonators, blasting agents, initiating explosives, blasting caps, safety fuse, fuse lighters, fuse igniters, squibs, cordeau detonant fuse, instantaneous fuse, igniter cord, igniters, pyrotechnics, special industrial explosive materials, small arms ammunition, small arms ammunition primers, smokeless propellant, cartridges for propellant-actuated power devices, and cartridges for industrial guns. </P>
                            <P>(ii) Explosives are classified using the same classification system as used by DOT (see 49 CFR 173.50). Explosives are classified into the following divisions: </P>
                            <P>
                                (A) 
                                <E T="03">Division 1.1</E>
                                 consists of explosives that have a mass explosion hazard. A mass explosion is one which affects almost the entire load instantaneously. 
                            </P>
                            <P>
                                (B) 
                                <E T="03">Division 1.2</E>
                                 consists of explosives that have a projection hazard but not a mass explosion hazard. 
                            </P>
                            <P>
                                (C) 
                                <E T="03">Division 1.3</E>
                                 consists of explosives that have a fire hazard and either a minor blast hazard or a minor projection hazard or both, but not a mass explosion hazard. 
                            </P>
                            <P>
                                (D) 
                                <E T="03">Division 1.4</E>
                                 consists of explosives that present a minor explosion hazard. The explosive effects are largely confined to the package and no projection of fragments of appreciable size or range is to be expected. An external fire must not cause virtually instantaneous explosion of almost the entire contents of the package. 
                            </P>
                            <P>
                                (E) 
                                <E T="03">Division 1.5</E>
                                 consists of very insensitive explosives. This division is comprised of substances which have a mass explosion hazard but are so insensitive that there is very little probability of initiation or of transition from burning to detonation under normal conditions. (The probability of transition from burning to detonation is greater when large quantities are involved.) 
                            </P>
                            <P>
                                (F) 
                                <E T="03">Division 1.6</E>
                                 consists of extremely insensitive articles which do not have a mass explosive hazard. This division is comprised of articles which contain only extremely insensitive detonating substances and which demonstrate a negligible probability of accidental initiation or propagation. (The risk from articles of Division 1.6 is limited to the explosion of a single article.) 
                            </P>
                            <GPOTABLE COLS="2" OPTS="L2,i1" CDEF="s50,r50">
                                <TTITLE>Classification Conversion Table</TTITLE>
                                <BOXHD>
                                    <CHED H="1">Current OSHA/DOT classification </CHED>
                                    <CHED H="1">Prior OSHA classification </CHED>
                                </BOXHD>
                                <ROW>
                                    <ENT I="01">Division 1.1 </ENT>
                                    <ENT>Class A explosives. </ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="01">Division 1.2 </ENT>
                                    <ENT>Class A or Class B explosives. </ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="01">Division 1.3 </ENT>
                                    <ENT>Class B explosives. </ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="01">Division 1.4 </ENT>
                                    <ENT>Class C explosives. </ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="01">Division 1.5 </ENT>
                                    <ENT>Blasting agents. </ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="01">Division 1.6 </ENT>
                                    <ENT>No applicable hazard class. </ENT>
                                </ROW>
                            </GPOTABLE>
                            <P>
                                <E T="03">Hot work</E>
                                 means any work involving electric or gas welding, cutting, brazing, or similar flame or spark-producing operations. 
                            </P>
                            <P>
                                <E T="03">Magazine</E>
                                 means any building or structure, other than an explosives manufacturing building, used for the storage of explosives. 
                            </P>
                            <P>
                                <E T="03">Propellant-actuated power device</E>
                                 means any tool or special mechanized device or gas generator system which is actuated by a propellant or which releases and directs work through a smokeless propellant charge. 
                                <PRTPAGE P="18837"/>
                            </P>
                            <P>
                                <E T="03">Pyrotechnics</E>
                                 means combustible or explosive compositions or manufactured articles designed and prepared for the purpose of producing audible or visible effects by combustion, deflagration, or detonation. They are commonly referred to as fireworks. 
                            </P>
                            <P>
                                <E T="03">Semiconductive hose</E>
                                 means a hose with an electrical resistance high enough to limit flow of stray electric currents to safe levels, yet not so high as to prevent drainage of static electric charges to ground; or a hose of not more than two megohms resistance over its entire length and of not less than 1,000 ohms per foot. 
                            </P>
                            <P>
                                <E T="03">Small arms ammunition</E>
                                 means any shotgun, rifle, pistol, or revolver cartridge, and cartridges for propellant-actuated power devices and industrial guns. Military-type ammunition containing explosive-bursting charges, or incendiary, tracer, spotting, or pyrotechnic projectiles are excluded from this definition. 
                            </P>
                            <P>
                                <E T="03">Small arms ammunition primers</E>
                                 mean small percussion-sensitive explosive charges, encased in a cap, and used to ignite propellant powder. 
                            </P>
                            <P>
                                <E T="03">Smokeless propellants</E>
                                 mean solid propellants, commonly called smokeless powders, used in small arms ammunition, cannons, rockets, and propellant-actuated power devices. 
                            </P>
                            <P>
                                <E T="03">Special industrial explosive materials</E>
                                 mean shaped materials and sheet forms and various other extrusions, pellets, and packages of high explosives, which include dynamite, trinitrotoluene (TNT), pentaerythritol tetranitrate (PETN), hexahydro-1,3,5-trinitro-s-triazine (RDX), and other similar compounds used for high-energy-rate forming, expanding, and shaping in metal fabrication, and for dismemberment and quick reduction of scrap metal. 
                            </P>
                            <P>
                                <E T="03">Vehicle</E>
                                 means any motor vehicle, machine, tractor, trailer, or semi-trailer propelled or drawn by mechanical power and used in the transportation of explosives. 
                            </P>
                            <P>
                                <E T="03">Water gels or slurries</E>
                                 mean explosives that contain substantial proportions of water, oxidizers, and fuel with a cross-linking agent, a gelling, or a thickening agent added. Water gels or slurries, depending on their properties, are classified as Division 1.1 explosives or Division 1.5 blasting agents. 
                            </P>
                            <P>
                                (c) 
                                <E T="03">General provisions.</E>
                                 (1) 
                                <E T="03">Explosives hazards.</E>
                                 The employer shall ensure the following: 
                            </P>
                            <P>(i) Explosives are manufactured, stored, sold, transported, handled, and used in a safe manner; </P>
                            <P>(ii) Only persons trained in accordance with paragraph (j) of this section handle or use explosives; </P>
                            <P>(iii) Blasting equipment or explosives that are unsafe due to deterioration, damage, or other causes are not used, and are disposed of by an experienced person as soon as possible in accordance with manufacturers' recommendations; </P>
                            <P>(iv) Proper housekeeping is performed to prevent hazardous accumulations of explosives, oxidizers, or fuels and other sensitizers in, on, or in close proximity to facilities and equipment containing explosives; </P>
                            <P>(v) All equipment is maintained in good working condition; </P>
                            <P>(vi) A program of systematic maintenance of equipment is conducted on a regular schedule; </P>
                            <P>(vii) No person is allowed to enter facilities containing explosives, or to transport, handle, or use explosives while under the influence of intoxicating liquors, narcotics, or other drugs that may cause the person to act in an unsafe manner in the workplace; </P>
                            <P>(viii) No person enters a facility containing explosives or a blast site unless authorized to do so by the employer; and </P>
                            <P>(ix) No flammable cleaning solvents are permitted in facilities containing explosives except where authorized by the employer who determines that their presence does not endanger the safety of employees. </P>
                            <P>
                                (2) 
                                <E T="03">Electrical hazards.</E>
                                 (i) The employer shall ensure that the primary electrical supply to a facility containing explosives can be disconnected at a safe remote location away from the facility. 
                            </P>
                            <P>(ii) During the approach and progress of an electrical storm, the employer shall ensure that: </P>
                            <P>(A) All explosive manufacturing and blasting operations are suspended; and </P>
                            <P>(B) Employees located in or near facilities containing explosives or in blast sites are withdrawn immediately to a safe remote location. </P>
                            <P>
                                (3) 
                                <E T="03">Fire and Explosion Prevention.</E>
                                 (i) The employer shall ensure that explosives are handled in a manner that minimizes their spillage and jarring, the generation of explosive dust, and the creation of friction in or in close proximity to explosives. 
                            </P>
                            <P>(ii) When a fire is in imminent danger of contact with explosives, the employer shall ensure that: </P>
                            <P>(A) Employees do not fight the fire; </P>
                            <P>(B) All employees are immediately removed to a safe area; and </P>
                            <P>(C) The fire area is guarded against intruders. </P>
                            <P>(iii) The employer shall ensure that: </P>
                            <P>(A) No open flames, matches, or spark-producing devices are located within 50 feet (15.2 m) of explosives or facilities containing explosives; </P>
                            <P>(B) Smoking is only permitted in authorized smoking areas located a safe distance from explosives; </P>
                            <P>(C) No person carries firearms, ammunition, or similar articles in facilities containing explosives or blast sites except as required for work duties; and </P>
                            <P>(D) Vehicles are not refueled within 50 feet (15.25 m) of a facility containing explosives or a blast site. </P>
                            <P>
                                (4) 
                                <E T="03">Maintenance and Repairs.</E>
                                 The employer shall ensure the following: 
                            </P>
                            <P>(i) Before maintenance or repairs are started in or in close proximity to any facility containing explosives or in a blast site, the immediate area surrounding the maintenance or repair work is free of explosives, including residues and dusts containing explosives; and </P>
                            <P>(ii) The fire prevention and protection requirements in § 1910.252(a) and paragraph (c)(3)(iii) of this section are implemented prior to beginning hot work operations. </P>
                            <P>
                                (5) 
                                <E T="03">Labels.</E>
                                 (i) The employer shall communicate hazards associated with explosives in accordance with the requirements of the Hazard Communication Standard, § 1910.1200. Where labeling of explosives is required under § 1910.1200, Globally Harmonized System (GHS) labels shall be used as shown in the figure below for different divisions of explosives. The labels shall have a signal word, a hazard statement, and either a division designation or a pictogram as shown in the figure below. The pictogram shall be black on a white background with a red frame sufficiently large to be clearly visible. 
                            </P>
                            <BILCOD>BILLING CODE 4510-26-P</BILCOD>
                            <GPH SPAN="3" DEEP="640">
                                <PRTPAGE P="18838"/>
                                <GID>EP13AP07.000</GID>
                            </GPH>
                            <BILCOD>BILLING CODE 4510-26-C</BILCOD>
                            <P>
                                (ii) The employer shall ensure that DOT markings, placards, and labels are retained in accordance with § 1910.1201. 
                                <PRTPAGE P="18839"/>
                            </P>
                            <P>
                                (d) 
                                <E T="03">Storage of ammonium nitrate.</E>
                                 (1) 
                                <E T="03">Applicability.</E>
                                 (i) Paragraph (d) of this section applies to the storage of ammonium nitrate in quantities of 1,000 pounds (454 kg) or more to be used in the manufacture of explosives. 
                            </P>
                            <P>(ii) Paragraph (d) of this section does not apply to ammonium nitrate that can be classified as an explosive as defined in paragraph (b) of this section. </P>
                            <P>
                                (2) 
                                <E T="03">Storage buildings.</E>
                                 (i) Buildings or structures constructed and used to store ammonium nitrate since before August 27, 1971, and that do not meet the requirements of paragraph (d)(2) of this section, shall be deemed to be acceptable for continued storage use when such use does not endanger the safety of employees. 
                            </P>
                            <P>(ii) The employer shall ensure the following: </P>
                            <P>(A) Ammonium nitrate is stored in a manner that minimizes as far as possible fire and explosion hazards, including exposure to toxic vapors from burning or decomposing ammonium nitrate; </P>
                            <P>(B) Storage buildings are not over one story in height above ground level; </P>
                            <P>(C) Storage buildings do not have basements unless the basements are open on at least one side; </P>
                            <P>(D) Storage buildings are adequately ventilated to prevent unsafe heat or fume accumulations; </P>
                            <P>(E) Storage building walls are constructed to meet a four-hour fire resistant rating whenever they face and are within 50 feet (15.2 m) of a combustible building, forest, pile of combustible materials, or other similar hazards. In lieu of a four-hour fire resistant wall, other equivalent means of exposure protection may be used; </P>
                            <P>(F) At a minimum, the roof coverings afford a light degree of fire protection to the roof deck, do not slip from position, and do not present a flying brand hazard; </P>
                            <P>(G) Storage buildings do not exceed a height of 40 feet unless constructed of noncombustible material or adequate facilities for fighting a roof fire are available; </P>
                            <P>(H) All flooring is of noncombustible material; </P>
                            <P>(I) All flooring is protected against impregnation by ammonium nitrate; </P>
                            <P>(J) Flooring has no drains or piping into which any molten ammonium nitrate could flow and be confined in the event of fire; </P>
                            <P>(K) Storage buildings are dry and free from water seepage; </P>
                            <P>(L) Unauthorized persons do not enter an ammonium nitrate storage area; </P>
                            <P>(M) Ammonium nitrate and storage buildings containing ammonium nitrate are located at a safe distance from readily combustible fuels; and </P>
                            <P>
                                (N) In areas where lightning storms are prevalent, lightning protection systems are provided. Lightning protection systems meeting the safety requirements found in Appendix K of National Fire Protection Association (NFPA) 780-2004, 
                                <E T="03">Standard for the Installation of Lightning Protection Systems</E>
                                , or other equally protective criteria would meet the requirements of this provision. 
                            </P>
                            <P>
                                (3) 
                                <E T="03">Storage of ammonium nitrate in bags and containers.</E>
                                 The employer shall ensure that: 
                            </P>
                            <P>(i) Bags and containers used for ammonium nitrate storage are: </P>
                            <P>(A) Constructed in accordance with DOT regulations (49 CFR chapter I); and </P>
                            <P>(B) Labeled in accordance with DOT regulations (49 CFR chapter I) or § 1910.1200, as applicable; </P>
                            <P>(ii) Bags and containers of ammonium nitrate are not placed into storage when the temperature of the ammonium nitrate exceeds 130 F° (54 °C); </P>
                            <P>(iii) Bags and containers of ammonium nitrate are not stored within 30 inches (76.2 cm) of storage building walls and partitions; </P>
                            <P>(iv) Stacks of bags or containers of ammonium nitrate do not exceed 20 feet (6.1 m) in height or 20 feet (6.1 m) in width; </P>
                            <P>(v) Stacks of bags or containers of ammonium nitrate are limited to 50 feet (15.2 m) in length unless located in a building of non-combustible construction or protected by an automatic sprinkler system; </P>
                            <P>(vi) Bags or containers of ammonium nitrate are not stacked within 36 inches (91.4 cm) of the roof or overhead supporting structure of the storage building; </P>
                            <P>(vii) Aisles at least 3-feet (91.4 cm) wide are provided to separate stacks of bags or containers of ammonium nitrate; and </P>
                            <P>(viii) At least one main aisle separating stacks of bags or containers of ammonium nitrate in the storage area is at least 4-feet (1.2 m) wide. </P>
                            <P>
                                (4) 
                                <E T="03">Storage of bulk ammonium nitrate.</E>
                                 The employer shall ensure the following: 
                            </P>
                            <P>(i) Bulk storage bins used to store ammonium nitrate are clean and free of materials which may contaminate ammonium nitrate; </P>
                            <P>(ii) Galvanized iron, copper, lead, and zinc are not used in the construction of ammonium nitrate bulk storage bins, unless suitably protected against the corrosive and reactive properties of ammonium nitrate, to avoid contamination of the ammonium nitrate by these metals; </P>
                            <P>(iii) Aluminum and wooden bulk storage bins used to store ammonium nitrate are protected against ammonium nitrate impregnation; </P>
                            <P>(iv) The partitions dividing stored ammonium nitrate from other products are constructed to prevent contamination of the ammonium nitrate with these other products; </P>
                            <P>(v) Ammonium nitrate bulk storage bins or piles are clearly identified by signs reading “Ammonium Nitrate” with letters at least 2 inches (5.1 cm) high; </P>
                            <P>(vi) Ammonium nitrate in piles or in bulk storage bins is loosened or moved periodically to minimize caking; </P>
                            <P>(vii) Explosives are not used to break up or loosen caked ammonium nitrate; </P>
                            <P>(viii) The top of an ammonium nitrate pile is no closer than 36 inches (91.4 cm) below the roof or supporting structure of the storage building; and </P>
                            <P>(ix) Bulk ammonium nitrate is not placed into storage when its temperature exceeds 130 °F (54 °C); </P>
                            <P>
                                (5) 
                                <E T="03">Contaminants.</E>
                                 The employer shall ensure that: 
                            </P>
                            <P>(i) Ammonium nitrate is kept in a separate building or is separated from flammable, combustible, corrosive, explosive, or contaminating materials or processes by a wall with at least a 1-hour fire-resistant rating. This separation wall shall extend at least to the underside of the roof. In lieu of separation walls, ammonium nitrate may be separated from these materials or processes by a space of at least 30 feet (9.1 m) with means to prevent mixing, such as sills or curbs; </P>
                            <P>(ii) Flammable liquids are not placed or stored in buildings used for the storage of ammonium nitrate except in accordance with § 1910.106, and paragraph (d)(5)(i) of this section; </P>
                            <P>(iii) No liquefied petroleum gas is placed or stored in the storage building except in accordance with § 1910.110; and </P>
                            <P>(iv) Sulfur and finely divided metals are not stored in the same building with ammonium nitrate. </P>
                            <P>
                                (6) 
                                <E T="03">Fire protection.</E>
                                 The employer shall ensure the following: 
                            </P>
                            <P>(i) Buildings in which greater than 2500 tons (2268 metric tons) of ammonium nitrate is stored are equipped with an automatic sprinkler system that complies with § 1910.159; and </P>
                            <P>(ii) All fire protection equipment and systems in ammonium nitrate storage buildings meet the requirements of subpart L of this part. </P>
                            <P>
                                (e) 
                                <E T="03">Transportation of explosives.</E>
                                 (1) 
                                <E T="03">General provisions.</E>
                                 The employer shall ensure that: 
                            </P>
                            <P>
                                (i) No employee smokes, carries matches or any other flame-producing device, or carries any firearms or 
                                <PRTPAGE P="18840"/>
                                cartridges (except firearms and cartridges required to be carried by guards) while in, or within 25 feet (7.63m) of, a vehicle containing explosives; 
                            </P>
                            <P>(ii) No employee drives, loads, or unloads a vehicle containing explosives in an unsafe manner; </P>
                            <P>(iii) Explosives are not transferred from one vehicle to another without informing local fire and police departments. A competent person shall supervise the transfer of explosives. In the event of breakdown or collision, the local fire and police departments shall be promptly notified; </P>
                            <P>(iv) No repair work, other than emergency repairs that do not present a source of ignition, is performed on a vehicle containing explosives; </P>
                            <P>(v) Detonators are not transported with other explosives on the same vehicle, unless packaged, segregated, and transported in accordance with the regulations of DOT (49 CFR 177.835(g)); </P>
                            <P>(vi) When explosives are transported on a railway car utilizing private railroad tracks, the car, its contents, and method of loading are in accordance with the regulations of DOT (49 CFR chapter I); </P>
                            <P>(vii) Explosives at a railway facility, truck terminal, pier, harbor facility, or airport terminal, whether for delivery to a consignee or forwarded to some other destination, are kept in a manner that minimizes risk to employees; and </P>
                            <P>(viii) The driver or other employee attending the vehicle is knowledgeable about the nature and hazards of the explosives contained in the vehicle and the procedures for handling emergency situations. </P>
                            <P>
                                (2) 
                                <E T="03">Vehicles.</E>
                                 (i) The employer shall ensure that any vehicle used to carry explosives: 
                            </P>
                            <P>(A) Is able to safely carry the designated load; </P>
                            <P>(B) Has close-fitting floors; and </P>
                            <P>(C) Has wood or other non-sparking materials covering any exposed spark-producing metal on the inside of the vehicle body. </P>
                            <P>(ii) The employer shall ensure that any vehicle containing explosives or oxidizers located at a private facility or blast site has exterior markings or placards designed and displayed in accordance with the regulations of DOT (49 CFR chapter I). </P>
                            <P>(iii) For all open-bodied vehicles containing explosives, the employer shall ensure that: </P>
                            <P>(A) The explosives are protected with a flameproof and moisture-proof tarpaulin or other effective means of protection from fire, sparks, and moisture; and </P>
                            <P>(B) The explosives are not loaded above the sides of the vehicle. </P>
                            <P>(iv) For each vehicle used to carry explosives, the employer shall ensure that: </P>
                            <P>(A) The vehicle is equipped with at least two fire extinguishers filled and in good working order, each having a rating of at least 4-A:40-B:C; </P>
                            <P>(B) One of the fire extinguishers on the vehicle is located in close proximity to the driver's seat; and </P>
                            <P>(C) The fire extinguishers on the vehicle are listed or approved by a nationally recognized testing laboratory (refer to § 1910.155(c)(3)(iv)(A) for definition of listed fire extinguishers, and § 1910.7 for nationally recognized testing laboratories). </P>
                            <P>(v) For each vehicle used for carrying explosives, the employer shall ensure the following: </P>
                            <P>(A) Fire extinguishers are used, maintained, and tested in accordance with § 1910.157; </P>
                            <P>(B) Fire extinguishers are used only to fight non-explosive fires; i.e., tire fires, battery fires, engine fires, cab fires, etc., where the fire has not yet reached the explosive cargo; and </P>
                            <P>(C) The explosive cargo cannot shift, spill, or become damaged during transit. </P>
                            <P>(vi) The employer shall ensure that any vehicle containing explosives is maintained in good and safe working condition for transporting explosives. </P>
                            <P>
                                (3) 
                                <E T="03">Operation of vehicles.</E>
                                 (i) The employer shall ensure that: 
                            </P>
                            <P>(A) Only employees designated by the employer ride in or drive a vehicle containing explosives; </P>
                            <P>(B) Vehicles containing explosives are only driven by and are in the charge of a driver who is familiar with relevant traffic regulations and the provisions of paragraph (e) of this section, and possesses a valid driver's license appropriate for the vehicle; </P>
                            <P>(C) Except under emergency conditions, no vehicle containing explosives is parked before reaching its destination on any public street adjacent to or in close proximity to any place of employment; </P>
                            <P>(D) No spark-producing metal, spark-producing tools, oils, matches, firearms, electric storage batteries, flammable substances, acids, oxidizers, or corrosive compounds are carried in the body of any vehicle containing explosives, unless the carrying of such dangerous articles and the explosives complies with DOT regulations (49 CFR chapter I); and </P>
                            <P>(E) Deliveries of explosives are received only by employees authorized by the employer to receive such explosives. </P>
                            <P>(ii) The employer shall ensure that every vehicle containing Division 1.1, 1.2, or 1.3 explosives at the employer's worksite or facility is attended at all times by the driver or other responsible person authorized by the employer. </P>
                            <P>(A) For the purposes of this section, the vehicle shall be considered “attended” only when the driver or other responsible person authorized by the employer is physically on or in the vehicle, or can see and reach the vehicle quickly and without any interference. “Attended” also means that the driver or other employee is awake, alert, and not engaged in other duties or activities which may divert attention from the vehicle; and </P>
                            <P>(B) The driver or other employee attending the vehicle shall be authorized, capable, and have the necessary means to drive the assigned vehicle safely. </P>
                            <P>
                                (f) 
                                <E T="03">Use of explosives for blasting.</E>
                                 (1) 
                                <E T="03">General provisions.</E>
                                 (i) The employer shall ensure that the blaster-in-charge: 
                            </P>
                            <P>(A) Is trained, knowledgeable, and experienced in the storage, transportation, handling, and use of explosives; </P>
                            <P>(B) Is knowledgeable about relevant federal, state, and local regulations pertaining to explosives; </P>
                            <P>(C) Is trained, knowledgeable, and experienced in the use of each type of blasting method being used; </P>
                            <P>(D) Is in control of the blasting operations, blast site, and blast area; and </P>
                            <P>(E) Evaluates each blast site and blast area for which he or she is responsible and implements the measures that will ensure the safety of employees and the security of those areas. </P>
                            <P>(ii) The employer shall ensure the following: (A) Explosives are used in accordance with manufacturers' recommendations; </P>
                            <P>(B) All employees involved in blasting operations work only under the supervision of the blaster-in-charge; </P>
                            <P>(C) Only Type 3 magazines or the original containers are used to transport detonators and other explosives from magazines to the blast site; </P>
                            <P>(D) Employees are protected from flying fragments produced during blasting operations by removing employees to a safe distance, using protective barricades, or utilizing other equivalent means to protect employees; </P>
                            <P>(E) Adequate precautions are taken to prevent sources of induced current, such as lightning, adjacent power lines, dust storms, snow storms, radar, radio transmitters, cellular phones, or other sources of extraneous electricity, from causing the accidental ignition of electric blasting caps; and </P>
                            <P>
                                (F) Signs are posted warning against the use of mobile radio transmitters or cellular phones on all roads within 350 
                                <PRTPAGE P="18841"/>
                                feet (106.7 m) of the blasting operations. The signs shall read: 
                            </P>
                            <HD SOURCE="HD3">WARNING </HD>
                            <HD SOURCE="HD3">EXPLOSIVES HAZARD </HD>
                            <HD SOURCE="HD3">DO NOT USE MOBILE RADIO TRANSMITTERS OR CELLULAR PHONES </HD>
                            <P>(iii) (A) The employer shall ensure that all surface blasting operations are conducted only during daylight hours; except as provided in (f)(1)(iii)(B) of this section. </P>
                            <P>(B) Unusual blasting operations associated with industrial processes, such as blasting slag pockets and dustcatchers, that are performed indoors are permitted at any time of day when a minimum illumination density of 20 lumens per square foot is provided within a 5-foot (1.5 m) radius of locations where explosives are being assembled, placed, or attached to detonators. </P>
                            <P>(iv) Whenever blasting operations are being conducted in close proximity to gas, electric, water, telephone, or other similar utilities, the employer shall not commence such blasting operations until receiving and documenting approval from the appropriate utility representatives. </P>
                            <P>
                                (2) 
                                <E T="03">Explosives at blast sites.</E>
                                 The employer shall ensure that: 
                            </P>
                            <P>(i) Empty containers and paper and fiber packing materials which previously contained explosives are disposed of in a safe manner, or reused in accordance with DOT regulations (49 CFR chapter I); </P>
                            <P>(ii) Only non-sparking tools shall be used to open containers of explosives; </P>
                            <P>(iii) No explosives are abandoned; and </P>
                            <P>(iv) All unused explosives are immediately returned to appropriate magazines. </P>
                            <P>
                                (3) 
                                <E T="03">Loading of explosives in drill holes.</E>
                                 The employer shall ensure that: 
                            </P>
                            <P>(i) All drill holes are of sufficient size to permit the free insertion of explosives; </P>
                            <P>(ii) Tamping of explosives is performed: </P>
                            <P>(A) Only with non-sparking tools; and </P>
                            <P>(B) In a manner that does not degrade or otherwise damage the explosives or cause the explosives to detonate; </P>
                            <P>(iii) Pneumatic loading of explosives into drill holes primed with electric detonators or other static electricity-sensitive initiation systems conforms to the following requirements: </P>
                            <P>(A) Equipment is bonded and grounded; </P>
                            <P>(B) A semi-conductive hose is used; and </P>
                            <P>(C) The blaster-in-charge evaluates all systems to assure that they will safely dissipate static electricity under potential field conditions; </P>
                            <P>(iv) No employee drills into explosives or any portion of a hole that at any time contained explosives; </P>
                            <P>(v) After loading for a blast is completed but before detonation, all remaining explosives, including detonators, are immediately returned to the appropriate magazines; </P>
                            <P>(vi) During the time that drill holes are loaded or are being loaded, only personnel who are engaged in drilling or loading operations, or are otherwise authorized by the employer, may enter the blast site; and </P>
                            <P>(vii) After the loaded drill holes are connected but prior to them being connected to a source of initiation: </P>
                            <P>(A) The blast area shall be barricaded and posted, guarded, or both. If barricaded and posted, the posted sign shall read “DANGER—EXPLOSIVES HAZARD—DO NOT ENTER” or equivalent language; and </P>
                            <P>(B) All personnel shall be removed from the blast area. </P>
                            <P>
                                (4) 
                                <E T="03">Initiation of explosive charges.</E>
                                 The employer shall ensure that: 
                            </P>
                            <P>(i) Where sources of extraneous electricity in excess of fifty (50) milliamperes (flowing through a one-ohm resistor) are present, electric detonators are used only if sufficient measures are taken to ensure that the detonators will not inadvertently activate; </P>
                            <P>(ii) The blaster-in-charge supervises selection and installation of the initiation system; </P>
                            <P>(iii) The initiation system is used in accordance with the manufacturer's recommendations; </P>
                            <P>(iv) The blaster-in-charge checks the initiation system visually after blast hookup; </P>
                            <P>(v) The blaster-in-charge tests the blast layout for continuity as recommended by the manufacturer; </P>
                            <P>(vi) Where deemed necessary by the blaster-in-charge, a double trunk line or closed-loop hookup is used in the initiation system; </P>
                            <P>(vii) When a safety fuse is used, only a crimper approved by the detonator manufacturer or the safety fuse manufacturer is used to connect the detonator to the safety fuse; </P>
                            <P>(viii) All primers are assembled at least 50 feet (15.25 m) away from any magazine; </P>
                            <P>(ix) Primers are made up only as needed for immediate use; </P>
                            <P>(x) When an explosives cartridge that does not have a detonator well is used as a primer, a hole large enough to accommodate the detonator is made in the cartridge with a spark-resistant powder punch approved either by the explosives manufacturer or by the blaster-in-charge; </P>
                            <P>(xi) When testing electric circuits that lead to loaded drill holes, only blasting galvanometers or other instruments specifically designed for this purpose are used; and </P>
                            <P>(xii) In electrical firing: </P>
                            <P>(A) Only the person making the lead line connections or the blaster-in-charge shall fire the shot; and </P>
                            <P>(B) Blasting lead lines shall remain shunted (shorted) and not connected to the blasting machine or other source of current until the charge is to be fired. </P>
                            <P>
                                (5) 
                                <E T="03">Warning signal.</E>
                                 The employer shall ensure that, before a blast is fired, all persons and vehicles are at a safe distance outside the blast area or under sufficient cover, and that an adequate warning signal is given. 
                            </P>
                            <P>
                                (6) 
                                <E T="03">Post blast procedures.</E>
                                 After a blast, the employer shall ensure that: 
                            </P>
                            <P>(i) No other person enters the blast area until it is inspected by the blaster-in-charge and found to be free of misfires and other safety hazards and the blaster-in-charge has given an all-clear signal; and </P>
                            <P>(ii) The blaster-in-charge does not enter the blast site until sufficient time has passed to allow smoke and fumes to dissipate and dust to settle. </P>
                            <P>
                                (7) 
                                <E T="03">Misfires.</E>
                                 The employer shall ensure that: 
                            </P>
                            <P>(i) Whenever there is a misfire while using blasting cap and fuse or electronic detonators, all employees remain outside the blast area for at least 1 hour. If electric detonators or nonelectric detonators (other than cap and fuse) are used and a misfire occurs, this waiting period may be reduced to 30 minutes; </P>
                            <P>(ii) Whenever explosives remain in a misfired hole, a new primer is inserted and the hole is reblasted. Where reblasting presents a hazard, the remaining explosives shall be washed out with water, or, where the misfire is underwater, blown out with air; </P>
                            <P>(iii) Misfires are handled under the direction of the blaster-in-charge and all initiation paths are carefully traced and a thorough search made for unexploded charges; </P>
                            <P>(iv) Explosives recovered from blasting misfires are placed in a magazine that is used only for the storage of misfired explosives and are then disposed of as soon as possible in accordance with the manufacturers' recommendations; and </P>
                            <P>
                                (v) Detonators recovered from blasting misfires are not reused and are disposed of as soon as possible in accordance with the manufacturers' recommendations. 
                                <PRTPAGE P="18842"/>
                            </P>
                            <P>
                                (g) 
                                <E T="03">Blasting agents, water gels, slurries, and emulsions.</E>
                                 (1) 
                                <E T="03">General provisions.</E>
                            </P>
                            <P>(i) Unless otherwise set forth in this paragraph (g): </P>
                            <P>(A) Blasting agents, water gels, slurries, and emulsions shall be stored, transported, handled, and used in the same manner as other explosives; and </P>
                            <P>(B) Water gels, slurries, and emulsions classified as Division 1.1 or Division 1.5 shall meet the same requirements as blasting agents in paragraph (g). However, the manufacture of water gels, slurries, and emulsions classified as Division 1.1 explosives also shall comply with § 1910.119 Process Safety Management. </P>
                            <P>(ii) The employer shall ensure the following: </P>
                            <P>(A) Caked oxidizers, either in bags or in bulk, are not loosened by blasting; </P>
                            <P>(B) Equipment used for mixing and packaging of blasting agents is constructed of materials compatible with the blasting agent composition; </P>
                            <P>(C) Spills or leaks which may contaminate combustible materials are cleaned up immediately; </P>
                            <P>(D) Ingredients are not kept with incompatible materials; and </P>
                            <P>(E) Water gels, slurries, and emulsions, or their liquid ingredients maintain their liquid or water content. </P>
                            <P>(iii) If a Type 5 magazine is used as a bulk storage container for blasting agents, the employer shall ensure that any electrically driven conveyors used for loading or unloading the magazine are designed to minimize damage from corrosion. </P>
                            <P>
                                (2) 
                                <E T="03">Fixed location mixing.</E>
                                 (i) In a building used for the mixing of blasting agents, the employer shall ensure the following: 
                            </P>
                            <P>(A) The building is of noncombustible construction or constructed of sheet metal on wood studs; </P>
                            <P>(B) Floors are constructed of concrete or other minimally absorbent material and have no drains or piping into which molten materials could flow and be confined during a fire; </P>
                            <P>(C) The building is ventilated to prevent unsafe heat or fume accumulations; </P>
                            <P>(D) Heating, if supplied for the building, is provided in a manner that does not create a fire or ignition hazard; </P>
                            <P>(E) All direct sources of building heat shall be provided exclusively from units located outside the building; </P>
                            <P>(F) Heating units which do not depend on combustion processes may be used in the building if they do not create a fire or ignition hazard; </P>
                            <P>(G) All internal-combustion engines are located outside the building, or are safely ventilated and isolated by a fire barrier wall with at least a 1-hour rating; </P>
                            <P>(H) The exhaust systems on all internal-combustion engines are located so that no sparks or other ignition sources create a hazard to any materials in or in close proximity to the building; </P>
                            <P>(I) All electric equipment located in the mixing room is in accordance with the requirements in subpart S of this part for Class II, Division 2 locations; </P>
                            <P>(J) All fuel-oil storage facilities are separated from the mixing building and located in such a manner that in case of tank rupture, the oil will drain away from the building and other facilities containing explosives or employees. Alternatively, tanks may be diked in a manner that will contain the entire tank contents in case of rupture; and </P>
                            <P>(K) The land surrounding the building is kept clear of all combustible materials for a distance of at least 25 feet (7.63 m). </P>
                            <P>
                                (ii) 
                                <E T="03">Equipment used for mixing blasting agents.</E>
                                 The employer shall ensure that: 
                            </P>
                            <P>(A) The mixing equipment minimizes the possibility of frictional heating, compaction, and confinement; </P>
                            <P>(B) All surfaces of the mixing equipment are accessible for cleaning; </P>
                            <P>(C) All bearings and drive assemblies are mounted outside the mixer and protected against dust accumulation; </P>
                            <P>(D) Suitable means are provided to prevent the flow of fuel oil to the mixer in case of fire. In gravity-flow systems, an automatic spring-loaded shutoff valve with a fusible link shall be installed; </P>
                            <P>(E) Both equipment and handling procedures prevent the inadvertent introduction of foreign objects or materials into the mixing process; and </P>
                            <P>(F) Mixers, pumps, valves, and related equipment are regularly and periodically flushed, cleaned, dismantled, and inspected. </P>
                            <P>
                                (iii) 
                                <E T="03">Blasting agent compositions.</E>
                                 The employer shall ensure that: 
                            </P>
                            <P>(A) Oxidizers of small particle size, such as crushed ammonium nitrate prills or fines, which may be more sensitive than coarser products, are handled with additional care compared to the coarser products; </P>
                            <P>(B) No hydrocarbon liquid fuel with a flashpoint lower than 125 °F (51.7 °C) is used except at ambient air temperatures below 45 °F (7.2 °C) where fuel oils with flashpoints as low as 100 °F (37.8 °C) are used; </P>
                            <P>(C) Crude oil and crankcase oil are not used as a blasting agent ingredient; </P>
                            <P>(D) Metal powders such as aluminum are kept dry and stored in moisture-resistant or weather tight containers; </P>
                            <P>(E) Solid fuels are used in a manner that minimizes dust explosion hazards as far as possible; and </P>
                            <P>(F) Peroxides and chlorates are not used. </P>
                            <P>
                                (iv) 
                                <E T="03">Mixing operations.</E>
                                 The employer shall ensure the following: 
                            </P>
                            <P>(A) Empty ammonium nitrate bags are disposed of daily in a safe manner; </P>
                            <P>(B) No hot work or open flames are permitted in or around the mixing building unless the equipment and surrounding area have been completely washed down and all oxidizers and fuels removed; </P>
                            <P>(C) Before welding or repairing hollow shafts of mixing equipment, all blasting agents and their ingredients are removed from the outside and inside of the shaft, and the shaft is vented through an opening at least one-half inch in diameter; and </P>
                            <P>(D) No explosives other than blasting agents are located inside or within 50 feet (15.25 m) of any building used for the mixing of blasting agents. </P>
                            <P>
                                (3) 
                                <E T="03">Bulk delivery vehicles.</E>
                                 (i) 
                                <E T="03">Applicability.</E>
                                 The provisions of paragraph (e) of this section also apply to bulk delivery vehicles transporting blasting agents or their ingredients in bulk form. 
                            </P>
                            <P>
                                (ii) 
                                <E T="03">Bulk delivery vehicle construction.</E>
                                 The employer shall ensure that the following requirements are met for bulk delivery vehicles: 
                            </P>
                            <P>(A) The vehicle body is constructed of noncombustible materials; </P>
                            <P>(B) Vehicles have enclosed bodies; </P>
                            <P>(C) All moving parts of the mixing system are designed to prevent heat buildup; </P>
                            <P>(D) Shafts or axles which contact the blasting agent or blasting agent ingredients have outboard bearings with a 1-inch (2.54 cm) minimum clearance between the bearings and the outside of the product container; </P>
                            <P>(E) When electrical power is supplied by a self-contained generator located on the vehicle, the generator is located where it will not create a fire or ignition hazard; </P>
                            <P>(F) The vehicle is able to safely carry the designated load; </P>
                            <P>(G) The vehicle's processing equipment, including its mixing and conveying equipment, is compatible with the relative sensitivity of the materials being handled; </P>
                            <P>(H) All hollow shafts of the vehicle's processing equipment are constructed to permit venting through an opening at least one-half inch in diameter; and </P>
                            <P>(I) Means are provided on the vehicle to prevent the flow of fuel to the mixer in case of fire. In gravity flow systems, an automatic spring-loaded shut-off valve with fusible link shall be installed; </P>
                            <P>
                                (iii) 
                                <E T="03">Bulk delivery vehicle operation.</E>
                                 The employer shall ensure the following requirements are met for bulk delivery vehicle operation: 
                                <PRTPAGE P="18843"/>
                            </P>
                            <P>(A) The driver of the vehicle is trained and capable of safely operating the vehicle; </P>
                            <P>(B) The operator, whether the driver or another employee, is trained and capable of safely operating the mixing, conveying, and related equipment on the vehicle; </P>
                            <P>(C) Smoking, matches, open flames, spark-producing devices, and firearms (except firearms required to be carried by guards) are not permitted within 25 feet (7.63 m) of the vehicle; </P>
                            <P>(D) The transfer of blasting agents or their ingredients from one bulk delivery vehicle to another vehicle is performed at a safe distance away from any blast site where drill holes are loaded or in the process of being loaded; </P>
                            <P>(E) While the bulk delivery vehicle is in a blast site, caution is exercised to avoid driving the vehicle over hoses or dragging hoses over firing lines, detonating cords, detonator wires or tubes, or explosives; </P>
                            <P>(F) To ensure the safe movement of the bulk delivery vehicle in the blast site, the driver has the assistance of a second person to guide the vehicle's movements; </P>
                            <P>(G) Blasting agent ingredients are not mixed while the bulk delivery vehicle is in transit. </P>
                            <P>(H) A positive action parking brake, which will set the wheel brakes on at least one axle, is used during bulk delivery operations; </P>
                            <P>(I) At least two wheels are chocked whenever necessary to prevent vehicle movement; and </P>
                            <P>(J) The vehicle is maintained in good mechanical condition. </P>
                            <P>
                                (iv) 
                                <E T="03">Pneumatic loading from bulk delivery vehicles.</E>
                                 When drill holes, primed with electric detonators or other static-electricity sensitive systems, are pneumatically loaded from bulk delivery vehicles, the employer shall ensure that: 
                            </P>
                            <P>(A) The blaster-in-charge evaluates all systems to determine that they will adequately dissipate static electricity under potential field conditions; </P>
                            <P>(B) A grounding device is used to prevent the accumulation of static electricity; and </P>
                            <P>(C) A discharge hose is used that has a resistance range that will prevent conducting stray currents, but that is conductive enough to bleed off static buildup. </P>
                            <P>
                                (v) 
                                <E T="03">Repairs to bulk delivery vehicles.</E>
                                 The employer shall ensure that: 
                            </P>
                            <P>(A) No hot work is performed or open flames used on or around any part of the bulk delivery vehicle until all blasting agents and their ingredients have been removed and the vehicle has been completely washed down; and </P>
                            <P>(B) Before welding or repairing hollow shafts of equipment, all blasting agents and their ingredients are removed from the outside and inside of the shaft and the shaft is vented through an opening at least one-half inch in diameter. </P>
                            <P>
                                (h) 
                                <E T="03">Small arms ammunition, small arms primers, and smokeless propellants.</E>
                            </P>
                            <P>
                                (1) 
                                <E T="03">Applicability.</E>
                                 This paragraph does not apply to temporary in-process storage during the manufacture of small arms ammunition, small arms primers, or smokeless propellants. 
                            </P>
                            <P>
                                (2) 
                                <E T="03">Small arms ammunition.</E>
                                 The employer shall ensure that small arms ammunition is separated from flammable liquids, flammable solids, and oxidizing materials, by a fire barrier wall with at least a 1-hour rating or by a distance of at least 25 feet (7.6 m). 
                            </P>
                            <P>
                                (3) 
                                <E T="03">Smokeless propellants.</E>
                                 (i) The employer shall ensure that: 
                            </P>
                            <P>(A) All smokeless propellants are stored in shipping containers in accordance with DOT regulations at 49 CFR part 173 for smokeless propellants; and </P>
                            <P>(B) No more than 20 pounds (9.1 kg) of smokeless propellants, in containers not to exceed 1 pound (.45 kg), are displayed in a commercial establishment. </P>
                            <P>(ii) For commercial stocks of smokeless propellants, the employer shall ensure the following: </P>
                            <P>(A) Quantities over 20 pounds (9.1 kg) and not exceeding 100 pounds (45.4 kg) are stored in portable wooden boxes having walls at least 1-inch (2.54 cm) thick; </P>
                            <P>(B) Quantities over 100 pounds (45.4 kg) and not exceeding 750 pounds (340.5 kg) are stored in non-portable cabinets having walls at least 1-inch (2.54 cm) thick, and: </P>
                            <P>
                                (
                                <E T="03">1</E>
                                ) Not more than 400 pounds (181.6 kg) shall be permitted to be stored in any one non-portable cabinet; and 
                            </P>
                            <P>
                                (
                                <E T="03">2</E>
                                ) The non-portable cabinets shall be separated by a distance of at least 25 feet (7.6 m) or by a fire barrier wall with at least a 1-hour rating; and 
                            </P>
                            <P>(C) Quantities over 750 pounds (340.5 kg) and not exceeding 5,000 pounds (2270 kg) are not stored in a building unless the following requirements are met: </P>
                            <P>
                                (
                                <E T="03">1</E>
                                ) The warehouse or storage room shall not be accessible to unauthorized personnel; 
                            </P>
                            <P>
                                (
                                <E T="03">2</E>
                                ) Smokeless propellants shall be stored in non-portable storage cabinets having wood walls at least 1-inch (2.54 cm) thick and having shelves with no more than 3 feet (0.91 m) of separation between shelves; 
                            </P>
                            <P>
                                (
                                <E T="03">3</E>
                                ) No more than 400 pounds (181.6 kg) shall be stored in any one cabinet; 
                            </P>
                            <P>
                                (
                                <E T="03">4</E>
                                ) Cabinets shall be located against the walls of the storage room or warehouse; 
                            </P>
                            <P>
                                (
                                <E T="03">5</E>
                                ) Cabinets shall be separated by at least 40 feet (12.2 m). The separation between cabinets shall be permitted to be reduced to 20 feet (6.1) where barricades twice the height of the cabinets are attached to the wall midway between each cabinet. The barricades shall extend at least 10 feet (3.0 m) outward and be constructed of either 
                                <FR>1/4</FR>
                                -inch (6.35 mm) boiler plate, 2-inch (5.1 cm) thick wood, brick, or concrete block; 
                            </P>
                            <P>
                                (
                                <E T="03">6</E>
                                ) Smokeless propellant shall be separated from flammable liquids, flammable solids, and oxidizing materials by a distance of at least 25 feet (7.6 m) or by a fire barrier wall with at least a 1-hour rating; and 
                            </P>
                            <P>
                                (
                                <E T="03">7</E>
                                ) The building shall be protected by an automatic sprinkler system installed in accordance with § 1910.159. 
                            </P>
                            <P>(iii) The employer shall ensure that smokeless propellants exceeding 5,000 pounds (2270 kg) or not stored in accordance with paragraph (h)(3)(ii) of this section are stored in a Type 4 magazine in accordance with ATF regulations for the storage of explosives (27 CFR 555.203 and 555.210). </P>
                            <P>
                                (4) 
                                <E T="03">Small arms ammunition primers.</E>
                                 (i) The employer shall ensure that: 
                            </P>
                            <P>(A) Small arms ammunition primers are stored in shipping containers in accordance with the applicable regulations of DOT (49 CFR chapter I); </P>
                            <P>(B) Small arms ammunition primers are separated from flammable liquids, flammable solids, and oxidizing materials by a fire barrier wall with at least a 1-hour rating or by a distance of at least 25 feet (7.6 m); and </P>
                            <P>(C) No more than 10,000 small arms primers are displayed in a commercial establishment. </P>
                            <P>(ii) For commercial stocks of small arms primers, the employer shall ensure the following: </P>
                            <P>(A) When quantities of 750,000 or less are stored in a building: </P>
                            <P>(1) Not more than 100,000 shall be stored in any one pile; and </P>
                            <P>(2) Piles shall be at least 15 feet (4.6 m) apart; and </P>
                            <P>(B) When quantities in excess of 750,000 are stored in a building: </P>
                            <P>
                                (
                                <E T="03">1</E>
                                ) The warehouse or storage room shall not be accessible to unauthorized personnel; 
                            </P>
                            <P>
                                (
                                <E T="03">2</E>
                                ) Primers shall be stored in cabinets with no more than 200,000 primers stored in any one cabinet; 
                            </P>
                            <P>
                                (
                                <E T="03">3</E>
                                ) Shelves in cabinets shall have a vertical separation of at least 2 feet (0.6 m); 
                                <PRTPAGE P="18844"/>
                            </P>
                            <P>
                                (
                                <E T="03">4</E>
                                ) Cabinets shall be located against the walls of the warehouse or storage room; 
                            </P>
                            <P>
                                (
                                <E T="03">5</E>
                                ) Cabinets shall be separated by at least 40 feet (12.2 m). The separation between cabinets shall be permitted to be reduced to 20 feet (6.1 m) where barricades twice the height of the cabinets are firmly attached to the wall, midway between each cabinet. The barricades shall extend at least 10 feet (3.0 m) outward and shall be constructed of either 
                                <FR>1/4</FR>
                                -inch (6.35 mm) boiler plate, 2-inch (5t.2cm) thick wood, brick, or concrete block; 
                            </P>
                            <P>
                                (
                                <E T="03">6</E>
                                ) Primers shall be separated from materials classified by the U.S. Department of Transportation as flammable liquids, flammable solids, and oxidizing materials by a distance of at least 25 feet (7.6 m) or by a fire barrier wall with at least a 1-hour rating; and 
                            </P>
                            <P>
                                (
                                <E T="03">7</E>
                                ) The building shall be protected by an automatic sprinkler system installed in accordance with § 1910.159. 
                            </P>
                            <P>(iii) The employer shall ensure that small arms primers that are not stored in accordance with paragraph (h)(4)(ii) are stored in a Type 4 magazine in accordance with ATF regulations for the storage of explosives (27 CFR 555.203 and 555.210). </P>
                            <P>
                                (i) 
                                <E T="03">Pyrotechnics.</E>
                                 [Reserved] 
                            </P>
                            <P>
                                (j) 
                                <E T="03">Training.</E>
                                 (1) The employer shall provide information and training on safe work practices for each employee prior to or at the time of the employee's initial job assignment involving the manufacture, storage, sale, transportation, handling, or use of explosives, including repair or maintenance of related facilities and equipment. 
                            </P>
                            <P>(2) The employer shall ensure that the training provided under paragraph (j) of this section is specific to each employee's unique work duties. </P>
                            <P>(3) In addition to the information and training requirements of § 1910.1200, Hazard Communication, the employer shall inform each employee of the requirements in § 1910.109 that apply to the employee's work duties and make a copy of the § 1910.109 standard available to the employee.</P>
                            <P>(4) Employers shall train employees in all safety practices, including applicable emergency procedures, that relate to their work and are necessary for their safety. </P>
                            <P>(5) Whenever there are workplace changes, such as the institution of new or modified procedures or products, employees shall be retrained as necessary to ensure that each employee has the requisite proficiency in the relevant safe work practices. </P>
                            <P>(6) The employer shall conduct retraining whenever the employer has reason to believe that there are inadequacies in the employee's knowledge of or performance of safe work practices. </P>
                            <P>(7) The employer shall provide information and training in a manner that is understandable to each employee. </P>
                            <P>(8) The employer shall determine that each employee has demonstrated proficiency in all aspects of the training required by paragraph (j) of this section. </P>
                            <P>(9) An employer is deemed to be in compliance with an employee training provision in paragraph (j) of this section if an identical training provision has been satisfied for that employee under § 1910.1200, Hazard Communication or DOT training requirements (49 CFR part 172). </P>
                            <P>5. Paragraph (a)(1)(iii) of § 1910.119 is added to read as follows: </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 1910.119 </SECTNO>
                            <SUBJECT>Process safety management of highly hazardous chemicals. </SUBJECT>
                            <P>(a) * * * </P>
                            <P>(1) * * * </P>
                            <P>(iii) The manufacture of explosives as defined in § 1910.109(b), but does not apply to the manufacture of blasting agents, as defined in § 1910.109(b), including water gels, slurries, and emulsions classified as Division 1.5 explosives by the U.S. Department of Transportation (49 CFR Chapter I). </P>
                            <STARS/>
                        </SECTION>
                        <SUBPART>
                            <HD SOURCE="HED">Subpart Z—Toxic and Hazardous Substances </HD>
                        </SUBPART>
                        <P>6. The authority citation for subpart Z of part 1910 is revised to read as follows: </P>
                        <AUTH>
                            <HD SOURCE="HED">Authority:</HD>
                            <P>Sections 4, 6, and 8 of the Occupational Safety and Health Act of 1970 (29 U.S.C. 653, 655, and 657); Secretary of Labor's Order No. 12-71 (36 FR 8754), 8-76 (41 FR 25059), 9-83 (48 FR 35736), 1-90 (55 FR 9033), 6-96 (62 FR 111), 3-2000 (65 FR 50017), or 5-2002 (67 FR 65008), as applicable, and 29 CFR part 1911.</P>
                        </AUTH>
                        <EXTRACT>
                            <P>All of subpart Z issued under section 6(b) of the Occupational Safety and Health Act of 1970, except those substances that have exposure limits in Tables Z-1, Z-2, and Z-3 of 29 CFR 1910.1000. The latter were issued under section (6)(a) of the Act (29 U.S.C. 655(a)).</P>
                            <P>Section 1910.1000, Tables Z-1, Z-2, and Z-3 also issued under 5 U.S.C. 553, but not under 29 CFR part 1911, except for the inorganic arsenic, benzene, and cotton dust listings, and chromium (VI) listings. </P>
                            <P>Section 1910.1001 also issued under section 107 of the Contract Work Hours and Safety Standards Act (40 U.S.C. 3704) and 5 U.S.C. 553. </P>
                            <P>Section 1910.1002 also issued under 5 U.S.C. 553, but not under 29 U.S.C. 655 or 29 CFR part 1911. </P>
                            <P>Sections 1910.1018, 1910.1029, and 1910.1200 also issued under 29 U.S.C. 653. Section 1910.1030 also issued under Pub. L. 106-430, 114 Stat. 1901.</P>
                        </EXTRACT>
                        <P>7. The definition of “explosive” in paragraph (c) of § 1910.1200 is revised to read as follows: </P>
                        <SECTION>
                            <SECTNO>§ 1910.1200 </SECTNO>
                            <SUBJECT>Hazard communication. </SUBJECT>
                            <STARS/>
                            <P>(c) * * * </P>
                            <P>
                                <E T="03">Explosive</E>
                                 means any device, or liquid or solid chemical compound or mixture, the primary or common purpose of which is to function by explosion. 
                            </P>
                            <P>(i) The term “explosive” includes all material included as a Class 1 explosive by DOT in accordance with 49 CFR chapter I. The term includes, but is not limited to, dynamite, black powder, pellet powders, detonators, blasting agents, initiating explosives, blasting caps, safety fuse, fuse lighters, fuse igniters, squibs, cordeau detonant fuse, instantaneous fuse, igniter cord, igniters, pyrotechnics, special industrial explosive materials, small arms ammunition, small arms ammunition primers, smokeless propellant, cartridges for propellant-actuated power devices, and cartridges for industrial guns. </P>
                            <P>(ii) Explosives are classified using the same classification system as used by DOT (see 49 CFR § 173.50). Explosives are classified into the following divisions: </P>
                            <P>
                                (A) 
                                <E T="03">Division 1.1</E>
                                 consists of explosives that have a mass explosion hazard. A mass explosion is one which affects almost the entire load instantaneously. 
                            </P>
                            <P>
                                (B) 
                                <E T="03">Division 1.2</E>
                                 consists of explosives that have a projection hazard but not a mass explosion hazard. 
                            </P>
                            <P>
                                (C) 
                                <E T="03">Division 1.3</E>
                                 consists of explosives that have a fire hazard and either a minor blast hazard or a minor projection hazard or both, but not a mass explosion hazard. 
                            </P>
                            <P>
                                (D) 
                                <E T="03">Division 1.4</E>
                                 consists of explosives that present a minor explosion hazard. The explosive effects are largely confined to the package and no projection of fragments of appreciable size or range is to be expected. An external fire must not cause virtually instantaneous explosion of almost the entire contents of the package. 
                            </P>
                            <P>
                                (E) 
                                <E T="03">Division 1.5</E>
                                 consists of very insensitive explosives. This division is comprised of substances which have a mass explosion hazard but are so insensitive that there is very little probability of initiation or of transition from burning to detonation under normal conditions. (The probability of transition from burning to detonation is greater when large quantities are involved.) 
                            </P>
                            <P>
                                (F) 
                                <E T="03">Division 1.6</E>
                                 consists of extremely insensitive articles which do not have a 
                                <PRTPAGE P="18845"/>
                                mass explosive hazard. This division is comprised of articles which contain only extremely insensitive detonating substances and which demonstrate a negligible probability of accidental initiation or propagation. (The risk from articles of Division 1.6 is limited to the explosion of a single article.) 
                            </P>
                            <GPOTABLE COLS="2" OPTS="L2,i1" CDEF="s50,r50">
                                <TTITLE>Classification Conversion Table</TTITLE>
                                <BOXHD>
                                    <CHED H="1">Current OSHA/DOT classification </CHED>
                                    <CHED H="1">Prior OSHA classification </CHED>
                                </BOXHD>
                                <ROW>
                                    <ENT I="01">Division 1.1</ENT>
                                    <ENT>Class A explosives. </ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="01">Division 1.2</ENT>
                                    <ENT>Class A or Class B explosives. </ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="01">Division 1.3</ENT>
                                    <ENT>Class B explosives. </ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="01">Division 1.4</ENT>
                                    <ENT>Class C explosives. </ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="01">Division 1.5</ENT>
                                    <ENT>Blasting agents. </ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="01">Division 1.6</ENT>
                                    <ENT>No applicable hazard class. </ENT>
                                </ROW>
                            </GPOTABLE>
                            <STARS/>
                        </SECTION>
                    </PART>
                </SUPLINF>
                <FRDOC>[FR Doc. E7-6607 Filed 4-12-07; 8:45 am] </FRDOC>
                <BILCOD>BILLING CODE 4510-26-P </BILCOD>
            </PRORULE>
        </PRORULES>
    </NEWPART>
</FEDREG>
