<?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>76</VOL>
    <NO>116</NO>
    <DATE>Thursday, June 16, 2011</DATE>
    <UNITNAME>Contents</UNITNAME>
    <CNTNTS>
        <AGCY>
            <EAR>Agriculture</EAR>
            <PRTPAGE P="iii"/>
            <HD>Agriculture Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Animal and Plant Health Inspection Service</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Food and Nutrition Service</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Forest Service</P>
            </SEE>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals, </DOC>
                    <PGS>35185</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="0">2011-14994</FRDOCBP>
                </DOCENT>
                <SJ>Meetings:</SJ>
                <SJDENT>
                    <SJDOC>Deschutes Provincial Advisory Committee, </SJDOC>
                    <PGS>35185</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="0">2011-14793</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Air Force</EAR>
            <HD>Air Force Department</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Privacy Act; Systems of Records, </DOC>
                    <PGS>35195-35197</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="2">2011-14940</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Animal</EAR>
            <HD>Animal and Plant Health Inspection Service</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
                <SJDENT>
                    <SJDOC>Bovine Spongiform Encephalopathy; Importation of Animals and Animal Products, </SJDOC>
                    <PGS>35185-35186</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="1">2011-14989</FRDOCBP>
                </SJDENT>
                <DOCENT>
                    <DOC>Pest Risk Analysis for Interstate Movement of Rambutan From Puerto Rico Into the Continental United States; Availability, </DOC>
                    <PGS>35186-35187</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="1">2011-14992</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Army</EAR>
            <HD>Army Department</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Privacy Act; Systems of Records, </DOC>
                    <PGS>35197-35199</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="2">2011-14935</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Children</EAR>
            <HD>Children and Families Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals, </DOC>
                    <PGS>35219-35221</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="1">2011-14811</FRDOCBP>
                    <FRDOCBP T="16JNN1.sgm" D="1">2011-14869</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Coast Guard</EAR>
            <HD>Coast Guard</HD>
            <CAT>
                <HD>RULES</HD>
                <SJ>Safety Zones:</SJ>
                <SJDENT>
                    <SJDOC>Brandon Road Lock and Dam to Lake Michigan Including Des Plaines River, Chicago River, etc., Cicago, IL, </SJDOC>
                    <PGS>35106-35110</PGS>
                    <FRDOCBP T="16JNR1.sgm" D="4">2011-14925</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Waterway Closure, Atchafalaya River from Mile Marker 117 (Morgan City Railroad Bridge) to Mile Marker 0 (Simmesport, LA), </SJDOC>
                    <PGS>35104-35106</PGS>
                    <FRDOCBP T="16JNR1.sgm" D="2">2011-14922</FRDOCBP>
                </SJDENT>
            </CAT>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <DOCENT>
                    <DOC>Validation of Merchant Mariners' Vital Information; Issuance of Coast Guard Merchant Mariner's Documents, </DOC>
                    <PGS>35173-35176</PGS>
                    <FRDOCBP T="16JNP1.sgm" D="3">2011-14921</FRDOCBP>
                </DOCENT>
                <DOCENT>
                    <DOC>Validation of Merchant Mariners' Vital Information; Issuance of Coast Guard Merchant Mariner's Licenses and Certificates of Registry, </DOC>
                    <PGS>35169-35173</PGS>
                    <FRDOCBP T="16JNP1.sgm" D="4">2011-14920</FRDOCBP>
                </DOCENT>
            </CAT>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals, </DOC>
                    <PGS>35228-35229</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="1">2011-14924</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Commerce</EAR>
            <HD>Commerce Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Industry and Security Bureau</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>Commodity Futures</EAR>
            <HD>Commodity Futures Trading Commission</HD>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <SJ>Protection of Cleared Swaps Customer Contracts and Collateral:</SJ>
                <SJDENT>
                    <SJDOC>Conforming Amendments to the Commodity Broker Bankruptcy Provisions; Correction, </SJDOC>
                    <PGS>35141-35162</PGS>
                    <FRDOCBP T="16JNP1.sgm" D="21">2011-14907</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Defense Department</EAR>
            <HD>Defense Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Air Force Department</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Army Department</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Navy Department</P>
            </SEE>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
                <SJDENT>
                    <SJDOC>Federal Acquisition Regulation; Cost or Pricing Data Requirements and Information Other Than Cost or Pricing Data, </SJDOC>
                    <PGS>35218-35219</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="1">2011-14863</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Federal Acquisition Regulation; Payment by Electronic Fund Transfer, </SJDOC>
                    <PGS>35219</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="0">2011-14862</FRDOCBP>
                </SJDENT>
                <DOCENT>
                    <DOC>Arms Sales Notifications, </DOC>
                    <PGS>35188-35191</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="3">2011-14942</FRDOCBP>
                </DOCENT>
                <SJ>Meetings:</SJ>
                <SJDENT>
                    <SJDOC>Reserve Forces Policy Board, </SJDOC>
                    <PGS>35191</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="0">2011-14936</FRDOCBP>
                </SJDENT>
                <DOCENT>
                    <DOC>Privacy Act; Systems of Records, </DOC>
                    <PGS>35191-35195</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="4">2011-14941</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR/>
            <HD>Department of Transportation</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Pipeline and Hazardous Materials Safety Administration</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>Drug</EAR>
            <HD>Drug Enforcement Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Importers of Controlled Substances; Applications, </DOC>
                    <FRDOCBP T="16JNN1.sgm" D="0">2011-14954</FRDOCBP>
                    <PGS>35239-35242</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="1">2011-14956</FRDOCBP>
                    <FRDOCBP T="16JNN1.sgm" D="0">2011-14957</FRDOCBP>
                    <FRDOCBP T="16JNN1.sgm" D="1">2011-14972</FRDOCBP>
                    <FRDOCBP T="16JNN1.sgm" D="1">2011-14973</FRDOCBP>
                    <FRDOCBP T="16JNN1.sgm" D="0">2011-14975</FRDOCBP>
                    <FRDOCBP T="16JNN1.sgm" D="0">2011-14976</FRDOCBP>
                </DOCENT>
                <DOCENT>
                    <DOC>Importers of Controlled Substances; Registrations:, </DOC>
                    <PGS>35242</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="0">2011-14959</FRDOCBP>
                </DOCENT>
                <DOCENT>
                    <DOC>Manufacturers of Controlled Substances; Applications, </DOC>
                    <FRDOCBP T="16JNN1.sgm" D="0">2011-14953</FRDOCBP>
                    <FRDOCBP T="16JNN1.sgm" D="0">2011-14968</FRDOCBP>
                    <FRDOCBP T="16JNN1.sgm" D="0">2011-14974</FRDOCBP>
                    <PGS>35242-35243</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="1">2011-14977</FRDOCBP>
                </DOCENT>
                <DOCENT>
                    <DOC>Manufacturers of Controlled Substances; Registrations, </DOC>
                    <PGS>35243-35244</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="1">2011-14960</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Energy Department</EAR>
            <HD>Energy Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Energy Efficiency and Renewable Energy Office</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Federal Energy Regulatory Commission</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>Energy Efficiency</EAR>
            <HD>Energy Efficiency and Renewable Energy Office</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals, </DOC>
                    <PGS>35199-35200</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="1">2011-14997</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Environmental Protection</EAR>
            <HD>Environmental Protection Agency</HD>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <SJ>Revisions to the California State Implementation Plan:</SJ>
                <SJDENT>
                    <SJDOC>San Joaquin Valley Unified Air Pollution Control District, </SJDOC>
                    <PGS>35167-35169</PGS>
                    <FRDOCBP T="16JNP1.sgm" D="2">2011-15000</FRDOCBP>
                </SJDENT>
            </CAT>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Determination of Adequacy for Municipal Solid Waste Landfills:</SJ>
                <SJDENT>
                    <SJDOC>Ohio Research, Development and Demonstration Permit Provisions, </SJDOC>
                    <PGS>35214-35215</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="1">2011-15001</FRDOCBP>
                </SJDENT>
                <DOCENT>
                    <DOC>EPA Workshop on Sanitary Sewer Overflows and Peak Wet Weather Discharges, </DOC>
                    <PGS>35215-35216</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="1">2011-15003</FRDOCBP>
                </DOCENT>
                <SJ>Meetings:</SJ>
                <SJDENT>
                    <SJDOC>Chartered Science Advisory Board; Public Teleconference, </SJDOC>
                    <PGS>35216-35217</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="1">2011-15002</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR/>
            <HD>Executive Office of the President</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Presidential Documents</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>Export Import</EAR>
            <HD>Export-Import Bank</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Meetings:</SJ>
                <SJDENT>
                    <SJDOC>Sub-Saharan Africa Advisory Committee, </SJDOC>
                    <PGS>35217</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="0">2011-14908</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Farm Credit</EAR>
            <PRTPAGE P="iv"/>
            <HD>Farm Credit Administration</HD>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <SJ>Federal Agricultural Mortgage Corporation Funding and Fiscal Affairs:</SJ>
                <SJDENT>
                    <SJDOC>Farmer Mac Risk-Based Capital Stress Test, Version 5.0, </SJDOC>
                    <PGS>35138-35141</PGS>
                    <FRDOCBP T="16JNP1.sgm" D="3">2011-14985</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Federal Aviation</EAR>
            <HD>Federal Aviation Administration</HD>
            <CAT>
                <HD>RULES</HD>
                <SJ>Amendments of Federal Airways:</SJ>
                <SJDENT>
                    <SJDOC>Alaska, </SJDOC>
                    <PGS>35097-35098</PGS>
                    <FRDOCBP T="16JNR1.sgm" D="1">2011-14711</FRDOCBP>
                </SJDENT>
                <DOCENT>
                    <DOC>Standard Instrument Approach Procedures, and Takeoff Minimums and Obstacle Departure Procedures; Miscellaneous Amendments, </DOC>
                    <PGS>35098-35103</PGS>
                    <FRDOCBP T="16JNR1.sgm" D="2">2011-13951</FRDOCBP>
                    <FRDOCBP T="16JNR1.sgm" D="2">2011-13955</FRDOCBP>
                </DOCENT>
                <DOCENT>
                    <DOC>Training and Qualification Requirements for Check Airmen and Flight Instructors; Technical Amendment, </DOC>
                    <PGS>35103-35104</PGS>
                    <FRDOCBP T="16JNR1.sgm" D="1">2011-14999</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Federal Communications</EAR>
            <HD>Federal Communications Commission</HD>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <DOCENT>
                    <DOC>Operation of Radar Systems in 76-77 GHz Band, </DOC>
                    <PGS>35176-35181</PGS>
                    <FRDOCBP T="16JNP1.sgm" D="5">2011-14744</FRDOCBP>
                </DOCENT>
                <SJ>Wireless Backhaul:</SJ>
                <SJDENT>
                    <SJDOC>Fixed Service Sharing of 6875-7125 and 12700-13200 MHz Bands, </SJDOC>
                    <PGS>35181-35184</PGS>
                    <FRDOCBP T="16JNP1.sgm" D="3">2011-14721</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Federal Deposit</EAR>
            <HD>Federal Deposit Insurance Corporation</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Meetings; Sunshine Act, </DOC>
                    <PGS>35217</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="0">2011-15059</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Federal Emergency</EAR>
            <HD>Federal Emergency Management Agency</HD>
            <CAT>
                <HD>RULES</HD>
                <DOCENT>
                    <DOC>Final Flood Elevation Determinations, </DOC>
                    <PGS>35111-35130</PGS>
                    <FRDOCBP T="16JNR1.sgm" D="8">2011-14896</FRDOCBP>
                    <FRDOCBP T="16JNR1.sgm" D="11">2011-14897</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Federal Energy</EAR>
            <HD>Federal Energy Regulatory Commission</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Application Amendments:</SJ>
                <SJDENT>
                    <SJDOC>High Island Offshore System, LLC, </SJDOC>
                    <PGS>35200</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="0">2011-14899</FRDOCBP>
                </SJDENT>
                <SJ>Applications:</SJ>
                <SJDENT>
                    <SJDOC>Dominion Transmission, Inc., </SJDOC>
                    <PGS>35203</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="0">2011-14963</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Jersey Central Power and Light and PSEG Fossil LLC, </SJDOC>
                    <PGS>35201-35202</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="1">2011-14967</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Piedmont Natural Gas Co., Inc., </SJDOC>
                    <PGS>35202-35203</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="1">2011-14964</FRDOCBP>
                </SJDENT>
                <DOCENT>
                    <DOC>Combined Filings, </DOC>
                    <PGS>35203-35207</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="1">2011-14880</FRDOCBP>
                    <FRDOCBP T="16JNN1.sgm" D="1">2011-14881</FRDOCBP>
                    <FRDOCBP T="16JNN1.sgm" D="0">2011-14884</FRDOCBP>
                    <FRDOCBP T="16JNN1.sgm" D="1">2011-14888</FRDOCBP>
                </DOCENT>
                <SJ>Environmental Assessments; Availability, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Boott Hydropower, Inc., </SJDOC>
                    <PGS>35208</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="0">2011-14970</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Central New York Oil and Gas Co., LLC, </SJDOC>
                    <PGS>35208</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="0">2011-14962</FRDOCBP>
                </SJDENT>
                <SJ>Environmental Site Reviews:</SJ>
                <SJDENT>
                    <SJDOC>Pacific Gas and Electric Co., and Nevada Irrigation District, </SJDOC>
                    <PGS>35208-35209</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="1">2011-14969</FRDOCBP>
                </SJDENT>
                <SJ>Filings:</SJ>
                <SJDENT>
                    <SJDOC>FFP Qualified Hydro 14 LLC, </SJDOC>
                    <PGS>35209</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="0">2011-14971</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Orlando Utilities Commission, </SJDOC>
                    <PGS>35209</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="0">2011-14965</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Peetz Logan Interconnect, LLC, </SJDOC>
                    <PGS>35210</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="0">2011-14885</FRDOCBP>
                </SJDENT>
                <SJ>Initial Market-Based Rate Filings Including Requests for Blanket Section 204 Authorizations:</SJ>
                <SJDENT>
                    <SJDOC>El Segundo Energy Center LLC, </SJDOC>
                    <PGS>35211</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="0">2011-14886</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>LWP Lessee, LLC, </SJDOC>
                    <PGS>35211-35212</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="1">2011-14887</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Palmco Power DC, LLC, </SJDOC>
                    <PGS>35211</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="0">2011-14889</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>People's Power and Gas, LLC, </SJDOC>
                    <PGS>35210</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="0">2011-14883</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Pocahontas Prairie Wind, LLC, </SJDOC>
                    <PGS>35210-35211</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="1">2011-14882</FRDOCBP>
                </SJDENT>
                <SJ>License Amendment Applications:</SJ>
                <SJDENT>
                    <SJDOC>Northern States Power Co., </SJDOC>
                    <PGS>35212-35213</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="1">2011-14966</FRDOCBP>
                </SJDENT>
                <SJ>License Application Supplements:</SJ>
                <SJDENT>
                    <SJDOC>S. D. Warren Company, </SJDOC>
                    <PGS>35213</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="0">2011-14898</FRDOCBP>
                </SJDENT>
                <SJ>Preliminary Permit Applications:</SJ>
                <SJDENT>
                    <SJDOC>AJT Mining Properties, Inc., </SJDOC>
                    <PGS>35213-35214</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="1">2011-14961</FRDOCBP>
                </SJDENT>
                <SJ>Staff Attendances:</SJ>
                <SJDENT>
                    <SJDOC>Southwest Power Pool, Inc. Board of Directors, </SJDOC>
                    <PGS>35214</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="0">2011-14901</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Federal Highway</EAR>
            <HD>Federal Highway Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals, </DOC>
                    <PGS>35263-35266</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="2">2011-14892</FRDOCBP>
                    <FRDOCBP T="16JNN1.sgm" D="1">2011-14916</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Federal Reserve</EAR>
            <HD>Federal Reserve System</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Formations of, Acquisitions by, and Mergers of Bank Holding Companies, </DOC>
                    <PGS>35217-35218</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="1">2011-14979</FRDOCBP>
                </DOCENT>
                <DOCENT>
                    <DOC>Proposals to Engage in Permissible Nonbanking Activities or Acquire Companies Engaged in Permissible Nonbanking Activities, </DOC>
                    <PGS>35218</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="0">2011-14978</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Fish</EAR>
            <HD>Fish and Wildlife Service</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Endangered and Threatened Species Permit Applications, </DOC>
                    <PGS>35235-35236</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="1">2011-14927</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Food and Nutrition</EAR>
            <HD>Food and Nutrition Service</HD>
            <CAT>
                <HD>RULES</HD>
                <SJ>Special Supplemental Nutrition Program for Women, Infants and Children:</SJ>
                <SJDENT>
                    <SJDOC>Exclusion of Combat Pay from WIC Income Eligibility Determinations, </SJDOC>
                    <PGS>35095-35097</PGS>
                    <FRDOCBP T="16JNR1.sgm" D="2">2011-14904</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Forest</EAR>
            <HD>Forest Service</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Meetings:</SJ>
                <SJDENT>
                    <SJDOC>Fremont and Winema Resource Advisory Committee, </SJDOC>
                    <PGS>35187</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="0">2011-14939</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>General Services</EAR>
            <HD>General Services Administration</HD>
            <CAT>
                <HD>RULES</HD>
                <SJ>Federal Travel Regulations:</SJ>
                <SJDENT>
                    <SJDOC>Miscellaneous Expense Allowance, </SJDOC>
                    <PGS>35110-35111</PGS>
                    <FRDOCBP T="16JNR1.sgm" D="1">2011-14890</FRDOCBP>
                </SJDENT>
            </CAT>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
                <SJDENT>
                    <SJDOC>Federal Acquisition Regulation; Cost or Pricing Data Requirements and Information Other Than Cost or Pricing Data, </SJDOC>
                    <PGS>35218-35219</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="1">2011-14863</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Federal Acquisition Regulation; Payment by Electronic Fund Transfer, </SJDOC>
                    <PGS>35219</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="0">2011-14862</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Health and Human</EAR>
            <HD>Health and Human Services Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Children and Families Administration</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Indian Health Service</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>National Institutes of Health</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>Homeland</EAR>
            <HD>Homeland Security Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Coast Guard</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Federal Emergency Management Agency</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Transportation Security Administration</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>Housing</EAR>
            <HD>Housing and Urban Development Department</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
                <SJDENT>
                    <SJDOC>Housing Choice Voucher Program Administrative Fee Study Pretest, </SJDOC>
                    <PGS>35232-35233</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="1">2011-14906</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>McKinney-Vento Technical Assistance Narrative, Matrices, and Reporting Requirements, </SJDOC>
                    <PGS>35231</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="0">2011-14905</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Section 3 Business Self-Certification Application, </SJDOC>
                    <PGS>35231-35232</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="1">2011-14909</FRDOCBP>
                </SJDENT>
                <SJ>Funding Availability for Fiscal Year 2011:</SJ>
                <SJDENT>
                    <SJDOC>Choice Neighborhoods Initiative - Planning Grants, </SJDOC>
                    <PGS>35234</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="0">2011-14911</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Doctoral Dissertation Research Grant Program, </SJDOC>
                    <PGS>35233-35234</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="1">2011-14912</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <PRTPAGE P="v"/>
                    <SJDOC>Housing Opportunities for Persons With AIDS, </SJDOC>
                    <PGS>35233</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="0">2011-14910</FRDOCBP>
                </SJDENT>
                <SJ>Funding Awards for Fiscal Year 2010 Transformation Initiative:</SJ>
                <SJDENT>
                    <SJDOC>Natural Experiments Grant Program, </SJDOC>
                    <PGS>35234-35235</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="1">2011-14913</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Indian Health</EAR>
            <HD>Indian Health Service</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Epidemiology Program for American Indian-Alaska Native Tribes and Urban Indian Communities; Correction, </DOC>
                    <PGS>35221</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="0">2011-14794</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Industry</EAR>
            <HD>Industry and Security Bureau</HD>
            <CAT>
                <HD>RULES</HD>
                <SJ>Export Control Reform Initiative:</SJ>
                <SJDENT>
                    <SJDOC>Strategic Trade Authorization License Exception, </SJDOC>
                    <PGS>35276-35294</PGS>
                    <FRDOCBP T="16JNR2.sgm" D="18">2011-14705</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Interior</EAR>
            <HD>Interior Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Fish and Wildlife Service</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Land Management Bureau</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>International Trade Com</EAR>
            <HD>International Trade Commission</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Complaints, </DOC>
                    <PGS>35238</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="0">2011-14934</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Justice Department</EAR>
            <HD>Justice Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Drug Enforcement Administration</P>
            </SEE>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Lodging Of Consent Decrees Under the Clean Air Act, </DOC>
                    <PGS>35238-35239</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="1">2011-14914</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Labor Department</EAR>
            <HD>Labor Department</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Bahrain - U.S. Free Trade Agreement; Determinations:, </DOC>
                    <PGS>35244-35245</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="1">2011-14893</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Land</EAR>
            <HD>Land Management Bureau</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals, </DOC>
                    <PGS>35236-35238</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="2">2011-14984</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>NASA</EAR>
            <HD>National Aeronautics and Space Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
                <SJDENT>
                    <SJDOC>Federal Acquisition Regulation; Cost or Pricing Data Requirements and Information Other Than Cost or Pricing Data, </SJDOC>
                    <PGS>35218-35219</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="1">2011-14863</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Federal Acquisition Regulation; Payment by Electronic Fund Transfer, </SJDOC>
                    <PGS>35219</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="0">2011-14862</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>National Highway</EAR>
            <HD>National Highway Traffic Safety Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals, </DOC>
                    <PGS>35266-35271</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="1">2011-14993</FRDOCBP>
                    <FRDOCBP T="16JNN1.sgm" D="3">2011-14995</FRDOCBP>
                </DOCENT>
                <SJ>Receipt of Petition for Decision of Inconsequential Noncompliance:</SJ>
                <SJDENT>
                    <SJDOC>Toyota Motor North America, Inc., </SJDOC>
                    <PGS>35271-35273</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="2">2011-14902</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>National Institute</EAR>
            <HD>National Institutes of Health</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
                <SJDENT>
                    <SJDOC>NINR End-of-Life and Palliative Care Science Needs Assessment; Funding Source Questionnaire, </SJDOC>
                    <PGS>35221</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="0">2011-14878</FRDOCBP>
                </SJDENT>
                <SJ>Charter Renewals:</SJ>
                <SJDENT>
                    <SJDOC>Advisory Committee to the Director, </SJDOC>
                    <PGS>35221-35222</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="1">2011-15006</FRDOCBP>
                </SJDENT>
                <SJ>Meetings:</SJ>
                <SJDENT>
                    <SJDOC>Center for Scientific Review, </SJDOC>
                    <PGS>35223, 35225-35228</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="0">2011-14872</FRDOCBP>
                    <FRDOCBP T="16JNN1.sgm" D="0">2011-14873</FRDOCBP>
                    <FRDOCBP T="16JNN1.sgm" D="1">2011-15005</FRDOCBP>
                    <FRDOCBP T="16JNN1.sgm" D="0">2011-15012</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Eunice Kennedy Shriver National Institute of Child Health and Human Development, </SJDOC>
                    <PGS>35226</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="0">2011-14875</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>National Center for Complementary and Alternative Medicine, </SJDOC>
                    <PGS>35227</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="0">2011-15013</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>National Center for Research Resources, </SJDOC>
                    <PGS>35223-35224</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="1">2011-14877</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>National Human Genome Research Institute, </SJDOC>
                    <PGS>35223-35224</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="0">2011-14876</FRDOCBP>
                    <FRDOCBP T="16JNN1.sgm" D="0">2011-15011</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>National Institute of Allergy and Infectious Diseases, </SJDOC>
                    <PGS>35224-35225</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="1">2011-15009</FRDOCBP>
                    <FRDOCBP T="16JNN1.sgm" D="0">2011-15010</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>National Institute of Arthritis and Musculoskeletal and Skin Diseases, </SJDOC>
                    <PGS>35225</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="0">2011-15008</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>National Institute of Environmental Health Sciences, </SJDOC>
                    <PGS>35225</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="0">2011-15007</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>National Institute of General Medical Sciences, </SJDOC>
                    <PGS>35222</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="0">2011-14865</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>National Institute on Deafness and Other Communication Disorders, </SJDOC>
                    <FRDOCBP T="16JNN1.sgm" D="0">2011-14864</FRDOCBP>
                    <PGS>35222-35223</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="1">2011-14866</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>National Institute on Drug Abuse, </SJDOC>
                    <FRDOCBP T="16JNN1.sgm" D="0">2011-14868</FRDOCBP>
                    <PGS>35226-35228</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="1">2011-14870</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Navy</EAR>
            <HD>Navy Department</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Partially-Exclusive Patent Licenses:</SJ>
                <SJDENT>
                    <SJDOC>Sound Metrics Corp., </SJDOC>
                    <PGS>35199</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="0">2011-14930</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Nuclear Regulatory</EAR>
            <HD>Nuclear Regulatory Commission</HD>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <DOCENT>
                    <DOC>Vulnerability and Threat Information for Facilities Storing Spent Nuclear Fuel and High-Level Radioactive Waste; Public Meeting, </DOC>
                    <PGS>35137-35138</PGS>
                    <FRDOCBP T="16JNP1.sgm" D="1">2011-14666</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Pipeline</EAR>
            <HD>Pipeline and Hazardous Materials Safety Administration</HD>
            <CAT>
                <HD>RULES</HD>
                <SJ>Pipeline Safety:</SJ>
                <SJDENT>
                    <SJDOC>Control Room Management/Human Factors, </SJDOC>
                    <PGS>35130-35136</PGS>
                    <FRDOCBP T="16JNR1.sgm" D="6">2011-14991</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Presidential Documents</EAR>
            <HD>Presidential Documents</HD>
            <CAT>
                <HD>EXECUTIVE ORDERS</HD>
                <SJ>Government agencies and employees:</SJ>
                <SJDENT>
                    <SJDOC>Efficient, effective, and accountable government (EO13576), </SJDOC>
                    <PGS>35295-35299</PGS>
                    <FRDOCBP T="16JNE0.sgm" D="4">2011-15181</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Securities</EAR>
            <HD>Securities and Exchange Commission</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals, </DOC>
                    <PGS>35245</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="0">2011-14988</FRDOCBP>
                </DOCENT>
                <SJ>Applications:</SJ>
                <SJDENT>
                    <SJDOC>Allianz Life Insurance Company of North America, et al., </SJDOC>
                    <PGS>35249-35256</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="7">2011-14895</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>COUNTRY Investors Life Assurance Company, et al., </SJDOC>
                    <PGS>35245-35249</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="4">2011-14859</FRDOCBP>
                </SJDENT>
                <SJ>Self-Regulatory Organizations; Proposed Rule Changes:</SJ>
                <SJDENT>
                    <SJDOC>Chicago Stock Exchange, Inc., </SJDOC>
                    <PGS>35257-35259</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="2">2011-14894</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>NASDAQ OMX PHLX LLC, </SJDOC>
                    <PGS>35256-35257</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="1">2011-14903</FRDOCBP>
                </SJDENT>
                <SJ>Suspension of Trading Orders:</SJ>
                <SJDENT>
                    <SJDOC>Dawn Technologies, Inc., Distinctive Devices, Inc., Haber, Inc., and Independence Brewing Co., </SJDOC>
                    <PGS>35259-35260</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="1">2011-15055</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Samaritan Pharmaceuticals, Inc., et al., </SJDOC>
                    <PGS>35259</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="0">2011-15056</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Small Business</EAR>
            <HD>Small Business Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Disaster Declarations:</SJ>
                <SJDENT>
                    <SJDOC>Arkansas; Amendment 4, </SJDOC>
                    <PGS>35262</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="0">2011-14948</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Arkansas; Amendment 5, </SJDOC>
                    <PGS>35262</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="0">2011-14946</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Illinois, </SJDOC>
                    <PGS>35260-35261</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="1">2011-14951</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Minnesota, </SJDOC>
                    <PGS>35261</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="0">2011-14950</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Missouri; Amendment 3, </SJDOC>
                    <PGS>35262</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="0">2011-14947</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Missouri; Amendment 4, </SJDOC>
                    <PGS>35263</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="0">2011-14944</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>North Dakota; Amendment 2, </SJDOC>
                    <PGS>35262-35263</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="1">2011-14945</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Tennessee; Amendment 2, </SJDOC>
                    <PGS>35260</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="0">2011-14918</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <PRTPAGE P="vi"/>
                    <SJDOC>Tennessee; Amendment 3, </SJDOC>
                    <PGS>35261</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="0">2011-14949</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Tennnessee, </SJDOC>
                    <PGS>35260</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="0">2011-14917</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Texas; Amendment 1, </SJDOC>
                    <PGS>35260</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="0">2011-14955</FRDOCBP>
                </SJDENT>
                <SJ>Requests for Exemptions:</SJ>
                <SJDENT>
                    <SJDOC>Founders Equity SBIC ILP, </SJDOC>
                    <PGS>35263</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="0">2011-14958</FRDOCBP>
                </SJDENT>
                <DOCENT>
                    <DOC>Small Business Size Standards, Waiver of the Nonmanufacturer Rule; Correction, </DOC>
                    <PGS>35263</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="0">2011-14952</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Surface Transportation</EAR>
            <HD>Surface Transportation Board</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Trackage Rights Exemptions:</SJ>
                <SJDENT>
                    <SJDOC>CSX Transportation, Inc.; Indiana Rail Road Co., </SJDOC>
                    <PGS>35273</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="0">2011-14640</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Transportation Department</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>National Highway Traffic Safety Administration</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Pipeline and Hazardous Materials Safety Administration</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Surface Transportation Board</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Transportation Security Administration</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>Security</EAR>
            <HD>Transportation Security Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
                <SJDENT>
                    <SJDOC>Critical Facility Information of the Top 100 Most Critical Pipelines, </SJDOC>
                    <PGS>35229-35230</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="1">2011-14996</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Treasury</EAR>
            <HD>Treasury Department</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Meetings:</SJ>
                <SJDENT>
                    <SJDOC>President's Advisory Council on Financial Capability, </SJDOC>
                    <PGS>35273-35274</PGS>
                    <FRDOCBP T="16JNN1.sgm" D="1">2011-14998</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Veteran Affairs</EAR>
            <HD>Veterans Affairs Department</HD>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <DOCENT>
                    <DOC>Service Dogs, </DOC>
                    <PGS>35162-35167</PGS>
                    <FRDOCBP T="16JNP1.sgm" D="5">2011-14933</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <PTS>
            <HD SOURCE="HED">Separate Parts In This Issue</HD>
            <HD>Part II</HD>
            <DOCENT>
                <DOC>Commerce Department, Industry and Security Bureau, </DOC>
                <PGS>35276-35294</PGS>
                <FRDOCBP T="16JNR2.sgm" D="18">2011-14705</FRDOCBP>
            </DOCENT>
            <HD>Part III</HD>
            <DOCENT>
                <DOC>Presidential Documents, </DOC>
                <PGS>35295-35299</PGS>
                <FRDOCBP T="16JNE0.sgm" D="4">2011-15181</FRDOCBP>
            </DOCENT>
        </PTS>
        <AIDS>
            <HD SOURCE="HED">Reader Aids</HD>
            <P>Consult the Reader Aids section at the end of this page for phone numbers, online resources, finding aids, reminders, and notice of recently enacted public laws.</P>
            <P> </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>76</VOL>
    <NO>116</NO>
    <DATE>Thursday, June 16, 2011</DATE>
    <UNITNAME>Rules and Regulations</UNITNAME>
    <RULES>
        <RULE>
            <PREAMB>
                <PRTPAGE P="35095"/>
                <AGENCY TYPE="F">DEPARTMENT OF AGRICULTURE</AGENCY>
                <SUBAGY>Food and Nutrition Service</SUBAGY>
                <CFR>7 CFR Part 246</CFR>
                <RIN>RIN 0584-AE04</RIN>
                <SUBJECT>Special Supplemental Nutrition Program for Women, Infants and Children (WIC): Exclusion of Combat Pay From WIC Income Eligibility Determinations</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Food and Nutrition Service (FNS), USDA.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This final rule incorporates into the regulations governing the Special Supplemental Nutrition Program for Women, Infants and Children (WIC) a statutory provision set forth in Section 734(b) of the Agriculture, Rural Development, Food and Drug Administration, and Related Agencies Appropriations Act of 2010 (Pub. L. 111-80). The provision excludes combat pay from inclusion in the WIC income eligibility determination for deployed service members. It also makes conforming nomenclature changes throughout part 246 of WIC regulations to include the name change for what was formerly known as the Food Stamp Program to its new name—the Supplemental Nutrition Assistance Program (SNAP), as set forth in the Food, Conservation and Energy Act of 2008 (Pub. L. 110-246).</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        <E T="03">Effective Date:</E>
                         This rule is effective July 18, 2011.
                    </P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Debra R. Whitford, Director, Supplemental Food Programs Division, Food and Nutrition Service, USDA, 3101 Park Center Drive, Room 520, Alexandria, Virginia 22302; (703) 305-2746; 
                        <E T="03">e-mail: Debbie.Whitford@fns.usda.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Background</HD>
                <HD SOURCE="HD2">Combat Pay Exclusion</HD>
                <P>Section 734(b) of Public Law 111-80, the Agriculture, Rural Development, Food and Drug Administration, and Related Agencies Appropriations Act of 2010 (the Act), enacted on October 21, 2009, amended Section 17(d)(2) of the Child Nutrition Act of 1966 (42 U.S.C. 1786(d)(2)) to exclude from the WIC income eligibility determination, combat pay that is received by or from a member of the United States (U.S.) Armed Services that is received in addition to basic pay as a result of the service member's deployment or service in a designated combat zone. In addition, the pay must not have been received prior to serving in a combat zone. Combat pay includes any additional pay received pursuant to Chapter 5 of Title 37 of the United States Code, or otherwise designated by the Secretary to be appropriate for exclusion as combat pay.</P>
                <P>This provision was effective on October 21, 2009. On November 5, 2009, the Food and Nutrition Service directed WIC State and local agencies to implement this income exclusion immediately. This final rule amends 7 CFR 246.7, Certification of Participants, to reflect that combat pay is excluded from the WIC income eligibility determination process.</P>
                <HD SOURCE="HD2">Food Stamp Program Name Change</HD>
                <P>
                    Section 4001 of Public Law 110-246, the Food, Conservation, and Energy Act of 2008 (FCEA), which was enacted on June 18, 2008, amended and renamed the Food Stamp Act of 1977, 7 U.S.C. 2011, 
                    <E T="03">et seq.,</E>
                     as the Food and Nutrition Act of 2008. FCEA changed the name of the program from the “Food Stamp Program” to the “Supplemental Nutrition Assistance Program” or “SNAP”. This change in name reflects the fact that participants no longer receive stamps or coupons to make food purchases.
                </P>
                <P>Additionally, the new name reflects a focus on the nutritional aspect of the program. SNAP not only provides food assistance to low-income people, but also promotes nutrition to improve their health and well-being.</P>
                <P>Accordingly, this rule makes the following name changes in 7 CFR part 246 to make the Federal WIC regulations consistent with the name changes set forth in the FCEA:</P>
                <GPOTABLE COLS="2" OPTS="L2,tp0,i1" CDEF="s60,r75">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Previous name </CHED>
                        <CHED H="1">New name</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">“Food Stamp Program” </ENT>
                        <ENT>“Supplemental Nutrition Assistance Program (SNAP).”</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">“Food Stamp Act of 1977” </ENT>
                        <ENT>“Food and Nutrition Act of 2008.”</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">“food stamp” </ENT>
                        <ENT>“SNAP.”</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">“food coupons” </ENT>
                        <ENT>“SNAP benefits” or “benefits.”</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">“Food stamps” </ENT>
                        <ENT>“SNAP benefits” or “benefits.”</ENT>
                    </ROW>
                </GPOTABLE>
                <HD SOURCE="HD1">Notice and Comment</HD>
                <P>In accordance with the Secretary's Statement of Policy (36 FR 13804), it is found and determined with good cause that it is unnecessary to engage in the Notice and Comment provisions of 5 U.S.C. 553 normally required before the adoption of final regulations in an FNS-sponsored program. The exclusion of combat pay from consideration as income under the WIC Program is implemented in this final rule in accordance with Section 734(b) of the Act. The nondiscretionary nature of Section 734(b) means that notice and comment would serve no useful purpose in the promulgation of these regulations. The name changes related to SNAP are technical amendments designed to make the WIC portion of 7 CFR consistent with its SNAP counterparts.</P>
                <HD SOURCE="HD1">Executive Order 12866 and Executive Order 13563</HD>
                <P>Executive Orders 12866 and 13563 direct agencies to assess all costs and benefits of available regulatory alternatives and, if regulation is necessary, to select regulatory approaches that maximize net benefits (including potential economic, environmental, public health and safety effects, distributive impacts, and equity). Executive Order 13563 emphasizes the importance of quantifying both costs and benefits, of reducing costs, of harmonizing rules, and of promoting flexibility.</P>
                <P>This final rule has been designated a “significant regulatory action,” under section 3(f) of Executive Order 12866. Accordingly, the rule has been reviewed by the Office of Management and Budget.</P>
                <HD SOURCE="HD1">Regulatory Impact Analysis</HD>
                <P>
                    This rule has been designated as significant by the Office of Management and Budget; therefore, a Regulatory 
                    <PRTPAGE P="35096"/>
                    Impact Analysis (RIA) is required, as summarized below. The complete RIA is available upon request from the Food and Nutrition Service by contacting Debra R. Whitford, Director, Supplemental Food Programs Division, Food and Nutrition Service, USDA, 3101 Park Center Drive, Room 520, Alexandria, Virginia 22302; (703) 305-2746; e-mail 
                    <E T="03">Debbie.Whitford@fns.usda.gov</E>
                    .
                </P>
                <HD SOURCE="HD2">Need for Action</HD>
                <P>The final rule amends the WIC regulations to implement the exclusion of combat pay from income eligibility determination as mandated in Public Law 111-80, the Agriculture, Rural Development, Food and Drug Administration, and Related Agencies Appropriations Act, 2010, and changes references to the Food Stamp Program to its new name—the Supplemental Nutrition Assistance Program.</P>
                <HD SOURCE="HD2">Benefits</HD>
                <P>The benefit of this provision will extend eligibility to deployed service members who might otherwise not be eligible due to the inclusion of combat pay when determining income eligibility to receive WIC benefits.</P>
                <HD SOURCE="HD2">Costs</HD>
                <P>The provisions of this final rule will have an insignificant effect upon the administrative burden to the Department or to State agencies. Applicants who were previously found ineligible due to being over the WIC income eligibility limits may now be found eligible when combat pay is excluded from the income eligibility determination. This, in turn, may increase the number of persons served, resulting in a small cost increase to the WIC Program. We estimate that the rule will increase WIC costs by less than $1 million per year, or about $4 million from FY 2010 when State agencies began implementing the combat pay exclusion through FY 2014.</P>
                <HD SOURCE="HD1">Regulatory Flexibility Act</HD>
                <P>The Regulatory Flexibility Act (5 U.S.C. 601-612) requires Agencies to analyze the impact of rulemaking on small entities and consider alternatives that would minimize any significant impacts on a substantial number of small entities. Pursuant to that review, it is certified that this rule would not have a significant impact on small entities.</P>
                <P>The provisions of this rulemaking are applicable to all State and local agencies that administer the WIC Program.</P>
                <HD SOURCE="HD1">Unfunded Mandates Reform Act</HD>
                <P>Title II of the Unfunded Mandates Reform Act of 1995 (UMRA), Public Law 104-4, establishes requirements for Federal agencies to assess the effects of their regulatory actions on State, local, and Tribal governments and the private sector. Under Section 202 of the UMRA, FNS generally must prepare a written statement, including a cost-benefit analysis, for proposed and final rules with “Federal mandates” that may result in expenditures by State, local, or Tribal governments in the aggregate, or to the private sector, of $100 million or more in any one year. When such a statement is needed for a rule, Section 205 of the UMRA generally requires FNS to identify and consider a reasonable number of regulatory alternatives and adopt the least costly, more cost-effective or least burdensome alternative that achieves the objectives of the rule.</P>
                <P>This final rule contains no Federal mandates (under the regulatory provisions of Title II of the UMRA) for State, local or Tribal governments or the private sector of $100 million or more in any one year. Thus, the rule is not subject to the requirements of Sections 202 and 205 of the UMRA.</P>
                <HD SOURCE="HD1">Executive Order 12372</HD>
                <P>WIC is listed in the Catalog of Federal Domestic Assistance under No. 10.557. For the reasons set forth in the final rule at 7 CFR part 3015, Subpart V and related Notice (48 FR 29115, June 24, 1983), this program is included in the scope of Executive Order 12372 that requires intergovernmental consultation with State and local officials.</P>
                <HD SOURCE="HD1">Federalism Summary Impact Statement</HD>
                <P>Executive Order 13132 requires Federal agencies to consider the impact of their regulatory actions on State and local governments. Where such actions have federalism implications, agencies are directed to provide a statement for inclusion in the preamble to the regulations describing the agency's considerations in terms of the three categories called for under Section 6(b)(2)(B) of Executive Order 13132. FNS has considered the impact of this rule on State and local governments and has determined that this rule does not have federalism implications. Therefore, under Section 6(b) of the Executive Order, a federalism summary impact statement is not required.</P>
                <HD SOURCE="HD1">Executive Order 12988</HD>
                <P>This rule has been reviewed under Executive Order 12988, Civil Justice Reform. This rule is intended to have preemptive effect with respect to any State or local laws, regulations, or policies that conflict with its provisions or that would otherwise impede its full implementation. This rule is not intended to have retroactive effect unless so specified in the Dates paragraph of the preamble to the final rule. Prior to any judicial challenge to the application of the provisions of this rule, all applicable administrative procedures must be exhausted.</P>
                <P>In WIC, the administrative procedures are as follows: (1) State and local agencies, farmers, farmers' markets, and roadside stands—State agency hearing procedures issued pursuant to 7 CFR 246.18; (2) Applicants and participants—State agency hearing procedures pursuant to 7 CFR 246.18; (3) sanctions against State agencies (but not claims for repayment assessed against a State agency) pursuant to 7 CFR 246.19—administrative appeal in accordance with 7 CFR 246.16, and (4) procurement by State or local agencies—administrative appeal to the extent required by 7 CFR 3016.36.</P>
                <HD SOURCE="HD1">Civil Rights Impact Analysis</HD>
                <P>FNS has reviewed this rule in accordance with Departmental Regulations 4300-4, “Civil Rights Impact Analysis,” and 1512-1, “Regulatory Decision Making Requirements.” After a careful review of the rule's intent and provisions, FNS has determined that this rule is not intended to limit or reduce in any way the ability of protected classes of individuals to receive benefits in the WIC Program. Federal WIC regulations specifically prohibit State agencies that administer the WIC Program, and their cooperators, from engaging in actions that discriminate against any individual in any of the protected classes (see 7 CFR 246.8 for the nondiscrimination policy in the WIC Program). Where State agencies have options, and they choose to implement a certain provision, they must implement it in such a way that it complies with the WIC Program regulations set forth at § 246.8. This rule simply excludes combat pay given to United States Armed Service members that is received in addition to basic pay as a result of the service member's deployment or service in a designated combat zone from income eligibility determination for WIC, and codifies the name change for what was formerly known as the Food Stamp Program to its new name—SNAP.</P>
                <HD SOURCE="HD1">Executive Order 13175—Consultation and Coordination With Indian Tribal Governments</HD>
                <P>
                    E.O. 13175 requires Federal agencies to consult and coordinate with Tribes 
                    <PRTPAGE P="35097"/>
                    on a government-to-government basis on policies that have Tribal implications, including regulations, legislative comments or proposed legislation, and other policy statements or actions that have substantial direct effects 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. In late 2010 and early 2011, USDA engaged in a series of consultative sessions to obtain input by Tribal officials or their designees concerning the impact of this rule on the Tribe or Indian Tribal governments, or whether this rule may preempt Tribal law. Reports from these consultations will be made part of the USDA annual reporting on Tribal Consultation and Collaboration. USDA will respond in a timely and meaningful manner to all Tribal government requests for consultation concerning this rule and will provide additional venues, such as webinars and teleconferences, to periodically host collaborative conversations with Tribal officials or their designees concerning ways to improve this rule in Indian country.
                </P>
                <P>The policies contained in this rule would not have Tribal implications that preempt Tribal law.</P>
                <HD SOURCE="HD1">Paperwork Reduction Act</HD>
                <P>This rule does not constitute a collection of information under the Paperwork Reduction Act of 1995 (44 U.S.C. chapter 35).</P>
                <HD SOURCE="HD1">E-Government Act Compliance</HD>
                <P>FNS is committed to complying with the E-Government Act of 2002 to promote the use of the Internet and other information technologies to provide increased opportunities to provide for citizen access to government information and services, and for other purposes. State plan amendments regarding the implementation of the provision contained in this rule, as is the case with the entire State Plan, may be transmitted electronically by the State agency to FNS. Also, State agencies may provide WIC Program information, as well as their financial reports, to FNS electronically.</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 7 CFR Part 246</HD>
                    <P>Food assistance programs, Food donations, Grant programs—Social programs, Indians, Nutrition education, Public assistance programs, WIC.</P>
                </LSTSUB>
                <P>For reasons discussed above, 7 CFR part 246 is amended as follows:</P>
                <REGTEXT TITLE="7" PART="246">
                    <PART>
                        <HD SOURCE="HED">PART 246—SPECIAL SUPPLEMENTAL NUTRITION PROGRAM FOR WOMEN, INFANTS AND CHILDREN (WIC)</HD>
                    </PART>
                    <AMDPAR>1. The authority citation for part 246 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority: </HD>
                        <P>7 U.S.C. 1786.</P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="7" PART="246">
                    <AMDPAR>2. Part 246 of this chapter is amended as follows:</AMDPAR>
                    <AMDPAR>a. Remove the words “Food Stamp Program” and “the Food Stamp Program” and add in their place, the word “SNAP” each time they appear in this part;</AMDPAR>
                    <AMDPAR>b. Remove the words “Food Stamp Act of 1977” and add in their place, the words “Food and Nutrition Act of 2008” each time they appear in this part;</AMDPAR>
                    <AMDPAR>c. Remove the words “food stamp” and add in their place, the word “SNAP” each time it appears in this part; and</AMDPAR>
                    <AMDPAR>d. Remove the words “food stamps” wherever they appear and add in their place, the words “SNAP benefits”.</AMDPAR>
                </REGTEXT>
                <REGTEXT TITLE="7" PART="246">
                    <AMDPAR>
                        3. In § 246.2, a definition of 
                        <E T="03">Supplemental Nutrition Assistance Program (SNAP)</E>
                         is added, to read as follows:
                    </AMDPAR>
                    <SECTION>
                        <SECTNO>§ 246.2 </SECTNO>
                        <SUBJECT>Definitions.</SUBJECT>
                        <STARS/>
                        <P>
                            <E T="03">Supplemental Nutrition Assistance Program (SNAP),</E>
                             formerly known as the Food Stamp Program, is the program authorized by the Food and Nutrition Act of 2008 (7 U.S.C. 2011, 
                            <E T="03">et. seq.</E>
                            ), in which eligible households receive benefits that can be used to purchase food items from authorized retail stores and farmers' markets.
                        </P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="7" PART="246">
                    <AMDPAR>
                        4. In § 246.7, a new paragraph (d)(2)(iv)(D)(
                        <E T="03">35</E>
                        ) is added, to read as follows:
                    </AMDPAR>
                    <SECTION>
                        <SECTNO>§ 246.7 </SECTNO>
                        <SUBJECT>Certification of participants.</SUBJECT>
                        <STARS/>
                        <P>(d) * * *</P>
                        <P>(2) * * *</P>
                        <P>(iv) * * *</P>
                        <P>(D) * * *</P>
                        <P>
                            (
                            <E T="03">35</E>
                            ) Combat pay received by the household member under Chapter 5 of Title 37 or as otherwise designated by the Secretary.
                        </P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <SIG>
                    <DATED>Dated: June 8, 2011.</DATED>
                    <NAME>Kevin Concannon,</NAME>
                    <TITLE>Under Secretary, Food, Nutrition, and Consumer Services.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-14904 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3410-30-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <CFR>14 CFR Part 71</CFR>
                <DEPDOC>[Docket No. FAA-2011-0010; Airspace Docket No. 11-AAL-1]</DEPDOC>
                <SUBJECT>Amendment of Federal Airways; Alaska</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration (FAA), DOT.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule; delay of effective date.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This action changes the effective date for the amendment of all Anchorage, AK, Federal Airways that are affected by the relocation of the Anchorage VHF Omnidirectional Range (VOR) navigation aid. The FAA is taking this action due to a failed flight inspection.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The effective date of the rule published on April 28, 2011 (76 FR 23687), is delayed until further notice.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Ken McElroy, Airspace, Regulations and ATC Procedures Group, Office of Mission Support Services, Federal Aviation Administration, 800 Independence Avenue, SW., Washington, DC 20591; 
                        <E T="03">telephone:</E>
                         (202) 267-8783.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Background</HD>
                <P>
                    Federal Register Document FAA-2011-0010, Airspace Docket No. 11-AAL-1, published in the 
                    <E T="04">Federal Register</E>
                     on April 28, 2011 (76 FR 23687), proposed the amendment of all Anchorage Federal Airways affected by the relocation of the Anchorage VOR navigation aid. Although satisfactory flight inspection reports were filed in April 2011, these reports were in error. These Federal airways are being impacted by flight inspection delays due to the relocation of the navigation aid, thereby delaying the effective date of June 30, 2011, until further notice. This will allow better coordination for the charting of the airspace.
                </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. Therefore, this regulation (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 
                    <PRTPAGE P="35098"/>
                    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 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>This rulemaking is promulgated under the authority described in subtitle VII, part A, subpart I, section 40103. Under that section, the FAA is charged with prescribing regulations to assign the use of the airspace necessary to ensure the safety of aircraft and the efficient use of airspace. This regulation is within the scope of that authority as it modifies federal airways in Alaska.</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 14 CFR Part 71</HD>
                    <P>Airspace, Incorporation by reference, Navigation (air).</P>
                </LSTSUB>
                <HD SOURCE="HD1">Delay of Effective Date</HD>
                <P>
                    The effective date of the final rule, Airspace Docket 11-AAL-1, as published in the 
                    <E T="04">Federal Register</E>
                     on April 28, 2011 (76 FR 23687), is hereby delayed from June 30, 2011, until further notice.
                </P>
                <AUTH>
                    <HD SOURCE="HED">Authority: </HD>
                    <P> 49 U.S.C. 106(g), 40103, 40113, 40120; E.O. 10854, 24 FR 9565, 3 CFR, 1959-1963 Comp., p. 389.</P>
                </AUTH>
                <SIG>
                    <DATED>Issued in Washington, DC, on June 8, 2011.</DATED>
                    <NAME>Gary A. Norek,</NAME>
                    <TITLE>Acting Manager, Airspace, Regulations and ATC Procedures Group.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-14711 Filed 6-15-11; 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 97</CFR>
                <DEPDOC>[Docket No. 30786; Amdt. No. 3429]</DEPDOC>
                <SUBJECT>Standard Instrument Approach Procedures, and Takeoff Minimums and Obstacle Departure Procedures; Miscellaneous Amendments</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 rule establishes, amends, suspends, or revokes Standard Instrument Approach Procedures (SIAPs) and associated Takeoff Minimums and Obstacle Departure Procedures for operations at certain airports. These regulatory actions are needed because of the adoption of new or revised criteria, or because of changes occurring in the National Airspace System, such as the commissioning of new navigational facilities, adding new obstacles, or changing air traffic requirements. These changes are designed to provide safe and efficient use of the navigable airspace and to promote safe flight operations under instrument flight rules at the affected airports.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>This rule is effective June 16, 2011. The compliance date for each SIAP, associated Takeoff Minimums, and ODP is specified in the amendatory provisions.</P>
                    <P>The incorporation by reference of certain publications listed in the regulations is approved by the Director of the Federal Register as of June 16, 2011.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Availability of matter incorporated by reference in the amendment is as follows:</P>
                    <P>
                        <E T="03">For Examination</E>
                        —
                    </P>
                    <P>1. FAA Rules Docket, FAA Headquarters Building, 800 Independence Avenue, SW., Washington, DC 20591;</P>
                    <P>2. The FAA Regional Office of the region in which the affected airport is located;</P>
                    <P>3. The National Flight Procedures Office, 6500 South MacArthur Blvd., Oklahoma City, OK 73169 or</P>
                    <P>
                        4. 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/code_of_federal_regulations/ibr_locations.html</E>
                        .
                    </P>
                    <P>
                        <E T="03">Availability</E>
                        —All SIAPs are available online free of charge. Visit 
                        <E T="03">http://nfdc.faa.gov</E>
                         to register. Additionally, individual SIAP and Takeoff Minimums and ODP copies may be obtained from:
                    </P>
                    <P>1. FAA Public Inquiry Center (APA-200), FAA Headquarters Building, 800 Independence Avenue, SW., Washington, DC 20591; or</P>
                    <P>2. The FAA Regional Office of the region in which the affected airport is located.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Harry J. Hodges, Flight Procedure Standards Branch (AFS-420)Flight Technologies and Programs Division, Flight Standards Service, Federal Aviation Administration, Mike Monroney Aeronautical Center, 6500 South MacArthur Blvd., Oklahoma City, OK. 73169 (
                        <E T="03">Mail Address:</E>
                         P.O. Box 25082 Oklahoma City, OK 73125) 
                        <E T="03">telephone:</E>
                         (405) 954-4164.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>This rule amends Title 14, Code of Federal Regulations, Part 97 (14 CFR part 97) by amending the referenced SIAPs. The complete regulatory description of each SIAP is listed on the appropriate FAA Form 8260, as modified by the National Flight Data Center (FDC)/Permanent Notice to Airmen (P-NOTAM), and is incorporated by reference in the amendment under 5 U.S.C. 552(a), 1 CFR part 51, and § 97.20 of Title 14 of the Code of Federal Regulations.</P>
                <P>The large number of SIAPs, their complex nature, and the need for a special format make their verbatim publication in the Federal Register expensive and impractical. Further, airmen do not use the regulatory text of the SIAPs, but refer to their graphic depiction on charts printed by publishers of aeronautical materials. Thus, the advantages of incorporation by reference are realized and publication of the complete description of each SIAP contained in FAA form documents is unnecessary. This amendment provides the affected CFR sections and specifies the types of SIAP and the corresponding effective dates. This amendment also identifies the airport and its location, the procedure and the amendment number.</P>
                <HD SOURCE="HD1">The Rule</HD>
                <P>This amendment to 14 CFR part 97 is effective upon publication of each separate SIAP as amended in the transmittal. For safety and timeliness of change considerations, this amendment incorporates only specific changes contained for each SIAP as modified by FDC/P-NOTAMs.</P>
                <P>The SIAPs, as modified by FDC P-NOTAM, and contained in this amendment are based on the criteria contained in the U.S. Standard for Terminal Instrument Procedures (TERPS). In developing these changes to SIAPs, the TERPS criteria were applied only to specific conditions existing at the affected airports. All SIAP amendments in this rule have been previously issued by the FAA in a FDC NOTAM as an emergency action of immediate flight safety relating directly to published aeronautical charts. The circumstances which created the need for all these SIAP amendments requires making them effective in less than 30 days.</P>
                <P>
                    Because of the close and immediate relationship between these SIAPs and safety in air commerce, I find that notice and public procedure before adopting these SIAPs are impracticable and contrary to the public interest and, 
                    <PRTPAGE P="35099"/>
                    where applicable, that good cause exists for making these SIAPs effective in less than 30 days.
                </P>
                <HD SOURCE="HD1">Conclusion</HD>
                <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. For the same reason, the FAA certifies that this amendment will not have a significant economic impact on a substantial number of small entities under the criteria of the Regulatory Flexibility Act.</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 14 CFR Part 97</HD>
                    <P>Air Traffic Control, Airports, Incorporation by reference, and Navigation (Air).</P>
                </LSTSUB>
                <SIG>
                    <DATED>Issued in Washington, DC on May 27, 2011.</DATED>
                    <NAME>Ray Towles,</NAME>
                    <TITLE>Deputy Director, Flight Standards Service.</TITLE>
                </SIG>
                <HD SOURCE="HD1">Adoption of the Amendment</HD>
                <P>Accordingly, pursuant to the authority delegated to me, Title 14, Code of Federal regulations, Part 97, 14 CFR part 97, is amended by amending Standard Instrument Approach Procedures, effective at 0901 UTC on the dates specified, as follows:</P>
                <REGTEXT TITLE="14" PART="97">
                    <PART>
                        <HD SOURCE="HED">PART 97—STANDARD INSTRUMENT APPROACH PROCEDURES</HD>
                    </PART>
                    <AMDPAR>1. The authority citation for part 97 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P> 49 U.S.C. 106(g), 40103, 40106, 40113, 40114, 40120, 44502, 44514, 44701, 44719, 44721-44722.</P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="14" PART="97">
                    <AMDPAR>2. Part 97 is amended to read as follows:</AMDPAR>
                    <P>
                        <E T="04">§§ 97.23, 97.25, 97.27, 97.29, 97.31, 97.33 and 97.35 [Amended]</E>
                    </P>
                    <P>By amending: § 97.23 VOR, VOR/DME, VOR or TACAN, and VOR/DME or TACAN; § 97.25 LOC, LOC/DME, LDA, LDA/DME, SDF, SDF/DME; § 97.27 NDB, NDB/DME; § 97.29 ILS, ILS/DME, MLS, MLS/DME, MLS/RNAV; § 97.31 RADAR SIAPs; § 97.33 RNAV SIAPs; and § 97.35 COPTER SIAPs, Identified as follows: </P>
                    <HD SOURCE="HD2">* * * Effective Upon Publication</HD>
                    <GPOTABLE COLS="7" OPTS="L2,tp0,i1" CDEF="xs48,xls24,r50,r75,10,10,xs120">
                        <TTITLE> </TTITLE>
                        <BOXHD>
                            <CHED H="1">AIRAC date</CHED>
                            <CHED H="1">State</CHED>
                            <CHED H="1">City</CHED>
                            <CHED H="1">Airport</CHED>
                            <CHED H="1">FDC No.</CHED>
                            <CHED H="1">FDC date</CHED>
                            <CHED H="1">Subject</CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">30-Jun-11</ENT>
                            <ENT>NY</ENT>
                            <ENT>New York</ENT>
                            <ENT>La Guardia</ENT>
                            <ENT>1/0495</ENT>
                            <ENT>5/13/11</ENT>
                            <ENT>RNAV (RNP) Z RWY 4, Orig</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">30-Jun-11</ENT>
                            <ENT>NY</ENT>
                            <ENT>White Plains</ENT>
                            <ENT>Westchester County</ENT>
                            <ENT>1/0496</ENT>
                            <ENT>5/13/11</ENT>
                            <ENT>RNAV (RNP) Z RWY 16, Orig</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">30-Jun-11</ENT>
                            <ENT>FL</ENT>
                            <ENT>Miami</ENT>
                            <ENT>Miami Intl</ENT>
                            <ENT>1/0524</ENT>
                            <ENT>5/17/11</ENT>
                            <ENT>RNAV (RNP) Y RWY 26L, Orig-A</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">30-Jun-11</ENT>
                            <ENT>NY</ENT>
                            <ENT>New York</ENT>
                            <ENT>La Guardia</ENT>
                            <ENT>1/0893</ENT>
                            <ENT>5/13/11</ENT>
                            <ENT>RNAV (RNP) Z RWY 22, Orig-A</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">30-Jun-11</ENT>
                            <ENT>NY</ENT>
                            <ENT>White Plains</ENT>
                            <ENT>Westchester County</ENT>
                            <ENT>1/0894</ENT>
                            <ENT>5/13/11</ENT>
                            <ENT>RNAV (RNP) Z RWY 34, Orig-A</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">30-Jun-11</ENT>
                            <ENT>ME</ENT>
                            <ENT>Sanford</ENT>
                            <ENT>Sanford Rgnl</ENT>
                            <ENT>1/0969</ENT>
                            <ENT>5/6/11</ENT>
                            <ENT>VOR RWY 7, Amdt 4</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">30-Jun-11</ENT>
                            <ENT>ME</ENT>
                            <ENT>Sanford</ENT>
                            <ENT>Sanford Rgnl</ENT>
                            <ENT>1/0970</ENT>
                            <ENT>5/6/11</ENT>
                            <ENT>ILS OR LOC RWY 7, Amdt 4</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">30-Jun-11</ENT>
                            <ENT>TX</ENT>
                            <ENT>Dallas—Fort Worth</ENT>
                            <ENT>Dallas/Fort Worth Intl</ENT>
                            <ENT>1/0977</ENT>
                            <ENT>5/9/11</ENT>
                            <ENT>RNAV (RNP) Z RWY 13R, Orig-B</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">30-Jun-11</ENT>
                            <ENT>TX</ENT>
                            <ENT>Dallas—Fort Worth</ENT>
                            <ENT>Dallas/Fort Worth Intl</ENT>
                            <ENT>1/0979</ENT>
                            <ENT>5/9/11</ENT>
                            <ENT>RNAV (RNP) Z RWY 31L, Orig-B</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">30-Jun-11</ENT>
                            <ENT>TX</ENT>
                            <ENT>Dallas—Fort Worth</ENT>
                            <ENT>Dallas/Fort Worth Intl</ENT>
                            <ENT>1/1072</ENT>
                            <ENT>5/9/11</ENT>
                            <ENT>RNAV (RNP) Z RWY 31R, Amdt 1A</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">30-Jun-11</ENT>
                            <ENT>AK</ENT>
                            <ENT>Soldotna</ENT>
                            <ENT>Soldotna</ENT>
                            <ENT>1/3576</ENT>
                            <ENT>5/19/11</ENT>
                            <ENT>RNAV (GPS) RWY 7, Orig</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">30-Jun-11</ENT>
                            <ENT>AK</ENT>
                            <ENT>Soldotna</ENT>
                            <ENT>Soldotna</ENT>
                            <ENT>1/3577</ENT>
                            <ENT>5/19/11</ENT>
                            <ENT>RNAV (GPS) RWY 25, Orig</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">30-Jun-11</ENT>
                            <ENT>VA</ENT>
                            <ENT>Danville</ENT>
                            <ENT>Danville Rgnl</ENT>
                            <ENT>1/4009</ENT>
                            <ENT>4/25/11</ENT>
                            <ENT>ILS OR LOC RWY 2, Amdt 4</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">30-Jun-11</ENT>
                            <ENT>TX</ENT>
                            <ENT>Midland</ENT>
                            <ENT>Midland Airpark</ENT>
                            <ENT>1/7099</ENT>
                            <ENT>4/28/11</ENT>
                            <ENT>VOR OR GPS A, Amdt 2</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">30-Jun-11</ENT>
                            <ENT>TX</ENT>
                            <ENT>Midland</ENT>
                            <ENT>Midland Airpark</ENT>
                            <ENT>1/7100</ENT>
                            <ENT>4/28/11</ENT>
                            <ENT>VOR/DME OR GPS RWY 25, Amdt 3A</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">30-Jun-11</ENT>
                            <ENT>NH</ENT>
                            <ENT>Portsmouth</ENT>
                            <ENT>Portsmouth Intl At Pease</ENT>
                            <ENT>1/7109</ENT>
                            <ENT>4/25/11</ENT>
                            <ENT>VOR RWY 16, Amdt 5A</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">30-Jun-11</ENT>
                            <ENT>NH</ENT>
                            <ENT>Portsmouth</ENT>
                            <ENT>Portsmouth Intl At Pease</ENT>
                            <ENT>1/7110</ENT>
                            <ENT>4/25/11</ENT>
                            <ENT>VOR RWY 34, Orig-C</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">30-Jun-11</ENT>
                            <ENT>TX</ENT>
                            <ENT>Lufkin</ENT>
                            <ENT>Angelina County</ENT>
                            <ENT>1/8830</ENT>
                            <ENT>5/13/11</ENT>
                            <ENT>ILS OR LOC RWY 7, Amdt 2A</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">30-Jun-11</ENT>
                            <ENT>SC</ENT>
                            <ENT>Bamberg</ENT>
                            <ENT>Bamberg County</ENT>
                            <ENT>1/9179</ENT>
                            <ENT>5/2/11</ENT>
                            <ENT>RNAV (GPS) RWY 23, Orig</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">30-Jun-11</ENT>
                            <ENT>SC</ENT>
                            <ENT>Bamberg</ENT>
                            <ENT>Bamberg County</ENT>
                            <ENT>1/9180</ENT>
                            <ENT>5/2/11</ENT>
                            <ENT>RNAV (GPS) RWY 5, Orig</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">30-Jun-11</ENT>
                            <ENT>OK</ENT>
                            <ENT>Norman</ENT>
                            <ENT>University of Oklahoma Westheimer</ENT>
                            <ENT>1/9651</ENT>
                            <ENT>5/6/11</ENT>
                            <ENT>Takeoff Minimums and Obstacle DP, Orig</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">30-Jun-11</ENT>
                            <ENT>NH</ENT>
                            <ENT>Manchester</ENT>
                            <ENT>Manchester</ENT>
                            <ENT>1/9793</ENT>
                            <ENT>5/13/11</ENT>
                            <ENT>RNAV (RNP) Z RWY 17, Orig</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">30-Jun-11</ENT>
                            <ENT>IL</ENT>
                            <ENT>Chicago</ENT>
                            <ENT>Chicago Midway Intl</ENT>
                            <ENT>1/9795</ENT>
                            <ENT>5/6/11</ENT>
                            <ENT>RNAV (RNP) Y RWY 13C, Amdt 1</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">30-Jun-11</ENT>
                            <ENT>CO</ENT>
                            <ENT>Rifle</ENT>
                            <ENT>Garfield County Rgnl</ENT>
                            <ENT>1/9796</ENT>
                            <ENT>5/9/11</ENT>
                            <ENT>RNAV (RNP) Z RWY 8, Amdt 1</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">30-Jun-11</ENT>
                            <ENT>CO</ENT>
                            <ENT>Rifle</ENT>
                            <ENT>Garfield County Rgnl</ENT>
                            <ENT>1/9797</ENT>
                            <ENT>5/9/11</ENT>
                            <ENT>RNAV (RNP) Y RWY 26, Amdt 1</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">30-Jun-11</ENT>
                            <ENT>CO</ENT>
                            <ENT>Rifle</ENT>
                            <ENT>Garfield County Rgnl</ENT>
                            <ENT>1/9798</ENT>
                            <ENT>5/9/11</ENT>
                            <ENT>RNAV (RNP) Z RWY 26, Amdt 1</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">30-Jun-11</ENT>
                            <ENT>OH</ENT>
                            <ENT>Columbus</ENT>
                            <ENT>Port Columbus Intl</ENT>
                            <ENT>1/9799</ENT>
                            <ENT>5/9/11</ENT>
                            <ENT>RNAV (RNP) Z RWY 10L, Orig-A</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">30-Jun-11</ENT>
                            <ENT>OH</ENT>
                            <ENT>Columbus</ENT>
                            <ENT>Port Columbus Intl</ENT>
                            <ENT>1/9800</ENT>
                            <ENT>5/9/11</ENT>
                            <ENT>RNAV (RNP) Z RWY 28R, Orig</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">30-Jun-11</ENT>
                            <ENT>OH</ENT>
                            <ENT>Columbus</ENT>
                            <ENT>Port Columbus Intl</ENT>
                            <ENT>1/9801</ENT>
                            <ENT>5/9/11</ENT>
                            <ENT>RNAV (RNP) Z RWY 28L, Orig</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">30-Jun-11</ENT>
                            <ENT>OH</ENT>
                            <ENT>Columbus</ENT>
                            <ENT>Port Columbus Intl</ENT>
                            <ENT>1/9802</ENT>
                            <ENT>5/9/11</ENT>
                            <ENT>RNAV (RNP) Z RWY 10R, Orig</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">30-Jun-11</ENT>
                            <ENT>CO</ENT>
                            <ENT>Hayden</ENT>
                            <ENT>Yampa Valley</ENT>
                            <ENT>1/9803</ENT>
                            <ENT>5/9/11</ENT>
                            <ENT>RNAV (RNP) Z RWY 10, Amdt 1</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">30-Jun-11</ENT>
                            <ENT>CO</ENT>
                            <ENT>Gunnison</ENT>
                            <ENT>Gunnison—Crested Butte Rgnl</ENT>
                            <ENT>1/9804</ENT>
                            <ENT>5/9/11</ENT>
                            <ENT>RNAV (RNP) RWY 6, Orig</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">30-Jun-11</ENT>
                            <ENT>LA</ENT>
                            <ENT>New Orleans</ENT>
                            <ENT>Louis Armstrong New Orleans Intl</ENT>
                            <ENT>1/9805</ENT>
                            <ENT>5/6/11</ENT>
                            <ENT>RNAV (RNP) Z RWY 10, Orig</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">30-Jun-11</ENT>
                            <ENT>CO</ENT>
                            <ENT>Gunnison</ENT>
                            <ENT>Gunnison—Crested Butte Rgnl</ENT>
                            <ENT>1/9806</ENT>
                            <ENT>5/9/11</ENT>
                            <ENT>RNAV (RNP) RWY 24, Orig</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">30-Jun-11</ENT>
                            <ENT>LA</ENT>
                            <ENT>New Orleans</ENT>
                            <ENT>Louis Armstrong New Orleans Intl</ENT>
                            <ENT>1/9807</ENT>
                            <ENT>5/6/11</ENT>
                            <ENT>RNAV (RNP) Z RWY 28, Orig</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">30-Jun-11</ENT>
                            <ENT>TX</ENT>
                            <ENT>Corpus Christi</ENT>
                            <ENT>Corpus Christi Intl</ENT>
                            <ENT>1/9809</ENT>
                            <ENT>5/6/11</ENT>
                            <ENT>RNAV (RNP) Z RWY 13, Orig</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">30-Jun-11</ENT>
                            <ENT>TX</ENT>
                            <ENT>Lubbock</ENT>
                            <ENT>Lubbock Preston Smith Intl</ENT>
                            <ENT>1/9810</ENT>
                            <ENT>5/9/11</ENT>
                            <ENT>RNAV (RNP) Z RWY 35L, Orig</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">30-Jun-11</ENT>
                            <ENT>TX</ENT>
                            <ENT>Corpus Christi</ENT>
                            <ENT>Corpus Christi Intl</ENT>
                            <ENT>1/9811</ENT>
                            <ENT>5/6/11</ENT>
                            <ENT>RNAV (RNP) Z RWY 35, Orig</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">30-Jun-11</ENT>
                            <ENT>TX</ENT>
                            <ENT>Lubbock</ENT>
                            <ENT>Lubbock Preston Smith Intl</ENT>
                            <ENT>1/9812</ENT>
                            <ENT>5/9/11</ENT>
                            <ENT>RNAV (RNP) Z RWY 17R, Orig</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">30-Jun-11</ENT>
                            <ENT>TX</ENT>
                            <ENT>Corpus Christi</ENT>
                            <ENT>Corpus Christi Intl</ENT>
                            <ENT>1/9813</ENT>
                            <ENT>5/6/11</ENT>
                            <ENT>RNAV (RNP) Z RWY 31, Orig</ENT>
                        </ROW>
                        <ROW>
                            <PRTPAGE P="35100"/>
                            <ENT I="01">30-Jun-11</ENT>
                            <ENT>LA</ENT>
                            <ENT>New Orleans</ENT>
                            <ENT>Louis Armstrong New Orleans Intl</ENT>
                            <ENT>1/9814</ENT>
                            <ENT>5/6/11</ENT>
                            <ENT>RNAV (RNP) Z RWY 19, Orig</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">30-Jun-11</ENT>
                            <ENT>TX</ENT>
                            <ENT>Amarillo</ENT>
                            <ENT>Rick Husband Amarillo Intl</ENT>
                            <ENT>1/9815</ENT>
                            <ENT>5/6/11</ENT>
                            <ENT>RNAV (RNP) Z RWY 31, Orig</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">30-Jun-11</ENT>
                            <ENT>TX</ENT>
                            <ENT>Amarillo</ENT>
                            <ENT>Rick Husband Amarillo Intl</ENT>
                            <ENT>1/9822</ENT>
                            <ENT>5/6/11</ENT>
                            <ENT>RNAV (RNP) Z RWY 13, Orig</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">30-Jun-11</ENT>
                            <ENT>TX</ENT>
                            <ENT>Amarillo</ENT>
                            <ENT>Rick Husband Amarillo Intl</ENT>
                            <ENT>1/9823</ENT>
                            <ENT>5/6/11</ENT>
                            <ENT>RNAV (RNP) Z RWY 22, Orig</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">30-Jun-11</ENT>
                            <ENT>TX</ENT>
                            <ENT>Amarillo</ENT>
                            <ENT>Rick Husband Amarillo Intl</ENT>
                            <ENT>1/9824</ENT>
                            <ENT>5/6/11</ENT>
                            <ENT>RNAV (RNP) Z RWY 4, Orig</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">30-Jun-11</ENT>
                            <ENT>OK</ENT>
                            <ENT>Tulsa</ENT>
                            <ENT>Tulsa Intl</ENT>
                            <ENT>1/9825</ENT>
                            <ENT>5/9/11</ENT>
                            <ENT>RNAV (RNP) Z RWY 26, Orig</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">30-Jun-11</ENT>
                            <ENT>OK</ENT>
                            <ENT>Tulsa</ENT>
                            <ENT>Tulsa Intl</ENT>
                            <ENT>1/9826</ENT>
                            <ENT>5/9/11</ENT>
                            <ENT>RNAV (RNP) Z RWY 18R, Orig</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">30-Jun-11</ENT>
                            <ENT>WY</ENT>
                            <ENT>Jackson</ENT>
                            <ENT>Jackson Hole</ENT>
                            <ENT>1/9832</ENT>
                            <ENT>5/2/11</ENT>
                            <ENT>RNAV (RNP) Y RWY 1, Orig-A</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">30-Jun-11</ENT>
                            <ENT>WY</ENT>
                            <ENT>Jackson</ENT>
                            <ENT>Jackson Hole</ENT>
                            <ENT>1/9833</ENT>
                            <ENT>5/2/11</ENT>
                            <ENT>RNAV (RNP) Z RWY 1, Orig-B</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">30-Jun-11</ENT>
                            <ENT>WY</ENT>
                            <ENT>Jackson</ENT>
                            <ENT>Jackson Hole</ENT>
                            <ENT>1/9835</ENT>
                            <ENT>5/2/11</ENT>
                            <ENT>RNAV (RNP) Z RWY 19, Orig-A</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">30-Jun-11</ENT>
                            <ENT>NJ</ENT>
                            <ENT>Atlantic City</ENT>
                            <ENT>Atlantic City Intl</ENT>
                            <ENT>1/9836</ENT>
                            <ENT>5/13/11</ENT>
                            <ENT>RNAV (RNP) Z RWY 13, Orig</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">30-Jun-11</ENT>
                            <ENT>NJ</ENT>
                            <ENT>Atlantic City</ENT>
                            <ENT>Atlantic City Intl</ENT>
                            <ENT>1/9837</ENT>
                            <ENT>5/13/11</ENT>
                            <ENT>RNAV (RNP) Z RWY 31, Orig</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">30-Jun-11</ENT>
                            <ENT>OR</ENT>
                            <ENT>North Bend</ENT>
                            <ENT>Southwest Rgnl</ENT>
                            <ENT>1/9838</ENT>
                            <ENT>5/2/11</ENT>
                            <ENT>RNAV (RNP) Z RWY 4, Orig</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">30-Jun-11</ENT>
                            <ENT>MT</ENT>
                            <ENT>Bozeman</ENT>
                            <ENT>Gallatin Field</ENT>
                            <ENT>1/9840</ENT>
                            <ENT>5/2/11</ENT>
                            <ENT>RNAV (RNP) RWY 30, Orig</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">30-Jun-11</ENT>
                            <ENT>MT</ENT>
                            <ENT>Bozeman</ENT>
                            <ENT>Gallatin Field</ENT>
                            <ENT>1/9841</ENT>
                            <ENT>5/2/11</ENT>
                            <ENT>RNAV (RNP) Z RWY 12, Orig</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">30-Jun-11</ENT>
                            <ENT>TN</ENT>
                            <ENT>Nashville</ENT>
                            <ENT>Nashville Intl</ENT>
                            <ENT>1/9849</ENT>
                            <ENT>5/11/11</ENT>
                            <ENT>RNAV (RNP) Z RWY 31, Orig</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">30-Jun-11</ENT>
                            <ENT>TN</ENT>
                            <ENT>Nashville</ENT>
                            <ENT>Nashville Intl</ENT>
                            <ENT>1/9850</ENT>
                            <ENT>5/11/11</ENT>
                            <ENT>RNAV (RNP) Z RWY 20R, Orig</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">30-Jun-11</ENT>
                            <ENT>MT</ENT>
                            <ENT>Missoula</ENT>
                            <ENT>Missoula Intl</ENT>
                            <ENT>1/9851</ENT>
                            <ENT>5/6/11</ENT>
                            <ENT>RNAV (RNP) RWY 29, Orig</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">30-Jun-11</ENT>
                            <ENT>HI</ENT>
                            <ENT>Honolulu</ENT>
                            <ENT>Honolulu Intl</ENT>
                            <ENT>1/9852</ENT>
                            <ENT>5/9/11</ENT>
                            <ENT>RNAV (RNP) Z RWY 4R, Orig</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">30-Jun-11</ENT>
                            <ENT>HI</ENT>
                            <ENT>Honolulu</ENT>
                            <ENT>Honolulu Intl</ENT>
                            <ENT>1/9853</ENT>
                            <ENT>5/9/11</ENT>
                            <ENT>RNAV (RNP) RWY 26L, Orig-B</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">30-Jun-11</ENT>
                            <ENT>MD</ENT>
                            <ENT>Baltimore</ENT>
                            <ENT>Baltimore/Washington Intl Thurgood Marshal</ENT>
                            <ENT>1/9854</ENT>
                            <ENT>5/10/11</ENT>
                            <ENT>RNAV (RNP) Z RWY 15R, Orig-A</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">30-Jun-11</ENT>
                            <ENT>HI</ENT>
                            <ENT>Honolulu</ENT>
                            <ENT>Honolulu Intl</ENT>
                            <ENT>1/9855</ENT>
                            <ENT>5/9/11</ENT>
                            <ENT>RNAV (RNP) Z RWY 8L, Orig-A</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">30-Jun-11</ENT>
                            <ENT>TN</ENT>
                            <ENT>Nashville</ENT>
                            <ENT>Nashville Intl</ENT>
                            <ENT>1/9856</ENT>
                            <ENT>5/11/11</ENT>
                            <ENT>RNAV (RNP) Z RWY 2C, Orig</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">30-Jun-11</ENT>
                            <ENT>TN</ENT>
                            <ENT>Nashville</ENT>
                            <ENT>Nashville Intl</ENT>
                            <ENT>1/9857</ENT>
                            <ENT>5/11/11</ENT>
                            <ENT>RNAV (RNP) Z RWY 2L, Orig</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">30-Jun-11</ENT>
                            <ENT>TN</ENT>
                            <ENT>Nashville</ENT>
                            <ENT>Nashville Intl</ENT>
                            <ENT>1/9858</ENT>
                            <ENT>5/11/11</ENT>
                            <ENT>RNAV (RNP) Z RWY 2R, Orig</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">30-Jun-11</ENT>
                            <ENT>CA</ENT>
                            <ENT>Ontario</ENT>
                            <ENT>Ontario Intl</ENT>
                            <ENT>1/9859</ENT>
                            <ENT>5/6/11</ENT>
                            <ENT>RNAV (RNP) Z RWY 26L, Orig-B</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">30-Jun-11</ENT>
                            <ENT>TN</ENT>
                            <ENT>Nashville</ENT>
                            <ENT>Nashville Intl</ENT>
                            <ENT>1/9860</ENT>
                            <ENT>5/11/11</ENT>
                            <ENT>RNAV (RNP) Z RWY 20L, Orig</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">30-Jun-11</ENT>
                            <ENT>CA</ENT>
                            <ENT>Ontario</ENT>
                            <ENT>Ontario Intl</ENT>
                            <ENT>1/9861</ENT>
                            <ENT>5/6/11</ENT>
                            <ENT>RNAV (RNP) Z RWY 26R, Orig-B</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">30-Jun-11</ENT>
                            <ENT>MD</ENT>
                            <ENT>Baltimore</ENT>
                            <ENT>Baltimore/Washington Intl Thurgood Marshal</ENT>
                            <ENT>1/9862</ENT>
                            <ENT>5/10/11</ENT>
                            <ENT>RNAV (RNP) Z RWY 10, Amdt 1</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">30-Jun-11</ENT>
                            <ENT>MD</ENT>
                            <ENT>Baltimore</ENT>
                            <ENT>Baltimore/Washington Intl Thurgood Marshal</ENT>
                            <ENT>1/9863</ENT>
                            <ENT>5/10/11</ENT>
                            <ENT>RNAV (RNP) Z RWY 28, Orig-A</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">30-Jun-11</ENT>
                            <ENT>MD</ENT>
                            <ENT>Baltimore</ENT>
                            <ENT>Baltimore/Washington Intl Thurgood Marshal</ENT>
                            <ENT>1/9864</ENT>
                            <ENT>5/10/11</ENT>
                            <ENT>RNAV (RNP) Z RWY 33L, Amdt 1</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">30-Jun-11</ENT>
                            <ENT>CA</ENT>
                            <ENT>Ontario</ENT>
                            <ENT>Ontario Intl</ENT>
                            <ENT>1/9865</ENT>
                            <ENT>5/6/11</ENT>
                            <ENT>RNAV (RNP) Z RWY 8L, Orig-B</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">30-Jun-11</ENT>
                            <ENT>CA</ENT>
                            <ENT>San Francisco</ENT>
                            <ENT>San Francisco Intl</ENT>
                            <ENT>1/9867</ENT>
                            <ENT>5/11/11</ENT>
                            <ENT>RNAV (RNP) Y RWY 28R, Orig-B</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">30-Jun-11</ENT>
                            <ENT>CA</ENT>
                            <ENT>San Francisco</ENT>
                            <ENT>San Francisco Intl</ENT>
                            <ENT>1/9870</ENT>
                            <ENT>5/11/11</ENT>
                            <ENT>RNAV (RNP) Y RWY 10R, Orig</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">30-Jun-11</ENT>
                            <ENT>CA</ENT>
                            <ENT>Monterey</ENT>
                            <ENT>Monterey Peninsula</ENT>
                            <ENT>1/9878</ENT>
                            <ENT>5/6/11</ENT>
                            <ENT>RNAV (RNP) Z RWY 28L, Orig</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">30-Jun-11</ENT>
                            <ENT>CA</ENT>
                            <ENT>San Jose</ENT>
                            <ENT>Norman Y. Mineta San Jose Intl</ENT>
                            <ENT>1/9884</ENT>
                            <ENT>5/6/11</ENT>
                            <ENT>RNAV (RNP) Z RWY 30L, Amdt 1</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">30-Jun-11</ENT>
                            <ENT>CA</ENT>
                            <ENT>San Jose</ENT>
                            <ENT>Norman Y. Mineta San Jose Intl</ENT>
                            <ENT>1/9886</ENT>
                            <ENT>5/6/11</ENT>
                            <ENT>RNAV (RNP) Z RWY 12L, Orig</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">30-Jun-11</ENT>
                            <ENT>CA</ENT>
                            <ENT>San Jose</ENT>
                            <ENT>Norman Y. Mineta San Jose Intl</ENT>
                            <ENT>1/9889</ENT>
                            <ENT>5/6/11</ENT>
                            <ENT>RNAV (RNP) Z RWY 12R, Amdt 1</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">30-Jun-11</ENT>
                            <ENT>CA</ENT>
                            <ENT>San Jose</ENT>
                            <ENT>Norman Y. Mineta San Jose Intl</ENT>
                            <ENT>1/9890</ENT>
                            <ENT>5/6/11</ENT>
                            <ENT>RNAV (RNP) Z RWY 30R, Orig-A</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">30-Jun-11</ENT>
                            <ENT>AZ</ENT>
                            <ENT>Scottsdale</ENT>
                            <ENT>Scottsdale</ENT>
                            <ENT>1/9912</ENT>
                            <ENT>5/6/11</ENT>
                            <ENT>RNAV (RNP) Y RWY 3, Orig-A</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">30-Jun-11</ENT>
                            <ENT>AZ</ENT>
                            <ENT>Scottsdale</ENT>
                            <ENT>Scottsdale</ENT>
                            <ENT>1/9914</ENT>
                            <ENT>5/6/11</ENT>
                            <ENT>RNAV (RNP) Z RWY 3, Orig</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">30-Jun-11</ENT>
                            <ENT>AZ</ENT>
                            <ENT>Scottsdale</ENT>
                            <ENT>Scottsdale</ENT>
                            <ENT>1/9918</ENT>
                            <ENT>5/6/11</ENT>
                            <ENT>RNAV (RNP) RWY 21, Orig</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">30-Jun-11</ENT>
                            <ENT>CA</ENT>
                            <ENT>Bishop</ENT>
                            <ENT>Eastern Sierra Rgnl</ENT>
                            <ENT>1/9920</ENT>
                            <ENT>5/11/11</ENT>
                            <ENT>RNAV (RNP) RWY 30, Orig</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">30-Jun-11</ENT>
                            <ENT>GA</ENT>
                            <ENT>Atlanta</ENT>
                            <ENT>Dekalb—Peachtree</ENT>
                            <ENT>1/9924</ENT>
                            <ENT>5/13/11</ENT>
                            <ENT>RNAV (RNP) Z RWY 20L, Orig</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">30-Jun-11</ENT>
                            <ENT>PA</ENT>
                            <ENT>Philadelphia</ENT>
                            <ENT>Philadelphia Intl</ENT>
                            <ENT>1/9926</ENT>
                            <ENT>5/13/11</ENT>
                            <ENT>RNAV (RNP) Z RWY 9R, Orig</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">30-Jun-11</ENT>
                            <ENT>PA</ENT>
                            <ENT>Philadelphia</ENT>
                            <ENT>Philadelphia Intl</ENT>
                            <ENT>1/9927</ENT>
                            <ENT>5/13/11</ENT>
                            <ENT>RNAV (RNP) Z RWY 9L, Orig</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">30-Jun-11</ENT>
                            <ENT>FL</ENT>
                            <ENT>Sebring</ENT>
                            <ENT>Sebring Rgnl</ENT>
                            <ENT>1/9934</ENT>
                            <ENT>5/13/11</ENT>
                            <ENT>RNAV (RNP) RWY 18, Orig</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">30-Jun-11</ENT>
                            <ENT>FL</ENT>
                            <ENT>Tampa</ENT>
                            <ENT>Tampa Intl</ENT>
                            <ENT>1/9935</ENT>
                            <ENT>5/13/11</ENT>
                            <ENT>RNAV (RNP) Y RWY 19L, Amdt 1</ENT>
                        </ROW>
                    </GPOTABLE>
                </REGTEXT>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-13951 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-13-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <PRTPAGE P="35101"/>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <CFR>14 CFR Part 97</CFR>
                <DEPDOC>[Docket No. 30785; Amdt. No. 3428]</DEPDOC>
                <SUBJECT>Standard Instrument Approach Procedures, and Takeoff Minimums and Obstacle Departure Procedures; Miscellaneous Amendments</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 establishes, amends, suspends, or revokes Standard Instrument Approach Procedures (SIAPs) and associated Takeoff Minimums and Obstacle Departure Procedures for operations at certain airports. These regulatory actions are needed because of the adoption of new or revised criteria, or because of changes occurring in the National Airspace System, such as the commissioning of new navigational facilities, adding new obstacles, or changing air traffic requirements. These changes are designed to provide safe and efficient use of the navigable airspace and to promote safe flight operations under instrument flight rules at the affected airports.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>This rule is effective June 16, 2011. The compliance date for each SIAP, associated Takeoff Minimums, and ODP is specified in the amendatory provisions.</P>
                    <P>The incorporation by reference of certain publications listed in the regulations is approved by the Director of the Federal Register as of June 16, 2011. </P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Availability of matters incorporated by reference in the amendment is as follows:</P>
                    <P>For Examination—</P>
                    <P>1. FAA Rules Docket, FAA Headquarters Building, 800 Independence Avenue, SW., Washington, DC 20591;</P>
                    <P>2. The FAA Regional Office of the region in which the affected airport is located;</P>
                    <P>3. The National Flight Procedures Office, 6500 South MacArthur Blvd., Oklahoma City, OK 73169 or</P>
                    <P>
                        4. 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/code_of_federal_regulations/ibr_locations.html</E>
                        .
                    </P>
                    <P>
                        <E T="03">Availability</E>
                        —All SIAPs and Takeoff Minimums and ODPs are available online free of charge. Visit 
                        <E T="03">http://www.nfdc.faa.gov</E>
                         to register. Additionally, individual SIAP and Takeoff Minimums and ODP copies may be obtained from:
                    </P>
                    <P>1. FAA Public Inquiry Center (APA-200), FAA Headquarters Building, 800 Independence Avenue, SW., Washington, DC 20591; or</P>
                    <P>2. The FAA Regional Office of the region in which the affected airport is located.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Harry J. Hodges, Flight Procedure Standards Branch (AFS-420), Flight Technologies and Programs Divisions, Flight Standards Service, Federal Aviation Administration, Mike Monroney Aeronautical Center, 6500 South MacArthur Blvd., Oklahoma City, OK 73169 (Mail Address: P.O. Box 25082, Oklahoma City, OK 73125) 
                        <E T="03">Telephone:</E>
                         (405) 954-4164.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>This rule amends Title 14 of the Code of Federal Regulations, Part 97 (14 CFR part 97), by establishing, amending, suspending, or revoking SIAPS, Takeoff Minimums and/or ODPS. The complete regulators description of each SIAP and its associated Takeoff Minimums or ODP for an identified airport is listed on FAA form documents which are incorporated by reference in this amendment under 5 U.S.C. 552(a), 1 CFR part 51, and 14 CFR part 97.20. The applicable FAA Forms are FAA Forms 8260-3, 8260-4, 8260-5, 8260-15A, and 8260-15B when required by an entry on 8260-15A.</P>
                <P>
                    The large number of SIAPs, Takeoff Minimums and ODPs, in addition to their complex nature and the need for a special format make publication in the 
                    <E T="04">Federal Register</E>
                     expensive and impractical. Furthermore, airmen do not use the regulatory text of the SIAPs, Takeoff Minimums or ODPs, but instead refer to their depiction on charts printed by publishers of aeronautical materials. The advantages of incorporation by reference are realized and publication of the complete description of each SIAP, Takeoff Minimums and ODP listed on FAA forms is unnecessary. This amendment provides the affected CFR sections and specifies the types of SIAPs and the effective dates of the, associated Takeoff Minimums and ODPs. This amendment also identifies the airport and its location, the procedure, and the amendment number.
                </P>
                <HD SOURCE="HD1">The Rule</HD>
                <P>This amendment to 14 CFR part 97 is effective upon publication of each separate SIAP, Takeoff Minimums and ODP as contained in the transmittal. Some SIAP and Takeoff Minimums and textual ODP amendments may have been issued previously by the FAA in a Flight Data Center (FDC) Notice to Airmen (NOTAM) as an emergency action of immediate flight safety relating directly to published aeronautical charts. The circumstances which created the need for some SIAP and Takeoff Minimums and ODP amendments may require making them effective in less than 30 days. For the remaining SIAPS and Takeoff Minimums and ODPS, an effective date at least 30 days after publication is provided.</P>
                <P>Further, the SIAPs and Takeoff Minimums and ODPS contained in this amendment are based on the criteria contained in the U.S. Standard for Terminal Instrument Procedures (TERPS). In developing these SIAPS and Takeoff Minimums and ODPs, the TERPS criteria were applied to the conditions existing or anticipated at the affected airports. Because of the close and immediate relationship between these SIAPs, Takeoff Minimums and ODPs, and safety in air commerce, I find that notice and public procedures before adopting these SIAPS, Takeoff Minimums and ODPs are impracticable and contrary to the public interest and, where applicable, that good cause exists for making some SIAPs effective in less than 30 days.</P>
                <HD SOURCE="HD1">Conclusion</HD>
                <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. For the same reason, the FAA certifies that this amendment will not have a significant economic impact on a substantial number of small entities under the criteria of the Regulatory Flexibility Act.</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 14 CFR Part 97</HD>
                    <P>Air Traffic Control, Airports, Incorporation by reference, and Navigation (Air).</P>
                </LSTSUB>
                <SIG>
                    <DATED>Issued in Washington, DC, on May 27, 2011.</DATED>
                    <NAME>Ray Towles,</NAME>
                    <TITLE>Deputy Director, Flight Standards Service.</TITLE>
                </SIG>
                <HD SOURCE="HD1">Adoption Of The Amendment</HD>
                <P>
                    Accordingly, pursuant to the authority delegated to me, Title 14, 
                    <PRTPAGE P="35102"/>
                    Code of Federal Regulations, Part 97 (14 CFR part 97) is amended by establishing, amending, suspending, or revoking Standard Instrument Approach Procedures and/or Takeoff Minimums and/or Obstacle Departure Procedures effective at 0902 UTC on the dates specified, as follows:
                </P>
                <REGTEXT TITLE="14" PART="97">
                    <PART>
                        <HD SOURCE="HED">PART 97—STANDARD INSTRUMENT APPROACH PROCEDURES</HD>
                    </PART>
                    <AMDPAR>1. The authority citation for part 97 continues to read as follows:</AMDPAR>
                    <EXTRACT>
                        <AUTH>
                            <HD SOURCE="HED">Authority: </HD>
                            <P>49 U.S.C. 106(g), 40103, 40106, 40113, 40114, 40120, 44502, 44514, 44701, 44719, 44721-44722.</P>
                        </AUTH>
                    </EXTRACT>
                </REGTEXT>
                <REGTEXT TITLE="14" PART="97">
                    <AMDPAR>2. Part 97 is amended to read as follows:</AMDPAR>
                    <EXTRACT>
                        <HD SOURCE="HD1">Effective 30 JUN 2011</HD>
                        <FP SOURCE="FP-1">St. Paul Island, AK, St. Paul Island, ILS OR LOC/DME RWY 36, Amdt 3A</FP>
                        <FP SOURCE="FP-1">Talladega, AL, Talladega Muni, ILS or LOC/DME RWY 3, Orig</FP>
                        <FP SOURCE="FP-1">Talladega, AL, Talladega Muni, RNAV (GPS) RWY 3, Amdt 1</FP>
                        <FP SOURCE="FP-1">Talladega, AL, Talladega Muni, RNAV (GPS) RWY 21, Amdt 1</FP>
                        <FP SOURCE="FP-1">Telluride, CO, Telluride Rgnl, LOC/DME RWY 9, Amdt 2</FP>
                        <FP SOURCE="FP-1">Telluride, CO, Telluride Rgnl, Takeoff Minimums and Obstacle DP, Amdt 2</FP>
                        <FP SOURCE="FP-1">Telluride, CO, Telluride Rgnl, VOR/DME-A, Amdt 1</FP>
                        <FP SOURCE="FP-1">Venice, FL, Venice Muni, RNAV (GPS) RWY 13, Amdt 1</FP>
                        <FP SOURCE="FP-1">Venice, FL, Venice Muni, RNAV (GPS) RWY 31, Amdt 1</FP>
                        <FP SOURCE="FP-1">Atlanta, GA, Dekalb-Peachtree, RNAV (RNP) RWY 2R, Amdt 1</FP>
                        <FP SOURCE="FP-1">Cornelia, GA, Habersham County, NDB RWY 6, Amdt 2</FP>
                        <FP SOURCE="FP-1">Cornelia, GA, Habersham County, RNAV (GPS) RWY 6, Amdt 1</FP>
                        <FP SOURCE="FP-1">Cornelia, GA, Habersham County, RNAV (GPS) RWY 24, Amdt 1</FP>
                        <FP SOURCE="FP-1">Thomson, GA, Thomson-McDuffie County, ILS OR LOC/NDB RWY 10, Amdt 1</FP>
                        <FP SOURCE="FP-1">Thomson, GA, Thomson-McDuffie County, NDB RWY 10, Amdt 1</FP>
                        <FP SOURCE="FP-1">Thomson, GA, Thomson-McDuffie County, RNAV (GPS) RWY 10, Orig</FP>
                        <FP SOURCE="FP-1">Thomson, GA, Thomson-McDuffie County, RNAV (GPS) RWY 28, Orig</FP>
                        <FP SOURCE="FP-1">Thomson, GA, Thomson-McDuffie County, VOR/DME-A, Amdt 4</FP>
                        <FP SOURCE="FP-1">Centerville, IA, Centerville Muni, NDB OR GPS RWY 16, Amdt 1B, CANCELLED</FP>
                        <FP SOURCE="FP-1">Centerville, IA, Centerville Muni, NDB OR GPS RWY 34, Amdt 1B, CANCELLED</FP>
                        <FP SOURCE="FP-1">Creston, IA, Creston Muni, RNAV (GPS) RWY 16, Amdt 1</FP>
                        <FP SOURCE="FP-1">Creston, IA, Creston Muni, RNAV (GPS) RWY 34, Amdt 1</FP>
                        <FP SOURCE="FP-1">Mason City, IA, Mason City Muni, RNAV (GPS) RWY 18, Amdt 2</FP>
                        <FP SOURCE="FP-1">Mason City, IA, Mason City Muni, RNAV (GPS) RWY 30, Amdt 1</FP>
                        <FP SOURCE="FP-1">Mason City, IA, Mason City Muni, RNAV (GPS) RWY 36, Amdt 1</FP>
                        <FP SOURCE="FP-1">Dixon, IL, Dixon Muni-Charles R. Walgreen Field, Takeoff Minimums and Obstacle DP, Amdt 3</FP>
                        <FP SOURCE="FP-1">Burlington, KS, Coffey County, GPS RWY 18, Orig, CANCELLED</FP>
                        <FP SOURCE="FP-1">Burlington, KS, Coffey County, GPS RWY 36, Orig, CANCELLED</FP>
                        <FP SOURCE="FP-1">Burlington, KS, Coffey County, RNAV (GPS) RWY 18, Orig</FP>
                        <FP SOURCE="FP-1">Burlington, KS, Coffey County, RNAV (GPS) RWY 36, Orig</FP>
                        <FP SOURCE="FP-1">Lawrence, MA, Lawrence Muni, ILS OR LOC Y RWY 5, Amdt 4</FP>
                        <FP SOURCE="FP-1">Lawrence, MA, Lawrence Muni, ILS OR LOC Z RWY 5, Orig</FP>
                        <FP SOURCE="FP-1">Lawrence, MA, Lawrence Muni, NDB RWY 5, Amdt 6</FP>
                        <FP SOURCE="FP-1">Lawrence, MA, Lawrence Muni, RNAV (GPS) RWY 5, Orig</FP>
                        <FP SOURCE="FP-1">Lawrence, MA, Lawrence Muni, RNAV (GPS) RWY 23, Orig</FP>
                        <FP SOURCE="FP-1">Lawrence, MA, Lawrence Muni, VOR RWY 23, Amdt 11</FP>
                        <FP SOURCE="FP-1">Frederick, MD, Frederick Muni, Takeoff Minimums and Obstacle DP, Amdt 3</FP>
                        <FP SOURCE="FP-1">Augusta, ME, Augusta State, Takeoff Minimums and Obstacle DP, Amdt 3</FP>
                        <FP SOURCE="FP-1">Minneapolis, MN, Flying Cloud, RNAV (GPS) RWY 28L, Amdt 1</FP>
                        <FP SOURCE="FP-1">Rochester, MN, Rochester Intl, RNAV (GPS) RWY 2, Amdt 2</FP>
                        <FP SOURCE="FP-1">Rochester, MN, Rochester Intl, RNAV (GPS) RWY 20, Amdt 1</FP>
                        <FP SOURCE="FP-1">Rochester, MN, Rochester Intl, VOR/DME RWY 20, Amdt 14</FP>
                        <FP SOURCE="FP-1">Two Harbors, MN, Richard B Helgeson, GPS RWY 24, Orig, CANCELLED</FP>
                        <FP SOURCE="FP-1">Two Harbors, MN, Richard B Helgeson, RNAV (GPS) RWY 6, Orig</FP>
                        <FP SOURCE="FP-1">Two Harbors, MN, Richard B Helgeson, RNAV (GPS) RWY 24, Orig</FP>
                        <FP SOURCE="FP-1">Olive Branch, MS, Olive Branch, LOC/DME RWY 36, Orig</FP>
                        <FP SOURCE="FP-1">Kenansville, NC, Duplin County, GPS RWY 5, Orig-B, CANCELLED</FP>
                        <FP SOURCE="FP-1">Kenansville, NC, Duplin County, GPS RWY 23, Orig-B, CANCELLED</FP>
                        <FP SOURCE="FP-1">Kenansville, NC, Duplin County, LOC/NDB RWY 23, Amdt 1</FP>
                        <FP SOURCE="FP-1">Kenansville, NC, Duplin County, RNAV (GPS) RWY 5, Orig</FP>
                        <FP SOURCE="FP-1">Kenansville, NC, Duplin County, RNAV (GPS) RWY 23, Orig</FP>
                        <FP SOURCE="FP-1">Salisbury, NC, Rowan County, ILS OR LOC RWY 20, Amdt 1</FP>
                        <FP SOURCE="FP-1">Salisbury, NC, Rowan County, NDB RWY 20, Amdt 1</FP>
                        <FP SOURCE="FP-1">Salisbury, NC, Rowan County, RNAV (GPS) RWY 2, Amdt 1</FP>
                        <FP SOURCE="FP-1">Salisbury, NC, Rowan County, RNAV (GPS) RWY 20, Amdt 1</FP>
                        <FP SOURCE="FP-1">Salisbury, NC, Rowan County, Takeoff Minimums and Obstacle DP, Amdt 1</FP>
                        <FP SOURCE="FP-1">Hillsboro, ND, Hillsboro Muni, RNAV (GPS) RWY 16, Amdt 1</FP>
                        <FP SOURCE="FP-1">Hillsboro, ND, Hillsboro Muni, RNAV (GPS) RWY 34, Amdt 1</FP>
                        <FP SOURCE="FP-1">Beatrice, NE, Beatrice Muni, RNAV (GPS) RWY 14, Amdt 1</FP>
                        <FP SOURCE="FP-1">Beatrice, NE, Beatrice Muni, RNAV (GPS) RWY 18, Amdt 2</FP>
                        <FP SOURCE="FP-1">Beatrice, NE, Beatrice Muni, RNAV (GPS) RWY 32, Amdt 1</FP>
                        <FP SOURCE="FP-1">Beatrice, NE, Beatrice Muni, RNAV (GPS) RWY 36, Amdt 2</FP>
                        <FP SOURCE="FP-1">Beatrice, NE, Beatrice Muni, VOR RWY 14, Amdt 18</FP>
                        <FP SOURCE="FP-1">Beatrice, NE, Beatrice Muni, VOR RWY 18, Amdt 2</FP>
                        <FP SOURCE="FP-1">Beatrice, NE, Beatrice Muni, VOR RWY 36, Amdt 9</FP>
                        <FP SOURCE="FP-1">Central City, NE, Central City Muni-Larry Reineke Field, RNAV (GPS) RWY 16, Orig</FP>
                        <FP SOURCE="FP-1">Central City, NE, Central City Muni-Larry Reineke Field, RNAV (GPS) RWY 34, Orig</FP>
                        <FP SOURCE="FP-1">Central City, NE, Central City Muni-Larry Reineke Field, Takeoff Minimums and Obstacle DP, Orig</FP>
                        <FP SOURCE="FP-1">Millville, NJ, Millville Muni, ILS OR LOC RWY 10, Amdt 2</FP>
                        <FP SOURCE="FP-1">Brockport, NY, Ledgedale Airpark, RNAV (GPS) RWY 28, Amdt 1</FP>
                        <FP SOURCE="FP-1">Schenectady, NY, Schenectady County, GPS RWY 22, Orig-D, CANCELLED</FP>
                        <FP SOURCE="FP-1">Schenectady, NY, Schenectady County, GPS RWY 28, Orig-B, CANCELLED</FP>
                        <FP SOURCE="FP-1">Schenectady, NY, Schenectady County, ILS OR LOC RWY 4, Amdt 5</FP>
                        <FP SOURCE="FP-1">Schenectady, NY, Schenectady County, NDB RWY 22, Amdt 16</FP>
                        <FP SOURCE="FP-1">Schenectady, NY, Schenectady County, RNAV (GPS) RWY 4, Orig</FP>
                        <FP SOURCE="FP-1">Schenectady, NY, Schenectady County, RNAV (GPS) RWY 10, Orig</FP>
                        <FP SOURCE="FP-1">Schenectady, NY, Schenectady County, RNAV (GPS) RWY 22, Orig</FP>
                        <FP SOURCE="FP-1">Schenectady, NY, Schenectady County, RNAV (GPS) RWY 28, Orig</FP>
                        <FP SOURCE="FP-1">Watertown, NY, Watertown Intl, RNAV (GPS) RWY 10, Orig</FP>
                        <FP SOURCE="FP-1">Watertown, NY, Watertown Intl, RNAV (GPS) RWY 28, Orig</FP>
                        <FP SOURCE="FP-1">Beaver Falls, PA, Beaver County, RNAV (GPS) RWY 10, Orig</FP>
                        <FP SOURCE="FP-1">Beaver Falls, PA, Beaver County, RNAV (GPS) RWY 28, Orig</FP>
                        <FP SOURCE="FP-1">Beaver Falls, PA, Beaver County, VOR RWY 28, Amdt 10</FP>
                        <FP SOURCE="FP-1">Lehighton, PA, Jake Arner Memorial, RNAV (GPS) RWY 8, Amdt 1A</FP>
                        <FP SOURCE="FP-1">Lehighton, PA, Jake Arner Memorial, RNAV (GPS) RWY 26, Amdt 1A</FP>
                        <FP SOURCE="FP-1">Philadelphia, PA, Philadelphia Intl, CONVERGING ILS RWY 17, Amdt 6</FP>
                        <FP SOURCE="FP-1">Philadelphia, PA, Philadelphia Intl, ILS OR LOC RWY 17, Amdt 8</FP>
                        <FP SOURCE="FP-1">Philadelphia, PA, Philadelphia Intl, RNAV (GPS) RWY 17, Amdt 3</FP>
                        <FP SOURCE="FP-1">Philadelphia, PA, Philadelphia Intl, RNAV (GPS) RWY 35, Amdt 3</FP>
                        <FP SOURCE="FP-1">York, PA, York, NDB RWY 17, Amdt 7</FP>
                        <FP SOURCE="FP-1">York, PA, York, RNAV (GPS) RWY 17, Amdt 2</FP>
                        <FP SOURCE="FP-1">York, PA, York, RNAV (GPS) RWY 35, Amdt 1</FP>
                        <FP SOURCE="FP-1">Gettysburg, SD, Gettysburg Muni, RNAV (GPS) RWY 13, Amdt 1</FP>
                        <FP SOURCE="FP-1">Gettysburg, SD, Gettysburg Muni, RNAV (GPS) RWY 31, Amdt 1</FP>
                        <FP SOURCE="FP-1">Mobridge, SD, Mobridge Muni, NDB RWY 12, Amdt 2, CANCELLED</FP>
                        <FP SOURCE="FP-1">Mobridge, SD, Mobridge Muni, RNAV (GPS) RWY 30, Amdt 1</FP>
                        <FP SOURCE="FP-1">Mobridge, SD, Mobridge Muni, Takeoff Minimums and Obstacle DP, Amdt 1</FP>
                        <FP SOURCE="FP-1">Spearfish, SD, Black Hills-Clyde Ice Field, GPS RWY 12, Orig-D, CANCELLED</FP>
                        <FP SOURCE="FP-1">Spearfish, SD, Black Hills-Clyde Ice Field, NDB-A, Amdt 1</FP>
                        <FP SOURCE="FP-1">Spearfish, SD, Black Hills-Clyde Ice Field, RNAV (GPS) RWY 13, Orig</FP>
                        <FP SOURCE="FP-1">Spearfish, SD, Black Hills-Clyde Ice Field, RNAV (GPS) RWY 31, Orig</FP>
                        <FP SOURCE="FP-1">
                            Sturgis, SD, Sturgis Muni, GPS RWY 29, Orig-A, CANCELLED
                            <PRTPAGE P="35103"/>
                        </FP>
                        <FP SOURCE="FP-1">Sturgis, SD, Sturgis Muni, RNAV (GPS) RWY 11, Orig</FP>
                        <FP SOURCE="FP-1">Sturgis, SD, Sturgis Muni, RNAV (GPS) RWY 29, Orig</FP>
                        <FP SOURCE="FP-1">Sturgis, SD, Sturgis Muni, Takeoff Minimums and Obstacle DP, Amdt 1</FP>
                        <FP SOURCE="FP-1">Dyersburg, TN, Dyersburg Rgnl, RNAV (GPS) RWY 4, Amdt 2</FP>
                        <FP SOURCE="FP-1">Dyersburg, TN, Dyersburg Rgnl, RNAV (GPS) RWY 22, Amdt 1</FP>
                        <FP SOURCE="FP-1">Dyersburg, TN, Dyersburg Rgnl, VOR-A, Amdt 18</FP>
                        <FP SOURCE="FP-1">Dyersburg, TN, Dyersburg Rgnl, VOR/DME RWY 4, Amdt 4</FP>
                        <FP SOURCE="FP-1">Memphis, TN, General Dewitt Spain, GPS RWY 17, Orig-A, CANCELLED</FP>
                        <FP SOURCE="FP-1">Memphis, TN, General Dewitt Spain, RNAV (GPS) RWY 17, Orig</FP>
                        <FP SOURCE="FP-1">Morristown, TN, Moore-Murrell, NDB RWY 5, Amdt 5</FP>
                        <FP SOURCE="FP-1">Morristown, TN, Moore-Murrell, RNAV (GPS) RWY 5, Orig</FP>
                        <FP SOURCE="FP-1">Morristown, TN, Moore-Murrell, RNAV (GPS) RWY 23, Orig</FP>
                        <FP SOURCE="FP-1">Morristown, TN, Moore-Murrell, SDF RWY 5, Amdt 5</FP>
                        <FP SOURCE="FP-1">Waverly, TN, Humphreys County, RNAV (GPS) RWY 3, Orig</FP>
                        <FP SOURCE="FP-1">Waverly, TN, Humphreys County, RNAV (GPS) RWY 21, Orig</FP>
                        <FP SOURCE="FP-1">Wendover, UT, Wendover, RNAV (GPS) RWY 8, Orig</FP>
                        <FP SOURCE="FP-1">Wendover, UT, Wendover, RNAV (GPS)-C, Orig</FP>
                        <FP SOURCE="FP-1">Waynesboro, VA, Eagle's Nest, RNAV (GPS) RWY 6, Orig</FP>
                        <FP SOURCE="FP-1">Waynesboro, VA, Eagle's Nest, RNAV (GPS) RWY 24, Orig</FP>
                        <FP SOURCE="FP-1">Highgate, VT, Franklin County State, RNAV (GPS) RWY 1, Amdt 3</FP>
                        <FP SOURCE="FP-1">Highgate, VT, Franklin County State, RNAV (GPS) RWY 19, Amdt 1</FP>
                        <FP SOURCE="FP-1">Highgate, VT, Franklin County State, Takeoff Minimums and Obstacle DP, Amdt 1</FP>
                        <FP SOURCE="FP-1">Highgate, VT, Franklin County State, VOR/DME RWY 19, Amdt 5</FP>
                        <FP SOURCE="FP-1">Springfield, VT, Hartness State (Springfield), Takeoff Minimums and Obstacle DP, Amdt 3</FP>
                        <FP SOURCE="FP-1">Ladysmith, WI, Rusk County, NDB RWY 32, Amdt 3</FP>
                        <FP SOURCE="FP-1">Ladysmith, WI, Rusk County, RNAV (GPS) RWY 14, Orig</FP>
                        <FP SOURCE="FP-1">Ladysmith, WI, Rusk County, RNAV (GPS) RWY 32, Orig</FP>
                        <FP SOURCE="FP-1">Marshfield, WI, Marshfield Muni, NDB RWY 5, Amdt 14</FP>
                        <FP SOURCE="FP-1">Marshfield, WI, Marshfield Muni, NDB RWY 16, Amdt 10</FP>
                        <FP SOURCE="FP-1">Milwaukee, WI, General Mitchell Intl, ILS OR LOC RWY 19R, Amdt 11</FP>
                        <FP SOURCE="FP-1">Milwaukee, WI, General Mitchell Intl, RNAV (GPS) RWY 19R, Amdt 1</FP>
                        <FP SOURCE="FP-1">Milwaukee, WI, General Mitchell Intl, RNAV (GPS) Y RWY 19R, Orig, CANCELLED</FP>
                        <FP SOURCE="FP-1">Sparta, WI, Sparta/Fort McCoy, NDB RWY 29, Amdt 4</FP>
                        <FP SOURCE="FP-1">Sparta, WI, Sparta/Fort McCoy, RNAV (GPS) RWY 11, Amdt 1</FP>
                        <FP SOURCE="FP-1">Sparta, WI, Sparta/Fort McCoy, Takeoff Minimums and Obstacle DP, Amdt 2</FP>
                    </EXTRACT>
                    <HD SOURCE="HD1">On MAY 04, 2011 (76 FR 25233) the FAA published an Amendment in Docket No. 30779, Amdt 3422 to Part 97 of the Federal Aviation Regulations under section 97.33. The following entries, published in TL 11-11 effective for 30 JUNE 2011, are hereby rescinded:</HD>
                    <EXTRACT>
                        <FP SOURCE="FP-1">Anchorage, AK, Merill Field, RNAV (GPS)-A, Amdt 1</FP>
                        <FP SOURCE="FP-1">Anchorage, AK, Merill Field, Takeoff Minimums and Obstacle DP, Amdt 1</FP>
                        <FP SOURCE="FP-1">Big Lake, AK, Big Lake, RNAV (GPS) RWY 7, Amdt 1</FP>
                        <FP SOURCE="FP-1">Big Lake, AK, Big Lake, RNAV (GPS) RWY 25, Amdt 1</FP>
                        <FP SOURCE="FP-1">Big Lake, AK, Big Lake, Takeoff Minimums and Obstacle DP, Amdt 2</FP>
                        <FP SOURCE="FP-1">Big Lake, AK, Big Lake, VOR RWY 7, Amdt 7</FP>
                        <FP SOURCE="FP-1">Galena, AK, Edward G. Pitka Sr, VOR/DME RWY 7, Amdt 7B</FP>
                        <FP SOURCE="FP-1">Galena, AK, Edward G. Pitka Sr, VOR/DME RWY 25, Amdt 10B</FP>
                        <FP SOURCE="FP-1">Kenai, AK, Kenai Muni, ILS OR LOC RWY 19R, Amdt 4</FP>
                        <FP SOURCE="FP-1">Kenai, AK, Kenai Muni, RNAV (GPS) RWY 1L, Amdt 2</FP>
                        <FP SOURCE="FP-1">Kenai, AK, Kenai Muni, RNAV (GPS) RWY 19R, Amdt 2</FP>
                        <FP SOURCE="FP-1">Kenai, AK, Kenai Muni, VOR RWY 19R, Amdt 19</FP>
                        <FP SOURCE="FP-1">Kenai, AK, Kenai Muni, VOR/DME RWY 1L, Amdt 8</FP>
                        <FP SOURCE="FP-1">Wasilla, AK, Wasilla, Takeoff Minimums and Obstacle DP, Amdt 1</FP>
                    </EXTRACT>
                    <HD SOURCE="HD1">On MAY 16, 2011 (76 FR 28172) the FAA published an Amendment in Docket No. 30781, Amdt 3424 to Part 97 of the Federal Aviation Regulations under section 97.33. The following entries, published in TL 11-12 effective for 30 JUNE 2011, are hereby rescinded:</HD>
                    <EXTRACT>
                        <FP SOURCE="FP-1">Anchorage, AK, Ted Stevens Anchorage Intl, ILS OR LOC/DME RWY 7L, ILS RWY 7L (SA CAT I), ILS RWY 7L (CAT II), Amdt 2</FP>
                        <FP SOURCE="FP-1">Anchorage, AK, Ted Stevens Anchorage Intl, ILS RWY 15, Amdt 5</FP>
                        <FP SOURCE="FP-1">Anchorage, AK, Ted Stevens Anchorage Intl, RNAV (GPS) RWY 7L, Amdt 2</FP>
                        <FP SOURCE="FP-1">Anchorage, AK, Ted Stevens Anchorage Intl, RNAV (GPS) RWY 15, Amdt 2</FP>
                        <FP SOURCE="FP-1">Anchorage, AK, Ted Stevens Anchorage Intl, Takeoff Minimum and Obstacle DP, Amdt 6</FP>
                        <FP SOURCE="FP-1">Anchorage, AK, Ted Stevens Anchorage Intl, VOR RWY 7R, Amdt 13A, CANCELLED</FP>
                        <FP SOURCE="FP-1">Kodiak, AK, Kodiak, ILS OR LOC/DME Y RWY 25, Amdt 1A</FP>
                        <FP SOURCE="FP-1">Kodiak, AK, Kodiak, VOR Y RWY 25, Amdt 1A</FP>
                        <FP SOURCE="FP-1">Soldotna, AK, Soldotna, NDB RWY 7, Amdt 2</FP>
                        <FP SOURCE="FP-1">Soldotna, AK, Soldotna, NDB RWY 25, Amdt 3</FP>
                        <FP SOURCE="FP-1">Soldotna, AK, Soldotna, VOR-A, Amdt 7</FP>
                    </EXTRACT>
                    <HD SOURCE="HD1">On MAY 26, 2011 (76 FR 30536) the FAA published an Amendment in Docket No. 30783, Amdt 3426 to Part 97 of the Federal Aviation Regulations under section 97.33. The following entries, published in TL 11-13 effective for 30 JUNE 2011, are hereby rescinded:</HD>
                    <EXTRACT>
                        <FP SOURCE="FP-1">Valdez, AK, Valdez Pioneer Field, LDA/DME-H, Orig-A</FP>
                    </EXTRACT>
                </REGTEXT>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-13955 Filed 6-15-11; 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 Parts 121 and 135</CFR>
                <DEPDOC>[Docket No. 28471; Amendment Nos. 121-355 and 135-125]</DEPDOC>
                <RIN>RIN 2120-AF08</RIN>
                <SUBJECT>Training and Qualification Requirements for Check Airmen and Flight Instructors; Technical Amendment</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration (FAA), DOT.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule; technical amendment.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The FAA is amending its regulations regarding separate requirements for check airmen who check only in flight simulators and flight instructors who instruct only in flight simulators. This document corrects minor technical errors in the codified text of those regulations.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Effective June 16, 2011.</P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Eric Friedman, Air Transportation Division, AFS-200, Federal Aviation Administration, 800 Independence Avenue, SW., Washington, DC 20591; 
                        <E T="03">telephone:</E>
                         202-493-5259; 
                        <E T="03">e-mail: eric.friedman@faa.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Background</HD>
                <P>On June 17, 1996, the FAA published a final rule entitled, “Training and Qualification Requirements for Check Airmen and Flight Instructors” (61 FR 30734).</P>
                <P>
                    In that final rule the FAA established separate requirements for check airmen who check only in flight simulators and flight instructors who instruct only in flight simulators. To ensure an equivalent level of safety, the affected check airmen and flight instructors must accomplish the following: Recency of experience requirements, including completion of an approved line-observation program within each 12-
                    <PRTPAGE P="35104"/>
                    month period; and required training, including recurrent ground and flight training. Additionally this rule allowed check airman and flight instructors to obtain all of their flight training in simulators, as opposed to the then current scheme in which initial and transition flight training must include an in-flight element.
                </P>
                <HD SOURCE="HD1">Technical Amendment</HD>
                <P>This technical amendment makes two revisions to the final rule: (1) The language in § 121.412(f)(2) incorrectly uses the term “check airman” when the term “flight instructor” should have been used; and (2) the language in § 135.338(f)(2) incorrectly uses the term “check airman” when the term “flight instructor” should have been used. Accordingly, this technical amendment revises §§ 121.412(f)(2) and 135.338(f)(2).</P>
                <P>Because the changes in this technical amendment result in no substantive change, we find good cause exists under 5 U.S.C. 553(d)(3) to make the amendment effective in less than 30 days.</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects</HD>
                    <CFR>14 CFR Part 121</CFR>
                    <P>Air carriers, Aircraft, Airmen, Alcohol abuse, Aviation safety, Charter flights, Drug abuse, Drug testing, Reporting and recordkeeping requirements, Safety, and Transportation.</P>
                    <CFR>14 CFR Part 135</CFR>
                    <P>Air taxis, Aircraft, Airmen, Alcohol abuse, Aviation safety, Drug abuse, Drug testing, and Reporting and recordkeeping requirements. </P>
                </LSTSUB>
                <HD SOURCE="HD1">The Amendments</HD>
                <P>In consideration of the foregoing, the Federal Aviation Administration amends chapter I of title 14, Code of Federal Regulations as follows:</P>
                <REGTEXT TITLE="14" PART="121">
                    <PART>
                        <HD SOURCE="HED">PART 121—OPERATING REQUIREMENTS: DOMESTIC, FLAG, AND SUPPLEMENTAL OPERATIONS</HD>
                    </PART>
                    <AMDPAR>1. The authority citation for part 121 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority: </HD>
                        <P>49 U.S.C. 106(g), 40113, 40119, 41706, 44101, 44701-44702, 44705, 44709-44711, 44713, 44716-44717, 44722, 46105.</P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="14" PART="121">
                    <AMDPAR>2. Amend § 121.412 by revising paragraph (f)(2) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 121.412 </SECTNO>
                        <SUBJECT>Qualifications: Flight instructors (airplane) and flight instructors (simulator).</SUBJECT>
                        <STARS/>
                        <P>(f) * * *</P>
                        <P>(2) Satisfactorily complete an approved line-observation program within the period prescribed by that program preceding the performance of any flight instructor duty in a flight simulator.</P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="14" PART="135">
                    <PART>
                        <HD SOURCE="HED">PART 135—OPERATING REQUIREMENTS: COMMUTER AND ON DEMAND OPERATIONS AND RULES GOVERNING PERSONS ON BOARD SUCH AIRCRAFT</HD>
                    </PART>
                    <AMDPAR>3. The authority citation for part 135 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P> 49 U.S.C. 106(g), 41706, 40113, 44701-44702, 44705, 44709, 44711-44713, 44715-44717, 44722, 45101-45105.</P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="14" PART="135">
                    <AMDPAR>4. Amend § 135.338 by revising paragraph (f)(2) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 135.338 </SECTNO>
                        <SUBJECT>Qualifications: Flight instructors (aircraft) and flight instructors (simulator).</SUBJECT>
                        <STARS/>
                        <P>(f) * * *</P>
                        <P>(2) Satisfactorily complete an approved line-observation program within the period prescribed by that program preceding the performance of any flight instructor duty in a flight simulator.</P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <SIG>
                    <DATED>Issued in Washington, DC, on June 10, 2011.</DATED>
                    <NAME>Dennis R. Pratte,</NAME>
                    <TITLE>Acting Director, Office of Rulemaking.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-14999 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-13-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
                <SUBAGY>Coast Guard</SUBAGY>
                <CFR>33 CFR Part 165</CFR>
                <DEPDOC>[Docket No. USCG-2011-0433]</DEPDOC>
                <RIN>RIN 1625-AA00</RIN>
                <SUBJECT>Safety Zone; Waterway Closure, Atchafalaya River From Mile Marker 117 (Morgan City Railroad Bridge) to Mile Marker 0 (Simmesport, LA)</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 closing the Atchafalaya River to all commercial traffic from MM 117 (Morgan City Railroad Bridge) to MM 0 (Simmesport, LA). This temporary safety zone is needed to protect the general public, vessels and tows from destruction, and the levee system from destruction, loss or injury due to hazards associated with rising flood water.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        <E T="03">Effective Date:</E>
                         this rule is effective in the CFR from June 16, 2011 until 11:59 p.m. July 31, 2011. This rule is effective with actual notice for purposes of enforcement beginning 12:01 a.m. May 16, 2011 through 11:59 p.m. July 31, 2011.
                    </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Documents indicated in this preamble as being available in the docket are part of docket USCG-2011-0433 and are available online by going to 
                        <E T="03">http://www.regulations.gov,</E>
                         inserting USCG-2011-0433 the “Keyword” box, and then clicking “Search.” They are also available for inspection or copying at the Docket Management Facility (M-30), U.S. Department of Transportation, West Building Ground Floor, Room W12-140, 1200 New Jersey Avenue, SE., Washington, DC 20590, between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        If you have questions on this temporary rule, call or e-mail Lieutenant (LT) Russell Pickering, Coast Guard; telephone 985-380-5334, e-mail 
                        <E T="03">russell.t.pickering@uscg.mil.</E>
                         If you have questions on viewing the docket, call Renee V. Wright, Program Manager, Docket Operations, telephone 202-366-9826.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Regulatory Information</HD>
                <P>The Coast Guard is issuing this temporary final rule without prior notice and opportunity to comment pursuant to authority under section 4(a) of the Administrative Procedure Act (APA) (5 U.S.C. 553(b)). This provision authorizes an agency to issue a rule without prior notice and opportunity to comment when the agency for good cause finds that those procedures are “impracticable, unnecessary, or contrary to the public interest.” Under 5 U.S.C. 553(b)(B), the Coast Guard finds that good cause exists for not publishing a notice of proposed rulemaking (NPRM) with respect to this rule because publishing a NPRM would be impracticable since immediate action is needed to protect the general public, levee system, vessels and tows from the hazards associated with rising flood water on the Atchafalaya River.</P>
                <P>
                    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>
                    . Publishing a NPRM and delaying its effective date would be impracticable since immediate action is needed to protect the general public, levee system, vessels and tows from destruction, loss or injury due to the 
                    <PRTPAGE P="35105"/>
                    hazards associated with rising flood water in the Atchafalaya River.
                </P>
                <HD SOURCE="HD1">Basis and Purpose</HD>
                <P>Captain of the Port Morgan City, Louisiana has determined that there is a need to establish a temporary safety zone due to high water. This temporary safety zone is needed to protect the general public, levee system, vessels and tows from destruction, loss or injury from flood waters and associated hazards.</P>
                <HD SOURCE="HD1">Discussion of Rule</HD>
                <P>The Coast Guard is establishing a temporary Safety Zone in the Atchafalaya River for all commercial traffic from MM 117 (Morgan City Railroad Bridge) to MM 0 (Simmesport, LA). Vessels and tows may not enter this zone unless authorized by the Captain of the Port Morgan City or designated representative.</P>
                <HD SOURCE="HD1">Regulatory Analyses</HD>
                <P>We developed this rule after considering numerous statutes and executive orders related to rulemaking. Below we summarize our analyses based on 13 of these statutes or executive orders.</P>
                <HD SOURCE="HD1">Regulatory Planning and Review</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.</P>
                <P>Although this regulation will restrict access to the area, the effect of the rule will not be significant because vessels requiring entry into or passage through the Safety Zone may request permission from the Captain of the Port Morgan City, or a designated representative and entry will be evaluated on a case-by-case basis to minimize impact and protect the general public, levee system, vessels and tows from destruction, loss or injury due to the hazards associated with rising flood water. Notifications to the marine community will be made through broadcast notices to mariners and Local Notices to Mariners and Marine Safety Information Bulletins.</P>
                <HD SOURCE="HD1">Small Entities</HD>
                <P>Under the Regulatory Flexibility Act (5 U.S.C. 601-612), we have considered whether this rule would have a significant economic impact on a substantial number of small entities. The term “small entities” comprises small businesses, not-for-profit organizations that are independently owned and operated and are not dominant in their fields, and governmental jurisdictions with populations of less than 50,000.</P>
                <P>The Coast Guard certifies under 5 U.S.C. 605(b) that this rule will not have a significant economic impact on a substantial number of small entities. This rule will affect the following entities, some of which may be small entities: The owners or operators of vessels intending to transit through the Safety Zone from May 16, 2011 through July 31, 2011. This temporary safety zone is not expected to have a significant economic impact on a substantial number of small entities because vessels and tows requiring entry into or passage through the temporary safety zone may request permission from the Captain of the Port Morgan City, or a designated representative. If you are a small business entity and are significantly affected by this regulation, please contact LT Russell Pickering, Marine Safety Unit Morgan City, at (985) 380-5334.</P>
                <HD SOURCE="HD1">Assistance for Small Entities</HD>
                <P>Under section 213(a) of the Small Business Regulatory Enforcement Fairness Act of 1996 (Pub. L. 104-121), we offer to assist small entities in understanding the rule so that they can better evaluate its effects on them and participate in the rulemaking process.</P>
                <P>Small businesses may send comments on the actions of Federal employees who enforce, or otherwise determine compliance with, Federal regulations to the Small Business and Agriculture Regulatory Enforcement Ombudsman and the Regional Small Business Regulatory Fairness Boards. The Ombudsman evaluates these actions annually and rates each agency's responsiveness to small business. If you wish to comment on actions by employees of the Coast Guard, call 1-888-REG-FAIR (1-888-734-3247). The Coast Guard will not retaliate against small entities that question or complain about this rule or any policy or action of the Coast Guard.</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 affect a taking of private property or otherwise have taking implications under Executive Order 12630, Governmental Actions and Interference with Constitutionally Protected Property Rights.</P>
                <HD SOURCE="HD1">Civil Justice Reform</HD>
                <P>This rule meets applicable standards in sections 3(a) and 3(b)(2) of Executive Order 12988, Civil Justice Reform, to minimize litigation, eliminate ambiguity, and reduce burden.</P>
                <HD SOURCE="HD1">Protection of Children</HD>
                <P>We have analyzed this rule under Executive Order 13045, Protection of Children from Environmental Health Risks and Safety Risks. This rule is not an economically significant rule and does not create an environmental risk to health or 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 
                    <PRTPAGE P="35106"/>
                    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 Department of Homeland Security Management Directive 023-01 and Commandant Instruction M16475.lD, 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 this action is one of a category of actions which do not individually or cumulatively have a significant effect on the human environment. This rule is categorically excluded, under figure 2-1, paragraph (34) (g.), of the Instruction. This rule involves an emergency situation and will be in effect for over one week, but is not expected to result in any significant adverse environmental impact as described in NEPA.</P>
                <P>
                    An environmental analysis checklist and a categorical exclusion determination will be provided and made available at the docket as indicated in the 
                    <E T="02">ADDRESSES</E>
                     section.
                </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>
                <P>For the reasons discussed in the preamble, the Coast Guard amends 33 CFR part 165 as follows:</P>
                <REGTEXT TITLE="33" PART="165">
                    <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. 1231; 46 U.S.C. Chapter 701, 3306, 3703; 50 U.S.C. 191, 195; 33 CFR 1.05-1, 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. A new temporary § 165.T08-0433 is added to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 165.T08-0433</SECTNO>
                        <SUBJECT>Safety Zone; Waterway Closure, Atchafalaya River from Mile Marker 117 (Morgan City Railroad Bridge) to Mile Marker 0 (Simmesport, LA).</SUBJECT>
                        <P>
                            (a) 
                            <E T="03">Location.</E>
                             This temporary safety zone is located on the specified waters of the Atchafalaya River between MM 117 (Morgan City Railroad Bridge) and MM 0 (Simmesport, LA).
                        </P>
                        <P>
                            (b) 
                            <E T="03">Effective date.</E>
                             This rule is effective May 16, 2011 through July 31, 2011 and enforceable with actual notice upon signature, May 16, 2011.
                        </P>
                        <P>
                            (c) 
                            <E T="03">Regulations.</E>
                             (1) In accordance with the general regulations in § 165.23 of this part, entry into this zone is prohibited unless authorized by the Captain of the Port Morgan City.
                        </P>
                        <P>(2) Vessels requiring entry into or passage through the Safety Zone must request permission from the Captain of the Port Morgan City, or a designated representative. They may be contacted on VHF Channel 13 or 16, or by telephone at 985-380-5370.</P>
                        <P>(3) All persons and vessels shall comply with the instructions of the Captain of the Port Morgan City and designated on-scene patrol personnel. On-scene patrol personnel include commissioned, warrant, and petty officers of the U.S. Coast Guard.</P>
                    </SECTION>
                </REGTEXT>
                <SIG>
                    <DATED>Dated: May 16, 2011.</DATED>
                    <NAME>J.C. Burton,</NAME>
                    <TITLE>Captain, U.S. Coast Guard, Captain of the Port Morgan City, Louisiana.</TITLE>
                    <NAME>E.M. Stanton,</NAME>
                    <TITLE>Captain, U.S. Coast Guard Captain of the Port New Orleans, Louisiana.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-14922 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 9110-04-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
                <SUBAGY>Coast Guard</SUBAGY>
                <CFR>33 CFR Part 165</CFR>
                <DEPDOC>[Docket No. USCG-2011-0228]</DEPDOC>
                <RIN>RIN 1625-AA00</RIN>
                <SUBJECT>Safety Zone, Brandon Road Lock and Dam to Lake Michigan Including Des Plaines River, Chicago Sanitary and Ship Canal, Chicago River, and Calumet-Saganashkee Channel, Chicago, IL</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Coast Guard, DHS.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Coast Guard is establishing a permanent safety zone from Brandon Road Lock and Dam to Lake Michigan. This safety zone will cover 77 miles of navigable waterways in the Chicago area and is intended to restrict vessels from entering certain segments of the navigable waters of the Des Plaines River, the Chicago Sanitary and Ship Canal, branches of the Chicago River, and the Calumet-Saganashkee Channel. This safety zone is necessary to protect the waters, waterway users and vessels from hazards associated with a myriad of actions designed to control the spread of aquatic nuisance species. Because the Asian Carp Regional Coordinating Committee (ACRCC) may take such actions at any time and in any segment of the waterways covered by this safety zone, this safety zone will provide the Captain of the Port, Sector Lake Michigan, the ability to take targeted and expeditious action to protect vessels and persons from the hazards associated with any Federal and state efforts to control aquatic nuisance species.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>This rule is effective July 18, 2011.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Comments and material received from the public, as well as documents indicated in this preamble as being available in the docket, are part of docket USCG-2011-0228 and are available online at 
                        <E T="03">http://www.regulations.gov</E>
                        . This material is also available for inspection or copying at two locations: The Docket Management Facility (M-30), U.S. Department of Transportation, West Building Ground Floor, Room W12-140, 1200 New Jersey Avenue, SE., Washington, DC 20590, between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays and the U.S. Coast Guard Sector Lake Michigan, 2420 South Lincoln Memorial Drive, Milwaukee, WI 53207, between 8 a.m. 
                        <PRTPAGE P="35107"/>
                        and 3 p.m., Monday through Friday, except Federal holidays.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        If you have questions on this rule, call BM1 Adam Kraft, Prevention Department, Coast Guard Sector Lake Michigan, Milwaukee, WI at (414) 747-7148 or e-mail him at 
                        <E T="03">Adam.D.Kraft@uscg.mil.</E>
                         If you have questions on viewing or submitting material to the docket, call Renee V. Wright, Program Manager, Docket Operations, telephone 202-366-9826.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Regulatory Information</HD>
                <P>
                    On April 27, 2011, we published a Notice of Proposed Rule Making (NPRM) entitled Safety Zones; Brandon Road Lock and Dam to Lake Michigan including Des Plaines River, Chicago Sanitary and Ship Canal, Chicago River, and Calumet-Saganashkee Channel, Chicago, IL, in the 
                    <E T="04">Federal Register</E>
                     (76 FR 23524). We received zero letters commenting on the proposed rule. No public meeting was requested, and none was held.
                </P>
                <HD SOURCE="HD1">Background and Purpose</HD>
                <P>In 2007, the Department of the Interior through the Fish and Wildlife Service listed the Asian Carp and the Silver Carp as Injurious Wildlife Species. Based upon testing conducted by the United States Army Corps of Engineers (USACE), the Asian carp are believed to be migrating toward the Great Lakes through the Chicago Sanitary and Ship Canal and connected tributaries. Scientists are concerned that if these aquatic nuisance species reach the Great Lakes in sufficient numbers that they might devastate the Great Lakes commercial and sport fishing industries.</P>
                <P>The Nonindigenous Aquatic Nuisance Prevention and Control Act of 1990, as amended by the National Invasive Species Act of 1996, authorized the USACE to conduct a demonstration project to identify an environmentally sound method for preventing and reducing the dispersal of non-indigenous aquatic nuisance species through the Chicago Sanitary and Ship Canal.</P>
                <P>Subsequently, the USACE put in place an electric barrier to prevent and reduce the dispersal of Asian carp in the Chicago Sanitary and Ship Canal. Specifically, a demonstration dispersal barrier (Barrier I) was constructed and has been in operation since April 2002. It is located approximately 30 miles from Lake Michigan and creates an electric field in the water by pulsing low voltage DC current through steel cables secured to the bottom of the canal. A second barrier (Barrier IIA) was constructed 800 to 1300 feet downstream of Barrier I. Barrier IIA is currently operating at two volts per inch, 15 Hertz, and 6.5ms. Construction on Barrier IIB was completed in early 2011. Operational and safety testing was conducted on Barrier IIB in February 2011 and is being analyzed. The completion of Barrier IIB should allow for maintenance operations with reduced need for the use of other aquatic nuisance species countermeasures.</P>
                <P>
                    In addition to the aforementioned electric dispersal barriers, the ACRCC has been conducting fish sampling in the Chicago Area Waterway System. The purpose of this sampling is to detect the potential presence of Asian Carp and other aquatic nuisance species within the waters covered by this safety zone. Upon detection of the presence of Asian Carp or other aquatic nuisance species within any segment of the waterways covered by this safety zone, the ACRCC will take action designed to control the spread of aquatic nuisance species within the area of detection. The various types of actions that the ACRCC might take are outlined in the Asian Carp Control Strategy Framework, which can be found on the ACRCC's Web site: 
                    <E T="03">http://asiancarp.org</E>
                    .
                </P>
                <P>Because of the ACRCC's testing and countermeasure activity, the Captain of the Port, Sector Lake Michigan, put in place a Temporary Interim Rule (TIR) on May 1, 2010. This TIR established a 77 mile long safety zone from Brandon Road Lock to Lake Michigan in Chicago, IL. The purpose of that safety zone was to provide the Captain of the Port, Sector Lake Michigan, with the ability to take targeted and expeditious action to protect vessels and persons from the hazards associated with the aquatic nuisance testing and the countermeasure activities detailed in the ACRCC's Asian Carp Control Strategy Framework. Although that TIR expired on March 1, 2011, the ACRCC will continue their testing and countermeasure activities. Thus, the Captain of the Port, Sector Lake Michigan, still finds it necessary to have the ability to take targeted and expeditious actions in the affected waterways to protect vessels and persons from the ACRCC's expected actions. For this reason, the Captain of the Port, Sector Lake Michigan, is establishing a permanent safety zone along the same waterways covered in the previously published TIR. Like the safety zone established in the TIR, this safety zone will only be enforced when testing and countermeasure activity require the Captain of the Port, Sector Lake Michigan to enforce the safety zone.</P>
                <HD SOURCE="HD1">Discussion of Comments and Changes</HD>
                <P>No comments on the proposed rulemaking were received and no changes are being made to the rule.</P>
                <HD SOURCE="HD1">Regulatory Analysis</HD>
                <P>We developed this rule after considering numerous statutes and executive orders related to rulemaking. Below we summarize our analyses based on 13 of these statutes or executive orders.</P>
                <HD SOURCE="HD1">Regulatory Planning and Review</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.</P>
                <P>We expect the economic impact of this rule to be minimal. This determination is based on the following: (1) While this rule establishes a safety zone that is 77 miles long, the Captain of the Port, Sector Lake Michigan, will enforce the safety zone only in relatively small segments. The Captain of the Port, Sector Lake Michigan, will have the flexibility to enforce the safety zone in only the segments of the safety zone affected by the application of piscicide, targeted fishing operations or other countermeasures to address the problem of aquatic nuisance species invasion; and (2) The Captain of the Port, Sector Lake Michigan, will make every effort to reduce the closure time of the enforced segments of the safety zone.</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.</P>
                <P>
                    This rule will affect the following entities, some of which might be small entities: The owners and operators of vessels intending to transit or anchor in any enforced segment of the 77 mile 
                    <PRTPAGE P="35108"/>
                    safety zone. This rule will not have a significant impact on a substantial number of small entities because only small segments of the safety zone will be enforced at any one time. Also, enforcement periods will be relatively short. Furthermore, in certain instances vessels may pass around an enforced segment of the zone. Finally, transit through an enforced segment of the zone may be permitted by the Captain of the Port, Sector Lake Michigan, or his or her on-scene representative when deemed practical.
                </P>
                <P>
                    On April 27, 2011, the Coast Guard published a Notice of Proposed Rule Making (NPRM) entitled Safety Zones; Brandon Road Lock and Dam to Lake Michigan including Des Plaines River, Chicago Sanitary and Ship Canal, Chicago River, and Calumet-Saganashkee Channel, Chicago, IL, in the 
                    <E T="04">Federal Register</E>
                     (76 FR 23524). The Coast Guard received zero public submissions commenting on the impact to small entities by this rule. There have been no changes made to the rule as proposed.
                </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 want to assist small entities in understanding this rule so that they can better evaluate its effects on them and participate in the rulemaking process.</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>
                <P>
                    On April 27, 2011, the Coast Guard published a Notice of Proposed Rule Making (NPRM) entitled Safety Zones; Brandon Road Lock and Dam to Lake Michigan including Des Plaines River, Chicago Sanitary and Ship Canal, Chicago River, and Calumet-Saganashkee Channel, Chicago, IL, in the 
                    <E T="04">Federal Register</E>
                     (76 FR 23524). The Coast Guard received zero public submissions commenting on the impact to small entities by this rule. There have been no changes made to the rule as proposed.
                </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 (adjusted for inflation) or more in any one year. Though this rule would not result in such an expenditure, we do discuss the effects of this rule elsewhere in this preamble.</P>
                <P>
                    On April 27, 2011, the Coast Guard published a Notice of Proposed Rule Making (NPRM) entitled Safety Zones; Brandon Road Lock and Dam to Lake Michigan including Des Plaines River, Chicago Sanitary and Ship Canal, Chicago River, and Calumet-Saganashkee Channel, Chicago, IL, in the 
                    <E T="04">Federal Register</E>
                     (76 FR 23524). The Coast Guard received zero public submissions commenting on the impact to small entities by this rule. There have been no changes made to the rule as proposed.
                </P>
                <HD SOURCE="HD1">Taking of Private Property</HD>
                <P>This rule will not cause a taking of private property or otherwise have taking implications under Executive Order 12630, Governmental Actions and Interference with Constitutionally Protected Property Rights.</P>
                <P>
                    On April 27, 2011, the Coast Guard published a Notice of Proposed Rule Making (NPRM) entitled Safety Zones; Brandon Road Lock and Dam to Lake Michigan including Des Plaines River, Chicago Sanitary and Ship Canal, Chicago River, and Calumet-Saganashkee Channel, Chicago, IL, in the 
                    <E T="04">Federal Register</E>
                     (76 FR 23524). The Coast Guard received zero public submissions commenting on the impact to small entities by this rule. There have been no changes made to the rule as proposed.
                </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>
                <P>
                    On April 27, 2011, the Coast Guard published a Notice of Proposed Rule Making (NPRM) entitled Safety Zones; Brandon Road Lock and Dam to Lake Michigan including Des Plaines River, Chicago Sanitary and Ship Canal, Chicago River, and Calumet-Saganashkee Channel, Chicago, IL, in the 
                    <E T="04">Federal Register</E>
                     (76 FR 23524). The Coast Guard received zero public submissions commenting on the impact to small entities by this rule. There have been no changes made to the rule as proposed.
                </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>
                <P>
                    On April 27, 2011, the Coast Guard published a Notice of Proposed Rule Making (NPRM) entitled Safety Zones; Brandon Road Lock and Dam to Lake Michigan including Des Plaines River, Chicago Sanitary and Ship Canal, Chicago River, and Calumet-Saganashkee Channel, Chicago, IL, in the 
                    <E T="04">Federal Register</E>
                     (76 FR 23524). The Coast Guard received zero public submissions commenting on the impact to small entities by this rule. There have been no changes made to the rule as proposed.
                </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>
                <P>
                    On April 27, 2011, the Coast Guard published a Notice of Proposed Rule Making (NPRM) entitled Safety Zones; Brandon Road Lock and Dam to Lake Michigan including Des Plaines River, Chicago Sanitary and Ship Canal, Chicago River, and Calumet-Saganashkee Channel, Chicago, IL, in the 
                    <E T="04">Federal Register</E>
                     (76 FR 23524). The Coast Guard received zero public submissions commenting on the impact to small entities by this rule. There have been no changes made to the rule as proposed.
                </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 
                    <PRTPAGE P="35109"/>
                    has not designated it as a significant energy action. Therefore, it does not require a Statement of Energy Effects under Executive Order 13211.
                </P>
                <P>
                    On April 27, 2011, the Coast Guard published a Notice of Proposed Rule Making (NPRM) entitled Safety Zones; Brandon Road Lock and Dam to Lake Michigan including Des Plaines River, Chicago Sanitary and Ship Canal, Chicago River, and Calumet-Saganashkee Channel, Chicago, IL, in the 
                    <E T="04">Federal Register</E>
                     (76 FR 23524). The Coast Guard received zero public submissions commenting on the impact to small entities by this rule. There have been no changes made to the rule as proposed.
                </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 T="03">e.g.,</E>
                     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>
                <P>
                    On April 27, 2011, the Coast Guard published a Notice of Proposed Rule Making (NPRM) entitled Safety Zones; Brandon Road Lock and Dam to Lake Michigan including Des Plaines River, Chicago Sanitary and Ship Canal, Chicago River, and Calumet-Saganashkee Channel, Chicago, IL, in the 
                    <E T="04">Federal Register</E>
                     (76 FR 23524). The Coast Guard received zero public submissions commenting on the impact to small entities by this rule. There have been no changes made to the rule as proposed.
                </P>
                <HD SOURCE="HD1">Environment</HD>
                <P>
                    We have analyzed this rule under Department of Homeland Security Management Directive 023-01 and Commandant Instruction M16475.lD, 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 this action is one of the category of actions which do not individually or cumulatively have significant effect on the human environment. Therefore, this rule is categorically excluded, under section 2.B.2 Figure 2-1, paragraph (34)(g), of the Instruction and neither an environmental assessment nor an environmental impact statement is required. This rule involves the establishing of a safety zone. An environmental analysis checklist and a categorical exclusion determination are available in the docket where indicated under 
                    <E T="02">ADDRESSES</E>
                    . The Coast Guard's responsibilities to assess environmental impacts extend only to the creation of the safety zone and do not include the application of piscicide or any other countermeasures to combat invasive species.
                </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>
                <P>For the reasons discussed in the preamble, the Coast Guard amends 33 CFR part 165 as follows:</P>
                <REGTEXT TITLE="33" PART="165">
                    <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. 1231; 46 U.S.C. Chapter 701; 50 U.S.C. 191, 195; 33 CFR 1.05-1, 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 § 165.930 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 165.930 </SECTNO>
                        <SUBJECT>Safety Zone, Brandon Road Lock and Dam to Lake Michigan including Des Plaines River, Chicago Sanitary and Ship Canal, Chicago River, and Calumet-Saganashkee Channel, Chicago, IL.</SUBJECT>
                        <P>
                            (a) 
                            <E T="03">Location.</E>
                             The safety zone consists of the following areas:
                        </P>
                        <P>
                            (1) 
                            <E T="03">Des Plaines River.</E>
                             All U.S. waters of the Des Plaines River located between mile marker 286.0 (Brandon Road Lock and Dam) and mile marker 290.0 (point at which the Des Plaines River connects with the Chicago Sanitary and Ship Canal).
                        </P>
                        <P>
                            (2) 
                            <E T="03">Chicago Sanitary and Ship Canal.</E>
                             All U.S. waters of the Chicago Sanitary and Ship Canal between mile marker 290.0 (point at which the Chicago Sanitary and Ship Canal connects to the Des Plaines River) and mile marker 321.8 (point at which the Chicago Sanitary and Ship Canal Connects to the South Branch Chicago River).
                        </P>
                        <P>
                            (3) 
                            <E T="03">South Branch Chicago River.</E>
                             All U.S. waters of the South Branch Chicago River between mile marker 321.8 (point at which the South Branch Chicago River connects to the Chicago Sanitary and Ship Canal) and mile marker 325.6 (point at which the South Branch Chicago River connects to the Chicago River (Main Branch) and North Branch Chicago River).
                        </P>
                        <P>
                            (4) 
                            <E T="03">Chicago River (Main Branch).</E>
                             All U.S. waters of the Chicago River (Main Branch) between mile marker 325.6 (point at which the Chicago River connects to the South Branch Chicago River) and 100 yards extending past the end of the Chicago River covering the area of the Federal channel within Chicago Harbor.
                        </P>
                        <P>
                            (5) 
                            <E T="03">North Branch Chicago River.</E>
                             All U.S. waters of the North Branch Chicago River between mile marker 325.6 (point at which the North Branch Chicago River connects to the Chicago River (Main Branch) and the South Branch Chicago River) and mile marker 331.4 (end of navigation channel).
                        </P>
                        <P>
                            (6) 
                            <E T="03">Calumet-Saganashkee Channel.</E>
                             All U.S. waters of the Calumet-Saganashkee Channel between mile marker 303.5 (point at which the Calumet-Saganashkee Channel connects to the Chicago Sanitary and Ship Canal) and mile marker 333.0; all U.S. waters of the Calumet-Saganashkee Channel between mile marker 333.0 and Lake Michigan (Calumet Harbor).
                        </P>
                        <P>
                            (b) 
                            <E T="03">Effective Period.</E>
                             This rule is effective July 18, 2011.
                        </P>
                        <P>
                            (c) 
                            <E T="03">Enforcement.</E>
                             (1) The Captain of the Port, Sector Lake Michigan, may enforce this safety zone in whole, in segments, or by any combination of segments. The Captain of the Port, Sector Lake Michigan, may suspend the enforcement of any segment of this safety zone for which notice of enforcement had been given.
                        </P>
                        <P>
                            (2) The safety zone established by this section will be enforced, pursuant to paragraph (c)(1) of this section, only upon notice by the Captain of the Port, Sector Lake Michigan. Suspension of any previously announced period of enforcement will also be provided by the Captain of the Port, Sector Lake Michigan. All notices of enforcement and notices of suspension of enforcement will clearly describe any segments of the safety zone affected by the notice. At a minimum, notices of enforcement and notices of suspension of enforcement will identify any affected segments by reference to mile markers. When possible, the Captain of the Port, Sector Lake Michigan, will also identify enforced segments of this safety zone by referencing readily identifiable geographical points. In addition to providing the geographical bounds of any enforced segment of this safety zone, notices of enforcement will also provide the date(s) and time(s) at which enforcement will commence or suspend.
                            <PRTPAGE P="35110"/>
                        </P>
                        <P>
                            (3) The Captain of the Port, Sector Lake Michigan, will publish notices of enforcement and notices of suspension of enforcement in accordance with 33 CFR 165.7(a) and in a manner that provides as much notice to the public as possible. The primary method of notification will be through publication in the 
                            <E T="04">Federal Register</E>
                            . The Captain of the Port, Sector Lake Michigan, will also provide notice through other means, such as Broadcast Notice to Mariners, local Notice to Mariners, local news media, distribution in leaflet form, and on-scene oral notice. Additionally, the Captain of the Port, Sector Lake Michigan, may notify representatives from the maritime industry through telephonic and email notifications.
                        </P>
                        <P>
                            (d) 
                            <E T="03">Regulations.</E>
                             (1) In accordance with the general regulations in § 165.23 of this part, entry into, transiting, mooring, laying up, or anchoring within any enforced segment of the safety zone is prohibited unless authorized by the Captain of the Port, Sector Lake Michigan, or his or her designated representative.
                        </P>
                        <P>(2) The “designated representative” of the Captain of the Port, Sector Lake Michigan, is any Coast Guard commissioned, warrant or petty officer who has been designated by the Captain of the Port, Sector Lake Michigan, to act on his or her behalf. The designated representative of the Captain of the Port, Sector Lake Michigan, will be aboard a Coast Guard, Coast Guard Auxiliary, or other designated vessel or will be on shore and will communicate with vessels via VHF radio, loudhailer, or by phone. The Captain of the Port, Sector Lake Michigan, or his or her designated representative may be contacted via VHF radio Channel 16 or the Coast Guard Sector Lake Michigan Command Center at 414-747-7182.</P>
                        <P>(3) To obtain permission to enter or operate within an enforced segment of the safety zone established by this section, Vessel operators must contact the Captain of the Port, Sector Lake Michigan, or his or her designated representative. Vessel operators given permission to operate in an enforced segment of the safety zone must comply with all directions given to them by the Captain of the Port, Sector Lake Michigan, or his or her designated representative.</P>
                        <P>(4) When a segment of the safety zone is being enforced, it will be closed to all vessel traffic, except as may be permitted by the Captain of the Port, Sector Lake Michigan, or his or her designated representative. As soon as operations permit, the Captain of the Port, Sector Lake Michigan, will issue a notice of suspension of enforcement as specified in paragraph (c) of this section.</P>
                        <P>(5) All persons entering any enforced segment of the safety zone established in this section are advised that they do so at their own risk.</P>
                    </SECTION>
                </REGTEXT>
                <SIG>
                    <DATED>Dated: June 3, 2011.</DATED>
                    <NAME>L. Barndt,</NAME>
                    <TITLE>Captain, U.S. Coast Guard Captain of the Port, U.S. Coast Guard Sector Lake Michigan.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-14925 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 9110-04-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">GENERAL SERVICES ADMINISTRATION</AGENCY>
                <CFR>41 CFR Part 302-16</CFR>
                <DEPDOC>[FTR Amendment 2011-02; FTR Case 2011-306; Docket Number 2011-0013, Sequence 1]</DEPDOC>
                <RIN>RIN 3090-AJ17</RIN>
                <SUBJECT>Federal Travel Regulation (FTR); Miscellaneous Expense Allowance (MEA)</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of Governmentwide Policy, General Services Administration (GSA).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>GSA is amending the Federal Travel Regulation (FTR) by increasing the set lump-sum rate amount to be paid for the miscellaneous expenses allowance (MEA), when the employee chooses not to provide documentation of miscellaneous expenses.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        <E T="03">Effective date:</E>
                         This final rule is effective on July 18, 2011.
                    </P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        The Regulatory Secretariat (MVCB), 1275 First Street, NE., Washington, DC 20417, (202) 501-4755, for information pertaining to status or publication schedules. For clarification of content, contact Rick Miller, Office of Governmentwide Policy, Travel Management Policy, at (202) 501-3822 or e-mail at 
                        <E T="03">rodney.miller@gsa.gov.</E>
                         Please cite FTR Amendment 2011-02; FTR case 2011-306.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">A. Background</HD>
                <P>Pursuant to 5 U.S.C. 5738, the Administrator of General Services is authorized to prescribe regulations necessary to implement laws regarding Federal employees when assigned a temporary change of station or when otherwise officially relocated. The overall implementing authority is the Federal Travel Regulation (FTR) (41 CFR Chapters 300-304).</P>
                <P>Pursuant to 5 U.S.C. 5724a(f), an employee who is transferred in the interest of the Government is entitled to reimbursement for certain miscellaneous expenses. The purpose of the miscellaneous expense allowance (MEA) is to defray various contingent costs associated with discontinuing a residence at one location and establishing a residence at a new location. The costs covered include items such as fees for disconnecting and connecting appliances, cutting and fitting rugs, draperies, and curtains moved from one residence to another, utility fees or deposits that are not offset by eventual refunds, forfeiture of medical, dental, and other non-transferrable contracts, and the cost of automobile registration and driver's licenses.</P>
                <P>The FTR provides that a MEA may be paid in one of two alternative amounts. A transferring employee without an immediate family is automatically entitled to a lump-sum of one week's basic gross pay, up to $500, and an employee with an immediate family is entitled to a lump-sum of two weeks' basic gross pay, up to $1000. If additional amounts are justified, with supporting documentation, MEA may be reimbursed up to a maximum of one or two weeks basic pay depending on whether or not the employee has an immediate family, not to exceed the maximum rate payable for a position at GS-13, Step 10, of the General Schedule provided in 5 U.S.C. 5332. Since the establishment of MEA in 1966, the lump-sum has only been increased twice. The last increase was on February 19, 2002.</P>
                <P>This final rule will revise section 302-16.102 of the FTR by increasing the lump sums from $500 to $650 for employees with no immediate family and from $1000 to $1300, for employees who have an immediate family. These figures are based upon an increase in the Consumer Price Index.</P>
                <P>This final rule also makes one clerical correction to section 302-16.104.</P>
                <HD SOURCE="HD1">B. Executive Orders 12866 and 13563</HD>
                <P>
                    Executive Orders 12866 and 13563 direct agencies to assess all costs and benefits of available regulatory alternatives and, if regulation is necessary, to select regulatory approaches that maximize net benefits (including potential economic, environmental, public health and safety effects, distributive impacts, and equity). Executive Order 13563 emphasizes the importance of quantifying both costs and benefits, of reducing costs, of harmonizing rules, and of promoting flexibility. This is not a significant regulatory action and, therefore, was not subject to review 
                    <PRTPAGE P="35111"/>
                    under Section 6(b) of Executive Order 12866, Regulatory Planning and Review, dated September 30, 1993. This rule is not a major rule under 5 U.S.C. 804.
                </P>
                <HD SOURCE="HD1">C. Regulatory Flexibility Act</HD>
                <P>
                    This final rule will not have significant economic impact on a substantial number of small entities within the meaning of the Regulatory Flexibility Act, 5 U.S.C. 601, 
                    <E T="03">et seq.</E>
                     This final rule is also exempt from Regulatory Flexibility Act per 5 U.S.C. 553(a)(2), because it applies to agency management or personnel. However, this final rule is being published to provide transparency in the promulgation of Federal policies.
                </P>
                <HD SOURCE="HD1">D. Paperwork Reduction Act</HD>
                <P>
                    The Paperwork Reduction Act does not apply because the changes to the FTR do not impose recordkeeping or information collection requirements, or the collection of information from offerors, contractors, or members of the public that require the approval of the Office of Management and Budget under 44 U.S.C. 3501, 
                    <E T="03">et seq.</E>
                </P>
                <HD SOURCE="HD1">E. Small Business Regulatory Enforcement Fairness Act</HD>
                <P>This final rule is also exempt from congressional review prescribed under 5 U.S.C. 801 since it relates solely to agency management and personnel.</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 41 CFR Part 302-16</HD>
                    <P>Government employees, Relocation, Travel, and Transportation expenses.</P>
                </LSTSUB>
                <SIG>
                    <DATED>Dated: May 5, 2011.</DATED>
                    <NAME>Martha Johnson,</NAME>
                    <TITLE>Administrator of General Services.</TITLE>
                </SIG>
                <P>For the reasons set forth in the preamble, pursuant to 5 U.S.C. 5721-5738, 41 CFR part 302-16 is amended to read as follows:</P>
                <REGTEXT TITLE="41" PART="302-16">
                    <PART>
                        <HD SOURCE="HED">PART 302-16—ALLOWANCE FOR MISCELLANEOUS EXPENSES</HD>
                    </PART>
                    <AMDPAR>1. The authority citation for 41 CFR part 302-16 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P> 5 U.S.C. 5738; 20 U.S.C. 905(a); E.O. 11609, 36 FR 13747; 3 CFR 1971-1975 Comp., p. 586.</P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="41" PART="302-16">
                    <SECTION>
                        <SECTNO>§ 302-16.102 </SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>2. Amend § 302-16.102 by—</AMDPAR>
                    <AMDPAR>a. Removing “$500” in paragraph (a) and adding “$650” in its place.</AMDPAR>
                    <AMDPAR>b. Removing “$1,000” in paragraph (b) and adding “$1,300” in its place.</AMDPAR>
                </REGTEXT>
                <REGTEXT TITLE="41" PART="302-16">
                    <SECTION>
                        <SECTNO>§ 302-16.104 </SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>3. Amend § 302-16.104 by removing “§ 302-16.101” and adding “§ 302-16.102” in its place.</AMDPAR>
                </REGTEXT>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-14890 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6820-14-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
                <SUBAGY>Federal Emergency Management Agency</SUBAGY>
                <CFR>44 CFR Part 67</CFR>
                <DEPDOC>[Docket ID FEMA-2011-0002]</DEPDOC>
                <SUBJECT>Final 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>Base (1% annual-chance) Flood Elevations (BFEs) and modified BFEs are made final for the communities listed below. The BFEs and modified BFEs are the basis for the floodplain management measures that each community is required either to adopt or to show evidence of being already in effect in order to qualify or remain qualified for participation in the National Flood Insurance Program (NFIP).</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The date of issuance of the Flood Insurance Rate Map (FIRM) showing BFEs and modified BFEs for each community. This date may be obtained by contacting the office where the maps are available for inspection as indicated in the table below.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>The final 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>
                        Luis Rodriguez, Chief, Engineering Management Branch, Federal Insurance and Mitigation Administration, Federal Emergency Management Agency, 500 C Street, SW., Washington, DC 20472, (202) 646-4064, or (e-mail) 
                        <E T="03">luis.rodriguez1@dhs.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The Federal Emergency Management Agency (FEMA) makes the final determinations listed below for the modified BFEs for each community listed. These modified elevations have been published in newspapers of local circulation and ninety (90) days have elapsed since that publication. The Deputy Federal Insurance and Mitigation Administrator has resolved any appeals resulting from this notification.</P>
                <P>This final rule is issued in accordance with section 110 of the Flood Disaster Protection Act of 1973, 42 U.S.C. 4104, and 44 CFR part 67. FEMA has developed criteria for floodplain management in floodprone areas in accordance with 44 CFR part 60.</P>
                <P>Interested lessees and owners of real property are encouraged to review the proof Flood Insurance Study and FIRM available at the address cited below for each community.</P>
                <P>The BFEs and modified BFEs are made final in the communities listed below. Elevations at selected locations in each community are shown.</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.
                </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 67</HD>
                    <P>Administrative practice and procedure, Flood insurance, Reporting and recordkeeping requirements.</P>
                </LSTSUB>
                <P>Accordingly, 44 CFR part 67 is amended as follows:</P>
                <REGTEXT TITLE="44" PART="67">
                    <PART>
                        <HD SOURCE="HED">PART 67—[AMENDED]</HD>
                    </PART>
                    <AMDPAR>1. The authority citation for part 67 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="67">
                    <SECTION>
                        <SECTNO>§ 67.11 </SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>
                        2. The tables published under the authority of § 67.11 are amended as follows:
                        <PRTPAGE P="35112"/>
                    </AMDPAR>
                    <GPOTABLE COLS="4" OPTS="L2,tp0,i1" CDEF="s25,r50,15,r25">
                        <TTITLE> </TTITLE>
                        <BOXHD>
                            <CHED H="1">Flooding source(s)</CHED>
                            <CHED H="1">Location of referenced elevation</CHED>
                            <CHED H="1">
                                * Elevation in feet 
                                <LI>(NGVD)</LI>
                                <LI>+ Elevation in feet</LI>
                                <LI>(NAVD)</LI>
                                <LI># Depth in feet above ground</LI>
                                <LI>‸ Elevation </LI>
                                <LI>in meters (MSL)</LI>
                                <LI>Modified</LI>
                            </CHED>
                            <CHED H="1">Communities affected</CHED>
                        </BOXHD>
                        <ROW EXPSTB="03">
                            <ENT I="21">
                                <E T="02">Conway County, Arkansas, and Incorporated Areas</E>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="21">
                                <E T="02">Docket No.: FEMA-B-1087</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="01">Arkansas River</ENT>
                            <ENT>Approximately 1.0 mile downstream of State Highway 9</ENT>
                            <ENT>+295</ENT>
                            <ENT>Unincorporated Areas of Conway County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 1.0 mile upstream of Lock &amp; Dam No. 9</ENT>
                            <ENT>+303</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Caney Creek</ENT>
                            <ENT>Approximately 1,300 feet downstream of the confluence with Park Creek</ENT>
                            <ENT>+306</ENT>
                            <ENT>Unincorporated Areas of Conway County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 0.6 mile upstream of State Highway 9</ENT>
                            <ENT>+325</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Cherokee Creek</ENT>
                            <ENT>Just downstream of Union Pacific Railroad</ENT>
                            <ENT>+311</ENT>
                            <ENT>Unincorporated Areas of Conway County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Just downstream of Green Lane</ENT>
                            <ENT>+319</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Point Remove Creek</ENT>
                            <ENT>At the confluence with the Arkansas River</ENT>
                            <ENT>+299</ENT>
                            <ENT>Unincorporated Areas of Conway County.</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 2.0 miles upstream of Old Cherokee Road</ENT>
                            <ENT>+301</ENT>
                        </ROW>
                        <ROW EXPSTB="03">
                            <ENT I="22">* National Geodetic Vertical Datum.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">+ North American Vertical Datum.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"># Depth in feet above ground.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">‸ Mean Sea Level, rounded to the nearest 0.1 meter.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="21">
                                <E T="02">ADDRESSES</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="21">
                                <E T="02">Unincorporated Areas of Conway County</E>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="22">Maps are available for inspection at 117 South Moose Street, Morrilton, AR 72110.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="21">
                                <E T="02">Washington County, Florida, and Incorporated Areas</E>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="21">
                                <E T="02">Docket No.: FEMA-B-1097</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="01">Alligator Creek</ENT>
                            <ENT>At the upstream side of County Road 166</ENT>
                            <ENT>+76</ENT>
                            <ENT>Unincorporated Areas of Washington County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 3.2 miles upstream of County Road 166</ENT>
                            <ENT>+81</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Bear Bay Creek</ENT>
                            <ENT>At the confluence with Pine Log Creek</ENT>
                            <ENT>+44</ENT>
                            <ENT>Unincorporated Areas of Washington County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 3.9 miles upstream of the confluence with Pine Log Creek</ENT>
                            <ENT>+76</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Botheration Creek</ENT>
                            <ENT>At the confluence with Pine Log Creek</ENT>
                            <ENT>+32</ENT>
                            <ENT>Unincorporated Areas of Washington County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 200 feet downstream of the county boundary</ENT>
                            <ENT>+90</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Brock Mill Branch</ENT>
                            <ENT>At the confluence with Jones Rice Mill Branch</ENT>
                            <ENT>+54</ENT>
                            <ENT>Unincorporated Areas of Washington County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 100 feet downstream of State Road 77</ENT>
                            <ENT>+109</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Flat Creek</ENT>
                            <ENT>At the confluence with Hard Labor Creek</ENT>
                            <ENT>+50</ENT>
                            <ENT>Unincorporated Areas of Washington County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 9.7 miles upstream of the confluence with Hard Labor Creek</ENT>
                            <ENT>+160</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Hard Labor Creek</ENT>
                            <ENT>At State Road 277</ENT>
                            <ENT>+43</ENT>
                            <ENT>Unincorporated Areas of Washington County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 15.6 miles upstream of the confluence with Holmes Creek</ENT>
                            <ENT>+114</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Helms Branch</ENT>
                            <ENT>At the confluence with Alligator Creek</ENT>
                            <ENT>+78</ENT>
                            <ENT>City of Chipley, Unincorporated Areas of Washington County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 3.2 miles upstream of the confluence with Alligator Creek</ENT>
                            <ENT>+89</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Johnson Branch</ENT>
                            <ENT>At Roche Avenue</ENT>
                            <ENT>+37</ENT>
                            <ENT>City of Vernon, Unincorporated Areas of Washington County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 3.8 miles upstream of the confluence with Holmes Creek</ENT>
                            <ENT>+101</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Jones Rice Mill Branch</ENT>
                            <ENT>At the upstream side of State Road 277</ENT>
                            <ENT>+54</ENT>
                            <ENT>Unincorporated Areas of Washington County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 5.9 miles upstream of the confluence with Holmes Creek</ENT>
                            <ENT>+146</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Pine Log Creek</ENT>
                            <ENT>Approximately 1.9 miles upstream of the confluence with the East River</ENT>
                            <ENT>+21</ENT>
                            <ENT>Town of Ebro, Unincorporated Areas of Washington County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>At the confluence with Bear Bay Creek</ENT>
                            <ENT>+44</ENT>
                        </ROW>
                        <ROW>
                            <PRTPAGE P="35113"/>
                            <ENT I="01">Piney Branch</ENT>
                            <ENT>At State Road 77</ENT>
                            <ENT>+40</ENT>
                            <ENT>Unincorporated Areas of Washington County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 6.6 miles upstream of the confluence with Holmes Creek</ENT>
                            <ENT>+193</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Pippen Mill Creek</ENT>
                            <ENT>At Roche Avenue</ENT>
                            <ENT>+37</ENT>
                            <ENT>City of Vernon, Unincorporated Areas of Washington County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 5.4 miles upstream of the confluence with Holmes Creek</ENT>
                            <ENT>+95</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Reedy Creek</ENT>
                            <ENT>At the confluence with Hard Labor Creek</ENT>
                            <ENT>+59</ENT>
                            <ENT>Town of Wausau, Unincorporated Areas of Washington County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 3.8 miles upstream of the confluence with Hard Labor Creek</ENT>
                            <ENT>+105</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Unnamed Tributary 1 to Alligator Creek</ENT>
                            <ENT>Approximately 765 feet upstream of State Road 277</ENT>
                            <ENT>+68</ENT>
                            <ENT>Unincorporated Areas of Washington County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 1.4 miles upstream of State Road 277</ENT>
                            <ENT>+121</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Unnamed Tributary 2 to Alligator Creek</ENT>
                            <ENT>Approximately 0.4 mile upstream of the confluence with Alligator Creek</ENT>
                            <ENT>+72</ENT>
                            <ENT>City of Chipley, Unincorporated Areas of Washington County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 2.2 miles upstream of the confluence with Alligator Creek</ENT>
                            <ENT>+111</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Unnamed Tributary 3 to Alligator Creek</ENT>
                            <ENT>At the confluence with Alligator Creek</ENT>
                            <ENT>+76</ENT>
                            <ENT>City of Chipley, Unincorporated Areas of Washington County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 2 miles upstream of the confluence with Alligator Creek</ENT>
                            <ENT>+102</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Unnamed Tributary to Helms Branch</ENT>
                            <ENT>Approximately 300 feet downstream of Brickyard Road</ENT>
                            <ENT>+117</ENT>
                            <ENT>City of Chipley, Unincorporated Areas of Washington County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 0.6 mile upstream of Brickyard Road</ENT>
                            <ENT>+131</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Unnamed Tributary to Holmes Creek</ENT>
                            <ENT>Approximately 0.4 mile upstream of the confluence with Holmes Creek</ENT>
                            <ENT>+36</ENT>
                            <ENT>City of Vernon, Unincorporated Areas of Washington County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 2.2 miles upstream of the confluence with Holmes Creek</ENT>
                            <ENT>+52</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Unnamed Tributary to Holmes Creek East Branch</ENT>
                            <ENT>At the confluence with Unnamed Tributary to Holmes Creek</ENT>
                            <ENT>+42</ENT>
                            <ENT>City of Vernon, Unincorporated Areas of Washington County.</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 1.3 miles upstream of the confluence with Unnamed Tributary to Holmes Creek</ENT>
                            <ENT>+55</ENT>
                        </ROW>
                        <ROW EXPSTB="03">
                            <ENT I="22">* National Geodetic Vertical Datum.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">+ North American Vertical Datum.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"># Depth in feet above ground.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">‸ Mean Sea Level, rounded to the nearest 0.1 meter.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="21">
                                <E T="02">ADDRESSES</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">
                                <E T="02">City of Chipley</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">Maps are available for inspection at City Hall, 1442 Jackson Avenue, Chipley, FL 32428.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">
                                <E T="02">City of Vernon</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">Maps are available for inspection at 2808 Yellow Jacket Drive, Vernon, FL 32462.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">
                                <E T="02">Town of Ebro</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">Maps are available for inspection at the Town Hall, 6629 Dog Track Road, Ebro, FL 32437.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">
                                <E T="02">Town of Wausau</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">Maps are available for inspection at the Town Hall, 1607 2nd Avenue, Wausau, FL 32463.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="21">
                                <E T="02">Unincorporated Areas of Washington County</E>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="22">Maps are available for inspection at the Washington County Clerk's Office, 1293 Jackson Avenue, Chipley, FL 32428.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="21">
                                <E T="02">Delaware County, Indiana, and Incorporated Areas</E>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="21">
                                <E T="02"> Docket No.: FEMA-B-1064</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="01">Muncie Creek</ENT>
                            <ENT>Just downstream of McCulloch Boulevard</ENT>
                            <ENT>+939</ENT>
                            <ENT>City of Muncie, Unincorporated Areas of Delaware County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Just downstream of Norfolk Southern Railroad</ENT>
                            <ENT>+959</ENT>
                        </ROW>
                        <ROW>
                            <PRTPAGE P="35114"/>
                            <ENT I="01">West Fork White River</ENT>
                            <ENT>Approximately 2,200 feet downstream of I-69</ENT>
                            <ENT>+873</ENT>
                            <ENT>City of Muncie, Town of Daleville, Town of Yorktown, Unincorporated Areas of Delaware County.</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 17,780 feet upstream of County Road 700</ENT>
                            <ENT>+992</ENT>
                        </ROW>
                        <ROW EXPSTB="03">
                            <ENT I="22">* National Geodetic Vertical Datum.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">+ North American Vertical Datum.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"># Depth in feet above ground.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">‸ Mean Sea Level, rounded to the nearest 0.1 meter.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="21">
                                <E T="02">ADDRESSES</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">
                                <E T="02">City of Muncie</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">Maps are available for inspection at City Hall, 300 North High Street, Muncie, IN 47334.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">
                                <E T="02">Town of Daleville</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">Maps are available for inspection at the Town Hall, 8019 Walnut Street, Daleville, IN 47334.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">
                                <E T="02">Town of Yorktown</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">Maps are available for inspection at the Town Hall, 9800 West Smith Street, Yorktown, IN 47396.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="21">
                                <E T="02">Unincorporated Areas of Delaware County</E>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="22">Maps are available for inspection at the Delaware County Building, 100 West Main Street, Muncie, IN 47305.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="21">
                                <E T="02">Allen County, Kentucky, and Incorporated Areas</E>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="21">
                                <E T="02">Docket No.: FEMA-B-1078</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="01">Barren River Lake</ENT>
                            <ENT>Entire shoreline of Barren River Lake from just upstream of Barren River Dam to approximately 0.5 mile upstream of Brownsfield Road</ENT>
                            <ENT>+590</ENT>
                            <ENT>Unincorporated Areas of Allen County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Barren River Tributary 20 (backwater effects from Barren River Lake)</ENT>
                            <ENT>From the confluence with Barren River Lake to approximately 0.8 mile upstream of the confluence with Barren River Lake</ENT>
                            <ENT>+590</ENT>
                            <ENT>Unincorporated Areas of Allen County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Barren River Tributary 23 (backwater effects from Barren River Lake)</ENT>
                            <ENT>From the confluence with Barren River Lake to approximately 0.4 mile upstream of the confluence with Barren River Lake</ENT>
                            <ENT>+590</ENT>
                            <ENT>Unincorporated Areas of Allen County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Barren River Tributary 26 (backwater effects from Barren River Lake)</ENT>
                            <ENT>From the confluence with Barren River Lake to approximately 1,900 feet upstream of the confluence with Barren River Lake</ENT>
                            <ENT>+590</ENT>
                            <ENT>Unincorporated Areas of Allen County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Barren River Tributary 28 (backwater effects from Barren River Lake)</ENT>
                            <ENT>From the confluence with Barren River Lake to approximately 0.4 mile upstream of the confluence with Barren River Lake</ENT>
                            <ENT>+590</ENT>
                            <ENT>Unincorporated Areas of Allen County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Barren River Tributary 29 (backwater effects from Barren River Lake)</ENT>
                            <ENT>From the confluence with Barren River Lake to approximately 0.4 mile upstream of the confluence with Barren River Lake</ENT>
                            <ENT>+590</ENT>
                            <ENT>Unincorporated Areas of Allen County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Bear Creek (backwater effects from Barren River Lake)</ENT>
                            <ENT>From the confluence with Rhoden Creek Lake to approximately 0.7 mile upstream of the confluence with Rhoden Creek</ENT>
                            <ENT>+590</ENT>
                            <ENT>Unincorporated Areas of Allen County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Hurricane Creek (backwater effects from Barren River Lake)</ENT>
                            <ENT>From the confluence with Barren River Lake to approximately 0.7 mile upstream of the confluence with Barren River Lake</ENT>
                            <ENT>+590</ENT>
                            <ENT>Unincorporated Areas of Allen County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Hurricane Creek Tributary 3 (backwater effects from Barren River Lake)</ENT>
                            <ENT>From the confluence with Hurricane Creek to approximately 1,000 feet upstream of the confluence with Hurricane Creek</ENT>
                            <ENT>+590</ENT>
                            <ENT>Unincorporated Areas of Allen County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>From the confluence with Barren River Lake to approximately 1,900 feet upstream of the confluence with Barren River Lake</ENT>
                            <ENT>+590</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Hurricane Creek Tributary 4 (backwater effects from Barren River Lake)</ENT>
                            <ENT>From the confluence with Barren River Lake to approximately 0.4 mile upstream of the confluence with Barren River Lake</ENT>
                            <ENT>+590</ENT>
                            <ENT>Unincorporated Areas of Allen County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Manley Branch (backwater effects from Barren River Lake)</ENT>
                            <ENT>From the confluence with Barren River Lake to approximately 1 mile upstream of the confluence with Barren River Lake</ENT>
                            <ENT>+590</ENT>
                            <ENT>Unincorporated Areas of Allen County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Manley Branch Tributary 3 (backwater effects from Barren River Lake)</ENT>
                            <ENT>From the confluence with Barren River Lake to approximately 0.8 mile upstream of the confluence with Barren River Lake</ENT>
                            <ENT>+590</ENT>
                            <ENT>Unincorporated Areas of Allen County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Rhoden Creek (backwater effects from Barren River Lake)</ENT>
                            <ENT>From the confluence with Barren River Lake to approximately 1.4 miles upstream of the confluence with Barren River Lake</ENT>
                            <ENT>+590</ENT>
                            <ENT>Unincorporated Areas of Allen County.</ENT>
                        </ROW>
                        <ROW>
                            <PRTPAGE P="35115"/>
                            <ENT I="01">Trace Creek (backwater effects from Barren River Lake)</ENT>
                            <ENT>From the confluence with Barren River Lake to approximately 1 mile upstream of the confluence with Barren River Lake</ENT>
                            <ENT>+590</ENT>
                            <ENT>Unincorporated Areas of Allen County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Walnut Creek (backwater effects from Barren River Lake)</ENT>
                            <ENT>From the confluence with Barren River Lake to approximately 1.1 miles upstream of the confluence with Barren River Lake</ENT>
                            <ENT>+590</ENT>
                            <ENT>Unincorporated Areas of Allen County.</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="01">Walnut Creek Tributary 7 (backwater effects from Barren River Lake)</ENT>
                            <ENT>From the confluence with Walnut Creek Lake to approximately 1.1 miles upstream of the confluence with Walnut Creek</ENT>
                            <ENT>+590</ENT>
                            <ENT>Unincorporated Areas of Allen County.</ENT>
                        </ROW>
                        <ROW EXPSTB="03">
                            <ENT I="22">* National Geodetic Vertical Datum.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">+ North American Vertical Datum.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"># Depth in feet above ground.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">‸ Mean Sea Level, rounded to the nearest 0.1 meter.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="21">
                                <E T="02">ADDRESSES</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="21">
                                <E T="02">Unincorporated Areas of Allen County</E>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="22">Maps are available for inspection at 201 West Main Street, Scottsville, KY 42164.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="21">
                                <E T="02">Boyle County, Kentucky, and Incorporated Areas</E>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="21">
                                <E T="02">Docket No.: FEMA-B-1117</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="01">Balls Branch (backwater effects from Clarks Run)</ENT>
                            <ENT>From the confluence with Clarks Run to approximately 0.7 mile upstream of the confluence with Clarks Run</ENT>
                            <ENT>+875</ENT>
                            <ENT>Unincorporated Areas of Boyle County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Clarks Run</ENT>
                            <ENT>Approximately 1.2 miles upstream of Goggin Road</ENT>
                            <ENT>+849</ENT>
                            <ENT>City of Danville, Unincorporated Areas of Boyle County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 0.6 mile downstream of Alum Springs Cross Pike</ENT>
                            <ENT>+965</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Dix River Tributary 2 (backwater effects from Herrington Lake)</ENT>
                            <ENT>From the confluence with Herrington Lake to approximately 1,158 feet upstream of the confluence with Herrington Lake</ENT>
                            <ENT>+760</ENT>
                            <ENT>Unincorporated Areas of Boyle County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Herrington Lake</ENT>
                            <ENT>Entire shoreline</ENT>
                            <ENT>+760</ENT>
                            <ENT>Unincorporated Areas of Boyle County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Spears Creek</ENT>
                            <ENT>Approximately 0.6 mile upstream of the confluence with Herrington Lake</ENT>
                            <ENT>+788</ENT>
                            <ENT>City of Danville, Unincorporated Areas of Boyle County.</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 780 feet upstream of the North Danville Bypass</ENT>
                            <ENT>+919</ENT>
                        </ROW>
                        <ROW EXPSTB="03">
                            <ENT I="22">* National Geodetic Vertical Datum.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">+ North American Vertical Datum.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"># Depth in feet above ground.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">‸ Mean Sea Level, rounded to the nearest 0.1 meter.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="21">
                                <E T="02">ADDRESSES</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">
                                <E T="02">City of Danville</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">Maps are available for inspection at City Hall, 455 West Main Street, Danville, KY 40422.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="21">
                                <E T="02">Unincorporated Areas of Boyle County</E>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="22">Maps are available for inspection at the Boyle County Courthouse, 321 West Main Street, Danville, KY 40422.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="21">
                                <E T="02">St. James Parish, Louisiana, and Incorporated Areas</E>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="21">
                                <E T="02">Docket No.: FEMA-B-1091</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="01">Mississippi River</ENT>
                            <ENT>Approximately 0.9 mile downstream of State Highway 3213</ENT>
                            <ENT>+27</ENT>
                            <ENT>Town of Gramercy, Town of Lutcher, Unincorporated Areas of St. James Parish.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 1.2 miles upstream of State Highway 3213</ENT>
                            <ENT>+28</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Storage Areas from the Gulf (D2G model)</ENT>
                            <ENT>Approximately 1,079 feet south of State Highway 643</ENT>
                            <ENT>+1</ENT>
                            <ENT>Unincorporated Areas of St. James Parish.</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 60 feet south of the intersection of Sidney Road and Missouri Pacific Railroad, along the east side of the rail line</ENT>
                            <ENT>+14</ENT>
                        </ROW>
                        <ROW EXPSTB="03">
                            <ENT I="22">* National Geodetic Vertical Datum.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">+ North American Vertical Datum.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"># Depth in feet above ground.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">‸ Mean Sea Level, rounded to the nearest 0.1 meter.</ENT>
                        </ROW>
                        <ROW>
                            <PRTPAGE P="35116"/>
                            <ENT I="21">
                                <E T="02">ADDRESSES</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">
                                <E T="02">Town of Gramercy</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">Maps are available for inspection at 120 North Montz Avenue, Gramercy, LA 70052.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">
                                <E T="02">Town of Lutcher</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">Maps are available for inspection at 2500 Louisiana Avenue, Lutcher, LA 70071.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="21">
                                <E T="02">Unincorporated Areas of St. James Parish</E>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="22">Maps are available for inspection at 5800 Highway 44, Convent, LA 70723.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="21">
                                <E T="02">Worcester County, Massachusetts (All Jurisdictions)</E>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="21">
                                <E T="02">Docket Nos.: FEMA-B-1053 and FEMA-B-1139</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="01">Big Bummet River</ENT>
                            <ENT>Just downstream of State Highway 140</ENT>
                            <ENT>+385</ENT>
                            <ENT>Town of Shrewsbury.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>At the Town of Grafton corporate limits</ENT>
                            <ENT>+385</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Blackstone River</ENT>
                            <ENT>Approximately 1,750 feet downstream of Saint Paul Street</ENT>
                            <ENT>+159</ENT>
                            <ENT>City of Worcester, Town of Blackstone, Town of Grafton, Town of Millbury, Town of Millville, Town of Northbridge, Town of Sutton, Town of Uxbridge.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 250 feet downstream of Millbury Street</ENT>
                            <ENT>+444</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Cold Spring Brook</ENT>
                            <ENT>At the confluence with the Blackstone River</ENT>
                            <ENT>+323</ENT>
                            <ENT>Town of Sutton.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 150 feet downstream of State Highway 122A</ENT>
                            <ENT>+325</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Cronin Brook</ENT>
                            <ENT>At the confluence with the Blackstone River</ENT>
                            <ENT>+298</ENT>
                            <ENT>Town of Grafton.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 1,100 feet downstream of Follette Street</ENT>
                            <ENT>+302</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Goodridge Brook</ENT>
                            <ENT>Approximately 150 feet upstream of State Highway 70</ENT>
                            <ENT>+258</ENT>
                            <ENT>Town of Clinton.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 250 feet downstream of Parker Road</ENT>
                            <ENT>+258</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Leesville Pond</ENT>
                            <ENT>Entire shoreline</ENT>
                            <ENT>+486</ENT>
                            <ENT>City of Worcester.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Middle River</ENT>
                            <ENT>Approximately 250 feet downstream of Millbury Street</ENT>
                            <ENT>+444</ENT>
                            <ENT>City of Worcester.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 100 feet downstream of McKeon Road</ENT>
                            <ENT>+452</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Mill River</ENT>
                            <ENT>Approximately 3,900 feet downstream of Colonial Drive</ENT>
                            <ENT>+196</ENT>
                            <ENT>Town of Blackstone.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 1,300 feet downstream of Colonial Drive</ENT>
                            <ENT>+198</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Mumford River</ENT>
                            <ENT>At the confluence with the Blackstone River</ENT>
                            <ENT>+225</ENT>
                            <ENT>Town of Uxbridge.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 300 feet downstream of Mendon Street</ENT>
                            <ENT>+226</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Quinsigamond River</ENT>
                            <ENT>At the confluence with the Blackstone River</ENT>
                            <ENT>+293</ENT>
                            <ENT>Town of Grafton.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>At Pleasant Street</ENT>
                            <ENT>+293</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Ramshorn Pond</ENT>
                            <ENT>Entire shoreline</ENT>
                            <ENT>+632</ENT>
                            <ENT>Town of Sutton.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Riverdale Milles Sluice Gates and Tail Race</ENT>
                            <ENT>Approximately 600 feet upstream of the confluence with the Blackstone River</ENT>
                            <ENT>+256</ENT>
                            <ENT>Town of Northbridge.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 100 feet upstream of Riverdale Street</ENT>
                            <ENT>+259</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Singletary Brook</ENT>
                            <ENT>At the confluence with the Blackstone River</ENT>
                            <ENT>+393</ENT>
                            <ENT>Town of Millbury.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 300 feet downstream of Rhodes Street</ENT>
                            <ENT>+394</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Singletary Pond</ENT>
                            <ENT>Entire shoreline</ENT>
                            <ENT>+559</ENT>
                            <ENT>Town of Sutton.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Sudbury River</ENT>
                            <ENT>Approximately 1,200 feet downstream of Fruit Street</ENT>
                            <ENT>+264</ENT>
                            <ENT>Town of Westborough.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 3,000 feet upstream of Fruit Street</ENT>
                            <ENT>+276</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Summet Brook (backwater effects from Big Bummet Brook)</ENT>
                            <ENT>Approximately 2,800 feet upstream of the confluence with Big Bummet Brook, at the corporate limits</ENT>
                            <ENT>+363</ENT>
                            <ENT>Town of Shrewsbury.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 0.6 mile upstream of the confluence with Big Bummet Brook</ENT>
                            <ENT>+363</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Unnamed Tributary (backwater effects from Cronin Brook)</ENT>
                            <ENT>Approximately 1,100 feet upstream of the confluence with Cronin Brook, at the corporate limits</ENT>
                            <ENT>+331</ENT>
                            <ENT>Town of Millbury.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 2,200 feet upstream of the confluence with Cronin Brook</ENT>
                            <ENT>+331</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">West River</ENT>
                            <ENT>At the confluence with the Blackstone River</ENT>
                            <ENT>+224</ENT>
                            <ENT>Town of Uxbridge.</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 200 feet upstream of Henry Street</ENT>
                            <ENT>+225</ENT>
                        </ROW>
                        <ROW EXPSTB="03">
                            <ENT I="22">* National Geodetic Vertical Datum.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">+ North American Vertical Datum.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"># Depth in feet above ground.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">‸ Mean Sea Level, rounded to the nearest 0.1 meter.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="21">
                                <E T="02">ADDRESSES</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">
                                <E T="02">City of Worcester</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">Maps are available for inspection at City Hall, 455 Main Street, Worcester, MA 01608.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">
                                <E T="02">Town of Blackstone</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">Maps are available for inspection at the Town Hall, 15 Saint Paul Street, Blackstone, MA 01504.</ENT>
                        </ROW>
                        <ROW>
                            <PRTPAGE P="35117"/>
                            <ENT I="22">
                                <E T="02">Town of Clinton</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">Maps are available for inspection at the Town Hall, 242 Church Street, Clinton, MA 01510.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">
                                <E T="02">Town of Grafton</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">Maps are available for inspection at the Town Hall, 30 Providence Road, Grafton, MA 01519.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">
                                <E T="02">Town of Millbury</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">Maps are available for inspection at the Town Hall, 127 Elm Street, Millbury, MA 01527.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">
                                <E T="02">Town of Millville</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">Maps are available for inspection at the Town Hall, 8 Central Street, Millville, MA 01529.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">
                                <E T="02">Town of Northbridge</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">Maps are available for inspection at the Northbridge Town Hall, 7 Main Street, Whitinsville, MA 01588.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">
                                <E T="02">Town of Shrewsbury</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">Maps are available for inspection at the Town Hall, 100 Maple Avenue, Shrewsbury, MA 01545.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">
                                <E T="02">Town of Sutton</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">Maps are available for inspection at the Town Hall, 4 Uxbridge Road, Sutton, MA 01590.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">
                                <E T="02">Town of Uxbridge</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">Maps are available for inspection at the Town Hall, 21 South Main Street, Uxbridge, MA 01569.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">
                                <E T="02">Town of Westborough</E>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="22">Maps are available for inspection at the Town Hall, 34 West Main Street, Westborough, MA 01581.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="21">
                                <E T="02">Marshall County, Mississippi, and Incorporated Areas</E>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="21">
                                <E T="02">Docket No.: FEMA-B-1098</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="01">Byhalia Creek</ENT>
                            <ENT>Approximately 200 feet downstream of U.S. Route 178</ENT>
                            <ENT>+332</ENT>
                            <ENT>Town of Byhalia.</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 900 feet upstream of the railroad</ENT>
                            <ENT>+334</ENT>
                        </ROW>
                        <ROW EXPSTB="03">
                            <ENT I="22">* National Geodetic Vertical Datum.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">+ North American Vertical Datum.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"># Depth in feet above ground.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">‸ Mean Sea Level, rounded to the nearest 0.1 meter.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="21">
                                <E T="02">ADDRESSES</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">
                                <E T="02">Town of Byhalia</E>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="22">Maps are available for inspection at 161 Highway 309 South, Byhalia, MS 38611.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="21">
                                <E T="02">Howell County, Missouri, and Incorporated Areas</E>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="21">
                                <E T="02">Docket No.: FEMA-B-1105</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="01">Burton Branch</ENT>
                            <ENT>Approximately 2,200 feet upstream of Davis Lane</ENT>
                            <ENT>+1022</ENT>
                            <ENT>City of West Plains, Unincorporated Areas of Howell County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 3,700 feet upstream of Davis Lane</ENT>
                            <ENT>+1031</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Drainage Ditch Number 1</ENT>
                            <ENT>Approximately 315 feet upstream of the City of Willow Springs corporate limits</ENT>
                            <ENT>+1255</ENT>
                            <ENT>Unincorporated Areas of Howell County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 3,400 feet upstream of the City of Willow Springs corporate limits</ENT>
                            <ENT>+1279</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Drainage Ditch Number 4</ENT>
                            <ENT>Approximately 1,300 feet upstream of U.S. Route 60/63</ENT>
                            <ENT>+1197</ENT>
                            <ENT>City of Willow Springs, Unincorporated Areas of Howell County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 525 feet upstream of County Road 3280</ENT>
                            <ENT>+1225</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Eleven Point River</ENT>
                            <ENT>Approximately 1,500 feet downstream of the City of Willow Springs corporate limits</ENT>
                            <ENT>+1183</ENT>
                            <ENT>City of Willow Springs, Unincorporated Areas of Howell County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 425 feet upstream of the City of Willow Springs corporate limits</ENT>
                            <ENT>+1289</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Jam Up Creek</ENT>
                            <ENT>At County Road 3160</ENT>
                            <ENT>+1098</ENT>
                            <ENT>Unincorporated Areas of Howell County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 100 feet upstream of County Road 3890</ENT>
                            <ENT>+1099</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Mustion Creek</ENT>
                            <ENT>Approximately 330 feet downstream of the City of West Plains corporate limits</ENT>
                            <ENT>+997</ENT>
                            <ENT>Unincorporated Areas of Howell County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 160 feet downstream of the City of West Plains corporate limits</ENT>
                            <ENT>+998</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">South Fork Howell Creek</ENT>
                            <ENT>Just upstream of Katherine Street</ENT>
                            <ENT>+1025</ENT>
                            <ENT>Unincorporated Areas of Howell County.</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 400 feet upstream of Katherine Street</ENT>
                            <ENT>+1027</ENT>
                        </ROW>
                        <ROW EXPSTB="03">
                            <ENT I="22">* National Geodetic Vertical Datum.</ENT>
                        </ROW>
                        <ROW>
                            <PRTPAGE P="35118"/>
                            <ENT I="22">+ North American Vertical Datum.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"># Depth in feet above ground.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">‸ Mean Sea Level, rounded to the nearest 0.1 meter.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="21">
                                <E T="02">ADDRESSES</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">
                                <E T="02">City of West Plains</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">Maps are available for inspection at 1910 Holiday Lane, West Plains, MO 65775.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">
                                <E T="02">City of Willow Springs</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">Maps are available for inspection at 900 West Main Street, Willow Springs, MO 65793.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="21">
                                <E T="02">Unincorporated Areas of Howell County</E>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="22">Maps are available for inspection at 101 Courthouse, West Plains, MO 65775.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="21">
                                <E T="02">Johnson County, Missouri, and Incorporated Areas</E>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="21">
                                <E T="02">Docket No.: FEMA-B-1105</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="01">Clear Fork</ENT>
                            <ENT>Approximately 550 feet downstream of County Road 751</ENT>
                            <ENT>+701</ENT>
                            <ENT>City of Knob Noster, Unincorporated Areas of Johnson County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 1,750 feet upstream of U.S. Route 50</ENT>
                            <ENT>+724</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Hughes Branch</ENT>
                            <ENT>Approximately 550 feet downstream of County Road 75</ENT>
                            <ENT>+737</ENT>
                            <ENT>Unincorporated Areas of Johnson County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 100 feet upstream of State Highway 132</ENT>
                            <ENT>+745</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 200 feet upstream of State Street</ENT>
                            <ENT>+769</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 2,000 feet upstream of State Street</ENT>
                            <ENT>+778</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Tributary 2</ENT>
                            <ENT>Approximately 50 feet downstream of State Highway 132</ENT>
                            <ENT>+749</ENT>
                            <ENT>Unincorporated Areas of Johnson County.</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 300 feet upstream of State Highway 132</ENT>
                            <ENT>+750</ENT>
                        </ROW>
                        <ROW EXPSTB="03">
                            <ENT I="22">* National Geodetic Vertical Datum.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">+ North American Vertical Datum.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"># Depth in feet above ground.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">‸ Mean Sea Level, rounded to the nearest 0.1 meter.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="21">
                                <E T="02">ADDRESSES</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">
                                <E T="02">City of Knob Noster</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">Maps are available for inspection at 218 North State Street, Knob Noster, MO 65336.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="21">
                                <E T="02">Unincorporated Areas of Johnson County</E>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="22">Maps are available for inspection at 122 Hout Street, Warrensburg, MO 64093.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="21">
                                <E T="02">Ste. Genevieve County, Missouri, and Incorporated Areas</E>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="21">
                                <E T="02">Docket No.: FEMA-B-1126</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="01">Mississippi River</ENT>
                            <ENT>At the easternmost portion of the county near the confluence with the Kaskaskia River</ENT>
                            <ENT>+392</ENT>
                            <ENT>City of Ste. Genevieve, Unincorporated Areas of Ste. Genevieve County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 2 miles upstream of the confluence with Isle du Bois Creek</ENT>
                            <ENT>+404</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Old Mississippi River Channel</ENT>
                            <ENT>Approximately 0.66 mile downstream of the confluence with Walnut Creek</ENT>
                            <ENT>+391</ENT>
                            <ENT>City of St. Mary, Unincorporated Areas of Ste. Genevieve County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 2.75 miles upstream of the confluence with Walnut Creek</ENT>
                            <ENT>+392</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">St. Laurent Branch</ENT>
                            <ENT>At the confluence with St. Laurent Creek</ENT>
                            <ENT>+391</ENT>
                            <ENT>City of St. Mary, Unincorporated Areas of Ste. Genevieve County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Just upstream of Mulberry Street</ENT>
                            <ENT>+391</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">St. Laurent Creek</ENT>
                            <ENT>At the confluence with the Old Mississippi River Channel</ENT>
                            <ENT>+391</ENT>
                            <ENT>City of St. Mary, Unincorporated Areas of Ste. Genevieve County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>At the confluence with St. Laurent Branch</ENT>
                            <ENT>+391</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Walnut Creek</ENT>
                            <ENT>At the confluence with the Old Mississippi River Channel</ENT>
                            <ENT>+392</ENT>
                            <ENT>City of St. Mary.</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 1,940 feet upstream of the Old Mississippi River Channel</ENT>
                            <ENT>+392</ENT>
                        </ROW>
                        <ROW EXPSTB="03">
                            <ENT I="22">* National Geodetic Vertical Datum.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">+ North American Vertical Datum.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"># Depth in feet above ground.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">‸ Mean Sea Level, rounded to the nearest 0.1 meter.</ENT>
                        </ROW>
                        <ROW>
                            <PRTPAGE P="35119"/>
                            <ENT I="21">
                                <E T="02">ADDRESSES</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">
                                <E T="02">City of Ste. Genevieve</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">Maps are available for inspection at 165 South 4th Street, Ste. Genevieve, MO 63670.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">
                                <E T="02">City of St. Mary</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">Maps are available for inspection at 782 3rd Street, St. Mary, MO 63673.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="21">
                                <E T="02">Unincorporated Areas of Ste. Genevieve County</E>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="22">Maps are available for inspection at 165 South 4th Street, Ste. Genevieve, MO 63670.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="21">
                                <E T="02">Cameron County, Pennsylvania (All Jurisdictions)</E>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="21">
                                <E T="02">Docket No.: FEMA-B-1126</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="01">Bennett Branch Sinnemahoning Creek</ENT>
                            <ENT>Approximately 0.60 mile downstream of Sterling Run Road</ENT>
                            <ENT>+809</ENT>
                            <ENT>Township of Gibson.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 0.55 mile downstream of Sterling Run Road</ENT>
                            <ENT>+814</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Driftwood Branch Sinnemahoning Creek</ENT>
                            <ENT>Approximately 1,835 feet downstream of Castle Garden Road</ENT>
                            <ENT>+905</ENT>
                            <ENT>Township of Gibson.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 980 feet downstream of Castle Garden Road</ENT>
                            <ENT>+905</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Driftwood Branch Sinnemahoning Creek</ENT>
                            <ENT>Approximately 1.28 miles downstream of the confluence with Sinnemahoning Portage Creek</ENT>
                            <ENT>+1000</ENT>
                            <ENT>Township of Portage.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 1.18 miles downstream of the confluence with Sinnemahoning Portage Creek</ENT>
                            <ENT>+1001</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Sinnemahoning Creek</ENT>
                            <ENT>Approximately 980 feet downstream of Castle Garden Road</ENT>
                            <ENT>+809</ENT>
                            <ENT>Township of Gibson.</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 90 feet upstream of the confluence with Boyer Run</ENT>
                            <ENT>+809</ENT>
                        </ROW>
                        <ROW EXPSTB="03">
                            <ENT I="22">* National Geodetic Vertical Datum.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">+ North American Vertical Datum.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"># Depth in feet above ground.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">‸ Mean Sea Level, rounded to the nearest 0.1 meter.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="21">
                                <E T="02">ADDRESSES</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">
                                <E T="02">Township of Gibson</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">Maps are available for inspection at the Gibson Township Municipal Building, 7657 Bridge Street, Driftwood, PA 15834.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">
                                <E T="02">Township of Portage</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">Maps are available for inspection at the Portage Township Municipal Building, 523 Sizer Run, Emporium, PA 15832.</ENT>
                        </ROW>
                    </GPOTABLE>
                </REGTEXT>
                <EXTRACT>
                    <FP>(Catalog of Federal Domestic Assistance No. 97.022, “Flood Insurance.”)</FP>
                </EXTRACT>
                <SIG>
                    <DATED>Dated: June 9, 2011.</DATED>
                    <NAME>Sandra K. Knight,</NAME>
                    <TITLE>Deputy Federal Insurance and Mitigation Administrator, Mitigation, Department of Homeland Security, Federal Emergency Management Agency.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-14896 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 9110-12-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
                <SUBAGY>Federal Emergency Management Agency</SUBAGY>
                <CFR>44 CFR Part 67</CFR>
                <DEPDOC>[Docket ID FEMA-2011-0002]</DEPDOC>
                <SUBJECT>Final 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>Base (1% annual-chance) Flood Elevations (BFEs) and modified BFEs are made final for the communities listed below. The BFEs and modified BFEs are the basis for the floodplain management measures that each community is required either to adopt or to show evidence of being already in effect in order to qualify or remain qualified for participation in the National Flood Insurance Program (NFIP).</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The date of issuance of the Flood Insurance Rate Map (FIRM) showing BFEs and modified BFEs for each community. This date may be obtained by contacting the office where the maps are available for inspection as indicated in the table below.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>The final 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>
                        Luis Rodriguez, Chief, Engineering Management Branch, Federal Insurance and Mitigation Administration, Federal Emergency Management Agency, 500 C Street, SW., Washington, DC 20472, 
                        <PRTPAGE P="35120"/>
                        (202) 646-4064, or (e-mail) 
                        <E T="03">luis.rodriguez1@dhs.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The Federal Emergency Management Agency (FEMA) makes the final determinations listed below for the modified BFEs for each community listed. These modified elevations have been published in newspapers of local circulation and ninety (90) days have elapsed since that publication. The Deputy Federal Insurance and Mitigation Administrator has resolved any appeals resulting from this notification.</P>
                <P>This final rule is issued in accordance with section 110 of the Flood Disaster Protection Act of 1973, 42 U.S.C. 4104, and 44 CFR part 67. FEMA has developed criteria for floodplain management in floodprone areas in accordance with 44 CFR part 60.</P>
                <P>Interested lessees and owners of real property are encouraged to review the proof Flood Insurance Study and FIRM available at the address cited below for each community. The BFEs and modified BFEs are made final in the communities listed below. Elevations at selected locations in each community are shown.</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.
                </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 67</HD>
                    <P>Administrative practice and procedure, Flood insurance, Reporting and recordkeeping requirements.</P>
                </LSTSUB>
                <REGTEXT TITLE="44" PART="67">
                    <P>Accordingly, 44 CFR part 67 is amended as follows:</P>
                    <PART>
                        <HD SOURCE="HED">PART 67—[AMENDED]</HD>
                    </PART>
                    <AMDPAR>1. The authority citation for part 67 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="67">
                    <SECTION>
                        <SECTNO>§ 67.11 </SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>2. The tables published under the authority of § 67.11 are amended as follows:</AMDPAR>
                    <GPOTABLE COLS="5" OPTS="L2,tp0,i1" CDEF="s25,r25,xs96,xs150,15">
                        <TTITLE> </TTITLE>
                        <BOXHD>
                            <CHED H="1">State</CHED>
                            <CHED H="1">City/town/county</CHED>
                            <CHED H="1">Source of flooding</CHED>
                            <CHED H="1">Location</CHED>
                            <CHED H="1">
                                * Elevation in feet 
                                <LI>(NGVD) </LI>
                                <LI>+ Elevation in feet </LI>
                                <LI>(NAVD) </LI>
                                <LI># Depth in feet above ground </LI>
                                <LI>‸ Elevation</LI>
                                <LI>in meters </LI>
                                <LI>(MSL)</LI>
                                <LI>Modified</LI>
                            </CHED>
                        </BOXHD>
                        <ROW EXPSTB="04">
                            <ENT I="21">
                                <E T="02">City of Alexandria, Virginia</E>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="21">
                                <E T="02">Docket No.: FEMA-B-1089</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="01">Virginia</ENT>
                            <ENT>City of Alexandria</ENT>
                            <ENT>Backlick Run</ENT>
                            <ENT>Approximately 0.4 mile downstream of South Van Dorn Street</ENT>
                            <ENT>+80</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT>Approximately 600 feet upstream of South Van Dorn Street</ENT>
                            <ENT>+95</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Virginia</ENT>
                            <ENT>City of Alexandria</ENT>
                            <ENT>Cameron Run</ENT>
                            <ENT>Just upstream of the confluence with Hooffs Run</ENT>
                            <ENT>+12</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT>Approximately 1,750 feet upstream of I-495 (Capital Beltway)</ENT>
                            <ENT>+25</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Virginia</ENT>
                            <ENT>City of Alexandria</ENT>
                            <ENT>Holmes Run</ENT>
                            <ENT>Approximately 450 feet downstream of I-395</ENT>
                            <ENT>+81</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT>Just downstream of I-395</ENT>
                            <ENT>+90</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Virginia</ENT>
                            <ENT>City of Alexandria</ENT>
                            <ENT>Hooffs Run</ENT>
                            <ENT>At the confluence with Cameron Run</ENT>
                            <ENT>+12</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT>Approximately 260 feet upstream of East Linden Street</ENT>
                            <ENT>+18</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Virginia</ENT>
                            <ENT>City of Alexandria</ENT>
                            <ENT>Old Cameron Run Channel</ENT>
                            <ENT>At the confluence with Hooffs Run</ENT>
                            <ENT>+12</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT>Approximately 270 feet upstream of Mill Road/Andrews Lane</ENT>
                            <ENT>+13</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Virginia</ENT>
                            <ENT>City of Alexandria</ENT>
                            <ENT>Strawberry Run</ENT>
                            <ENT>Just upstream of Eisenhower Avenue</ENT>
                            <ENT>+35</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT>Approximately 650 feet upstream of Fort Williams Parkway</ENT>
                            <ENT>+138</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Virginia</ENT>
                            <ENT>City of Alexandria</ENT>
                            <ENT>Taylor Run</ENT>
                            <ENT>Approximately 300 feet downstream of Mill Road</ENT>
                            <ENT>+25</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT>Approximately 0.7 mile upstream of Janneys Lane</ENT>
                            <ENT>+148</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Virginia</ENT>
                            <ENT>City of Alexandria</ENT>
                            <ENT>Timber Branch</ENT>
                            <ENT>Just upstream of Timber Branch Parkway</ENT>
                            <ENT>+70</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT>Approximately 350 feet upstream of West Braddock Road</ENT>
                            <ENT>+134</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Virginia</ENT>
                            <ENT>City of Alexandria</ENT>
                            <ENT>Tributary 1 to Cameron Run</ENT>
                            <ENT>Approximately 200 feet upstream of the confluence with Cameron Run</ENT>
                            <ENT>+46</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT>Approximately 0.5 mile upstream of the confluence with Cameron Run</ENT>
                            <ENT>+66</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Virginia</ENT>
                            <ENT>City of Alexandria</ENT>
                            <ENT>Tributary 1 to Taylor Run</ENT>
                            <ENT>At the confluence with Taylor Run</ENT>
                            <ENT>+25</ENT>
                        </ROW>
                        <ROW>
                            <PRTPAGE P="35121"/>
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT>Approximately 1,000 feet upstream of the confluence with Taylor Run</ENT>
                            <ENT>+29</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Virginia</ENT>
                            <ENT>City of Alexandria</ENT>
                            <ENT>Tributary 2 to Taylor Run</ENT>
                            <ENT>At the confluence with Taylor Run</ENT>
                            <ENT>+82</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT>Just downstream of Key Drive</ENT>
                            <ENT>+164</ENT>
                        </ROW>
                        <ROW EXPSTB="04">
                            <ENT I="22">* National Geodetic Vertical Datum.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">+ North American Vertical Datum.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"># Depth in feet above ground.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">‸ Mean Sea Level, rounded to the nearest 0.1 meter.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="21">
                                <E T="02">ADDRESSES</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">
                                <E T="02">City of Alexandria</E>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="22">Maps are available for inspection at 301 King Street, Alexandria, VA 22314.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="21">
                                <E T="02">Town of Ennis, Montana</E>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="21">
                                <E T="02">Docket No.: FEMA-B-1083</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="01">Montana</ENT>
                            <ENT>Town of Ennis</ENT>
                            <ENT>Moores Creek</ENT>
                            <ENT>Approximately 5,450 feet downstream of 1st Street</ENT>
                            <ENT>+4915</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="22"> </ENT>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT>Approximately 650 feet upstream of Moores Creek Road</ENT>
                            <ENT>+5030</ENT>
                        </ROW>
                        <ROW EXPSTB="04">
                            <ENT I="22">* National Geodetic Vertical Datum.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">+ North American Vertical Datum.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"># Depth in feet above ground.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">‸ Mean Sea Level, rounded to the nearest 0.1 meter.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="21">
                                <E T="02">ADDRESSES</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">
                                <E T="02">Town of Ennis</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">Maps are available for inspection at 328 West Main Street, Ennis, MT 59729.</ENT>
                        </ROW>
                    </GPOTABLE>
                    <GPOTABLE COLS="4" OPTS="L2,tp0,i1" CDEF="s50,r100,15,r50">
                        <TTITLE> </TTITLE>
                        <BOXHD>
                            <CHED H="1">Flooding source(s)</CHED>
                            <CHED H="1">Location of referenced elevation</CHED>
                            <CHED H="1">
                                * Elevation in feet 
                                <LI>(NGVD) </LI>
                                <LI>+ Elevation in feet</LI>
                                <LI>(NAVD)</LI>
                                <LI># Depth in feet above ground</LI>
                                <LI>‸ Elevation in meters (MSL)</LI>
                                <LI>Modified</LI>
                            </CHED>
                            <CHED H="1">
                                Communities
                                <LI>affected</LI>
                            </CHED>
                        </BOXHD>
                        <ROW EXPSTB="03">
                            <ENT I="21">
                                <E T="02">Pima County, Arizona, and Incorporated Areas</E>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="21">
                                <E T="02">Docket No.: FEMA-B-1069</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="01">Ponding Areas (AH Zones)</ENT>
                            <ENT>Extensive ponding areas north of I-10 Frontage Road (northern wash lowest elevation) (FIRM panels affected: 0420 and 1010)</ENT>
                            <ENT>+1947</ENT>
                            <ENT>Town of Marana, Unincorporated Areas of Pima County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Extensive ponding areas north of I-10 Frontage Road (northern wash highest elevation) (FIRM panels affected: 0420 and 1010)</ENT>
                            <ENT>+1952</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Extensive ponding areas north of I-10 Frontage Road (southern wash lowest elevation) (FIRM panels affected: 1010, 1030, 1035, 1045, 1065, and 1655)</ENT>
                            <ENT>+1948</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Extensive ponding areas north of I-10 Frontage Road (southern wash highest elevation) (FIRM panels affected: 1010, 1030, 1035, 1045, 1065, and 1655)</ENT>
                            <ENT>+2184</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Sheet Flow Areas (AO Zones)</ENT>
                            <ENT>Extensive sheet flow areas in the vicinity of Central Arizona Project Canal (lowest depth) (FIRM panels affected: 0420, 0440, 0445, 1010, 1030, 1035, 1045, 1055, 1060, 1065, 1070, and 1655)</ENT>
                            <ENT>#1</ENT>
                            <ENT>Town of Marana, Unincorporated Areas of Pima County.</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="22"> </ENT>
                            <ENT>Extensive sheet flow areas in the vicinity of Central Arizona Project Canal (highest depth) (FIRM panels affected: 0420, 0440, 0445, 1010, 1030, 1035, 1045, 1055, 1060, 1065, 1070, and 1655)</ENT>
                            <ENT>#4</ENT>
                        </ROW>
                        <ROW EXPSTB="03">
                            <ENT I="22">* National Geodetic Vertical Datum.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">+ North American Vertical Datum.</ENT>
                        </ROW>
                        <ROW>
                            <PRTPAGE P="35122"/>
                            <ENT I="22"># Depth in feet above ground.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">‸ Mean Sea Level, rounded to the nearest 0.1 meter.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="21">
                                <E T="02">ADDRESSES</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">
                                <E T="02">Town of Marana</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">Maps are available for inspection at the Engineering Department, 11555 West Civic Center Drive, Marana, AZ 85653.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="21">
                                <E T="02">Unincorporated Areas of Pima County</E>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="22">Maps are available for inspection at the Pima County Flood Control District Offices, 97 East Congress Street, 3rd Floor, Tucson, AZ 85701.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="21">
                                <E T="02">Christian County, Illinois, and Incorporated Areas</E>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="21">
                                <E T="02">Docket No.: FEMA-B-1105</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="01">Sangamon River</ENT>
                            <ENT>Approximately 1,350 feet downstream of 1725 East Road extended</ENT>
                            <ENT>+574</ENT>
                            <ENT>Unincorporated Areas of Christian County.</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 200 feet upstream of Meridan Road extended</ENT>
                            <ENT>+587</ENT>
                        </ROW>
                        <ROW EXPSTB="03">
                            <ENT I="22">* National Geodetic Vertical Datum.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">+ North American Vertical Datum.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"># Depth in feet above ground.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">‸ Mean Sea Level, rounded to the nearest 0.1 meter.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="21">
                                <E T="02">ADDRESSES</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="21">
                                <E T="02">Unincorporated Areas of Christian County</E>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="22">Maps are available for inspection at the Christian County Courthouse, 101 South Main Street, Taylorville, IL 62568.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="21">
                                <E T="02">Macon County, Illinois, and Incorporated Areas</E>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="21">
                                <E T="02">Docket No.: FEMA-B-1126</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="01">Friends Creek</ENT>
                            <ENT>Approximately 130 feet upstream of IL-48</ENT>
                            <ENT>+645</ENT>
                            <ENT>Village of Argenta.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 1,440 feet upstream of IL-48</ENT>
                            <ENT>+646</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Long Creek</ENT>
                            <ENT>At Baltimore Avenue</ENT>
                            <ENT>+619</ENT>
                            <ENT>City of Decatur.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>At IL-121</ENT>
                            <ENT>+627</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Long Creek Tributary</ENT>
                            <ENT>At the confluence with Long Creek</ENT>
                            <ENT>+619</ENT>
                            <ENT>City of Decatur.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 600 feet upstream of Lost Bridge Road</ENT>
                            <ENT>+620</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Sand Creek</ENT>
                            <ENT>At South Shores Drive (County Highway 31)</ENT>
                            <ENT>+619</ENT>
                            <ENT>Unincorporated Areas of Macon County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 20 feet upstream of the railroad</ENT>
                            <ENT>+619</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Sangamon River</ENT>
                            <ENT>Approximately 1.1 miles downstream of the confluence with Stevens Creek</ENT>
                            <ENT>+602</ENT>
                            <ENT>City of Decatur, Unincorporated Areas of Macon County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 1,400 feet upstream of Nesbit Bridge</ENT>
                            <ENT>+625</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">South Spring Creek</ENT>
                            <ENT>At the confluence with the Sangamon River</ENT>
                            <ENT>+608</ENT>
                            <ENT>City of Decatur.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 1,100 feet downstream of Heritage Road</ENT>
                            <ENT>+649</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Spring Creek</ENT>
                            <ENT>Approximately 200 feet upstream of the confluence with Stevens Creek</ENT>
                            <ENT>+620</ENT>
                            <ENT>Unincorporated Areas of Macon County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 0.6 mile upstream of Spring Creek Tributary</ENT>
                            <ENT>+659</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Spring Creek Tributary</ENT>
                            <ENT>At the confluence with Spring Creek</ENT>
                            <ENT>+657</ENT>
                            <ENT>Unincorporated Areas of Macon County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>At the downstream side of Mound Road</ENT>
                            <ENT>+659</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Stevens Creek</ENT>
                            <ENT>Approximately 400 feet upstream of the confluence with the Sangamon River</ENT>
                            <ENT>+603</ENT>
                            <ENT>Unincorporated Areas of Macon County, Village of Forsyth.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 150 feet upstream of I-72</ENT>
                            <ENT>+645</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Stevens Creek Tributary A</ENT>
                            <ENT>At the confluence with Stevens Creek</ENT>
                            <ENT>+619</ENT>
                            <ENT>Unincorporated Areas of Macon County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 1,230 feet upstream of Trump Hill Lane</ENT>
                            <ENT>+619</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Stevens Creek Tributary B</ENT>
                            <ENT>At the confluence with Stevens Creek</ENT>
                            <ENT>+629</ENT>
                            <ENT>Unincorporated Areas of Macon County.</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 985 feet upstream of the confluence with Stevens Creek</ENT>
                            <ENT>+630</ENT>
                        </ROW>
                        <ROW EXPSTB="03">
                            <ENT I="22">* National Geodetic Vertical Datum.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">+ North American Vertical Datum.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"># Depth in feet above ground.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">‸ Mean Sea Level, rounded to the nearest 0.1 meter.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="21">
                                <E T="02">ADDRESSES</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">
                                <E T="02">City of Decatur</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <PRTPAGE P="35123"/>
                            <ENT I="22">Maps are available for inspection at City Hall, 1 Gary K. Anderson Plaza, Decatur, IL 62523.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="21">
                                <E T="02">Unincorporated Areas of Macon County</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">Maps are available for inspection at the Macon County Courthouse, 141 South Main Street, Decatur, IL 62523.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">
                                <E T="02">Village of Argenta</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">Maps are available for inspection at the Village Hall, 330 North Warren, Argenta, IL 62501.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">
                                <E T="02">Village of Forsyth</E>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="22">Maps are available for inspection at the Village Hall, 301 South Route 51, Forsyth, IL 62535.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="21">
                                <E T="02">Piatt County, Illinois, and Incorporated Areas</E>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="21">
                                <E T="02">Docket No.: FEMA-B-1105</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="01">North East Tributary</ENT>
                            <ENT>Approximately 200 feet downstream of State Street</ENT>
                            <ENT>+652</ENT>
                            <ENT>City of Monticello, Unincorporated Areas of Piatt County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>At the downstream side of State Street</ENT>
                            <ENT>+656</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">North Unnamed Creek</ENT>
                            <ENT>Approximately 1,000 feet downstream of Front Street</ENT>
                            <ENT>+646</ENT>
                            <ENT>City of Monticello, Unincorporated Areas of Piatt County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 940 feet upstream of Market Street</ENT>
                            <ENT>+650</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Sangamon River</ENT>
                            <ENT>Approximately 2.52 miles downstream of the abandoned railroad bridge in the City of Monticello</ENT>
                            <ENT>+644</ENT>
                            <ENT>City of Monticello, Unincorporated Areas of Piatt County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>At the downstream side of the railroad</ENT>
                            <ENT>+649</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Unnamed Tributary to Sangamon River</ENT>
                            <ENT>At the confluence with the Sangamon River</ENT>
                            <ENT>+645</ENT>
                            <ENT>City of Monticello, Unincorporated Areas of Piatt County.</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 610 feet upstream of County Farm Road</ENT>
                            <ENT>+645</ENT>
                        </ROW>
                        <ROW EXPSTB="03">
                            <ENT I="22">* National Geodetic Vertical Datum.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">+ North American Vertical Datum.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"># Depth in feet above ground.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">‸ Mean Sea Level, rounded to the nearest 0.1 meter.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="21">
                                <E T="02">ADDRESSES</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">
                                <E T="02">City of Monticello</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">Maps are available for inspection at City Hall, 210 North Hamilton Street, Monticello, IL 61856.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="21">
                                <E T="02">Unincorporated Areas of Piatt County</E>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="22">Maps are available for inspection at the Piatt County Courthouse, 101 West Washington Street, Monticello, IL 61856.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="21">
                                <E T="02">Henry County, Kentucky, and Incorporated Areas</E>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="21">
                                <E T="02">Docket No.: FEMA-B-1100</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="01">Aaron Branch (backwater effects from Kentucky River)</ENT>
                            <ENT>From the confluence with Pot Ripple Creek to approximately 0.5 mile upstream of the confluence with Pot Ripple Creek</ENT>
                            <ENT>+488</ENT>
                            <ENT>Unincorporated Areas of Henry County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Boiling Branch (backwater effects from Kentucky River)</ENT>
                            <ENT>From the confluence with Sulphur Creek to approximately 0.5 mile upstream of the confluence with Sulphur Creek</ENT>
                            <ENT>+481</ENT>
                            <ENT>Unincorporated Areas of Henry County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Cane Run (backwater effects from Kentucky River)</ENT>
                            <ENT>From the confluence with the Kentucky River to approximately 0.5 mile upstream of Ford Lane</ENT>
                            <ENT>+476</ENT>
                            <ENT>Unincorporated Areas of Henry County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Drennon Creek (backwater effects from Kentucky River)</ENT>
                            <ENT>From the confluence with the Kentucky River to approximately 0.8 mile upstream of the confluence with Drennon Creek Tributary 9</ENT>
                            <ENT>+480</ENT>
                            <ENT>Unincorporated Areas of Henry County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Drennon Creek Tributary 49 (backwater effects from Kentucky River)</ENT>
                            <ENT>From the confluence with Drennon Creek to approximately 680 feet upstream of the confluence with Drennon Creek</ENT>
                            <ENT>+480</ENT>
                            <ENT>Unincorporated Areas of Henry County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Emily Run (backwater effects from Kentucky River)</ENT>
                            <ENT>From the confluence with Drennon Creek to approximately 708 feet upstream of Drennon Road</ENT>
                            <ENT>+480</ENT>
                            <ENT>Unincorporated Areas of Henry County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Greens Fork (backwater effects from Kentucky River)</ENT>
                            <ENT>From the confluence with Sulphur Creek to approximately 1,360 feet upstream of the confluence with Sulphur Creek</ENT>
                            <ENT>+481</ENT>
                            <ENT>Unincorporated Areas of Henry County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Gullion Creek Tributary 1 (backwater effects from Kentucky River)</ENT>
                            <ENT>From the confluence with Gullion Run to approximately 470 feet upstream of Gullion Branch Road</ENT>
                            <ENT>+474</ENT>
                            <ENT>Unincorporated Areas of Henry County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Gullion Run (backwater effects from Kentucky River)</ENT>
                            <ENT>From the confluence with the Kentucky River to approximately 885 feet upstream of the confluence with Gullion Creek Tributary 1</ENT>
                            <ENT>+474</ENT>
                            <ENT>Unincorporated Areas of Henry County.</ENT>
                        </ROW>
                        <ROW>
                            <PRTPAGE P="35124"/>
                            <ENT I="01">Hances Branch (backwater effects from Kentucky River)</ENT>
                            <ENT>From the confluence with Sixmile Creek to approximately 1,335 feet upstream of Six Mile Creek Road</ENT>
                            <ENT>+487</ENT>
                            <ENT>Unincorporated Areas of Henry County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Joes Branch (backwater effects from Kentucky River)</ENT>
                            <ENT>From the confluence with Sixmile Creek to approximately 785 feet upstream of Six Mile Creek Road</ENT>
                            <ENT>+487</ENT>
                            <ENT>Unincorporated Areas of Henry County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Kentucky River</ENT>
                            <ENT>Approximately 0.9 mile downstream of the confluence with Gullion Run</ENT>
                            <ENT>+473</ENT>
                            <ENT>Unincorporated Areas of Henry County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 5.0 miles upstream of the confluence with Stevens Creek West</ENT>
                            <ENT>+498</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Longs Branch (backwater effects from Kentucky River)</ENT>
                            <ENT>From the confluence with Sixmile Creek to approximately 1,280 feet upstream of the confluence with Sixmile Creek</ENT>
                            <ENT>+487</ENT>
                            <ENT>Unincorporated Areas of Henry County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Martini Run (backwater effects from Kentucky River)</ENT>
                            <ENT>From the confluence with Drennon Creek to approximately 1,490 feet upstream of Drennon Road</ENT>
                            <ENT>+480</ENT>
                            <ENT>Unincorporated Areas of Henry County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Pot Ripple Creek (backwater effects from Kentucky River)</ENT>
                            <ENT>From the confluence with the Kentucky River to approximately 0.8 mile upstream of the confluence with Aaron Branch</ENT>
                            <ENT>+488</ENT>
                            <ENT>Unincorporated Areas of Henry County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Sixmile Creek (backwater effects from Kentucky River)</ENT>
                            <ENT>From the confluence with the Kentucky River to approximately 1,410 feet upstream of the confluence with Longs Branch</ENT>
                            <ENT>+487</ENT>
                            <ENT>Unincorporated Areas of Henry County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Stevens Creek West (backwater effects from Kentucky River)</ENT>
                            <ENT>From the confluence with the Kentucky River to approximately 1.1 miles upstream of the confluence with the Kentucky River</ENT>
                            <ENT>+494</ENT>
                            <ENT>Unincorporated Areas of Henry County.</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="01">Sulphur Creek (backwater effects from Kentucky River)</ENT>
                            <ENT>From the confluence with Drennon Creek to approximately 1,200 feet upstream of the confluence with Greens Fork</ENT>
                            <ENT>+481</ENT>
                            <ENT>Unincorporated Areas of Henry County.</ENT>
                        </ROW>
                        <ROW EXPSTB="03">
                            <ENT I="22">* National Geodetic Vertical Datum.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">+ North American Vertical Datum.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"># Depth in feet above ground.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">‸ Mean Sea Level, rounded to the nearest 0.1 meter.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="21">
                                <E T="02">ADDRESSES</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="21">
                                <E T="02">Unincorporated Areas of Henry County</E>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="22">Maps are available for inspection at the Henry County Courthouse, 19 South Property Road, New Castle, KY 40050.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="21">
                                <E T="02">Lawrence County, Kentucky, and Incorporated Areas</E>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="21">
                                <E T="02">Docket No.: FEMA-B-1089</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="01">Big Branch (backwater effects from Yatesville Lake)</ENT>
                            <ENT>From the confluence with Brushy Creek to approximately 1.6 miles upstream of the confluence with Brushy Creek</ENT>
                            <ENT>+644</ENT>
                            <ENT>Unincorporated Areas of Lawrence County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Blaine Creek</ENT>
                            <ENT>Just downstream of the confluence with Hood Creek</ENT>
                            <ENT>+650</ENT>
                            <ENT>City of Blaine.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 0.5 mile upstream of the confluence with Hood Creek</ENT>
                            <ENT>+652</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Blaine Creek (backwater effects from Yatesville Lake)</ENT>
                            <ENT>From the confluence with Yatesville Lake to approximately 2.0 miles upstream of the confluence with Yatesville Lake</ENT>
                            <ENT>+644</ENT>
                            <ENT>Unincorporated Areas of Lawrence County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Borders Branch (backwater effects from Levisa Fork)</ENT>
                            <ENT>From the confluence with Levisa Fork to approximately 0.4 mile upstream of the confluence with Levisa Fork</ENT>
                            <ENT>+598</ENT>
                            <ENT>Unincorporated Areas of Lawrence County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Brushy Creek (backwater effects from Yatesville Lake)</ENT>
                            <ENT>From the confluence with Yatesville Lake to approximately 1.6 miles upstream of the confluence with Yatesville Lake</ENT>
                            <ENT>+644</ENT>
                            <ENT>Unincorporated Areas of Lawrence County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Daniels Creek (backwater effects from Yatesville Lake)</ENT>
                            <ENT>From the confluence with Yatesville Lake to approximately 0.5 mile upstream of the confluence with Yatesville Lake</ENT>
                            <ENT>+644</ENT>
                            <ENT>Unincorporated Areas of Lawrence County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Greenbrier Creek (backwater effects from Yatesville Lake)</ENT>
                            <ENT>From the confluence with Yatesville Lake to approximately 0.6 mile upstream of the confluence with Yatesville Lake</ENT>
                            <ENT>+644</ENT>
                            <ENT>Unincorporated Areas of Lawrence County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Harriet Branch (backwater effects from Yatesville Lake)</ENT>
                            <ENT>From the confluence with Yatesville Lake to approximately 0.5 mile upstream of the confluence with Yatesville Lake</ENT>
                            <ENT>+644</ENT>
                            <ENT>Unincorporated Areas of Lawrence County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Hood Creek (backwater effects from Blaine Creek)</ENT>
                            <ENT>From the confluence with Blaine Creek to approximately 1,700 feet upstream of the confluence with Blaine Creek</ENT>
                            <ENT>+650</ENT>
                            <ENT>City of Blaine.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Irish Creek (backwater effects from Yatesville Lake)</ENT>
                            <ENT>From the confluence with Blaine Creek to approximately 2.0 miles upstream of the confluence with Blaine Creek</ENT>
                            <ENT>+644</ENT>
                            <ENT>Unincorporated Areas of Lawrence County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Left Fork Little Blaine Creek (backwater effects from Yatesville Lake)</ENT>
                            <ENT>From the confluence with Yatesville Lake to approximately 0.9 mile upstream of the confluence with Yatesville Lake</ENT>
                            <ENT>+644</ENT>
                            <ENT>Unincorporated Areas of Lawrence County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Levisa Fork</ENT>
                            <ENT>At the confluence with Lick Creek East</ENT>
                            <ENT>+575</ENT>
                            <ENT>City of Louisa.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 1.5 miles downstream of KY-644</ENT>
                            <ENT>+575</ENT>
                        </ROW>
                        <ROW>
                            <PRTPAGE P="35125"/>
                            <ENT I="01">Lick Creek East (backwater effects from Levisa Fork)</ENT>
                            <ENT>From the confluence with Levisa Fork to Locust Street</ENT>
                            <ENT>+567</ENT>
                            <ENT>City of Louisa.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Newcomb Creek (backwater effects from Blaine Creek)</ENT>
                            <ENT>From approximately 350 feet upstream of KY-707 to approximately 0.5 mile upstream of KY-707</ENT>
                            <ENT>+567</ENT>
                            <ENT>Unincorporated Areas of Lawrence County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Pleas Creek (backwater effects from Yatesville Lake)</ENT>
                            <ENT>From the confluence with Yatesville Lake to approximately 0.3 mile upstream of the confluence with Yatesville Lake</ENT>
                            <ENT>+644</ENT>
                            <ENT>Unincorporated Areas of Lawrence County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Rich Creek (backwater effects from Yatesville Lake)</ENT>
                            <ENT>From the confluence with Yatesville Lake to approximately 0.9 mile upstream of the confluence with Yatesville Lake</ENT>
                            <ENT>+644</ENT>
                            <ENT>Unincorporated Areas of Lawrence County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Right Fork Irish Creek (backwater effects from Yatesville Lake)</ENT>
                            <ENT>From the confluence with Irish Creek to approximately 1,100 feet upstream of the confluence with Irish Creek</ENT>
                            <ENT>+644</ENT>
                            <ENT>Unincorporated Areas of Lawrence County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Right Fork Little Blaine Creek (backwater effects from Yatesville Lake)</ENT>
                            <ENT>From the confluence with Yatesville Lake to approximately 1.1 miles upstream of the confluence with Yatesville Lake</ENT>
                            <ENT>+644</ENT>
                            <ENT>Unincorporated Areas of Lawrence County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Rockcastle Creek (backwater effects from Tug Fork)</ENT>
                            <ENT>From just upstream of the confluence with Tug Fork to approximately 2.2 miles upstream of the confluence with Tug Fork</ENT>
                            <ENT>+598</ENT>
                            <ENT>Unincorporated Areas of Lawrence County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Two Mile Creek (backwater effects from Big Sandy River)</ENT>
                            <ENT>From CSX Railroad to approximately 600 feet upstream of CSX Railroad</ENT>
                            <ENT>+572</ENT>
                            <ENT>City of Louisa.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Upper Twin Branch (backwater effects from Yatesville Lake)</ENT>
                            <ENT>From the confluence with Yatesville Lake to approximately 0.3 mile upstream of the confluence with Yatesville Lake</ENT>
                            <ENT>+644</ENT>
                            <ENT>Unincorporated Areas of Lawrence County.</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="01">Yatesville Lake</ENT>
                            <ENT>Entire shoreline</ENT>
                            <ENT>+644</ENT>
                            <ENT>Unincorporated Areas of Lawrence County.</ENT>
                        </ROW>
                        <ROW EXPSTB="03">
                            <ENT I="22">* National Geodetic Vertical Datum</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">+ North American Vertical Datum.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"># Depth in feet above ground.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">‸ Mean Sea Level, rounded to the nearest 0.1 meter.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="21">
                                <E T="02">ADDRESSES</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">
                                <E T="02">City of Blaine</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">Maps are available for inspection at 591 KY-201 South, Blaine, KY 41124.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">
                                <E T="02">City of Louisa</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">Maps are available for inspection at 215 North Main Cross Street, Louisa, KY 41230.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="21">
                                <E T="02">Unincorporated Areas of Lawrence County</E>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="22">Maps are available for inspection at 122 Ricky Skaggs Boulevard, Louisa, KY 41230.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="21">
                                <E T="02">Kennebec County, Maine (All Jurisdictions)</E>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="21">
                                <E T="02">Docket Nos.: FEMA-B-1047 and FEMA-B-1120</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="01">Berry Pond</ENT>
                            <ENT>Entire shoreline north of Dexter Pond Road</ENT>
                            <ENT>+246</ENT>
                            <ENT>Town of Winthrop.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">China Lake</ENT>
                            <ENT>Entire shoreline within community</ENT>
                            <ENT>+199</ENT>
                            <ENT>Town of Albion, Town of Vassalboro.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Echo Lake</ENT>
                            <ENT>Entire shoreline within community</ENT>
                            <ENT>+317</ENT>
                            <ENT>Town of Fayette.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Kennebec River</ENT>
                            <ENT>Approximately 3.5 miles upstream of I-95</ENT>
                            <ENT>+44</ENT>
                            <ENT>Town of Vassalboro.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 2.6 miles downstream of Carter Memorial Drive</ENT>
                            <ENT>+55</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Kezar Brook</ENT>
                            <ENT>At the mouth of Cobboseecontee Lake</ENT>
                            <ENT>+169</ENT>
                            <ENT>Town of Winthrop.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Just downstream of South Road</ENT>
                            <ENT>+169</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Little Pond</ENT>
                            <ENT>Entire shoreline within community</ENT>
                            <ENT>+256</ENT>
                            <ENT>Town of Rome.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Long Pond</ENT>
                            <ENT>Entire shoreline within community</ENT>
                            <ENT>+187</ENT>
                            <ENT>Town of Windsor.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Lovejoy Pond</ENT>
                            <ENT>Entire shoreline within community</ENT>
                            <ENT>+304</ENT>
                            <ENT>Town of Fayette.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Messalonskee Stream</ENT>
                            <ENT>At the County Road Bridge</ENT>
                            <ENT>+105</ENT>
                            <ENT>Town of Oakland.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>At the City of Waterville/Somerset County boundary</ENT>
                            <ENT>+105</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">North Pond</ENT>
                            <ENT>Entire shoreline within community</ENT>
                            <ENT>+256</ENT>
                            <ENT>Town of Rome.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Sebasticook River</ENT>
                            <ENT>Approximately 2,500 feet downstream of the Town of Clifton/Waldo County boundary</ENT>
                            <ENT>+129</ENT>
                            <ENT>Township of Unity.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>At the Town of Clifton/Waldo County boundary</ENT>
                            <ENT>+132</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Threecornered Pond</ENT>
                            <ENT>Entire shoreline north of Weeks Mills Road</ENT>
                            <ENT>+196</ENT>
                            <ENT>Town of Windsor.</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="01">Threemile Pond</ENT>
                            <ENT>Entire shoreline north of Weeks Mills Road</ENT>
                            <ENT>+185</ENT>
                            <ENT>Town of Windsor.</ENT>
                        </ROW>
                        <ROW EXPSTB="03">
                            <ENT I="22">* National Geodetic Vertical Datum.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">+ North American Vertical Datum.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"># Depth in feet above ground.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">‸ Mean Sea Level, rounded to the nearest 0.1 meter.</ENT>
                        </ROW>
                        <ROW>
                            <PRTPAGE P="35126"/>
                            <ENT I="21">
                                <E T="02">ADDRESSES</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">
                                <E T="02">Town of Albion</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">Maps are available for inspection at the Town Office, 22 Main Street, Albion, ME 04910.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">
                                <E T="02">Town of Fayette</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">Maps are available for inspection at the Town Hall, 2589 Main Street, Fayette, ME 04349.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">
                                <E T="02">Town of Oakland</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">Maps are available for inspection at the Town Hall, 6 Cascade Mill Road, Oakland, ME 04963.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">
                                <E T="02">Town of Rome</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">Maps are available for inspection at the Town Hall, 8 Mercer Road, Rome, ME 04963.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">
                                <E T="02">Town of Vassalboro</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">Maps are available for inspection at the Vassalboro Town Hall, 682 Main Street, North Vassalboro, ME 04989.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">
                                <E T="02">Town of Windsor</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">Maps are available for inspection at the Town Hall, 523 Ridge Road, Windsor, ME 04363.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">
                                <E T="02">Town of Winthrop</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">Maps are available for inspection at the Town Office, 17 Highland Avenue, Winthrop, ME 04364.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">
                                <E T="02">Township of Unity</E>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="22">Maps are available for inspection at the Kennebec County Office, 125 State Street, Augusta, ME 04330.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="21">
                                <E T="02">Adams County, Mississippi, and Incorporated Areas</E>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="21">
                                <E T="02">Docket No.: FEMA-B-1089</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="01">Mississippi River</ENT>
                            <ENT>Approximately 1.9 miles downstream of John R. Junkin Drive</ENT>
                            <ENT>+76</ENT>
                            <ENT>Unincorporated Areas of Adams County.</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 1.3 miles downstream of John R. Junkin Drive</ENT>
                            <ENT>+76</ENT>
                        </ROW>
                        <ROW EXPSTB="03">
                            <ENT I="22">* National Geodetic Vertical Datum.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">+ North American Vertical Datum.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"># Depth in feet above ground.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">‸ Mean Sea Level, rounded to the nearest 0.1 meter.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="21">
                                <E T="02">ADDRESSES</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="21">
                                <E T="02">Unincorporated Areas of Adams County</E>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="22">Maps are available for inspection at 115 South Wall Street, Natchez, MS 39210.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="21">
                                <E T="02">Stone County, Mississippi, and Incorporated Areas</E>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="21">
                                <E T="02">Docket No.: FEMA-B-1108</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="01">Church House Branch</ENT>
                            <ENT>Approximately 0.5 mile downstream of East 5th Avenue</ENT>
                            <ENT>+211</ENT>
                            <ENT>City of Wiggins.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 385 feet upstream of East Borders Avenue</ENT>
                            <ENT>+245</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Flint Creek</ENT>
                            <ENT>Approximately 574 feet downstream of Clubhouse Drive</ENT>
                            <ENT>+171</ENT>
                            <ENT>City of Wiggins, Unincorporated Areas of Stone County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 1,290 feet upstream of State Highway 29</ENT>
                            <ENT>+187</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Flint Creek Tributary 2</ENT>
                            <ENT>At the confluence with Flint Creek</ENT>
                            <ENT>+174</ENT>
                            <ENT>City of Wiggins.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 350 feet upstream of Annis Lane</ENT>
                            <ENT>+254</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Four Mile Creek</ENT>
                            <ENT>Approximately 1 mile downstream of South Azalea Drive</ENT>
                            <ENT>+168</ENT>
                            <ENT>City of Wiggins, Unincorporated Areas of Stone County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 345 feet upstream of West Miles Avenue</ENT>
                            <ENT>+261</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Four Mile Creek Tributary 1</ENT>
                            <ENT>At the confluence with Four Mile Creek</ENT>
                            <ENT>+214</ENT>
                            <ENT>City of Wiggins.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 1,845 feet upstream of West Bond Avenue</ENT>
                            <ENT>+261</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Red Creek Tributary</ENT>
                            <ENT>Approximately 0.5 mile downstream of Mill Avenue</ENT>
                            <ENT>+166</ENT>
                            <ENT>City of Wiggins, Unincorporated Areas of Stone County.</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 1,345 feet upstream of State Highway 29</ENT>
                            <ENT>+220</ENT>
                        </ROW>
                        <ROW EXPSTB="03">
                            <ENT I="22">* National Geodetic Vertical Datum.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">+ North American Vertical Datum.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"># Depth in feet above ground.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">‸ Mean Sea Level, rounded to the nearest 0.1 meter.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="21">
                                <E T="02">ADDRESSES</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">
                                <E T="02">City of Wiggins</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">Maps are available for inspection at City Hall, 117 North 1st Street, Wiggins, MS 39577.</ENT>
                        </ROW>
                        <ROW>
                            <PRTPAGE P="35127"/>
                            <ENT I="21">
                                <E T="02">Unincorporated Areas of Stone County</E>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="22">Maps are available for inspection at the Stone County Courthouse, 323 East Cavers Street, Wiggins, MS 39577.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="21">
                                <E T="02">Camden County, Missouri, and Incorporated Areas</E>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="21">
                                <E T="02">Docket Nos: FEMA-B-1031 and FEMA-B-1089</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="01">Grand Glaize River</ENT>
                            <ENT>At U.S. Route 54</ENT>
                            <ENT>+664</ENT>
                            <ENT>City of Osage Beach, Unincorporated Areas of Camden County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 10.5 miles upstream of U.S. Route 54</ENT>
                            <ENT>+665</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Linn Creek</ENT>
                            <ENT>At the the Osage River confluence</ENT>
                            <ENT>+664</ENT>
                            <ENT>City of Linn Creek, Unincorporated Areas of Camden County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>At the Linn Creek North Fork confluence</ENT>
                            <ENT>+674</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Linn Creek North Fork</ENT>
                            <ENT>At the Linn Creek confluence</ENT>
                            <ENT>+674</ENT>
                            <ENT>City of Linn Creek, Unincorporated Areas of Camden County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 0.9 mile upstream of the Linn Creek confluence</ENT>
                            <ENT>+693</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Linn Creek South Fork</ENT>
                            <ENT>At Locust Street</ENT>
                            <ENT>+695</ENT>
                            <ENT>City of Linn Creek, Unincorporated Areas of Camden County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>At U.S. Route 54</ENT>
                            <ENT>+710</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Little Niangua River</ENT>
                            <ENT>At the Niangua River confluence</ENT>
                            <ENT>+664</ENT>
                            <ENT>Unincorporated Areas of Camden County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>At State Route J</ENT>
                            <ENT>+673</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Niangua River</ENT>
                            <ENT>At State Route 5</ENT>
                            <ENT>+664</ENT>
                            <ENT>City of Camdenton, Unincorporated Areas of Camden County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>At the Tunnel Dam</ENT>
                            <ENT>+732</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Osage River</ENT>
                            <ENT>At State Route MM</ENT>
                            <ENT>+664</ENT>
                            <ENT>City of Osage Beach, City of Sunrise Beach, Unincorporated Areas of Camden County, Village of Four Seasons.</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 36 miles upstream of State Route 5</ENT>
                            <ENT>+666</ENT>
                        </ROW>
                        <ROW EXPSTB="03">
                            <ENT I="22">* National Geodetic Vertical Datum.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">+ North American Vertical Datum.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"># Depth in feet above ground.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">‸ Mean Sea Level, rounded to the nearest 0.1 meter.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="21">
                                <E T="02">ADDRESSES</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">
                                <E T="02">City of Camdenton</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">Maps are available for inspection at City Hall, 437 West U.S. Route 54, Camdenton, MO 65020.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">
                                <E T="02">City of Linn Creek</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">Maps are available for inspection at City Hall, 102 East Valley Drive, Linn Creek, MO 65052.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">
                                <E T="02">City of Osage Beach</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">Maps are available for inspection at City Hall, 1000 City Parkway, Osage Beach, MO 65065.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">
                                <E T="02">City of Sunrise Beach</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">Maps are available for inspection at the Camden County Courthouse, 1 Court Circle, Camdenton, MO 65020.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="21">
                                <E T="02">Unincorporated Areas of Camden County</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">Maps are available for inspection at the Camden County Courthouse, 1 Court Circle, Camdenton, MO 65020.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">
                                <E T="02">Village of Four Seasons</E>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="22">Maps are available for inspection at the Village Hall, 133 Cherokee Road, Four Seasons, MO 65049.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="21">
                                <E T="02">St. Francois County, Missouri, and Incorporated Areas</E>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="21">
                                <E T="02">Docket No.: FEMA-B-1093</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="01">Flat River</ENT>
                            <ENT>Approximately 375 feet downstream of the confluence with Walker Branch</ENT>
                            <ENT>+683</ENT>
                            <ENT>City of Desloge, City of Park Hills, Unincorporated Areas of St. Francois County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>At St. Joe Drive</ENT>
                            <ENT>+701</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 875 feet downstream of East Elvins Boulevard</ENT>
                            <ENT>+750</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 3,000 feet upstream of State Highway 32</ENT>
                            <ENT>+784</ENT>
                        </ROW>
                        <ROW>
                            <PRTPAGE P="35128"/>
                            <ENT I="01">Kennedy Branch</ENT>
                            <ENT>Approximately 425 feet downstream of County Highway F</ENT>
                            <ENT>+837</ENT>
                            <ENT>City of Farmington, Unincorporated Areas of St. Francois County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 1,400 feet upstream of Middle Street</ENT>
                            <ENT>+893</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Koen Creek</ENT>
                            <ENT>Approximately 100 feet upstream of the City of Park Hills and City of Desloge corporate limits</ENT>
                            <ENT>+695</ENT>
                            <ENT>City of Desloge, City of Park Hills, Unincorporated Areas of St. Francois County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 2,350 feet upstream of Hurryville Road</ENT>
                            <ENT>+846</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Koen Creek Tributary</ENT>
                            <ENT>Approximately 325 feet upstream of the confluence with Keon Creek</ENT>
                            <ENT>+718</ENT>
                            <ENT>City of Park Hills, Unincorporated Areas of St. Francois County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 100 feet upstream of 5th Street</ENT>
                            <ENT>+792</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Shaw Creek</ENT>
                            <ENT>Approximately 700 feet upstream of the confluence with Flat Creek</ENT>
                            <ENT>+732</ENT>
                            <ENT>City of Park Hills, Unincorporated Areas of St. Francois County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 2,000 feet upstream of the City of Park Hills corporate limits</ENT>
                            <ENT>+767</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">St. Francois River</ENT>
                            <ENT>Approximately 2,000 feet downstream of U.S. Route 67</ENT>
                            <ENT>+844</ENT>
                            <ENT>City of Farmington, Unincorporated Areas of St. Francois County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 50 feet upstream of County Highway W</ENT>
                            <ENT>+859</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">St. Francois Tributary</ENT>
                            <ENT>Approximately 750 feet upstream of the confluence with the St. Francois River</ENT>
                            <ENT>+846</ENT>
                            <ENT>City of Farmington, Unincorporated Areas of St. Francois County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 75 feet upstream of County Highway W</ENT>
                            <ENT>+881</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 925 feet downstream of Liberty Street</ENT>
                            <ENT>+896</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 1,200 feet upstream of Liberty Street</ENT>
                            <ENT>+910</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Walker Branch</ENT>
                            <ENT>Approximately 600 feet upstream of the confluence with the Flat River</ENT>
                            <ENT>+685</ENT>
                            <ENT>Unincorporated Areas of St. Francois County.</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 7,000 feet upstream of Halter Road</ENT>
                            <ENT>+783</ENT>
                        </ROW>
                        <ROW EXPSTB="03">
                            <ENT I="22">* National Geodetic Vertical Datum.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">+ North American Vertical Datum.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"># Depth in feet above ground.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">‸ Mean Sea Level, rounded to the nearest 0.1 meter.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="21">
                                <E T="02">ADDRESSES</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">
                                <E T="02">City of Desloge</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">Maps are available for inspection at 300 North Lincoln Street, Desloge, MO 63601.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">
                                <E T="02">City of Farmington</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">Maps are available for inspection at 110 West Columbia Street, Farmington, MO 63640.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">
                                <E T="02">City of Park Hills</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">Maps are available for inspection at 9 Bennet Street, Park Hills, MO 63601.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="21">
                                <E T="02">Unincorporated Areas of St. Francois County</E>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="22">Maps are available for inspection at 1 West Liberty Street, Farmington, MO 63640.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="21">
                                <E T="02">Wayne County, Missouri, and Incorporated Areas</E>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="21">
                                <E T="02">Docket No.: FEMA-B-1093</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="01">Clearwater Lake</ENT>
                            <ENT>Entire shoreline within community</ENT>
                            <ENT>+572</ENT>
                            <ENT>Unincorporated Areas of Wayne County.</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="01">Lake Wappapello</ENT>
                            <ENT>Entire shoreline within community</ENT>
                            <ENT>+403</ENT>
                            <ENT>Unincorporated Areas of Wayne County.</ENT>
                        </ROW>
                        <ROW EXPSTB="03">
                            <ENT I="22">* National Geodetic Vertical Datum.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">+ North American Vertical Datum.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"># Depth in feet above ground.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">‸ Mean Sea Level, rounded to the nearest 0.1 meter.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="21">
                                <E T="02">ADDRESSES</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="21">
                                <E T="02">Unincorporated Areas of Wayne County</E>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="22">Maps are available for inspection at 109 Walnut Street, Greenville, MO 63944.</ENT>
                        </ROW>
                        <ROW>
                            <PRTPAGE P="35129"/>
                            <ENT I="21">
                                <E T="02">Lancaster County, South Carolina, and Incorporated Areas</E>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="21">
                                <E T="02">Docket No.: FEMA-B-1126</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="01">Cane Creek</ENT>
                            <ENT>Approximately 0.7 mile downstream of Grace Avenue</ENT>
                            <ENT>+430</ENT>
                            <ENT>Unincorporated Areas of Lancaster County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 1.0 mile downstream of Old Lansford Road</ENT>
                            <ENT>+433</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Catawba River</ENT>
                            <ENT>Approximately 2.3 miles upstream of the confluence with Waxahaw Creek</ENT>
                            <ENT>+465</ENT>
                            <ENT>Unincorporated Areas of Lancaster County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 0.5 mile downstream of the confluence with Catawba River Tributary 1</ENT>
                            <ENT>+481</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 0.6 mile upstream of the confluence with Catawba River Tributary 11</ENT>
                            <ENT>+484</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 1 mile upstream of the confluence with Catawba River Tributary 11</ENT>
                            <ENT>+486</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Sugar Creek</ENT>
                            <ENT>At the confluence with the Catawba River</ENT>
                            <ENT>+486</ENT>
                            <ENT>Unincorporated Areas of Lancaster County.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 1.2 miles upstream of the confluence with McAlpine Creek</ENT>
                            <ENT>+537</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Wateree Lake (Catawba River)</ENT>
                            <ENT>At the Fairfield/Kershaw County boundary</ENT>
                            <ENT>+240</ENT>
                            <ENT>Unincorporated Areas of Lancaster County.</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 3.3 miles upstream of the Fairfield/Kershaw County boundary</ENT>
                            <ENT>+244</ENT>
                        </ROW>
                        <ROW EXPSTB="03">
                            <ENT I="22">* National Geodetic Vertical Datum.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">+ North American Vertical Datum.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"># Depth in feet above ground.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">‸ Mean Sea Level, rounded to the nearest 0.1 meter.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="21">
                                <E T="02">ADDRESSES</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="21">
                                <E T="02">Unincorporated Areas of Lancaster County</E>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="22">Maps are available for inspection at the Building and Zoning Department, 101 North Main Street, Lancaster, SC 29720.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="21">
                                <E T="02">Marlboro County, South Carolina, and Incorporated Areas</E>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="21">
                                <E T="02">Docket No.: FEMA-B-1108</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="01">Great Pee Dee River</ENT>
                            <ENT>Approximately 2.8 miles downstream of U.S. Route 1</ENT>
                            <ENT>+93</ENT>
                            <ENT>Unincorporated Areas of Marlboro County.</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 1.1 miles upstream of the confluence with Marks Creek</ENT>
                            <ENT>+110</ENT>
                        </ROW>
                        <ROW EXPSTB="03">
                            <ENT I="22">* National Geodetic Vertical Datum.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">+ North American Vertical Datum.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"># Depth in feet above ground.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">‸ Mean Sea Level, rounded to the nearest 0.1 meter.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="21">
                                <E T="02">ADDRESSES</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="21">
                                <E T="02">Unincorporated Areas of Marlboro County</E>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="22">Maps are available for inspection at the Marlboro County Courthouse, 105 Main Street, Bennettsville, SC 29512.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="21">
                                <E T="02">Dinwiddie County, Virginia, and Incorporated Areas</E>
                            </ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="21">
                                <E T="02">Docket No.: FEMA-B-1104</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="01">Appomattox River</ENT>
                            <ENT>Approximately 1.65 miles downstream of Ferndale Road (State Route 600)</ENT>
                            <ENT>+55</ENT>
                            <ENT>Unincorporated Areas of Dinwiddie County.</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="22"> </ENT>
                            <ENT>Approximately 1.28 miles upstream of Vepco Dam</ENT>
                            <ENT>+131</ENT>
                        </ROW>
                        <ROW EXPSTB="03">
                            <ENT I="22">* National Geodetic Vertical Datum.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">+ North American Vertical Datum.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"># Depth in feet above ground.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">‸ Mean Sea Level, rounded to the nearest 0.1 meter.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="21">
                                <E T="02">ADDRESSES</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="21">
                                <E T="02">Unincorporated Areas of Dinwiddie County</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">Maps are available for inspection at the Dinwiddie County Government Center, Planning Department, 14016 Boydton Plank Road, Dinwiddie, VA 23841.</ENT>
                        </ROW>
                    </GPOTABLE>
                </REGTEXT>
                <EXTRACT>
                    <PRTPAGE P="35130"/>
                    <FP>(Catalog of Federal Domestic Assistance No. 97.022, “Flood Insurance.”)</FP>
                </EXTRACT>
                <SIG>
                    <DATED>Dated: May 11, 2011.</DATED>
                    <NAME>Sandra K. Knight,</NAME>
                    <TITLE>Deputy Federal Insurance and Mitigation Administrator, Mitigation, Department of Homeland Security, Federal Emergency Management Agency.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-14897 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 9110-12-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Pipeline and Hazardous Materials Safety Administration</SUBAGY>
                <CFR>49 CFR Parts 192 and 195</CFR>
                <DEPDOC>[Docket ID PHMSA-2007-27954; Amdt. Nos. 192-117; 195-97]</DEPDOC>
                <RIN>RIN 2137-AE64</RIN>
                <SUBJECT>Pipeline Safety: Control Room Management/Human Factors</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Pipeline and Hazardous Materials Safety Administration (PHMSA); DOT.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This rule expedites the program implementation deadlines in the Control Room Management/Human Factors regulations in order to realize the safety benefits sooner than established in the original rule. The deadline for pipeline operators to implement the procedures for roles and responsibilities, shift change, change management, and operating experience, fatigue mitigation education and training is now October 1, 2011, 16 months sooner than the original regulation. The deadline for pipeline operators to implement the other procedures for adequate information, shift lengths, maximum hours-of-service, and alarm management is now August 1, 2012, six months sooner than the original regulation. In general, training procedures must also be implemented by August 1, 2012, with certain exceptions.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>This rule is effective August 15, 2011.</P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        For further information contact Byron Coy at 609-989-2180 or by e-mail at 
                        <E T="03">Byron.Coy@dot.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Executive Summary</HD>
                <P>This final rule amends the program implementation deadlines originally published by PHMSA on December 3, 2009, in 49 CFR 192.631 and 195.446 (74 FR 63310), as corrected February 3, 2010 (75 FR 5536). By this amendment to the Control Room Management/Human Factors (CRM) rule, an operator must implement the procedures required by the rule according to the following schedule. The procedures required by Paragraphs (b) (roles and responsibilities), (c)(5) (shift change), (d)(2)-(3) (fatigue mitigation education and training), (f) (change management), and (g) (operating experience) of the rule must now be implemented no later than October 1, 2011. The procedures required by Paragraphs (c)(1)-(4) (adequate information), (d)(1) (shift lengths), (d)(4) (maximum hours-of-service), and (e) (alarm management) must now be implemented no later than August 1, 2012. The training procedures required by the remaining Paragraph (h) must now be implemented no later than August 1, 2012, except that any training required as a condition of compliance with another paragraph of the rule must be implemented no later than the corresponding deadline for implementing that part of the rule. Table 1 shows program implementation deadlines for different paragraphs.</P>
                <GPOTABLE COLS="8" OPTS="L2,p7,7/8,i1" CDEF="s30,r30,r30,r30,r30,r30,r30,r30">
                    <TTITLE>Table 1—Program Implementation Deadline for Different Paragraphs</TTITLE>
                    <BOXHD>
                        <CHED H="1">Paragraph</CHED>
                        <CHED H="1">
                            (b) Roles &amp; 
                            <LI>responsibilities</LI>
                        </CHED>
                        <CHED H="1">
                            (c) Adequate 
                            <LI>information</LI>
                        </CHED>
                        <CHED H="1">
                            (d) Fatigue 
                            <LI>mitigation</LI>
                        </CHED>
                        <CHED H="1">
                            (e) Alarm 
                            <LI>management</LI>
                        </CHED>
                        <CHED H="1">
                            (f) Change 
                            <LI>management</LI>
                        </CHED>
                        <CHED H="1">
                            (g) Operating 
                            <LI>experience</LI>
                        </CHED>
                        <CHED H="1">(h) Training</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Current Regulations</ENT>
                        <ENT>Feb 1, 2013</ENT>
                        <ENT>Feb 1, 2013</ENT>
                        <ENT>Feb 1, 2013</ENT>
                        <ENT>Feb 1, 2013</ENT>
                        <ENT>Feb 1, 2013</ENT>
                        <ENT>Feb 1, 2013</ENT>
                        <ENT>Feb 1, 2013.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NPRM</ENT>
                        <ENT>Aug 1, 2011</ENT>
                        <ENT>
                            C5 Aug 1, 2011 
                            <LI>C1-4 Aug 1, 2012</LI>
                        </ENT>
                        <ENT>Aug 1, 2011</ENT>
                        <ENT>Aug 1, 2012</ENT>
                        <ENT>Aug 1, 2011</ENT>
                        <ENT>Aug 1, 2011</ENT>
                        <ENT>Aug 1, 2011.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Final Rule</ENT>
                        <ENT>Oct 1, 2011</ENT>
                        <ENT>
                            C5 Oct 1, 2011 
                            <LI>C1-4 Aug 1, 2012</LI>
                        </ENT>
                        <ENT>
                            D2 &amp; D3 Oct 1, 2011 
                            <LI>D1 &amp; D4 Aug 1, 2012</LI>
                        </ENT>
                        <ENT>Aug 1, 2012</ENT>
                        <ENT>Oct 1, 2011</ENT>
                        <ENT>Oct 1, 2011</ENT>
                        <ENT>Training elements aligned to due date of each element.</ENT>
                    </ROW>
                </GPOTABLE>
                <P>Executive Orders 12866 and 13563 require agencies to regulate in the “most cost-effective manner,” to make a “reasoned determination that the benefits of the intended regulation justify its costs,” and to develop regulations that “impose the least burden on society.” The expected benefit of this rulemaking action is an expedited implementation deadline of the CRM rule that realizes the safety benefit to the public, property, and the environment sooner.</P>
                <GPOTABLE COLS="4" OPTS="L2,tp0,i1" CDEF="s50,14,14,14">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1"> </CHED>
                        <CHED H="1">
                            Low
                            <LI>($ millions)</LI>
                        </CHED>
                        <CHED H="1">
                            High
                            <LI>($ millions)</LI>
                        </CHED>
                        <CHED H="1">
                            Average
                            <LI>($ millions)</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Total Cost of Rule</ENT>
                        <ENT>$8.8</ENT>
                        <ENT>13.5</ENT>
                        <ENT>11.1</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Total Benefit of Rule</ENT>
                        <ENT>$13.9</ENT>
                        <ENT>13.9</ENT>
                        <ENT>13.9</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Net Benefit of Rule</ENT>
                        <ENT>$5.1</ENT>
                        <ENT>0.4</ENT>
                        <ENT>2.8</ENT>
                    </ROW>
                </GPOTABLE>
                <HD SOURCE="HD1">II. Background</HD>
                <P>On September 17, 2010, PHMSA published a Notice of Proposed Rulemaking (NPRM) proposing to expedite the program implementation deadlines in the CRM rule at §§ 192.631 and 195.446 (75 FR 56972). The NPRM proposed to expedite the deadline for implementing all the procedures required by the rule to August 1, 2011, except that procedures required by Paragraphs (c)(1)-(4) (adequate information) and (e) (alarm management) would have a program implementation deadline of August 1, 2012.</P>
                <P>
                    PHMSA received requests from several pipeline trade associations and pipeline operators to extend the comment period until after PHMSA's public workshop on pipeline control room management, which was held on November 17, 2010, in Houston, Texas (75 FR 67450). So, PHMSA extended the 
                    <PRTPAGE P="35131"/>
                    comment period deadline from November 16, 2010, to December 3, 2010 (75 FR 69912).
                </P>
                <HD SOURCE="HD1">III. Advisory Committees Meeting</HD>
                <P>On March 24, 2011, the Technical Pipeline Safety Standards Committee (TPSSC) and the Technical Hazardous Liquid Pipeline Safety Standards Committee (THLPSSC) met jointly in Arlington, Virginia. The TPSSC and THLPSSC are statutorily-mandated advisory committees that advise PHMSA on proposed safety standards, risk assessments, and safety policies for natural gas pipelines and for hazardous liquid pipelines. Both committees were established under the Federal Advisory Committee Act (Pub. L. 92-463, 5 U.S.C. App. 1) and the pipeline safety law (49 U.S.C. Chap. 601). Each committee consists of 15 members, with membership evenly divided among the Federal and state governments, the regulated industry, and the public. The committees advise PHMSA on technical feasibility, practicability, and cost-effectiveness of each proposed pipeline safety standard.</P>
                <P>During the meeting, the committees considered the NPRM to expedite the program implementation deadline of the CRM regulations. To assist the TPSSC and THLPSSC in their deliberations, PHMSA presented three options of program implementation deadlines. These included the program implementation deadlines as proposed in the NPRM, the program implementation deadline of February 1, 2013, in the original rule, and a third option that reflected the comments received on the proposed rule, comments received at the November 17, 2010, workshop, and PHMSA's internal discussions. PHMSA provided these options to facilitate the TPSSC and THLPSSC members' discussion of the rule and to provide a process by which the members could recommend a certain course of action by PHMSA with regard to the rule. Members were not limited to discussing these three options.</P>
                <P>After discussions, both the TPSSC and THLPSSC separately voted unanimously to recommend that PHMSA implement the NPRM with the changes reflected in the third option. Specifically, the TPSSC and THLPSSC recommended that the deadline for implementing Paragraphs (b) (roles and responsibilities), (c)(5) (shift change), (d)(2)-(3) (fatigue mitigation education and training), (f) (change management), and (g) (operating experience) be amended to August 1, 2011, the deadline for implementing Paragraphs (c)(1)-(4) (adequate information), (d)(1) (shift lengths), (d)(4) (maximum hours-of-service), and (e) (alarm management) be amended to August 1, 2012, and the deadline for training in Paragraph (h) be amended to August 1, 2012, except that any training required as a condition of compliance with another paragraph of the rule be implemented no later than the corresponding deadline for implementing that part of the rule. This final rule effectively adopts the recommendations of the TPSSC and THLPSSC except that the earliest date that any element must be implemented is October 1, 2011 and not August 1, 2011. This extra time is provided to provide operators proper notice after the publication of the final rule.</P>
                <HD SOURCE="HD1">IV. Summary and Response to Public Comments</HD>
                <P>PHMSA received a total of 16 comments on the NPRM: five comments from pipeline trade associations, nine comments from individual hazardous liquid and gas pipeline operators, one comment from a pipeline consultant, and one comment from an anonymous private citizen. In addition to the 16 comments, on March 1, 2011, the American Petroleum Institute (API) and the Association of Oil Pipe Lines (AOPL) submitted revised comments.</P>
                <HD SOURCE="HD2">A. General Comments</HD>
                <P>In their revised comments API &amp; AOPL stated that they did not oppose the proposed accelerated deadlines, except that acceleration of the deadline for Paragraphs (d) (fatigue mitigation) and (h) (training) was not appropriate.</P>
                <P>CenterPoint Energy, Panhandle Energy, Sunoco Pipeline LP (Sunoco), Texas Pipeline Association, and Williston Basin Interstate Pipeline Company opposed the proposed accelerated deadlines.</P>
                <P>Many of the same commenters and El Paso Pipeline Group (El Paso), Interstate Natural Gas Association of America (INGAA), and Northeast Gas Association (NGA), stated that the timing of PHMSA's release of Frequently Asked Questions (FAQs) guidance, inspection guidelines, and compliance criteria would affect their ability to meet the proposed accelerated deadlines if the content of the guidance differed significantly from their expectations.</P>
                <P>INGAA and El Paso also stated that while they previously supported the accelerated implementation schedule, the anticipated timing for PHMSA to release guidance material as stated at the public workshop, along with their uncertainty about the content of the guidance, has caused them to reconsider their support.</P>
                <P>Sunoco requested that the deadline for compliance be extended beyond those proposed because field control rooms cannot reasonably be included in PHMSA's assumption that the industry is largely ready now.</P>
                <P>American Gas Association (AGA), Avista, El Paso, NGA, Paiute Pipeline Company, and Southwest Gas Corporation (SWG) opposed the proposed accelerated deadlines for Paragraphs (d) (fatigue mitigation) and (h) (training). In addition, Paiute and SWG requested that Paragraph (f) (change management) be given an implementation deadline of August 1, 2012.</P>
                <P>NGA requested that if the proposed accelerated deadlines are implemented, PHMSA should consider modifying its review process during the first inspection cycle to include only recommended improvements, rather than Notices of Probable Violation and monetary penalties for companies that make efforts to implement their plans within the accelerated deadlines.</P>
                <P>Northern Natural Gas requested that the deadline for implementing all the procedures required by the rule only be accelerated to February 1, 2012, instead of August 1, 2011, as proposed, except that the procedures required by Paragraphs (c)(1)-(4) (adequate information), (e) (alarm management), and (f) (change management), should not be accelerated at all.</P>
                <P>Thomas Lael Services, L.P, a pipeline consultant, supported the proposed accelerated deadlines. He agreed with the statement in the NPRM that most if not all work associated with each requirement contained within the regulation has more than likely already been performed during the program development stage which already has a regulatory deadline of August 1, 2011. He agreed that due to the significance of this regulation and the potential for the increased safe operation of pipelines, an accelerated implementation deadline to August 1, 2012, is desirable and reasonable, but it is not clear whether he supported the August 1, 2012, deadline for all paragraphs. He added that recent pipeline incidents have initially pointed to control room issues as possible factors in the cause and, therefore, an accelerated deadline is prudent.</P>
                <P>The anonymous private citizen's comments were not deemed appropriate for consideration.</P>
                <P>
                    In general, while some commenters argued the NPRM should be withdrawn and the implementation deadlines in the current rule be kept, PHMSA did not find the general comments justified withdrawing the NPRM in order to leave in place the current program 
                    <PRTPAGE P="35132"/>
                    implementation deadlines for the reasons specified in more detail below. Some trade associations and pipeline operators stated that PHMSA has not released the FAQs document, inspection guidelines and compliance criteria. To address this concern, PHMSA released draft FAQs on February 3, 2011, and plans to release inspection forms and guidelines by early June 2011.
                </P>
                <HD SOURCE="HD2">B. Roles and Responsibilities, §§ 192.631(b) and 195.446(b)</HD>
                <P>Paragraph (b) of the rule requires operators to define the roles and responsibilities of a controller during normal, abnormal, and emergency operating conditions. The original rule established a deadline for operators to implement the procedures by February 1, 2013. The NPRM proposed that operators implement the procedures instead by August 1, 2011. The TPSSC and THLPSSC recommended that PHMSA amend the regulation as proposed.</P>
                <P>We received no comments specifically directed at the implementation deadline for this paragraph. Based on only the general comments we received and the TPSSC's and THLPSSC's recommendation, and in order to provide operators proper notice we are adopting the new implementation date of October 1, 2011.</P>
                <HD SOURCE="HD2">C. Provide Adequate Information, §§ 192.631(c) and 195.446(c)</HD>
                <P>Paragraph (c) of the rule requires operators to provide their controllers with the information, tools, processes and procedures necessary for the controllers to carry out the roles and responsibilities the operators have defined. The original rule established a deadline for operators to implement the procedures by February 1, 2013. The NPRM proposed that operators implement the procedures required by Paragraph (c)(1)-(4) instead by August 1, 2012, and the procedures required by Paragraph (c)(5) by August 1, 2011. The TPSSC and THLPSSC recommended that PHMSA amend the regulation as proposed.</P>
                <P>In addition to the general comments specified above, CenterPoint Energy stated that at a minimum, 12 months is needed from program development to full implementation in order to give operators an opportunity to assess their plans for one complete heating season and to make any necessary adjustments prior to actual implementation of the plan before the 2012 heating season.</P>
                <P>CenterPoint Energy agrees with PHMSA that the proposed 12 months is sufficient for program implementation deadline, but it is not clear that the operator agrees, as proposed, or for all sections in Paragraph (c). Based on this, other general comments received, the TPSSC's and THLPSSC's recommendation, the program implementation deadline for this paragraph is amended to October 1, 2011, for section (c)(5), and to August 1, 2012, for sections (c)(1)-(4).</P>
                <HD SOURCE="HD2">D. Fatigue Mitigation, §§ 192.631(d) and 195.446(d)</HD>
                <P>Paragraph (d) of the rule requires operators to implement fatigue mitigation methods to reduce the risk associated with controller fatigue that could inhibit a controller's ability to carry out the roles and responsibilities the operator has defined. The original rule established a deadline for operators to implement the procedures by February 1, 2013. The NPRM proposed that operators implement the procedures by August 1, 2011.</P>
                <P>The TPSSC and THLPSSC recommended that PHMSA amend the deadlines for Paragraphs (d)(2) and (d)(3) as proposed, but to establish an implementation deadline of August 1, 2012, for Paragraphs (d)(1) and (d)(4).</P>
                <P>In addition to the general comments specified above, INGAA believes that if PHMSA's guidance concerning controller scheduling and hours-of-service departs significantly from a paper on the subject published by the Southern Gas Association, it would severely jeopardize operators' ability to comply with the proposed deadlines, because operators would not be able to revise their implementation plans, increase their staffs, and complete the necessary process development in time. INGAA suggested, however, that operators could meet the expedited deadlines if their current understanding of the CRM regulations is implemented without major changes. INGAA estimated a minimum of six months would be needed for operators to implement their fatigue mitigation plans, including training, evaluation and revisions. Several individual operators agreed with these sentiments.</P>
                <P>AGA had concerns with PHMSA's proposal to accelerate the fatigue mitigation requirements by 18 months, because many operators have to hire new gas control personnel, and extensive time and effort are required to identify and train new personnel. AGA suggested that accelerating the implementation deadlines for these provisions could have the unintended consequence of moving individuals into gas controller positions with limited qualifications. Several individual operators agreed with this sentiment.</P>
                <P>API &amp; AOPL similarly stated that the accelerated timeline would not allow operators the appropriate time for implementation of human resources directives addressing the hiring and relocating of controllers. API &amp; AOPL also stated that a lack of guidance from PHMSA may cause uncertainty as to what will be considered as an acceptable limit on hours-of-service. API &amp; AOPL estimated a proper implementation period between eight and 12 months, although the comment appeared to be related more to training in general, rather than fatigue mitigation specifically.</P>
                <P>Avista was similarly concerned with the impact of the accelerated schedule for fatigue mitigation if enough time is not provided for operators to develop course material, create tests, arrange for subject matter experts to instruct courses, hire, and train new personnel.</P>
                <P>CenterPoint Energy supported the proposed accelerated deadlines for Paragraphs (d)(1) and (d)(4), but stated that Paragraphs (d)(2) and (d)(3) require additional time to implement, because training and education are ongoing activities that require flexibility and adjustment based on feedback from the trainees. CenterPoint Energy suggested 12 months for proper implementation of the required training and education requirements.</P>
                <P>Sunoco stated that a singular point of emphasis within the CRM is fatigue management, which clearly necessitates that the current 24/7 work schedules be analyzed to ensure that those shift designs mitigate, as much as possible, the fatigue that is associated with working around the clock. At PHMSA's Workshop, Sunoco stated that a PHMSA speaker stated that to complete analysis, the affected pipeline companies would have to have any modified/proposed shift schedule “verified” by a fatigue expert. Sunoco believes this would create a high demand for a relatively few fatigue experts within a very compressed timeframe. Sunoco stated that this verification would take much longer than the proposed implementation time.</P>
                <P>
                    After reviewing these comments and considered the TPSSC's and THLPSSC's recommendation, PHMSA believes many of the concerns are justified and that there should be some additional time between development and implementation of certain procedures related to fatigue mitigation. Based on the substantive comments provided, including estimated time frames, PHMSA believes that an implementation period of 12 months is reasonable for Paragraphs (d)(1) and (d)(4), which makes the amended 
                    <PRTPAGE P="35133"/>
                    deadline August 1, 2012. This would allow for an accelerated safety benefit in accordance with the intent of the NPRM, while also allowing operators additional time to conduct internal pilot testing, hiring and training of any new controllers, and other modifications to their schedule rotations and maximum hours-of-service, as needed.
                </P>
                <P>With regard to Paragraphs (d)(2) and (d)(3), PHMSA does not find the comments justify delaying the education and training of controllers and supervisors about fatigue mitigation strategies, how off-duty activities contribute to fatigue, and how to recognize the effects of fatigue. PHMSA believes the education and training of controllers and supervisors on the fundamental aspects of fatigue mitigation strategies can be undertaken upon program development and completed by August 1, 2011. However, due to the short time operators would have after the issuance of this rule, PHMSA is extending the program implementation deadline by two months to October 1, 2011. Of course, as operators develop more experience in fatigue mitigation strategies, they would be expected to update and improve their education and training program as necessary. Therefore, consistent with the recommendation of the TPSSC and THLPSSC, and the expected short time after issuance of this rule, the implementation deadline for Paragraphs (d)(2) and (d)(3) is amended to October 1, 2011.</P>
                <HD SOURCE="HD2">E. Alarm Management, §§ 192.631(e) and 195.446(e)</HD>
                <P>Paragraph (e) of the rule requires operators that use SCADA systems to have written alarm management plans to provide for effective controller response to alarms. The original rule established a deadline for operators to implement the procedures by February 1, 2013. The NPRM proposed that operators implement the procedures by August 1, 2012. The TPSSC and THLPSSC recommended that PHMSA amend the regulation as proposed.</P>
                <P>In addition to the general comments specified above, CenterPoint Energy stated that the full 18 months should be retained so that operators would be able to test their alarm management systems, modify their programs based on operator feedback, and repeat testing.</P>
                <P>Sunoco also requested that the original 18-month implementation period be retained because the company's ongoing efforts to install a new SCADA system and software program to help manage alarms will not be completed in its control rooms until 2013.</P>
                <P>PHMSA has reviewed these comments and considered the TPSSC's and THLPSSC's recommendation, and does not find that the full 18 months is necessary for program implementation, but that 12 months is sufficient for operators to implement this paragraph. Therefore, the program implementation deadline is amended, as proposed, to August 1, 2012.</P>
                <HD SOURCE="HD2">F. Change Management, §§ 192.631(f) and 195.446(f)</HD>
                <P>Paragraph (f) of the rule requires operators to assure that changes that could affect control room operations are coordinated with the control room personnel. The original rule established a deadline for operators to implement the procedures by February 1, 2013. The NPRM proposed that operators implement the procedures by August 1, 2011. The TPSSC and THLPSSC recommended that PHMSA amend the regulation as proposed.</P>
                <P>In addition to the general comments specified above, CenterPoint stated that PHMSA should allow six months for program implementation because the paragraph will require coordination across operator's organizations, which will be difficult to establish efficiently without an implementation period to educate the involved employees and make adjustments as necessary.</P>
                <P>Paiute Pipeline Company and SWG requested at least 12 months for implementing this requirement because it requires integration with existing processes and procedures, training of both controllers and field personnel, and evaluation of any other issues that can only be determined during an adequate implementation period.</P>
                <P>PHMSA has reviewed these comments and considered the TPSSC's and THLPSSC's recommendation, and does not find that an additional program implementation period is necessary for this requirement. This paragraph requires operators to assure that changes that could affect control room operations are coordinated with the control room personnel. Any changes that affect control room operations, including field changes, should be coordinated with controllers without delay once the program procedures are developed. Operators may still update and improve their change management procedures, if during implementation potential improvements are recognized. For these reasons, the program implementation deadline is amended to October 1, 2011.</P>
                <HD SOURCE="HD2">G. Operating Experience, §§ 192.631(g) and 195.446(g)</HD>
                <P>Paragraph (g) of the rule requires operators to assure that lessons learned from their operating experiences are incorporated, as appropriate, into their control room management procedures. The original rule established a deadline for operators to implement the procedures requiring the incorporation of operating experience by February 1, 2013. The NPRM proposed that operators implement the procedures by August 1, 2011. The TPSSC and THLPSSC recommended that PHMSA amend the regulation as proposed.</P>
                <P>In addition to the general comments specified above, CenterPoint Energy stated that at a minimum PHMSA should allow six months for implementation because the regulation will require coordination across operator's organizations and would be difficult to establish efficiently without an implementation period to educate the involved employees and make adjustments as necessary.</P>
                <P>PHMSA has reviewed the comments and the TPSSC's and THLPSSC's recommendation, and does not find an additional program implementation period is necessary for this requirement. Ensuring that lessons learned from operating experiences are incorporated, as appropriate, into operators' control room management procedures should be implemented once the program procedures are developed. Because incorporating lessons learned is a continuing process, operators can review accidents and incidents to determine if control room actions contributed to the event and correct issues, where necessary, while still updating and improving their change process during implementation if potential improvements are recognized. For these reasons, the program implementation deadline is amended, as proposed, to October 1, 2011.</P>
                <HD SOURCE="HD2">H. Training, §§ 192.631(h) and 195.446(h)</HD>
                <P>
                    Paragraph (h) of the rule requires operators to establish a controller training program and review the training program content to identify potential improvements at least once each calendar year, but at intervals not to exceed fifteen months. The original rule established a deadline for operators to implement the procedures by February 1, 2013. The NPRM proposed that operators implement the procedures by August 1, 2011. The TPSSC and THLPSSC recommended that PHMSA establish an implementation deadline of August 1, 
                    <PRTPAGE P="35134"/>
                    2012, for training, except that for any training required under one of the other paragraphs of the rule, that training must still be implemented in accordance with the corresponding deadline for that part of the rule.
                </P>
                <P>In addition to the general comments specified above, AGA stated that operators already have training methods, but many operators still need to formalize their processes, which takes extensive time and effort. In addition, AGA explained that new controllers that will be hired will not have time to complete the new training procedures by August 1, 2011. AGA stated that operators will be able to develop a training program that meets the control room management requirements by August 2011, but they will not be able to fully implement those training procedures with all controllers by that time.</P>
                <P>API &amp; AOPL estimated that training and qualification takes between eight and 12 months and additional time could be required to recruit capable and qualified candidates. They stated that the accelerated timeline does not allow enough time to complete training and, therefore, would lead to additional costs. Avista agreed with the sentiment that additional time is required to develop course material, create tests, arrange for subject matter experts to instruct courses, hire, and train new personnel, and suggested that PHMSA retain the 18-month implementation period in the original rule.</P>
                <P>CenterPoint Energy stated that at a minimum PHMSA should allow six months for implementation because the regulation will require coordination across operator's organizations that would be difficult to establish efficiently without an implementation period to educate the involved employees and make adjustments as necessary.</P>
                <P>El Paso stated that it has taken a leadership role in formulating joint industry training to meet the requirements of the final rule, but its effort is not expected to be completed until the middle of 2011. El Paso requested additional time beyond that proposed in the NPRM because they stated that they need to formalize the training program, have that program adopted within each operating company, and have all the controllers trained, including those not yet hired.</P>
                <P>Paiute Pipeline Company and SWG requested to keep the original 18-month implementation period, because the identification, hiring, training, as well as the period of supervised work experience and qualification of new controllers is a time consuming process. In addition, they stated some training requirements may go beyond controllers, such as training field employees impacting SCADA points, information services employees making changes to SCADA screens, and supervisors and managers being trained in fatigue mitigation strategies.</P>
                <P>Panhandle Energy also opposed the proposed amendment, stating that it typically takes upward of one year to provide the training and experience to be able to confidently utilize a new staff member as a gas controller.</P>
                <P>PHMSA has reviewed the comments and considered the TPSSC's and THLPSSC's recommendations concerning the time necessary to implement the new training procedures. PHMSA finds these comments justify an additional implementation period and that the proposed amendment could create an undue burden on operators to achieve compliance with Paragraph (h). While PHMSA still finds the original 18 months is not necessary, an implementation period of 12 months is reasonable, which makes the amended deadline August 1, 2012. This would allow for an accelerated safety benefit in accordance with the intent of the NPRM, while also allowing operators additional time to implement the new training procedures specified in Paragraph (h).</P>
                <P>
                    It must be clarified, however, that the training required by other paragraphs of the CRM rule (
                    <E T="03">e.g.,</E>
                     fatigue mitigation) must still be implemented in accordance with the corresponding deadline for that part of the rule (
                    <E T="03">e.g.,</E>
                     October 1, 2011).
                </P>
                <HD SOURCE="HD2">I. Other Paragraphs, §§ 192.631(i)-(j) and 195.446(i)-(j)</HD>
                <P>Paragraph (i) of the rule requires operators to submit their procedures, upon request, to PHMSA or, in the case of an intrastate pipeline facility regulated by a state, to the appropriate state agency. Paragraph (j) of the rule requires operators to maintain records that demonstrate compliance with the requirements of the rule, and documentation to demonstrate that any deviation from the procedures required by the rule was necessary for the safe operation of a pipeline facility. These requirements are self-executing and the NPRM did not propose to amend them. PHMSA received no comments on these paragraphs.</P>
                <HD SOURCE="HD1">V. Regulatory Analysis and Notice</HD>
                <HD SOURCE="HD2">Privacy Act Statement</HD>
                <P>
                    Anyone may search the electronic form of comments received in response to any of our dockets by the name of the individual submitting the comment (or signing the comment if submitted for an association, business, labor union,
                    <E T="03"> etc.</E>
                    ). You may review DOT's complete Privacy Act Statement in the 
                    <E T="04">Federal Register</E>
                     published on April 11, 2000 (65 FR 19477).
                </P>
                <HD SOURCE="HD2">Executive Order 12866, Executive Order 13563, and DOT Regulatory Policies and Procedures</HD>
                <P>This final rule is a significant regulatory action under section 3(f) of Executive Order 12866 (58 FR 51735) and, therefore, was reviewed by the Office of Management and Budget. This final rule is significant under the Regulatory Policies and Procedures of the Department of Transportation (44 FR 11034). PHMSA has also reviewed this regulation pursuant to Executive Order 13563, issued on January 18, 2011 (76 FR 3281, Jan. 21, 2011). EO 13563 is supplemental to and explicitly reaffirms the principles, structures, and definitions governing regulatory review established in Executive Order 12866. To the extent permitted by law, agencies are required to meet principles established by Executive Orders 12866 and 13563. PHMSA finds that, within the range of impacts analyzed in this rulemaking, the Control Room Management/Human Factors rule expediting the program implementation deadlines in the Control Room Management/Human Factors regulations is consistent with EO 12866 and 13563.</P>
                <P>
                    In this analysis we estimate that the average costs of this final rule are $11.15 million. We also estimate that the benefits of this final rule are $13.9 million. Two observations of note are (1) that the estimated annual benefits, $13.9 million, exceed the average estimated costs $11.15 million, by $2.75 million; (2) since the benefits do not include the non-quantified benefits, such as improved health and well-being of controllers and improved productivity for the reasons we discussed above it is likely that the actual benefits of the rule could be higher. A full Regulatory Analysis has been provided in the docket, while the chart below summarizes the estimated costs and benefits of this final rule.
                    <PRTPAGE P="35135"/>
                </P>
                <GPOTABLE COLS="4" OPTS="L2,tp0,i1" CDEF="s50,14,14,14">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1"> </CHED>
                        <CHED H="1">
                            Low
                            <LI>($ millions)</LI>
                        </CHED>
                        <CHED H="1">
                            High
                            <LI>($ millions)</LI>
                        </CHED>
                        <CHED H="1">
                            Average
                            <LI>($ millions)</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Total Cost of Rule</ENT>
                        <ENT>$8.8</ENT>
                        <ENT>$13.5</ENT>
                        <ENT>$11.1</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Total Benefit of Rule</ENT>
                        <ENT>13.9</ENT>
                        <ENT>13.9</ENT>
                        <ENT>13.9</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Net Benefit of Rule</ENT>
                        <ENT>5.1</ENT>
                        <ENT>0.4</ENT>
                        <ENT>2.8</ENT>
                    </ROW>
                </GPOTABLE>
                <HD SOURCE="HD2">Regulatory Flexibility Act</HD>
                <P>
                    Under the Regulatory Flexibility Act (5 U.S.C. 601 
                    <E T="03">et seq.</E>
                    ), PHMSA must consider whether rulemaking actions would have a significant economic impact on a substantial number of small entities. The original CRM rule included certain accommodations in consideration of small businesses. PHMSA estimated that the costs of those substantive requirements would be significantly less than one percent of revenues for most firms and there was not likely to be a significant economic impact on a substantial small number of operators, as explained in the original rule. PHMSA went on to say that the economic impact of the original CRM final rule on small entities will be minor and certified that that final rule will not have a significant economic impact on a substantial number of small entities. Since this final rule only expedites program implementation deadlines and does not establish any new substantive requirements, we likewise certify that this rule would not have a significant economic impact on a substantial number of small entities.
                </P>
                <HD SOURCE="HD2">Executive Order 13175</HD>
                <P>PHMSA has analyzed this rulemaking according to Executive Order 13175, “Consultation and Coordination with Indian Tribal Governments.” Because the rule would not significantly or uniquely affect the communities of the indian tribal governments or impose substantial direct compliance costs, the funding and consultation requirements of Executive Order 13175 do not apply.</P>
                <HD SOURCE="HD2">Paperwork Reduction Act</HD>
                <P>The rule does not require any additional paperwork burden on hazardous liquid and gas pipeline operators under the Paperwork Reduction Act of 1995.</P>
                <HD SOURCE="HD2">Unfunded Mandates Reform Act of 1995</HD>
                <P>This rule does not impose unfunded mandates under the Unfunded Mandates Reform Act of 1995. It does not result in costs of $141.3 million or more to either state, local, or tribal governments, in the aggregate, or to the private sector.</P>
                <HD SOURCE="HD2">National Environmental Policy Act</HD>
                <P>
                    PHMSA has examined the rule for purposes of the National Environmental Policy Act (42 U.S.C. 4321 
                    <E T="03">et seq.</E>
                    ). If pipeline operators comply with the technical elements of this rule within a shorter time, environmental benefits could be realized sooner and may reduce the number and severity of pipeline releases. PHMSA has concluded this rule would not have any significant impacts to the quality of the human environment under the National Environmental Policy Act.
                </P>
                <HD SOURCE="HD2">Executive Order 13132</HD>
                <P>PHMSA has analyzed this rule according to Executive Order 13132 (“Federalism”). The rule does not have a substantial direct effect on the states, the relationship between the national government and the states, or the distribution of power and responsibilities among the various levels of government. The rule does not impose substantial direct compliance costs on state and local governments. This rule would not preempt state law for intrastate pipelines. Therefore, the consultation and funding requirements of Executive Order 13132 do not apply.</P>
                <HD SOURCE="HD2">Executive Order 13211</HD>
                <P>Transporting gas and hazardous liquids impacts the nation's available energy supply. However, this rule is not a “significant energy action” under Executive Order 13211 and is not likely to have a significant adverse effect on the supply, distribution, or use of energy. Further, the Administrator of the Office of Information and Regulatory Affairs has not identified this rule as a significant energy action.</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects</HD>
                    <CFR>49 CFR Part 192</CFR>
                    <P>Gas, Natural gas, Pipeline safety, Reporting and recordkeeping requirements.</P>
                    <CFR>49 CFR Part 195</CFR>
                    <P>Anhydrous ammonia, Carbon dioxide, Petroleum, Pipeline safety, Reporting and recordkeeping requirements.</P>
                </LSTSUB>
                <P>For the reasons provided in the preamble, 49 CFR Parts 192 and 195 are amended as follows:</P>
                <REGTEXT TITLE="49" PART="192">
                    <PART>
                        <HD SOURCE="HED">PART 192—TRANSPORTATION OF NATURAL GAS AND OTHER GAS BY PIPELINE: MINIMUM FEDERAL SAFETY STANDARDS</HD>
                    </PART>
                    <AMDPAR>1. The authority citation for part 192 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P> 49 U.S.C. 5103, 60102, 60104, 60108, 60109, 60110, 60113, 60116, 60118, and 60137; and 49 CFR 1.53.</P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="49" PART="192">
                    <AMDPAR>2. Amend § 192.631 by removing the last sentence in paragraph (a)(2) and adding four sentences in its place to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 192.631 </SECTNO>
                        <SUBJECT>Control room management.</SUBJECT>
                        <P>(a) * * *</P>
                        <P>(2) * * * An operator must develop the procedures no later than August 1, 2011, and must implement the procedures according to the following schedule. The procedures required by paragraphs (b), (c)(5), (d)(2) and (d)(3), (f) and (g) of this section must be implemented no later than October 1, 2011. The procedures required by paragraphs (c)(1) through (4), (d)(1), (d)(4), and (e) must be implemented no later than August 1, 2012. The training procedures required by paragraph (h) must be implemented no later than August 1, 2012, except that any training required by another paragraph of this section must be implemented no later than the deadline for that paragraph.</P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="49" PART="195">
                    <PART>
                        <HD SOURCE="HED">PART 195—TRANSPORTATION OF HAZARDOUS LIQUIDS BY PIPELINE</HD>
                    </PART>
                    <AMDPAR>3. The authority citation for part 195 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority: </HD>
                        <P>49 U.S.C. 5103, 60102, 60104, 60108, 60109, 60116, 60118, and 60137; and 49 CFR 1.53.</P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="49" PART="195">
                    <AMDPAR>4. Amend § 195.446 by removing the last sentence in paragraph (a) and adding four sentences in its place to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 195.446 </SECTNO>
                        <SUBJECT>Control room management.</SUBJECT>
                        <P>
                            (a) * * * An operator must develop the procedures no later than August 1, 2011, and must implement the procedures according to the following schedule. The procedures required by paragraphs (b), (c)(5), (d)(2) and (d)(3), (f) and (g) of this section must be implemented no later than October 1, 2011. The procedures required by 
                            <PRTPAGE P="35136"/>
                            paragraphs (c)(1) through (4), (d)(1), (d)(4), and (e) must be implemented no later than August 1, 2012. The training procedures required by paragraph (h) must be implemented no later than August 1, 2012, except that any training required by another paragraph of this section must be implemented no later than the deadline for that paragraph.
                        </P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <SIG>
                    <DATED>Issued in Washington, DC, on June 10, 2011 under authority delegated in 49 CFR part 1.</DATED>
                    <NAME>Cynthia L. Quarterman,</NAME>
                    <TITLE>Administrator.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-14991 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-60-P</BILCOD>
        </RULE>
    </RULES>
    <VOL>76</VOL>
    <NO>116</NO>
    <DATE>Thursday, June 16, 2011</DATE>
    <UNITNAME>Proposed Rules</UNITNAME>
    <PRORULES>
        <PRORULE>
            <PREAMB>
                <PRTPAGE P="35137"/>
                <AGENCY TYPE="F">NUCLEAR REGULATORY COMMISSION</AGENCY>
                <CFR>10 CFR Parts 72 and 73</CFR>
                <DEPDOC>[NRC-2009-0558]</DEPDOC>
                <SUBJECT>Vulnerability and Threat Information for Facilities Storing Spent Nuclear Fuel and High-Level Radioactive Waste</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>U.S. Nuclear Regulatory Commission.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Public meeting.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The Nuclear Regulatory Commission (NRC) will discuss with affected stakeholders vulnerability and threat information associated with the forthcoming security rulemaking to revise Title 10 of the 
                        <E T="03">Code of Federal Regulations</E>
                         (10 CFR) Part 72, “Licensing Requirements for the Independent Storage of Spent Nuclear Fuel, High-Level Radioactive Waste, and Reactor-Related Greater Than Class C Waste,” and 73, “Physical Protection of Plants and Materials.” This information will be used to inform the regulatory basis for the rulemaking which will issue new risk-informed and performance-based security regulations for Spent Nuclear Fuel (SNF) and High-Level Radioactive Waste (HLW) storage facilities. The draft regulatory basis was published for comment in the 
                        <E T="04">Federal Register</E>
                         (FR) on December 16, 2009 (74 FR 66589).
                    </P>
                    <P>
                        This meeting will be closed under exemptions 3.a and 3.b of the Commission's policy statement 
                        <SU>1</SU>
                        <FTREF/>
                        , due to the expected discussion of classified information.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1</SU>
                             “Commission's Policy Statement on Enhancing Public Participation in NRC Meetings,” (67 FR 36920), May 28, 2002.
                        </P>
                    </FTNT>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Tuesday, July 26, 2011, 9 a.m. to 4 p.m. (Eastern Time) (Closed to Public—Requires Access to Classified Information)</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>U.S. Nuclear Regulatory Commission, One White Flint North, Commissioners' Conference Room, O-1 G16, 11555 Rockville Pike, Rockville, Maryland 20852.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Dennis Andrukat, Office of Nuclear Security and Incident Response, U.S. Nuclear Regulatory Commission, Washington, DC 20555-0001; telephone 301-415-3561; 
                        <E T="03">e-mail: Dennis.Andrukat@nrc.gov</E>
                        .
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Background</HD>
                <P>The NRC requires high assurance of adequate protection of public health and safety, the common defense and security, and the environment for the secure storage of SNF and HLW. The NRC meets this strategic goal by requiring Independent Spent Fuel Storage Installation licensees to comply with security requirements specified in 10 CFR Part 73. Following the terrorist attacks of September 11, 2001, the NRC has continued to achieve this requisite high assurance for all facilities licensed to store SNF through a combination of these existing security regulations and the issuance of security orders to individual licensees.</P>
                <P>Based on the Commission's direction presented in SRM-SECY-10-0114 (Agencywide Documents Access and Management System (ADAMS) Accession No. ML103210025) and stakeholder requests from the NRC sponsored May 2, 2011, open and closed public meetings (ADAMS Package Accession No. ML111450161), the staff is hosting this meeting to enhance stakeholder understanding of the security assessments used to inform the draft regulatory basis and to enhance staff understanding of the comments received. The meeting will discuss classified national security information.</P>
                <P>The NRC notes that the public, licensees, certificate holders, and other stakeholders will have a future opportunity to comment on the proposed rulemaking when that document is published in the FR.</P>
                <HD SOURCE="HD1">Availability of Documents</HD>
                <P>The following table indicates the related documents that are available to the public and how they may be obtained.</P>
                <GPOTABLE COLS="04" OPTS="L2,tp0,i1" CDEF="s75,12C,12C,xs60">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Document</CHED>
                        <CHED H="1">
                            Public 
                            <LI>Document Room (PDR)</LI>
                        </CHED>
                        <CHED H="1">Web</CHED>
                        <CHED H="1">
                            Electronic 
                            <LI>Reading Room </LI>
                            <LI>(ADAMS)</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Draft Technical Basis, Revision 1 (December 2009) [NRC-2009-0558]</ENT>
                        <ENT>X</ENT>
                        <ENT>X</ENT>
                        <ENT>ML093280743</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Commission: SECY-10-0114 (August 26, 2010)</ENT>
                        <ENT>X</ENT>
                        <ENT/>
                        <ENT>ML101960614</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Commission: SRM-SECY-10-0114 (November 16, 2010)</ENT>
                        <ENT>X</ENT>
                        <ENT>X</ENT>
                        <ENT>ML103210025</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Commission: SECY-07-0148 (redacted) (August 28, 2007)</ENT>
                        <ENT>X</ENT>
                        <ENT>X</ENT>
                        <ENT>ML080030050</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Commission: SRM-SECY-07-0148 (December 18, 2007)</ENT>
                        <ENT>X</ENT>
                        <ENT>X</ENT>
                        <ENT>ML073530119</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Public Meeting Notice for May 2, 2011 (March 30, 2011)</ENT>
                        <ENT>X</ENT>
                        <ENT/>
                        <ENT>ML110880263</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Meeting Summary Package for May 2, 2011 meeting</ENT>
                        <ENT>X</ENT>
                        <ENT/>
                        <ENT>ML111450161</ENT>
                    </ROW>
                </GPOTABLE>
                <P>You can access publicly available documents related to this notice using the following methods:</P>
                <P>
                    <E T="03">NRC's PDR:</E>
                     The public may examine and have copied, for a fee, publicly available documents at the NRC's PDR, Public File Area O-1 G21, One White Flint North, 11555 Rockville Pike, Rockville, Maryland 20852-2738.
                </P>
                <P>
                    <E T="03">NRC's ADAMS:</E>
                     Publicly available documents created or received at the NRC are available online in the NRC Library at 
                    <E T="03">http://www.nrc.gov/reading-rm/adams.html</E>
                    . From this page, the public can gain entry into ADAMS, which provides text and image files of NRC's public documents. If you do not have access to ADAMS or if there are problems in accessing the documents located in ADAMS, contact the NRC's PDR reference staff at 1-800-397-4209, 
                    <PRTPAGE P="35138"/>
                    301-415-4737, or by e-mail to 
                    <E T="03">pdr.resource@nrc.gov.</E>
                </P>
                <P>
                    <E T="03">Federal Rulemaking Site:</E>
                     Public comments and supporting materials related to this notice can be found at 
                    <E T="03">http://www.regulations.gov</E>
                     by searching on Docket ID: NRC-2009-0558.
                </P>
                <P>
                    <E T="03">Availability of Services:</E>
                </P>
                <P>The NRC provides reasonable accommodations to individuals with disabilities where appropriate. If you need a reasonable accommodation to participate in this meeting (e.g., sign language), or need this meeting notice or other information from the meeting in another format, please notify the NRC meeting contact, Dennis Andrukat at 301-415-3561 by July 5, 2011, so that arrangements can be made.</P>
                <P>All expected attendees must register with the NRC meeting contact by close of business on July 12, 2011. Attendees must provide their full name, company/organization, last four of social security number, phone number, acknowledgement of current access to Classified Information (minimum “L” clearance), and basis for need-to-know in order to verify that attendees are cleared for access to the information.</P>
                <P>No electronic devices will be allowed in the Commissioners' Conference Room during the meeting, this includes cell phones, laptops, pagers, PDAs, etc. No food or drink is allowed in the Commissioners' Conference Room.</P>
                <P>All attendees are to use the One White Flint North temporary entrance located on Marinelli Street. The NRC is accessible to the White Flint Metro Station. Visitor parking near the NRC buildings is limited. Parking is available at the White Flint Metro Station using the Metro Smart Card.</P>
                <SIG>
                    <DATED>Dated at Rockville, Maryland, this 7th day of June 2011.</DATED>
                    <P>For the Nuclear Regulatory Commission.</P>
                    <NAME>Sandra L. Wastler,</NAME>
                    <TITLE>Branch Chief, Division of Security Policy, Office of Nuclear Security and Incident Response.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-14666 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 7590-01-P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="N">FARM CREDIT ADMINISTRATION</AGENCY>
                <CFR>12 CFR Part 652</CFR>
                <RIN>RIN 3052-AC70</RIN>
                <SUBJECT>Federal Agricultural Mortgage Corporation Funding and Fiscal Affairs; Farmer Mac Risk-Based Capital Stress Test, Version 5.0</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Farm Credit Administration.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Advance notice of proposed rulemaking.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>In this advance notice of proposed rulemaking (ANPRM), the Farm Credit Administration (FCA, we, us, our) is requesting comments on alternatives to using credit ratings issued by nationally recognized statistical ratings organizations (NRSRO or credit rating agency) in regulations addressing the Risk-Based Capital Stress Test (RBCST or stress test) for the Federal Agricultural Mortgage Corporation (Farmer Mac or FAMC). Recent legislation requires every Federal agency to remove any references to credit ratings from its regulations and to substitute them with other standards of creditworthiness considered appropriate. Additionally, in response to this same legislative emphasis on ensuring appropriate prudential oversight of derivatives transactions, we are considering whether the RBCST should include a more explicit and comprehensive capital charge for counterparty risk stemming from derivative transactions. Lastly, through the ANPRM we are seeking public input on how we might revise the operational and strategic business planning requirements for FAMC to place greater emphasis on diversity and inclusion.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>You may send comments on or before August 15, 2011.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>We offer a variety of methods for you to submit comments. For accuracy and efficiency reasons, commenters are encouraged to submit comments by e-mail or through the FCA's Web site. As facsimiles (fax) are difficult for us to process and achieve compliance with section 508 of the Rehabilitation Act, we no longer accept comments submitted by fax. Regardless of the method you use, please do not submit your comment multiple times via different methods. You may submit comments by any of the following methods:</P>
                    <P>
                        • 
                        <E T="03">E-mail:</E>
                         Send us an e-mail at 
                        <E T="03">reg-comm@fca.gov.</E>
                    </P>
                    <P>
                        • 
                        <E T="03">FCA Web site: http://www.fca.gov.</E>
                         Select “Public Commenters”, then “Public Comments”, and follow the directions for “Submitting a Comment”.
                    </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>
                         Laurie A. Rea, Director, Office of Secondary Market Oversight, Farm Credit Administration, 1501 Farm Credit Drive, McLean, VA 22102-5090.
                    </P>
                    <P>
                        You may review copies of all comments we receive at our office in McLean, Virginia, or on our Web site at 
                        <E T="03">http://www.fca.gov.</E>
                         Once you are in the Web site, select “Public Commenters”, then “Public Comments”, and follow the directions for “Reading Submitted Public Comments”. We will show your comments as submitted, including any supporting data provided, but for technical reasons we may omit items such as logos and special characters. Identifying information that you provide, such as phone numbers and addresses, will be publicly available. However, we will attempt to remove e-mail addresses to help reduce Internet spam.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <FP SOURCE="FP-1">Joseph T. Connor, Associate Director for Policy and Analysis, Office of Secondary Market Oversight, Farm Credit Administration, McLean, VA 22102-5090, (703) 883-4280, TTY (703) 883-4434,</FP>
                    <FP>  Or</FP>
                    <FP SOURCE="FP-1">Laura McFarland, Senior Counsel, Office of the General Counsel, Farm Credit Administration, McLean, VA 22102-5090, (703) 883-4020, TTY (703) 883-4020.</FP>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Objective</HD>
                <P>The purpose of this ANPRM is to gather public input on how FCA might:</P>
                <P>• Revise existing Farmer Mac RBCST regulations to replace data from credit rating agencies.</P>
                <P>• Comprehensively address derivative counterparty exposure in the RBCST; and</P>
                <P>• Revise operational and strategic business planning requirements to place greater emphasis on diversity and inclusion.</P>
                <HD SOURCE="HD1">II. Background</HD>
                <P>
                    Farmer Mac is an institution of the Farm Credit System, regulated by FCA through the FCA Office of Secondary Market Oversight (OSMO). Farmer Mac was established and chartered by Congress to create a secondary market for agricultural real estate mortgage loans, rural housing mortgage loans, and rural utilities loans, and it is a stockholder-owned instrumentality of the United States. Title VIII of the Farm Credit Act of 1971, as amended, (Act) governs Farmer Mac.
                    <SU>1</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         Public Law 92 181, 85 Stat. 583, 12 U.S.C. 2001 
                        <E T="03">et seq.</E>
                         (December 10, 1971).
                    </P>
                </FTNT>
                <P>
                    On July 21, 2010, the Dodd-Frank Wall Street Reform and Consumer Protection Act of 2010 (Dodd-Frank Act) was enacted.
                    <SU>2</SU>
                    <FTREF/>
                     Section 939A of the Dodd-Frank Act requires Federal agencies to review all regulatory references to NRSRO credit ratings and replace those references with other appropriate standards for determining creditworthiness. The Dodd-Frank Act 
                    <PRTPAGE P="35139"/>
                    further provides that, to the extent feasible, agencies should adopt a uniform standard of creditworthiness for use in regulations, taking into account the entities regulated and the purposes for which such regulated entities would rely on the creditworthiness standard.
                </P>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         Public Law 111-203, 124 Stat. 1376, (H.R. 4173), July 21, 2010.
                    </P>
                </FTNT>
                <P>
                    The FCA uses credit rating agency data in its RBCST regulations for Farmer Mac. Section 8.32 of the Act required FCA to establish a risk-based capital stress test for Farmer Mac's portfolio.
                    <SU>3</SU>
                    <FTREF/>
                     This stress test determines the level of regulatory capital necessary for Farmer Mac to maintain positive capital during a 10-year period where stressful credit and interest rate conditions occur. We first published regulations on the stress test, and other requirements related to section 8.32 of the Act, in the 
                    <E T="04">Federal Register</E>
                     at 66 FR 19048 (April 12, 2001). Since then, we revised the stress test several times, most recently to capture capital requirements for Farmer Mac's rural utilities authorities. The existing RBCST for Farmer Mac is contained in 12 CFR part 652, subpart B, and it currently relies, in part, on NRSRO credit ratings when calculating regulatory minimum capital requirements.
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         12 U.S.C. 2279bb-1.
                    </P>
                </FTNT>
                <P>We have comprehensively reviewed our regulations that use or rely on credit ratings, including other sections in part 652 which govern Farmer Mac's non-program investments and liquidity reserve requirements. This ANPRM is one of several notices and proposed rules on which we will be seeking public input relating to use of credit ratings in our rules.</P>
                <HD SOURCE="HD2">A. Farmer Mac Programs</HD>
                <P>
                    Under the Farmer Mac I program, FAMC guarantees prompt payment of principal and interest on securities representing interests in, or obligations backed by, mortgage loans secured by first liens on agricultural real estate or rural housing. It also purchases, or commits to purchase, qualified loans or securities backed by qualified loans directly from lenders. Under the Farmer Mac II program, FAMC purchases and securitizes portions of certain loans guaranteed by the U.S. Department of Agriculture, including farm ownership and operating loans and rural business and community development loans. Farmer Mac also guarantees the timely payment of principal and interest on the securities created from these loans. In 2008, Congress granted Farmer Mac the authority to purchase and guarantee securities backed by loans to rural electric and telephone utility cooperatives as program business.
                    <SU>4</SU>
                    <FTREF/>
                     Farmer Mac also provides a secondary market for USDA-guaranteed farm program and rural development loans.
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         Section 5406 of Public Law 110-246, 122 Stat. 1651 (June 18, 2008) (repealing and replacing Pub. L. 110-234).
                    </P>
                </FTNT>
                <HD SOURCE="HD2">B. Risk-Based Capital and Credit Ratings</HD>
                <P>
                    Under our rules, Farmer Mac's regulatory capital must be sufficient so that it would remain positive during the 10-year time horizon of the stress test. One component of the RBCST accounts for the risk of loss on specific types of program investments (
                    <E T="03">i.e.,</E>
                     investments backed by agricultural real estate mortgage loans, rural housing loans, or rural utility cooperative loans) that include credit enhancement features. In this context, credit risk is adjusted downward based on the whole-letter credit rating of the counterparty on AgVantage and similarly structured assets. The adjustment is made to recognize the risk-reducing strength of the counterparty's general obligation backing of these securities. These securities are further backed by eligible loan collateral.
                </P>
                <P>
                    Another component of the RBCST estimates counterparty risk associated with non-program investments, 
                    <E T="03">e.g.,</E>
                     corporate debt, asset-backed securities and mortgage-related securities. In this context, the RBCST reduces earnings at rates related to the cumulative historical default and recovery rates of corporate debt by whole-letter credit rating category as published by Moody's Investor Services.
                    <SU>5</SU>
                    <FTREF/>
                     The RBCST's calculations in each of these two components use five whole-letter rating categories. It then assigns counterparties into these categories by referencing ratings issued by an NRSRO for the counterparty. The regulations, in turn, specify the change in expected cash flows during the stress period to reflect the risk of default by a counterparty based in part on the assigned ratings category. The changes in cash flows decrease projected losses on program assets and decrease earnings on non-program investments, which then translate to changes in equity over the modeling horizon and affect the required minimum regulatory capital calculated by the stress test.
                </P>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         Emery K., Ou S., Tennant, J., Kim F., Cantor R., “Corporate Default and Recovery Rates, 1920-2009,” published by Moody's Investors Service, February 2010.
                    </P>
                </FTNT>
                <P>FCA initially chose to use NRSRO ratings in the RBCST as a source of objective and neutral third-party assessments of the credit risk for particular instruments and counterparties. We used ratings because they were readily and publicly available. The use of NRSRO ratings was also, at the time, believed to offer enhanced consistency in credit evaluation across different components of the RBCST. In 2010, the Dodd-Frank Act addressed, in part, the structure of credit rating agencies, requiring revisions and imposing other requirements in an effort to resolve the conflicts of interest and other difficulties believed to be at the center of the 2008-2009 financial market crisis. The Dodd-Frank Act also questioned the value of these ratings when used as the primary data source in the assessment of the creditworthiness of a security or money market instrument. In connection with that, the Dodd-Frank Act requires every Federal agency to remove any reference to, or reliance on, credit rating agencies in its regulations and replace any such reference with an alternative standard of credit worthiness considered appropriate for the regulatory purpose. As a result, we are seeking suggestions on what alternative data sources would be most appropriate for the RBCST.</P>
                <HD SOURCE="HD2">C. Considerations and Objectives for a New Approach to Quantifying Relative Creditworthiness</HD>
                <P>
                    FCA believes that any new standard of creditworthiness should distinguish between different levels of credit risk, in an accurate and timely manner, and be transparent in its approach. We believe it should also be applied consistently across the multiple components of the RBCST and be reasonably simple, while not unduly burdensome to apply and not be easily subject to manipulation. FCA recognizes that any resulting system will likely involve trade-offs among these objectives, 
                    <E T="03">e.g.,</E>
                     simple versus accurate and timely, accurate and timely versus not burdensome to apply.
                </P>
                <P>
                    To eliminate the use of NRSRO ratings in calculating risk-based capital requirements for Farmer Mac, we need to develop an alternative basis to assess counterparty risk. One approach may be to identify objective criteria that Farmer Mac could apply to categorize credit exposures into different risk classes and assess counterparty risk accordingly. The criteria may be broadly designated. For example, credit exposures could be divided into government and non-government, secured and unsecured, or other categories, such as maturity. Such a broad approach, however, may not be able to sufficiently and consistently account for difference in relative risk among exposures that fall into the same category. FCA may also consider adopting criteria that reference certain 
                    <PRTPAGE P="35140"/>
                    financial or other metrics related to the obligor or counterparty. To be meaningful, the criteria would need to account for or bear a reasonable correlation to the potential riskiness of default among different obligors or counterparties. Any criteria would also need to be readily obtainable for all relevant counterparties by FCA, Farmer Mac and the public or it might not be sufficiently transparent and objective. The standards would need to ensure that the investment or position is not speculative, and carries credit risk appropriate for Farmer Mac's risk profile and the authorized purposes for non-program investments. As any new counterparty risk evaluation approach is initiated, there is the potential for increased risk as the new system is implemented.
                </P>
                <P>FCA might also consider an approach that builds on Farmer Mac's internal credit review process and allows it to assign risk ratings to various categories and assess risk based on qualitative and quantitative standards set by FCA regulations. For example, FCA could assign loss rate estimates based on Farmer Mac's internal ratings or some modification of such, as reviewed or approved by FCA—or simply review or approve Farmer Mac's mapping of its assigned risk ratings to estimated loss rates. This approach would be more subjective than the alternative discussed above but could allow FCA to leverage the data collection and analysis already performed by Farmer Mac. Under this approach, FCA would likely rely heavily on the supervisory process to make sure that Farmer Mac is strictly following its internal guidelines and not assuming high levels of credit risk.</P>
                <P>Questions (1) through (11) of Section III of this ANPRM address this topic.</P>
                <HD SOURCE="HD2">D. Counterparty Risk on Derivatives</HD>
                <P>As part of our Dodd-Frank Act review and the increasing emphasis by the financial industry on ensuring appropriate prudential oversight of derivatives transactions, we are also considering whether the RBCST should include a more explicit and comprehensive capital charge for counterparty risk stemming from derivative transactions.</P>
                <P>The RBCST produces a single comprehensive capital requirement for Farmer Mac by modeling changes in cash flows under a specific statutory stress scenario. We believe there may be opportunities to revise the RBCST to add a representation of counterparty default exposure on derivatives transactions by considering both net replacement cost as well as current exposure to individual cash flows based on an assessment of the counterparty's creditworthiness.</P>
                <P>Questions (12) and (13) of Section III. of this ANPRM address this topic.</P>
                <HD SOURCE="HD2">E. Capital and Business Planning</HD>
                <P>As part of this ANPRM, we are seeking input on how we might revise § 652.60(b) on operational and strategic business planning requirements to place greater emphasis on diversity and inclusion in both Farmer Mac's personnel as well as the borrowers and lenders who benefit from its secondary market activities.</P>
                <P>We believe an integral part of promoting and achieving inclusion and diversity can be accomplished through an effective operational plan that includes strategies to seek out qualified loans from a diverse group of sources and provides rural lenders with financing products that serve a diverse array of borrowers, such as small, beginning, new, disabled, female, and minority farmers, ranchers, and rural homeowners, as well as cooperatives with diversity of ownership. We believe promotion of inclusion and diversity should also extend to non-traditional agricultural producers, such as local food systems, organic or specialty crop farmers, and community-supported agriculture.</P>
                <P>Additionally, we are considering whether Farmer Mac's operational and strategic plans should include strategies and actions to achieve diversity and inclusion within FAMC's workforce, management, and governance structure, as well as an assessment of the progress FAMC has made in this area. We are also contemplating whether the plans should describe FAMC's succession programs.</P>
                <P>Questions (14) and (15) of Section III. of this ANPRM address this topic.</P>
                <HD SOURCE="HD1">III. Request for Comments</HD>
                <P>
                    FCA regulations governing the Farmer Mac RBCST contain specific references to credit ratings issued by NRSROs for purposes of calculating regulatory minimum capital requirements. FCA is issuing this ANPRM to identify standards that may be appropriate replacements for credit ratings issued by NRSROs, which maintain compliance with statutory design requirements for the RBCST. Other regulatory agencies have also issued ANPRMs as part of their process to address references to credit ratings in their capital regulations and prudential standards.
                    <SU>6</SU>
                    <FTREF/>
                     We encourage any interested person(s) to submit comments on the following questions and ask that you support your comments with relevant data or examples. We remind commenters that comments and data submitted in support of a comment are available to the public through our rulemaking files.
                </P>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         
                        <E T="03">See</E>
                         75 FR 49423 (Aug. 13, 2010), 75 FR 52283 (Aug. 25, 2010), and 76 FR 5292 (Jan. 31, 2011).
                    </P>
                </FTNT>
                <P>1. What core principles would be most important in FCA's development of new standards of creditworthiness?</P>
                <P>2. What qualitative and quantitative standards would FCA need to set to implement an approach that relied on the Farmer Mac to generate internal estimates of counterparty risk exposures? What are the strengths and weaknesses of such an approach?</P>
                <P>3. Is it important that FCA's approach to replacing its reliance on credit rating agency data be consistent with that of other financial regulators or with those of other Farm Credit System institutions? If so, how important and why?</P>
                <P>4. What specific creditworthiness or investment criteria should FCA use in its RBCST regulation?</P>
                <P>5. What types of objective criteria should be used to differentiate credit exposures and apply meaningful counterparty risk estimates in the RBCST?</P>
                <P>6. Should different criteria be used for different broad classes of investments or exposures? If so, what perverse incentives or other unintended consequences could that lead to? For example, could criteria that are perceived to be more flexible or subjective for a given asset class incent the regulated entity to accept a proportion of exposure to that asset class relative to its entire program (or non-program) portfolio that it might deem excessive without that incentive?</P>
                <P>7. What approach would estimate a meaningful and consistent level of counterparty risk for a variety of exposures by employing publicly available qualitative and quantitative metrics, such as individual obligor credit spreads and/or financial ratio analysis to estimate probability of default and recovery rates?</P>
                <P>
                    8. Alternatively, could such estimates be reasonably made at the level of the market (
                    <E T="03">e.g.,</E>
                     identifying an index of industry sector spreads and stratifying spreads into certain ranges) and mapped to loss rates set by FCA?
                </P>
                <P>9. How might a set of loss rates be developed for each spread stratum?</P>
                <P>10. Are there any existing objective tools or approaches that could readily replace references to ratings issued by NRSROs in the RBCST?</P>
                <P>
                    11. What other approaches or methodologies not discussed above should FCA consider?
                    <PRTPAGE P="35141"/>
                </P>
                <P>12. What methodologies or approaches should FCA consider to more explicitly incorporate a derivatives counterparty exposure charge into the RBCST?</P>
                <P>
                    13. What is the best manner of evaluating minimum capital requirements on derivative counterparty exposures in the RBCST and should a pre-processing model be constructed (
                    <E T="03">i.e.,</E>
                     a sub-model used to derive inputs into the RBCST) to represent this risk—both in terms of missed individual contractual cash flows as well the replacement cost on defaulted derivatives? If so, how should replacement costs be estimated?
                </P>
                <P>14. Should Farmer Mac be required to include strategies in its marketing plans that address how its secondary market programs and products will be offered to all qualified borrowers, including:</P>
                <P>(a) Minorities, the disabled, and women;</P>
                <P>(b) Young, beginning, small, and family farms and cooperatives; or</P>
                <P>(c) Non-traditional agricultural producers, such as local food systems, organic or specialty crop farmers and the lenders who serve them? Why or why not?</P>
                <P>
                    15. Should Farmer Mac's marketing plans set quantitative goals to increase purchases of, or commitments to purchase, loans to young, beginning, small, and family farms, and those owned or operated by minorities, the disabled, and women? If so, what would be the best method to apply such goals to rural utility cooperatives (
                    <E T="03">e.g.,</E>
                     minority-managed cooperatives or cooperatives that serve predominantly minority residential customers or minority-owned commercial customers)?
                </P>
                <P>16. To what extent should FCA regulations require Farmer Mac to develop a human capital plan as part of its strategic and operational business plan to foster diversity in its workforce and succession planning?</P>
                <SIG>
                    <DATED>Dated: June 10, 2011.</DATED>
                    <NAME>Mary Alice Donner,</NAME>
                    <TITLE>Acting Secretary, Farm Credit Administration Board.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-14985 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6705-01-P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="N">COMMODITY FUTURES TRADING COMMISSION</AGENCY>
                <CFR>17 CFR Parts 22 and 190</CFR>
                <RIN>RIN Number 3038-AC99</RIN>
                <SUBJECT>Protection of Cleared Swaps Customer Contracts and Collateral; Conforming Amendments to the Commodity Broker Bankruptcy Provisions; Correction</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Commodity Futures Trading Commission.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of proposed rulemaking; Correction.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        This document corrects the formatting of text and charts published in the 
                        <E T="04">Federal Register</E>
                         of June 09, 2011 (76 FR 33818), regarding Protection of Cleared Swaps Customer Contracts and Collateral; Conforming Amendments to the Commodity Broker Bankruptcy Provisions.
                    </P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Robert Wasserman, 202-418-5092 or M. Laura Astrada, 202-418-7622.</P>
                    <HD SOURCE="HD1">Correction</HD>
                    <P>In proposed rule document 2011-10737, in the issue of Thursday, June 09, 2011, on page 33864, in the last column, the text which begins “1. Sufficient Funds to Meet Non-XM and XM Customer Claims:” through to the end of the chart on page 33877 should be replaced with the following:</P>
                    <BILCOD>BILLING CODE-P</BILCOD>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="35142"/>
                        <GID>EP16JN11.007</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="35143"/>
                        <GID>EP16JN11.008</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="616">
                        <PRTPAGE P="35144"/>
                        <GID>EP16JN11.009</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="630">
                        <PRTPAGE P="35145"/>
                        <GID>EP16JN11.010</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="35146"/>
                        <GID>EP16JN11.011</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="634">
                        <PRTPAGE P="35147"/>
                        <GID>EP16JN11.012</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="639">
                        <PRTPAGE P="35148"/>
                        <GID>EP16JN11.013</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="631">
                        <PRTPAGE P="35149"/>
                        <GID>EP16JN11.014</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="35150"/>
                        <GID>EP16JN11.015</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="634">
                        <PRTPAGE P="35151"/>
                        <GID>EP16JN11.016</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="35152"/>
                        <GID>EP16JN11.017</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="630">
                        <PRTPAGE P="35153"/>
                        <GID>EP16JN11.018</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="633">
                        <PRTPAGE P="35154"/>
                        <GID>EP16JN11.019</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="637">
                        <PRTPAGE P="35155"/>
                        <GID>EP16JN11.020</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="629">
                        <PRTPAGE P="35156"/>
                        <GID>EP16JN11.021</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="633">
                        <PRTPAGE P="35157"/>
                        <GID>EP16JN11.022</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="636">
                        <PRTPAGE P="35158"/>
                        <GID>EP16JN11.023</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="35159"/>
                        <GID>EP16JN11.024</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="35160"/>
                        <GID>EP16JN11.025</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="635">
                        <PRTPAGE P="35161"/>
                        <GID>EP16JN11.026</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="282">
                        <PRTPAGE P="35162"/>
                        <GID>EP16JN11.027</GID>
                    </GPH>
                    <SIG>
                        <DATED>Issued in Washington, DC, on June 10, 2011 by the Commission.</DATED>
                        <NAME>David A. Stawick,</NAME>
                        <TITLE>Secretary of the Commission.</TITLE>
                    </SIG>
                </FURINF>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-14907 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE-C</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF VETERANS AFFAIRS</AGENCY>
                <CFR>38 CFR Part 17</CFR>
                <RIN>RIN 2900-AN51</RIN>
                <SUBJECT>Service Dogs</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Department of Veterans Affairs.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Proposed rule.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Department of Veterans Affairs (VA) proposes to amend its regulations concerning veterans in need of service dogs. Under current regulations, VA provides benefits to veterans with guide dogs, and this rulemaking would broaden and clarify those benefits. This rulemaking would also implement new benefits related to service dogs.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be received by VA on or before August 15, 2011.</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 (02REG), Department of Veterans Affairs, 810 Vermont Ave., NW., Room 1068, Washington, DC 20420; or by fax to (202) 273-9026. Comments should indicate that they are submitted in response to “RIN 2900-AN51—Service Dogs.” 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) 461-4902 for an appointment. (This is not a toll-free number.) In addition, during the comment period, comments may be viewed online through the Federal Docket Management System (FDMS) at h
                        <E T="03">ttp://www.Regulations.gov.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Neal Eckrich, Office of Patient Care Services (113), Veterans Health Administration, Department of Veterans Affairs, 810 Vermont Avenue, NW., Washington, DC 20420, (202) 461-1804. (This is not a toll-free number.)</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>Pursuant to 38 U.S.C. 1714(b) and (c), VA may provide to veterans enrolled under 38 U.S.C. 1705 guide dogs trained for the aid of people who are blind and service dogs trained for the aid of the hearing impaired or persons with a spinal cord injury or dysfunction or other chronic impairment that substantially limits mobility. Under section 1714(d), VA is also authorized to provide certain travel expenses related to the provision of such dogs.</P>
                <P>
                    In 1961, VA promulgated 38 CFR 17.118(a) (recodified as current 38 CFR 17.154(a) in 1996) restating the statutory language, which at that time limited VA's authority to the provision of guide dogs for blind veterans. Under both the statutory and regulatory language VA may provide or furnish a guide dog to a veteran but is not required to do so. VA interpreted “provide” in section 1714 and “furnished” in § 17.154(a) to mean that VA need not actually purchase or acquire dogs for eligible veterans if there is an appropriate alternative. (We also note that nothing in 38 U.S.C. 1714 requires VA to provide a dog to a disabled veteran—the statutory authority is that we “may” do so). Accordingly, it has long been VA's policy to apply current § 17.154(a) by recognizing guide dogs that are obtained by the veteran from private (usually non-profit) organizations dedicated to training guide dogs. In this manner, we can rely on the professional expertise of these organizations without having to house the animals and hire trainers. Currently, VA regulations recognize only guide dogs and not service dogs. To assist the veteran, VA provides financial assistance for veterinary care, and provides hardware required by the dog at no cost to the veteran. The provision of travel benefits is authorized by current § 17.154(a), and the provision of hardware is authorized by current § 17.154(b). This proposed rule would authorize VA to provide benefits for 
                    <PRTPAGE P="35163"/>
                    eligible veterans in need of service dogs, and clearly define the benefit.
                </P>
                <P>In 2001, Congress amended section 1714 to provide that VA may also provide service dogs for veterans with other disabilities. See Department of Veterans Affairs Health Care Programs Enhancement Act of 2001, Public Law 107-135 (2001). This rulemaking would implement that statutory amendment and would establish a single regulation relating to the provision of assistive dogs by VA. In so doing, we would remove current § 17.154(a) and establish the criteria proposed in § 17.148 so that the proposed rule would be the only regulatory authority for benefits related to service dogs. As explained below, the proposed rule would offer the same travel benefit offered under current § 17.154(a). The proposed rule would also clarify that VA interprets section 1714 as authorizing the provision of veterinary-care benefits and would establish a clear procedure for awarding such benefits.</P>
                <P>Proposed paragraph (a) would define service dogs as “guide or service dogs prescribed for a disabled veteran under this section.” This rule would provide the same benefit to all eligible veterans, so it is unnecessary to distinguish dogs by the services that they provide. For example, we do not use the term “guide dogs”, which appears under current 38 CFR 17.154, because for the purposes of this rulemaking, veterans who are eligible due to blindness would receive the same benefit.</P>
                <P>Proposed paragraph (b) would establish the clinical requirements to obtain service-dog benefits. First, we would authorize benefits only if the veteran is diagnosed as having a visual, hearing, or substantial mobility impairment. These requirements incorporate the eligibility criteria in section 1714. Second, we would require a clinical determination by a VA clinician, which would be based upon the clinician's medical judgment that “it is optimal for the veteran to manage such impairment and live independently through the assistance of a trained service dog.” By this, we intend to exclude situations in which a VA clinician's medical judgment indicates that there are means other than a dog, such as technological devices or rehabilitative techniques, which would enable and encourage the veteran to live independently. To emphasize this point, we would note that “[i]f other means (such as technological devices or rehabilitative therapy) will provide the same level of independence, then VA will not authorize benefits under this section.” VA does not intend to allow cost or any other factors to discourage the use of new technologies and equipment to maximize the independence of veterans. We believe that providing VA with discretion to choose between a service dog or assistive technology based on medical judgment rather than cost-effectiveness would ensure that VA's patients receive the highest quality of care that the VA-system can provide.</P>
                <P>Third, for the purposes of this section, we would define substantial mobility impairment as a spinal cord injury or dysfunction or other chronic impairment that substantially limits mobility. In providing guide-dog benefits, Congress intended to assist a group of veterans whose visual impairment prevents them from physically moving about in society. In providing service-dog benefits for veterans with hearing or spinal cord injuries or other chronic impairment that substantially limits mobility, Congress intended to help veterans with physical limitations. Both of these benefits increase a veteran's overall ability to move independently and safely in his or her home, community, or both. However, the statute is silent as to a veteran who can see and who does not have an injury that prevents full range of motion but who nevertheless cannot move independently and safely in his or her home, community, or both. Therefore, we would interpret chronic impairment that substantially limits mobility to include, but not be limited to, disabilities such as a traumatic brain injury that compromises the ability to make appropriate decisions based on environmental cues such as traffic lights or a seizure disorder that renders a veteran immobile during and after a seizure event.</P>
                <P>In 2009, Congress authorized VA to provide service dogs for the aid of persons with mental illnesses by amending section 1714. Although VA welcomes the possibility that trained dogs may provide valuable services to veterans diagnosed with certain mental illness, at this time we do not have any scientific data to determine, from a purely clinical standpoint, whether or when service dogs are most appropriately provided to veterans with mental illness, including post-traumatic stress disorder. In the National Defense Authorization Act for Fiscal Year 2010, Pub. L. 111-84 (2009), Congress mandated a 3-year study on the effectiveness of dogs for mental health purposes. The results of this study will help us learn more about the services that trained dogs can provide for veterans diagnosed with mental health conditions. Upon the completion of the study and analysis of its results, VA may revise its regulations in order to provide this service to our veterans.</P>
                <P>Proposed paragraph (c) would establish criteria for obtaining a service dog recognized under this section for purposes of obtaining benefits. Under paragraphs (c)(1) and (2), we would recognize service dogs obtained through an organization that is accredited by Assistance Dogs International (ADI) or the International Guide Dog Federation (IGDF). Proof of completion would be established by a certificate from the organization. ADI is an international coalition of nonprofit organizations that train and place service dogs. ADI has established an accreditation procedure for service dog organizations, setting minimum standards for safety and cleanliness of the training facility, fair and ethical treatment of clients, proper health care for the dogs, humane training methods, screening the suitability of dogs and clients, matching dogs and clients, and compliance with all relevant laws. ADI does not accredit organizations that provide guide dogs—ADI only does so for service-dog organizations that train dogs to perform services for individuals with conditions other than blindness. Accreditation of guide-dog programs is done by IGDF, with whom ADI has a joint protocol. ADI will only accredit guide-dog programs if they are also involved in training service dogs, and even then ADI accredits only that portion of the training related to service dogs—IGDF accredits the guide-dog portion. IGDF does not accredit any non-guide dog programs. IGDF is an international coalition of member organizations. IGDF is committed to improving the guide dog industry throughout the world and has published standards that cover a wide range of activities conducted by guide dog organizations, such as organizational structure, fundraising, recordkeeping, technical matters relating to dog health and welfare, dog and client training, and school facilities.</P>
                <P>
                    VA has reviewed ADI's and IGDF's standards thoroughly, and we believe that they represent appropriate criteria for training and placing guide and service dogs. We are also unaware of any other organizations that similarly scrutinize the process of training and placing guide or service dogs. We note that there are no Federal regulations governing the training of guide or service dogs, and VA does not have the expertise, experience, or resources to develop independent criteria. Therefore, we would rely on ADI and IGDF accreditation to conclude that a dog is qualified and capable of performing the tasks that are clinically required by the medical determination prescribed under 
                    <PRTPAGE P="35164"/>
                    proposed paragraph (b)(2), i.e., that the dog will benefit the veteran in a way that other assistive means cannot.
                </P>
                <P>For dogs acquired before the effective date of this rule, we would require the veteran to provide a certificate showing that the veteran and dog have completed a training course offered by a guide or service dog organization in existence before such date. We would limit this authority to organizations that existed before the effective date of the regulation. The purpose of this paragraph is to ensure that veterans who obtained dogs prior to the publication of this regulation, but not through ADI or IGDF accredited organizations, would be eligible for the benefits prescribed by this regulation. We would allow veterans who obtained dogs through such non-accredited organizations up to 1 year after the effective date of this rule to obtain the required certification. Alternatively, the veteran and dog could obtain the certification from ADI or IGDF described under proposed paragraph (c)(1).</P>
                <P>Proposed paragraph (d) would outline the benefits provided by VA under this section. As required by section 1714(a) and (b), benefits would be based on the veteran being enrolled under 38 U.S.C. 1705.</P>
                <P>Although Congress has authorized VA to provide service dogs and has expressly authorized the payment of certain travel and incidental expenses related to a veteran's adjustment to the dog, Congress did not address certain important aspects of the program. Veterans who have been furnished a dog must also maintain the health of the dog, and most will also need to purchase and maintain hardware related to the use of the dog. Without financial assistance, some veterans may not be able to afford such veterinary care and hardware. We believe that providing service dogs under the statute necessarily includes providing veterinary treatment and hardware, and repairs to such hardware, required by the dog to perform in service to the veteran. Consistent with this interpretation of our statutory authority, we propose to authorize payments for the care of service dogs that will help maintain the dogs' ability to perform as service dogs. However, we would not provide assistance for additional expenses such as license tags, non-prescription food, grooming, insurance for personal injury, non-sedated dental cleanings, nail trimming, boarding, pet sitting or dog walking services, over-the-counter medications, or other goods and services not expressly prescribed by regulation. This limitation would help ensure that VA's service dog program is able to continue to provide critical assistance to a larger number of veterans and would ensure that the financial assistance provided by VA would not be used to provide services that are not directly related to the dogs' ability to provide assistive service. We believe that limiting benefits for service dogs to necessary veterinary care, hardware, repairs to hardware, and travel expenses associated with obtaining a dog is similarly within the scope of the benefit authorized by Congress.</P>
                <P>Under proposed paragraph (d)(1), we would provide, as the mechanism for providing payment for veterinary care, an insurance policy to every eligible veteran. Because VA does not employ veterinarians, we lack the expertise to directly provide veterinary care, or to determine whether care is medically appropriate. We also lack the resources to review whether a veterinarian is appropriately licensed or charges appropriate fees for veterinary care. Thus, we have determined that an insurance policy is the most efficient way to provide appropriate veterinary care under this section, and we would pay any premiums, copayments, or deductibles associated with the insurance policy.</P>
                <P>Under proposed paragraph (d)(1)(i), we would require that VA, and not the veteran will be billed for any premiums, copayments, or deductibles associated with the policy. This is to ensure that the veteran is not overburdened when obtaining care under this section. However, we would note that the policies could be subject to an annual cap, depending upon what policies are actually negotiated when this rule become effective. If an annual cap were in place, care that exceeds the maximum authorized by the policy would be the responsibility of the veteran. Annual caps are a common limitation on insurance policies for service dogs, and we intend to rely on the reasonable cost-control methodologies calculated by experts in the field of veterinary insurance. When determining which companies to form relationships with, of course, VA will carefully review the maximum amounts authorized for particular procedures, as well as any annual caps on expenditures, to ensure that our veterans are getting the best insurance plan possible. To further protect veterans, we would require that the policy ensure advance notice whenever reasonably possible that a particular treatment may exceed the policy's limits. Obviously, it may not be possible to provide advance notice when an animal requires emergency care; however, where a veterinarian prescribes a future treatment event or an ongoing course of treatment, the insurer should be expected to notify the veteran that he or she may have some financial responsibility. Proposed paragraph (d)(1)(ii) would require that the policy guarantee coverage for all treatment, subject to any annual caps that may be in place under the policy, including euthanasia, so long as it is determined to be medically necessary by a veterinarian recognized by the insurance carrier. This is to ensure that the policy does not exclude medically necessary treatment. Proposed paragraph (d)(1)(iii) would bar policies from excluding dogs with preexisting conditions that do not prevent the dog from being a service dog.</P>
                <P>Under proposed paragraph (d)(2), VA would provide any and all hardware clinically determined to be needed by the dog to perform its task. Such hardware would include standard equipment such as harnesses for service dogs. Often, service dogs will require certain hardware in order to perform specific tasks for the unique needs of each veteran, and VA would ensure that every veteran receives the equipment that fulfills his or her clinical needs. VA would also provide necessary repairs or replacements for such hardware. This is consistent with current practice. In order to obtain hardware and/or repairs, veterans would call the Prosthetics Office at their local VA Medical Center and specify the hardware needed or repairs to be made. The Office will then provide the necessary hardware or repairs.</P>
                <P>
                    Under paragraph (d)(3), we propose to implement 38 U.S.C. 1714(d), which allows VA to pay travel expenses “under the terms and conditions set forth in [38 U.S.C. 111]” for a veteran who is provided a service dog. We propose to implement this provision by considering such veterans as eligible beneficiaries under 38 CFR Part 70. This will facilitate administration of the benefit and will allow VA to avoid any additional expenses associated with establishing a “new” travel benefit. We believe that the language of 38 U.S.C. 1714(d) can be read to interpret obtaining a dog as “examination, treatment, or care” under 38 U.S.C. 111. In addition, 38 U.S.C. 111 limits eligibility to certain veterans. Most (if not all) veterans who would be eligible for a service dog will meet the eligibility requirements of 38 U.S.C. 111. For example, most will have a service-connected disability rated at 30 percent or more under 38 U.S.C. 111(b)(1)(B). However, we would explicitly state in the regulation that the limitations on eligibility found in section 111 (as well 
                    <PRTPAGE P="35165"/>
                    as in VA's implementing regulations in 38 CFR Part 70) will not limit eligibility for veterans seeking to obtain a dog. Again, we interpret section 1714(d) as authorizing payment of travel expenses associated with obtaining a service dog. Proposed paragraph (d)(4) would clarify the limitation of the benefits provided. We would exclude payment for any expenses that are not clinically prescribed by a veterinarian or otherwise authorized by the proposed rule. Our policy would be, in essence, to treat the dog as a surrogate for an assistive device, requiring that the veteran use the device responsibly and provide general care and maintenance. We would also clarify that VA will not take possession of, or responsibility for, the dog under any circumstances.
                </P>
                <P>Finally, under proposed paragraph (e), we would require that the dog maintain its ability to function as a service dog in order for benefits to be provided under this section. We would provide that, when VA learns from any source that the dog is unable to maintain its assistive role, or VA determines that the veteran no longer requires the dog from a clinical perspective, VA will provide the veteran at least 30 days notice before benefits are terminated. The determination of such continued ability will generally be made by either a veterinarian (if the issue involves the animal's health) or by a VA clinician (if the issue is whether the veteran still meets the clinical prerequisite for eligibility under paragraph (b)(2)). The veteran may, but is not required to, notify VA or the insurer that the dog is medically unable to maintain its role as a service dog. However, we note that VA will not provide the benefit for two dogs simultaneously, which is discussed in the introductory text of proposed paragraph (d), so VA must first terminate the coverage for the dog that is no longer performing its duties before it would cover the training of a new dog to perform such services for the veteran. Since the veteran may often be the first person to know whether the dog can no longer perform its duties, we would encourage the veteran to notify VA so that we may expedite the transfer of benefits to a new dog, and make any other clinically appropriate arrangements for the veteran as the new dog is trained.</P>
                <P>Current § 17.154(a) provides that VA may furnish a guide dog for blind veterans as well as travel expenses incurred by the veteran as a result of adjustment to the guide dog. Current § 17.154(b) provides that VA may supply mechanical and/or electronic equipment to beneficiaries to help overcome the handicap of blindness. In accordance with the proposed changes discussed above, we propose to revise § 17.154 by removing paragraph (a) and removing the designation of paragraph (b), and by making technical revisions to the title and language to accord with the removal of paragraph (a). It will continue to authorize VA to provide equipment to blind veterans.</P>
                <HD SOURCE="HD1">Effect of Rulemaking</HD>
                <P>We would rescind certain sections of the following VHA Handbooks, which contain conflicting provisions. We would rescind “Aids for the Blind and Visually Impaired,” 1173.05, paragraph 12, concerning issuance of guide dogs; “Eligibility,” 1173.1, paragraph 7(b)(1), referencing “veterinary treatment for guide dogs;” and “Furnishing Prosthetic Appliances and Services,” 1173.2, paragraph 4(a)(4), referencing “veterinary treatment for guide dogs.” Additionally, we would rescind the reference to “dog guide” in “Furnishing Prosthetic Appliances and Services,” 1173.2, paragraph 4(c)(a)(2)(b), which limits the Prosthetics Service Card amount to $100. Finally, we propose to amend the citations to current 38 CFR 17.154 to proposed § 17.148 and § 17.154 in “Benefits Overview,” 1601A.04, A-1(6) and A-7(22).</P>
                <HD SOURCE="HD1">Unfunded Mandates</HD>
                <P>The Unfunded Mandates Reform Act of 1995 requires, at 2 U.S.C. 1532, that agencies prepare an assessment of anticipated costs and benefits before issuing any rule that may result in an expenditure by state, local, and tribal governments, in the aggregate, or by the private sector, of $100 million or more (adjusted annually for inflation) in any given year. This proposed rule would have no such effect on state, local, and tribal governments, or on the private sector.</P>
                <HD SOURCE="HD1">Paperwork Reduction Act</HD>
                <P>This proposed rule includes provisions constituting collections of information under the Paperwork Reduction Act (44 U.S.C. 3501-3521) that require approval by the Office of Management and Budget (OMB). Accordingly, under section 3507(d) of the Act, VA has submitted a copy of this rulemaking to OMB for review. OMB assigns a control number for each collection of information it approves. Except for emergency approvals under 44 U.S.C. 3507(j), VA 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. Proposed § 17.148(c)(1) and (d)(2) contain collections of information under the Paperwork Reduction Act (44 U.S.C. 3501-3521). If OMB does not approve the collections of information as requested, VA will immediately remove the provisions containing a collection of information or take such other action as is directed by OMB.</P>
                <P>
                    Comments on the collections of information contained in this proposed rule should be submitted to the Office of Management and Budget, 
                    <E T="03">Attention:</E>
                     Desk Officer for the Department of Veterans Affairs, Office of Information and Regulatory Affairs, Washington, DC 20503, with copies sent by mail or hand delivery to: Director, Office of Regulation Policy and Management (02REG), Department of Veterans Affairs, 810 Vermont Ave., NW., Room 1068, Washington, DC 20420; fax to (202) 273-9026; or through 
                    <E T="03">http://www.Regulations.gov</E>
                    . Comments should indicate that they are submitted in response to “RIN 2900-AN51, Service Dogs.”
                </P>
                <P>
                    OMB is required to make a decision concerning the collections of information contained in this proposed rule between 30 and 60 days after publication of this document in the 
                    <E T="04">Federal Register</E>
                    . Therefore, a comment to OMB is best assured of having its full effect if OMB receives it within 30 days of publication. This does not affect the deadline for the public to comment on the proposed rule.
                </P>
                <P>VA considers comments by the public on proposed collections of information in—</P>
                <P>• Evaluating whether the proposed collections of information are necessary for the proper performance of the functions of VA, including whether the information will have practical utility;</P>
                <P>• Evaluating the accuracy of VA's estimate of the burden of the proposed collections of information, including the validity of the methodology and assumptions used;</P>
                <P>• Enhancing the quality, usefulness, and clarity of the information to be collected; and</P>
                <P>
                    • Minimizing the burden of the collections of information on those who are to respond, including through the use of appropriate automated, electronic, mechanical, or other technological collection techniques or other forms of information technology, 
                    <E T="03">e.g.,</E>
                     permitting electronic submission of responses.
                </P>
                <P>
                    The proposed amendments to title 38, CFR Chapter 17 contain collections of information under the Paperwork Reduction Act for which we are requesting approval by OMB. These collections of information are described 
                    <PRTPAGE P="35166"/>
                    immediately following this paragraph, under their respective titles.
                </P>
                <P>
                    <E T="03">Title:</E>
                     Service Dogs.
                </P>
                <P>
                    <E T="03">Summary of collection of information:</E>
                     The proposed rule at § 17.148(c) requires the veteran to either (1) provide a certificate of completion from an ADI or IGDF-certified organization if the service dog is acquired by the veteran after the publication of the final rule; or (2) provide a certificate of completion from any then-existing guide or service dog organization if the dog is acquired prior to publication of the final rule.
                </P>
                <P>
                    <E T="03">Description of the need for information and proposed use of information:</E>
                     This information is needed for VA to determine that the dog is suitable for the clinical needs of the veteran that it would be required to fulfill and is able to behave appropriately in public.
                </P>
                <P>
                    <E T="03">Description of likely respondents:</E>
                     Veterans.
                </P>
                <P>
                    <E T="03">Estimated number of respondents per year:</E>
                     Approximately 600 veterans will need to provide certification for existing service dogs, and approximately 100 veterans will obtain service dogs each year; therefore 700 submissions in year one and 100 submissions annually.
                </P>
                <P>
                    <E T="03">Estimated frequency of responses per year:</E>
                     Veterans will submit certification for approximately 600 existing service dogs and 100 new service dogs each year; 700 submissions in year one and 100 submissions each year thereafter.
                </P>
                <P>
                    <E T="03">Estimated total annual reporting and recordkeeping burden:</E>
                     It is expected that this burden will take less than 5 minutes per veteran, per dog. The estimated total annual reporting and recordkeeping burden is 3500 minutes in year one and 500 minutes each year thereafter.
                </P>
                <HD SOURCE="HD1">Executive Order 12866</HD>
                <P>Executive Order 12866 directs agencies to assess all costs and benefits of available regulatory alternatives and, when regulation is necessary, to select regulatory approaches that maximize net benefits (including potential economic, environmental, public health and safety, and other advantages; distributive impacts; and equity). The Executive Order classifies a “significant regulatory action,” requiring review by the Office of Management and Budget (OMB) unless OMB waives such review, as any regulatory action that is likely to result in a rule that may: (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; (2) create a serious inconsistency or otherwise interfere with an action taken or planned by another agency; (3) materially alter the budgetary impact of entitlements, grants, user fees, or loan programs or the rights and obligations of recipients thereof; or (4) raise novel legal or policy issues arising out of legal mandates, the President's priorities, or the principles set forth in the Executive Order.</P>
                <P>The economic, interagency, budgetary, legal, and policy implications of this regulatory action have been examined and it has been determined not to be a significant regulatory action under the Executive Order.</P>
                <HD SOURCE="HD1">Regulatory Flexibility Act</HD>
                <P>The Secretary hereby certifies that this proposed rule would not have a significant economic impact on a substantial number of small entities as they are defined in the Regulatory Flexibility Act, 5 U.S.C. 601-612. We believe that most service-dog providers that provide dogs to veterans are already accredited in accordance with the proposed rule. We do not believe that gaining accreditation should result in a significant financial burden, as the standards for approval by ADI and IGDF are reasonable thresholds that are generally expected and accepted within the industry. The approximate cost to be an accredited organization by IGDF is a one-time fee of $795, with an annual fee of $318 and a per unit fee of $39.45. The approximate cost to be an accredited organization by ADI is $1,000 every 5 years with annual fees of approximately $50. The vast majority of accredited programs do not provide dogs to veterans. Therefore, pursuant to 5 U.S.C. 605(b), this proposed rule is exempt from the initial and final regulatory flexibility analysis requirements of sections 603 and 604.</P>
                <HD SOURCE="HD1">Catalog of Federal Domestic Assistance Numbers</HD>
                <P>The Catalog of Federal Domestic Assistance numbers and titles are 64.009 Veterans Medical Care Benefits, 64.010 Veterans Nursing Home Care and 64.011 Veterans Dental Care.</P>
                <HD SOURCE="HD1">Signing Authority</HD>
                <P>The Secretary of Veterans Affairs, or designee, approved this document and authorized the undersigned to sign and submit the document to the Office of the Federal Register for publication electronically as an official document of the Department of Veterans Affairs. John R. Gingrich, Chief of Staff, Department of Veterans Affairs, approved this document on May 11, 2011, for publication.</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 38 CFR Part 17</HD>
                    <P>Administrative practice and procedure, Alcohol abuse, Alcoholism, Claims, Day care, Dental health, Drug abuse, Foreign relations, Government contracts, Grant programs—health, Government programs—veterans, Health care, Health facilities, Health professions, Health records, Homeless, Medical and dental schools, Medical devices, Medical research, Mental health programs, Nursing home care, Reporting and recordkeeping requirements, Scholarships and fellowships, Travel and transportation expenses, Veterans.</P>
                </LSTSUB>
                <SIG>
                    <DATED>Dated: June 13, 2011.</DATED>
                    <NAME>Robert C. McFetridge,</NAME>
                    <TITLE>Director, Regulation Policy and Management, Office of General Counsel, Department of Veterans Affairs.</TITLE>
                </SIG>
                <P>For the reasons stated in the preamble, VA proposes to amend 38 CFR part 17 as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 17—MEDICAL</HD>
                    <P>1. The authority citation for part 17 continues to read as follows:</P>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>38 U.S.C. 501, and as noted in specific sections.</P>
                    </AUTH>
                    <P>2. Add § 17.148 after the undesignated center heading “PROSTHETIC, SENSORY, AND REHABILITATIVE AIDS”, to read as follows:</P>
                    <SECTION>
                        <SECTNO>§ 17.148 </SECTNO>
                        <SUBJECT>Service dogs.</SUBJECT>
                        <P>
                            (a) 
                            <E T="03">Definitions.</E>
                             For the purposes of this section:
                        </P>
                        <P>
                            <E T="03">Service dogs</E>
                             are guide or service dogs prescribed for a disabled veteran under this section.
                        </P>
                        <P>
                            (b) 
                            <E T="03">Clinical requirements.</E>
                             VA will provide benefits under this section to a veteran with a service dog only if:
                        </P>
                        <P>(1) The veteran is diagnosed as having a visual, hearing, or substantial mobility impairment; and</P>
                        <P>(2) A VA clinician determines based upon medical judgment that it is optimal for the veteran to manage such impairment and live independently through the assistance of a trained service dog. Note: If other means (such as technological devices or rehabilitative therapy) will provide the same level of independence, then VA will not authorize benefits under this section.</P>
                        <P>
                            (3) For the purposes of this section, substantial mobility impairment means a spinal cord injury or dysfunction or other chronic impairment that substantially limits mobility. A chronic impairment that substantially limits 
                            <PRTPAGE P="35167"/>
                            mobility includes but is not limited to a traumatic brain injury that compromises a veteran's ability to make appropriate decisions based on environmental cues (
                            <E T="03">i.e.,</E>
                             traffic lights or dangerous obstacles) or a seizure disorder that causes a veteran to become immobile during and after a seizure event.
                        </P>
                        <P>
                            (c) 
                            <E T="03">Recognized service dogs.</E>
                             VA will recognize, for the purpose of paying benefits under this section, the following service dogs:
                        </P>
                        <P>(1) The dog and veteran must have successfully completed a training program offered by an organization accredited by Assistance Dogs International or the International Guide Dog Federation, or both (for dogs that perform both service- and guide-dog assistance). The veteran must provide to VA a certificate showing successful completion issued by the accredited organization that provided such program.</P>
                        <P>
                            (2) Dogs obtained before [
                            <E T="03">date of publication of final rule in the</E>
                              
                            <E T="7462">Federal Register</E>
                            ] will be recognized if a guide or service dog training organization in existence before [
                            <E T="03">date of publication of final rule in the</E>
                              
                            <E T="7462">Federal Register</E>
                            ] certifies that the veteran and dog, as a team, successfully completed, no later than [
                            <E T="03">date 1 year after date of publication of final rule in the </E>
                              
                            <E T="7462">Federal Register</E>
                            ], a training program offered by that training organization. The veteran must provide to VA a certificate showing successful completion issued by the organization that provided such program. Alternatively, the veteran and dog will be recognized if they comply with paragraph (c)(1) of this section.
                        </P>
                        <P>
                            (d) 
                            <E T="03">Authorized benefits.</E>
                             VA will provide to a veteran enrolled under 38 U.S.C. 1705 only the following benefits for one service dog at any given time in accordance with this section:
                        </P>
                        <P>(1) A commercially available insurance policy that meets the following minimum requirements:</P>
                        <P>(i) VA, and not the veteran, will be billed for any premiums, copayments, or deductibles associated with the policy; however, the veteran will be responsible for any cost of care that exceeds the maximum amount authorized by the policy for a particular procedure, course of treatment, or policy year. If a dog requires care that may exceed the policy's limit, the insurer will, whenever reasonably possible under the circumstances, provide advance notice to the veteran.</P>
                        <P>(ii) The policy will guarantee coverage for all treatment (and associated prescription medications), subject to premiums, copayments, deductibles or annual caps, determined to be medically necessary, including euthanasia, by any veterinarian who meets the requirements of the insurer.</P>
                        <P>(iii) The policy will not exclude dogs with preexisting conditions that do not prevent the dog from being a service dog.</P>
                        <P>(2) Hardware, or repairs or replacements for hardware, that are clinically determined to be required by the dog to perform the tasks necessary to assist the veteran with his or her impairment. To obtain such devices, the veteran must contact the Prosthetic and Sensory Aids Service at his or her local VA medical facility and request the items needed.</P>
                        <P>(3) Payments for travel expenses associated with obtaining a dog under paragraph (c)(1) of this section. Travel costs will be provided only to a veteran who has been prescribed a service dog by a VA clinician under paragraph (b) of this section. Payments will be made as if the veteran is an eligible beneficiary under 38 U.S.C. 111 and 38 CFR part 70, without regard to whether the veteran meets the eligibility criteria as set for in 38 CFR part 70.</P>
                        <P>(4) The veteran is responsible for procuring and paying for any items or expenses not authorized by this section. This means that VA will not pay for items such as license tags, non-prescription food, grooming, insurance for personal injury, non-sedated dental cleanings, nail trimming, boarding, pet-sitting or dog-walking services, over-the-counter medications, or other goods and services not covered by the policy. The dog is not the property of VA; VA will never assume responsibility for, or take possession of, any service dog.</P>
                        <P>
                            (e) 
                            <E T="03">Dog must maintain ability to function as a service dog.</E>
                             To continue to receive benefits under this section, the service dog must maintain its ability to function as a service dog. If at any time VA learns from any source that the dog is medically unable to maintain that role, or VA makes a clinical determination that the veteran no longer requires the dog, VA will provide at least 30 days notice to the veteran before benefits will no longer be authorized.
                        </P>
                        <SECAUTH>(Authority 38 U.S.C. 501, 1714)</SECAUTH>
                        <P>3. Revise § 17.154 to read as follows:</P>
                    </SECTION>
                    <SECTION>
                        <SECTNO>§ 17.154 </SECTNO>
                        <SUBJECT>Equipment for blind veterans.</SUBJECT>
                        <P>VA may furnish mechanical and/or electronic equipment considered necessary as aids to overcoming the handicap of blindness to blind ex-members of the Armed Forces entitled to disability compensation for a service-connected disability.</P>
                        <SECAUTH>(Authority: 38 U.S.C. 1714)</SECAUTH>
                    </SECTION>
                </PART>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-14933 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 8320-01-P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="N">ENVIRONMENTAL PROTECTION AGENCY</AGENCY>
                <CFR>40 CFR Part 52</CFR>
                <DEPDOC>[EPA-R09-OAR-2011-0312; FRL-9319-8]</DEPDOC>
                <SUBJECT>Revisions to the California State Implementation Plan, San Joaquin Valley Unified Air Pollution Control District (SJVUAPCD)</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 revisions to the SJVUAPCD portion of the California State Implementation Plan (SIP). These revisions concern volatile organic compounds (VOCs) from architectural coatings. We are approving a local rule that regulates these emission sources under the Clean Air Act as amended in 1990 (CAA or the Act). We are taking comments on this proposal and plan to follow with a final action.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Any comments must arrive by July 18, 2011.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Submit comments, identified by docket number EPA-R09-OAR-2011-0312, by one of the following methods:</P>
                    <P>
                        1. 
                        <E T="03">Federal eRulemaking Portal: http://www.regulations.gov</E>
                        . Follow the on-line instructions.
                    </P>
                    <P>
                        2. 
                        <E T="03">E-mail: steckel.andrew@epa.gov.</E>
                    </P>
                    <P>
                        3. 
                        <E T="03">Mail or deliver:</E>
                         Andrew Steckel (Air-4), U.S. Environmental Protection Agency Region IX, 75 Hawthorne Street, San Francisco, CA 94105-3901.
                    </P>
                    <P>
                        <E T="03">Instructions:</E>
                         All comments will be included in the public docket without change and may be made available online at 
                        <E T="03">http://www.regulations.gov,</E>
                         including any personal information provided, unless the comment includes Confidential Business Information (CBI) or other information whose disclosure is restricted by statute. Information that you consider CBI or otherwise protected should be clearly identified as such and should not be submitted through 
                        <E T="03">http://www.regulations.gov</E>
                         or e-mail. 
                        <E T="03">http://www.regulations.gov</E>
                         is an “anonymous access” system, and EPA will not know your identity or contact information unless you provide it in the body of your comment. If you send e-mail directly to EPA, your e-mail address will be automatically captured and included as part of the public comment. If EPA cannot read your 
                        <PRTPAGE P="35168"/>
                        comment due to technical difficulties and cannot contact you for clarification, EPA may not be able to consider your comment.
                    </P>
                    <P>
                        <E T="03">Docket:</E>
                         Generally, documents in the docket for this action are available electronically at 
                        <E T="03">http://www.regulations.gov</E>
                         and in hard copy at EPA Region IX, 75 Hawthorne Street, San Francisco, California. While all documents in the docket are listed at 
                        <E T="03">http://www.regulations.gov,</E>
                         some information may be publicly available only at the hard copy location (
                        <E T="03">e.g.,</E>
                         copyrighted material, large maps), and some may not be publicly available in either location (
                        <E T="03">e.g.,</E>
                         CBI). To inspect the hard copy materials, please schedule an appointment during normal business hours with the contact listed in the 
                        <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                         section.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        David Grounds, EPA Region IX, (415) 972-3019, 
                        <E T="03">grounds.david@epa.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>Throughout this document, “we,” “us” and “our” refer to EPA.</P>
                <EXTRACT>
                    <HD SOURCE="HD1">Table of Contents</HD>
                    <FP SOURCE="FP-2">I. The State's Submittal</FP>
                    <FP SOURCE="FP1-2">A. What rule did the State submit?</FP>
                    <FP SOURCE="FP1-2">B. Are there other versions of this rule?</FP>
                    <FP SOURCE="FP1-2">C. What is the purpose of the submitted rule revision?</FP>
                    <FP SOURCE="FP-2">II. EPA's Evaluation and Action</FP>
                    <FP SOURCE="FP1-2">A. How is EPA evaluating the rule?</FP>
                    <FP SOURCE="FP1-2">B. Does the rule meet the evaluation criteria?</FP>
                    <FP SOURCE="FP1-2">C. EPA Recommendations To Further Improve the Rule</FP>
                    <FP SOURCE="FP1-2">D. Public Comment and Final Action</FP>
                    <FP SOURCE="FP-2">III. Statutory and Executive Order Reviews</FP>
                </EXTRACT>
                <HD SOURCE="HD1">I. The State's Submittal</HD>
                <HD SOURCE="HD2">A. What rule did the State submit?</HD>
                <P>Table 1 lists the rule addressed by this proposal with the dates that it was adopted by the local air agency and submitted by the California Air Resources Board (CARB).</P>
                <GPOTABLE COLS="5" OPTS="L2,i1" CDEF="s25,12,r100,12,12">
                    <TTITLE>Table 1—Submitted Rules</TTITLE>
                    <BOXHD>
                        <CHED H="1">Local agency</CHED>
                        <CHED H="1">Rule No.</CHED>
                        <CHED H="1">Rule title</CHED>
                        <CHED H="1">Adopted</CHED>
                        <CHED H="1">Submitted</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">SJVUAPCD</ENT>
                        <ENT>4601</ENT>
                        <ENT>Architectural Coatings</ENT>
                        <ENT>12/17/09</ENT>
                        <ENT>5/17/10</ENT>
                    </ROW>
                </GPOTABLE>
                <P>On June 8, 2010, EPA determined that the submittal for SJVUAPCD Rule 4601 met the completeness criteria in 40 CFR part 51, Appendix V, which must be met before formal EPA review.</P>
                <HD SOURCE="HD2">B. Are there other versions of this rule?</HD>
                <P>We finalized a limited approval/limited disapproval on an earlier version of Rule 4601 into the SIP on 1/2/04 (69 FR 34). No versions were adopted since then besides the 12/17/09 version.</P>
                <HD SOURCE="HD2">C. What is the purpose of the submitted rule revision?</HD>
                <P>VOCs help produce ground-level ozone and smog, which harm human health and the environment. Section 110(a) of the CAA requires States to submit regulations that control VOC emissions. Rule 4601 limits VOC emissions during architectural coating, storage and clean-up operations. EPA's technical support document (TSD) has more information about this rule.</P>
                <HD SOURCE="HD1">II. EPA's Evaluation and Action</HD>
                <HD SOURCE="HD2">A. How is EPA evaluating the rule?</HD>
                <P>Generally, SIP rules must be enforceable (see section 110(a) of the Act), must require Reasonably Available Control Technology (RACT) for each category of sources covered by a Control Techniques Guidelines (CTG) document as well as each major source in nonattainment areas (see sections 182(a)(2) and (b)(2)), and must not relax existing requirements (see sections 110(l) and 193). The SJVUAPCD regulates an ozone nonattainment area (see 40 CFR part 81), but Rule 4601 does not regulate major sources, so Rule 4601 need not fulfill RACT.</P>
                <P>Guidance and policy documents that we use to evaluate enforceability and other requirements consistently include the following:</P>
                <P>1. “Issues Relating to VOC Regulation Cutpoints, Deficiencies, and Deviations,” EPA, May 25, 1988 (the Bluebook).</P>
                <P>2. “Guidance Document for Correcting Common VOC &amp; Other Rule Deficiencies,” EPA Region 9, August 21, 2001 (the Little Bluebook).</P>
                <P>3. Control of Volatile Organic Emissions from Existing Stationary Sources, Volume I: Control Methods for Surface Coating Operations (EPA-450/2-76-028, 11/76, NTIS PB-260-386).</P>
                <P>4. National VOC Emission Standards for Architectural Coatings (40 CFR 59 Subpart D, 9/11/98).</P>
                <P>5. Technical Review Group's Proposed Architectural Coatings SCM (CARB, 1989).</P>
                <P>6. Suggested Control Measure for Architectural Coatings (CARB, 2000).</P>
                <HD SOURCE="HD2">B. Does the rule meet the evaluation criteria?</HD>
                <P>We believe this rule is consistent with the relevant policy and guidance regarding enforceability, RACT, and SIP relaxations. The TSD has more information on our evaluation.</P>
                <HD SOURCE="HD2">C. EPA Recommendations To Further Improve the Rule</HD>
                <P>The TSD describes one additional rule revision that we recommend for the next time the local agency modifies the rule but is not currently the basis for rule disapproval.</P>
                <HD SOURCE="HD2">D. Public Comment and Final Action</HD>
                <P>Because EPA believes the submitted rule fulfills all relevant requirements, we are proposing to fully approve it as described in section 110(k)(3) of the Act. We will accept comments from the public on this proposal for the next 30 days. Unless we receive convincing new information during the comment period, we intend to publish a final approval action that will incorporate this rule into the federally enforceable SIP.</P>
                <HD SOURCE="HD1">III. Statutory and Executive Order Reviews</HD>
                <P>Under the Clean Air Act, the Administrator is required to approve a SIP submission that complies with the provisions of the Act and applicable Federal regulations. 42 U.S.C. 7410(k); 40 CFR 52.02(a). Thus, in reviewing SIP submissions, EPA's role is to approve State choices, provided that they meet the criteria of the Clean Air Act. Accordingly, this action merely approves State law as meeting Federal requirements and does not impose additional requirements beyond those imposed by State law. For that reason, this action:</P>
                <P>• Is not a “significant regulatory action” subject to review by the Office of Management and Budget under Executive Order 12866 (58 FR 51735, October 4, 1993);</P>
                <P>
                    • Does not impose an information collection burden under the provisions of the Paperwork Reduction Act (44 U.S.C. 3501 
                    <E T="03">et seq.</E>
                    );
                </P>
                <P>
                    • Is certified as not having 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>
                    );
                    <PRTPAGE P="35169"/>
                </P>
                <P>• Does not contain any unfunded mandate or significantly or uniquely affect small governments, as described in the Unfunded Mandates Reform Act of 1995 (Pub. L. 104-4);</P>
                <P>• Does not have Federalism implications as specified in Executive Order 13132 (64 FR 43255, August 10, 1999);</P>
                <P>• Is not an economically significant regulatory action based on health or safety risks subject to Executive Order 13045 (62 FR 19885, April 23, 1997);</P>
                <P>• Is not a significant regulatory action subject to Executive Order 13211 (66 FR 28355, May 22, 2001);</P>
                <P>• Is not subject to requirements of Section 12(d) of the National Technology Transfer and Advancement Act of 1995 (15 U.S.C. 272 note) because application of those requirements would be inconsistent with the Clean Air Act; and</P>
                <P>• Does not provide EPA with the discretionary authority to address disproportionate human health or environmental effects with practical, appropriate, and legally permissible methods under Executive Order 12898 (59 FR 7629, February 16, 1994).</P>
                <FP>In addition, this rule does not have tribal implications as specified by Executive Order 13175 (65 FR 67249, November 9, 2000), because the SIP is not approved to apply in Indian country located in the State, and EPA notes that it will not impose substantial direct costs on tribal governments or preempt tribal law.</FP>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 40 CFR Part 52</HD>
                    <P>Environmental protection, Air pollution control, Intergovernmental relations, Reporting and recordkeeping requirements, Volatile organic compounds.</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: May 19, 2011.</DATED>
                    <NAME>Jared Blumenfeld,</NAME>
                    <TITLE>Regional Administrator, Region IX.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-15000 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6560-50-P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
                <SUBAGY>Coast Guard</SUBAGY>
                <CFR>46 CFR Part 10</CFR>
                <DEPDOC>[Docket No. USCG-2004-17455]</DEPDOC>
                <RIN>RIN 1625-AA85</RIN>
                <SUBJECT>Validation of Merchant Mariners' Vital Information and Issuance of Coast Guard Merchant Mariner's Licenses and Certificates of Registry (MMLs)</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Coast Guard, DHS.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of intent with request for comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Coast Guard is advising the public of its intent to finalize regulations previously published as an interim rule on January 13, 2006. The IR was published to amend the maritime personnel licensing rules to include new security requirements when mariners apply for original, renewal, and raise-of-grade licenses and certificates of registry, but was never published as a final rule. Because of the lapse in time since the interim rule publication, the Coast Guard is seeking comments from the public on one remaining section of the interim rule that has remained unfinalized. The Coast Guard intends to finalize this one section of the interim rule.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be received on or before August 15, 2011.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may submit comments identified by docket number USCG-2004-17455 using any one of the following methods:</P>
                    <P>
                        (1) 
                        <E T="03">Federal eRulemaking Portal: http://www.regulations.gov.</E>
                    </P>
                    <P>
                        (2) 
                        <E T="03">Fax:</E>
                         202-493-2251.
                    </P>
                    <P>
                        (3) 
                        <E T="03">Mail:</E>
                         Docket Management Facility (M-30), U.S. Department of Transportation, West Building Ground Floor, Room W12-140, 1200 New Jersey Avenue, SE., Washington, DC 20590-0001.
                    </P>
                    <P>
                        (4) 
                        <E T="03">Hand delivery:</E>
                         Same as mail address above, between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays. The telephone number is 202-366-9329. To avoid duplication, please use only one of these four methods. See the “Public Participation and Request for Comments” portion of the 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                         section below for instructions on submitting comments.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        If you have questions on this proposed rule, call or e-mail Mr. Gerald Miante, Maritime Personnel Qualifications Division, Coast Guard; telephone 202-372-1407, e-mail 
                        <E T="03">Gerald.P.Miante@uscg.mil.</E>
                         If you have questions on viewing or submitting material to the docket, call Renee V. Wright, Program Manager, Docket Operations, telephone 202-366-9826.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <HD SOURCE="HD1">Request for Comments</HD>
                <P>
                    If you submit a comment, please include the docket number for this rulemaking (USCG-2004-17455), indicate the specific section of this document to which each comment applies, and provide a reason for each suggestion or recommendation. You may submit your comments and material online (via 
                    <E T="03">http://www.regulations.gov</E>
                    ) or by fax, mail, or hand delivery, but please use only one of these means. If you submit a comment online via 
                    <E T="03">http://www.regulations.gov,</E>
                     it will be considered received by the Coast Guard when you successfully transmit the comment. If you fax, hand deliver, or mail your comment, it will be considered as having been received by the Coast Guard when it is received at the Docket Management Facility. We recommend that you include your name and a mailing address, an e-mail address, or a phone number in the body of your document so that we can contact you if we have questions regarding your submission.
                </P>
                <P>
                    To submit your comment online, go to 
                    <E T="03">http://www.regulations.gov,</E>
                     click on the “submit a comment” box, which will then become highlighted in blue. In the “Select Document Type” drop down menu select “Proposed Rule” and insert “USCG-2004-17455” in the “Enter Keyword or ID” box. Click “Search” then click on the balloon shape in the “Actions” column. If you submit your comments by mail or hand delivery, submit them in an unbound format, no larger than 8
                    <FR>1/2</FR>
                     by 11 inches, suitable for copying and electronic filing. If you submit comments by mail and would like to know that they reached the Facility, please enclose a stamped, self-addressed postcard or envelope.
                </P>
                <P>We will consider all comments and material received during the comment period and may change this proposed rule based on your comments.</P>
                <HD SOURCE="HD2">Viewing Comments and Documents</HD>
                <P>
                    To view comments, as well as documents mentioned in this preamble as being available in the docket, go to 
                    <E T="03">http://www.regulations.gov,</E>
                     click on the “read comments” box, which will then become highlighted in blue. In the “Enter Keyword or ID” box insert “USCG-2004-17455” and click “Search.” Click the “Open Docket 
                    <PRTPAGE P="35170"/>
                    Folder” in the “Actions” column. You may also visit the Docket Management Facility in Room W12-140 on the ground floor of the Department of Transportation West Building, 1200 New Jersey Avenue, SE., Washington, DC 20590, between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays. We have an agreement with the Department of Transportation to use the Docket Management Facility.
                </P>
                <HD SOURCE="HD2">Privacy Act</HD>
                <P>
                    Anyone can search the electronic form of 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 a Privacy Act notice regarding our public dockets in the January 17, 2008, issue of the 
                    <E T="04">Federal Register</E>
                     (73 FR 3316).
                </P>
                <HD SOURCE="HD2">Public Meeting</HD>
                <P>
                    We do not now plan to hold a public meeting. But you may submit a request for one on or before July 6, 2011 using one of the four methods specified under 
                    <E T="02">ADDRESSES</E>
                    . Please explain why you believe a public meeting would be beneficial. If we determine that one would aid this rulemaking, we will hold one at a time and place announced by a later notice in the 
                    <E T="04">Federal Register</E>
                    .
                </P>
                <P>
                    For information on facilities or services for individuals with disabilities or to request special assistance at the public meeting, contact Mr. Gerald Miante, Maritime Personnel Qualifications Division, Coast Guard; at the telephone number or e-mail address indicated under the 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                     section of this notice.
                </P>
                <HD SOURCE="HD1">Abbreviations</HD>
                <EXTRACT>
                    <FP SOURCE="FP-1">§  Section symbol</FP>
                    <FP SOURCE="FP-1">FBI Federal Bureau of Investigation</FP>
                    <FP SOURCE="FP-1">
                        FR 
                        <E T="04">Federal Register</E>
                    </FP>
                    <FP SOURCE="FP-1">MMC Merchant Mariner Credential</FP>
                    <FP SOURCE="FP-1">MMD Merchant Mariner's Document</FP>
                    <FP SOURCE="FP-1">NMC National Maritime Center</FP>
                    <FP SOURCE="FP-1">REC Regional Examination Center</FP>
                    <FP SOURCE="FP-1">TSA Transportation Security Administration</FP>
                    <FP SOURCE="FP-1">TWIC Transportation Worker Identification Credential</FP>
                    <FP SOURCE="FP-1">U.S.C. U.S. Code</FP>
                </EXTRACT>
                <HD SOURCE="HD1">Basis and Purpose</HD>
                <P>
                    On January 13, 2006, the Coast Guard published in the 
                    <E T="04">Federal Register</E>
                     (71 FR 2154) an interim rule with request for comments. The interim rule described maritime personnel licensing rules to include new security requirements when mariners apply for original, renewal, and raise-of-grade licenses and certificates of registry. However, subsequent rulemakings have addressed the majority of the interim rule provisions. As a result, the Coast Guard intends to finalize the single remaining section that has not been addressed in subsequent rulemakings.
                </P>
                <P>
                    The most recent significant rulemaking documents for rulemakings addressing the interim rule provisions are as follows: 
                    <SU>1</SU>
                    <FTREF/>
                     (1) Transportation Worker Identification Credential (TWIC) Implementation in the Maritime Sector; Hazardous Materials Endorsement for a Commercial Driver's License (74 FR 13114); (2) Seafarer's Training, Certification and Watchkeeping Code (STCW Code) (75 FR 13715); (3) Maritime Identification Credentials (74 FR 2865); (4) Consolidation of Merchant Mariner Qualification Credentials (74 FR 11196); (5) Training and Service Requirements for Merchant Marine Officers (73 FR 52789); (6) Large Passenger Vessel Crew Requirements (74 FR 47729); and (7) Crewmember Identification Documents (74 FR 19135).
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         To find all the rulemaking documents associated with the rulemakings listed here, you can view each rulemaking's docket on 
                        <E T="03">http://www.regulations.gov.</E>
                    </P>
                </FTNT>
                <P>
                    The one section of the January 13, 2006 interim rule that has remained unfinalized is 46 CFR 10.107(b): 
                    <E T="03">Definitions in subchapter B,</E>
                     specifically, the definition of “Dangerous drug” defined as “a narcotic drug, a controlled substance, or a controlled-substance analogue (as defined in section 102 of the Comprehensive Drug Abuse and Control Act of 1970 (21 U.S.C. 802)).” This definition was originally published in the January 13, 2006 interim rule as 46 CFR 10.103. The subsequent rulemaking, Consolidation of Merchant Mariner Credentials, redesignated 
                    <E T="03">Definitions in subchapter B,</E>
                     to 46 CFR 10.107(b) (74 FR 11216). Our intent is to finalize this one remaining section of the interim rule in its current designation, 46 CFR 10.107(b), and we are asking for comment on this section only. You may submit a comment to the docket using one of the methods specified under 
                    <E T="02">ADDRESSES</E>
                    .
                </P>
                <HD SOURCE="HD2">Discussion of Comments</HD>
                <P>
                    As a result of our request for comments in the interim rule published on January 13, 2006 in the 
                    <E T="04">Federal Register</E>
                     (71 FR 2154), the Coast Guard heard from 364 respondents representing mariners and the industry. The respondents submitted numerous comments addressing a wide range of issues related to the interim rule. A discussion of the comments follows.
                </P>
                <P>One hundred and eighty commenters noted that the interim rule requirements resulted in lost work time, long travel times, and excessive expenses to visit one of only 17 Regional Exam Centers (RECs) for fingerprinting and identification checks. The commenters felt this was extremely burdensome and created a hardship for most mariners who work or reside a long distance from the nearest REC. In addition, the commenters felt long wait times at the RECs increased this burden. This proposal, the commenters believed, would not make the industry any safer and would cost excessive time and money, plus make more work for the Coast Guard. The commenters also felt that the cost of maintaining one's credential may have been a deterrent for new entrants into the merchant marine.</P>
                <P>One hundred and fifty four commenters suggested that instead of requiring visits to one of only 17 RECs, the Coast Guard should have allowed mariners to visit local law enforcement, Department of Motor Vehicles/Motor Vehicle Administrations, Federal Bureau of Investigation (FBI), Coast Guard Marine Safety Units, and other field offices both temporary and permanent. Locations such as post offices can take secure fingerprints for purposes such as passports, so the commenters felt the Coast Guard should allow mariners more options. The commenters suggested that the Coast Guard could also send traveling teams of examiners to places where a large number of applicants might require fingerprints and identification checks, and that the Coast Guard could notify mariners, shipping companies, and unions (through the local media), as to when and where these teams would be at any given time.</P>
                <P>Fifteen commenters asked the Coast Guard to rescind the interim rule and work with industry to come up with a better system for fingerprint and identification checks. The commenters encouraged the Coast Guard to explore less burdensome and expensive ways to accomplish this goal while providing a way to ensure all licensed mariners are identified and properly screened.</P>
                <P>Thirteen commenters expressed fear that the RECs may not have the manpower to provide fingerprinting and ID verification service and that the system will be overwhelmed. The commenters suggested that a traveling Coast Guard team also visit maritime schools, where there was a large concentration of mariners wishing to renew or upgrade their credentials.</P>
                <P>
                    These problems have been overcome by other Coast Guard rulemakings, including the Transportation Workers Identification Card (TWIC) rulemaking, which requires certain mariners who hold Coast Guard credentials to also 
                    <PRTPAGE P="35171"/>
                    hold a TWIC, and the Consolidation of Merchant Mariner Qualification Credentials rulemaking, which removed the requirement to appear at an REC for those mariners who must enroll for a TWIC. Moreover, the Transportation Security Agency (TSA) has set up more than 150 enrollment centers around the country at which cards may be applied for and distributed. Those mariners who are not required to obtain a TWIC must still undergo another vetting process.
                </P>
                <P>Six commenters said the interim rule should not apply to operators of uninspected passenger vessels. Also, the commenter noted, some of those mariners work on inland lakes and rivers where there are no Maritime Transportation Security Act-regulated facilities and many work on small passenger vessels or family-owned offshore supply vessels where risk of a security incident is minimal.</P>
                <P>The Coast Guard publishes regulations that implement laws passed by Congress. Section 102 of the Maritime Transportation Security Act of 2002, as codified in Title 46 U.S. Code (46 U.S.C.) section 70105(b)(2), required that every Coast Guard-credentialed mariner, and other specific mariners, obtain a TWIC. As noted above, TSA maintains more than 150 enrollment centers. However, the Coast Guard Authorization Act of 2010 modified the TWIC requirement for mariners by limiting it to only those mariners who need unescorted access to secure spaces on vessels required to have a security plan under 46 U.S.C. chapter 701. However, those mariners who are not required to obtain a TWIC must still undergo a vetting process.</P>
                <P>Ten commenters stated that a Coast Guard license was not an identity document, and since a license was not an identity document, and was not intended to be one, a license heist was not a likely terrorist consideration.</P>
                <P>The commenters are correct that a Coast Guard license is not an identity document. The fact that identity checks and fingerprinting are required to obtain a license does not in itself mean that the Coast Guard considers the license to be an identity document. At the time the interim rule was published, the Merchant Mariner Document (MMD) was the primary identity document for a mariner. Currently, the TWIC serves as the primary identity document. A license or a Merchant Mariner Credential (MMC) is a professional qualification document. The Coast Guard is concerned that any vessel master not required to hold an MMD could be in a position to cause serious damage to terminals, bridges, and vessels along inland routes. Therefore, license-only holders must go through the fingerprinting and identification-check process.</P>
                <P>Five commenters suggested that the Coast Guard work with the TSA for fingerprinting and identification verification.</P>
                <P>The TWIC rulemaking has addressed this issue. Those mariners who are not required to obtain a TWIC must still undergo another vetting process.</P>
                <P>Fourteen commenters argued that fingerprints should only be necessary on the first issuance of an MMC because fingerprints do not change over time. Also, the commenters believed that renewal applicants already had their fingerprints on file, making it easy to detect if someone were to try to renew an existing license fraudulently.</P>
                <P>To apply for an MMC, a mariner must have a valid TWIC, which requires a full set of fingerprints at each 5-year renewal. Those mariners who are not required to obtain a TWIC must still undergo another vetting process, which also requires the submission of fingerprints in order to perform an updated background check. Fingerprints can change somewhat with age and especially after working with hand-abrasives, chemicals, etc. Additionally, fingerprints kept on file for long periods of time can also degrade, making them unsuitable for matching purposes.</P>
                <P>One commenter asked if a mariner renewing his or her license for continuity would be required to give fingerprints and undergo an ID check.</P>
                <P>No. Renewals for continuity credentials do not require fingerprints.</P>
                <P>Three commenters objected to using convictions in foreign courts against any mariner wishing to renew their credentials.</P>
                <P>
                    The TSA has jurisdiction over this matter. For additional information on disqualifying crimes, please see the TWIC final rule revising 49 CFR 1572.103: 
                    <E T="03">Disqualifying Criminal Offenses</E>
                     (72 FR 3492). Those mariners who are not required to obtain a TWIC must still undergo another vetting process.
                </P>
                <P>One commenter stated that the licensing procedure should not be halted while the Coast Guard produces a final rule on the issue.</P>
                <P>An interim rule was necessary from an enforcement perspective until the TWIC process became operable. Licensing was not suspended during this period.</P>
                <P>One commenter said it is unnecessary for a credential holder to give fingerprints and submit to an ID check in order to renew a credential because that credential did not enable access to security facilities or information.</P>
                <P>Fingerprinting and ID checks are needed to perform the background check required by Coast Guard regulations.</P>
                <P>Seven commenters stated that the Coast Guard should have allowed for public meetings in several locations around the nation before publication of the interim rule.</P>
                <P>
                    Given the urgency at the time, the Coast Guard decided to issue an interim rule to make the regulations effective as soon as possible. Due to subsequent rulemakings that provided an opportunity for public comment (see the “Basis and Purpose” section of the preamble), the Coast Guard, at this time, is only finalizing one remaining section of the interim rule that has remained unfinalized: § 10.107(b): 
                    <E T="03">Definitions in subchapter B,</E>
                     specifically, the definition of “Dangerous Drug”. We have determined that a public meeting is not necessary, but those wishing to request one should follow the procedures outlined above under “Public meeting”.
                </P>
                <P>Two commenters suggested that the renewal process for credentials take place at local Coast Guard stations.</P>
                <P>According to Coast Guard regulations, renewal applications are submitted to the National Maritime Center (NMC), through an REC, for evaluation and processing. The U.S. Coast Guard's NMC has recently completed restructuring and centralizing the Mariner Licensing and Documentation (MLD) program in order to reduce credential processing time, improve customer service, and ensure the consistency and quality of U.S. credentials issued to more than 210,000 mariners. The major components of this project include: Centralizing many MLD functions that had historically been performed at 17 RECs at the NMC, which is now located in Martinsburg, WV; streamlining credential production processes at the NMC; aligning the organization of the RECs so that they report directly to the NMC; and relocating the MLD program policy functions to U.S. Coast Guard headquarters.</P>
                <P>One commenter noted that mariners are required to give fingerprints and undergo ID checks every 5 years (and have to travel longer distances to do so) while aliens are required to renew their Green Cards every 10 years.</P>
                <P>The Coast Guard's 5-year renewal process is mandated by law (Title 46 U.S.C. 7106).</P>
                <P>
                    One commenter said that the results of the fingerprinting and background checks required every 5 years should not change past determinations and 
                    <PRTPAGE P="35172"/>
                    findings on individuals under the guise of security.
                </P>
                <P>The 5-year renewal process is in place to ensure the mariner's record is current. As discussed above, fingerprints can change somewhat with age and fingerprints kept on file for long periods of time can also degrade, making them unsuitable for matching purposes. Additionally, the Coast Guard must ensure background checks contain current information. Without this, there is a break in the chain of trust that could present a lapse of security.</P>
                <P>Two commenters stated that the requirement to give fingerprints at an REC each time a mariner wishes to renew or upgrade his or her credentials was arrogant and inconsiderate of the burden it places on the industry. The commenters believed it did little to enhance national security and asked why it was necessary to continually submit fingerprints at an REC while military personnel can submit fingerprints at their stations.</P>
                <P>Beginning April 15, 2009, TSA collects fingerprints and proof of identity and forwards that information to the NMC to perform a background check. The Coast Guard will also be able to obtain certain information from the record TSA created when the mariner enrolled for his or her TWIC. Therefore, mariners will not have to appear at an REC. Those mariners who are not required to obtain a TWIC must still undergo another vetting process.</P>
                <P>One commenter said it is unnecessary for mariners to submit identity verification for a duplicate credential if a credential is lost, stolen, or burned.</P>
                <P>The Coast Guard disagrees. When a duplicate credential is issued, the Coast Guard needs to re-verify the identity of the mariner. Without this, there is a break in the chain of trust that presents a lapse of security.</P>
                <P>One commenter said that arrest records need not be revealed, referenced, or discussed in any matter during the credentialing process when the outcome is in question. The commenter also suggested removing misdemeanor convictions altogether from being a criterion by which a mariner or applicant is judged for certification and licensure.</P>
                <P>Although arrest records are not clear evidence of guilt, and therefore denial of credentialing is based on a court determination, the arrest serves as part of the record and is needed for full determination as required by 46 CFR 10.211. The Coast Guard acknowledges the commenter's concern. However, these issues have been resolved in the TWIC rulemaking. Those mariners who are not required to obtain a TWIC must still undergo another vetting process.</P>
                <P>Mariners who feel they were unfairly denied a credential, can appeal under the process available from TSA (49 CFR 1515) and/or the Coast Guard (46 CFR 1.03). Those mariners who are not required to obtain a TWIC must still undergo another vetting process.</P>
                <P>One commenter asked if the Coast Guard thought the state of Montana was a legitimate terrorist target and asked what a terrorist attack in the state would accomplish.</P>
                <P>A terrorist attack could happen anywhere in the United States, and the Coast Guard will require vetting of every merchant mariner seeking a credential. Please note that credentials are a Federal document and allow the holder to operate anywhere inland in the U.S., coastwise, or in foreign waters subject only to the restrictions on the credentials' face.</P>
                <P>One commenter expressed concern over the allowance of birth certificates and foreign passports as allowable identification. Another commenter took issue with the specific types of IDs accepted for verification.</P>
                <P>The Coast Guard understands the commenters' concerns. However, this requirement is moot as identification required for MMLs is addressed by the TWIC final rule which requires all mariners who hold Coast Guard credentials to also hold a TWIC. Those mariners who are not required to obtain a TWIC must still undergo another vetting process. See 49 CFR 1572.17, see also 46 CFR 10.221.</P>
                <P>One commenter asked the Coast Guard if fingerprinting/ID checks were so critical, why the Coast Guard mails the credential to an address at which someone other than the intended recipient might be waiting to intercept it.</P>
                <P>The Coast Guard acknowledges the commenter's concern. However, this concern has been addressed for mariners requiring a TWIC, which must be activated in person to complete the “chain of trust”. Those mariners who are not required to obtain a TWIC must still undergo another vetting process.</P>
                <P>One commenter called into question centralizing Marine Licensing and Documentation with the NMC and moving it to Martinsburg, WV. By doing this, the commenter said, all records could be wiped out with one calamity. The commenter was afraid that reducing facilities to one location would have the opposite effect on the backlog. Also, the commenter asked what happens when the system is down or has no power.</P>
                <P>This comment is beyond the scope of this rulemaking. However, current system performance has the average credential being processed in approximately 17 days of net processing time with greater than 80 percent being under 30 days. This is significantly less than the system performance while business was conducted at 17 disparate RECs. Performance at RECs varied significantly for many reasons. Among other benefits, centralization brings consistency across the program. Records were and are archived from the RECs to Federal Records Centers just as they are from the centralized NMC. Electronic records are backed up routinely. Records at any location are subject to loss from natural or man induced reasons. The NMC still continues to deal with cases of records lost due to Hurricane Katrina in New Orleans. The centralized location of the NMC has less potential natural perils than most of the coastally located RECs. When the RECs were doing evaluations, they were still accessing the same electronic system that they and the centralized NMC access today. There are redundant systems and backups to mitigate any lost time due to equipment and power failure.</P>
                <P>One commenter noted a conflict in 46 CFR 10.209 regarding the requirements of identity documents.</P>
                <P>New regulations are in place regarding identity verification. Therefore, this comment is now moot.</P>
                <P>One commenter was in favor of the changes in the interim rule because new security requirements make sense in today's world.</P>
                <P>The Coast Guard thanks the commenter and agrees.</P>
                <P>One commenter, who held a commercial pilot's license, asked why a mariner seeking a master's license must jump through so many hoops, including the $145 fee required for the license itself and the requirement to renew every 5 years.</P>
                <P>Under statutory mandate, a mariner's license is valid for 5 years and may be renewed, with the required background checks, for additional 5-year periods. 46 U.S.C. 7106. The Coast Guard has statutory authority to set fees for mariner services or things of value. 46 U.S.C. 2110. The fee is determined by the actual time and motion costs to the Coast Guard for the required evaluation, exam (if any), and issuance of the license.</P>
                <P>One commenter disagreed with reducing the number of “service centers” to 17 RECs and believed the user fees added a substantial financial burden to mariners.</P>
                <P>
                    The interim rule did not reduce the number of “service centers” or RECs. The current number of 17 RECs has 
                    <PRTPAGE P="35173"/>
                    been in place since 1982. As stated in the response to the previous commenter, the Coast Guard has statutory authority to set fees for mariner services or things of value. 46 U.S.C. 2110.
                </P>
                <P>One commenter noted that more than half of the personnel at Washington Island Ferry Line Inc., were not required to be licensed.</P>
                <P>Mariners who require no license or MMC were not expected to follow the procedures in the interim rule. However, mariners are encouraged to check with local authorities to see if a TWIC is necessary in a given port area.</P>
                <P>One commenter expressed concern about raising the standards defining “conviction”, which could disqualify some mariners from consideration when trying to obtain a credential. The commenter noted that there were situations where persons who have made mistakes, paid their debt to society and were living as responsible citizens, and they should be given a better opportunity to obtain a credential.</P>
                <P>The Coast Guard agrees with this commenter, that persons who have been convicted in the past may in fact qualify for work as a mariner. Not all crimes serve as permanent disqualifiers, and there are procedures in place to allow for waivers or review of certain convictions when the individual can show that they are not a security or safety risk. Please see TSA appeal and waiver procedures for security threat assessments for individuals at 49 CFR Part 1515, see also Coast Guard Merchant Mariner Credential, criminal record review at 46 CFR 10.211.</P>
                <P>Two commenters said credential renewals and upgrades needed to only establish that the candidate was the same person who received the original license and suggest the Coast Guard authorize employers to certify the identification of candidates. The commenters noted that employers were trusted to certify sea service and presence in a drug-testing pool.</P>
                <P>Identification verification meets only half of the criteria for the process of obtaining a credential. Candidates must also give fingerprints so the authorities can conduct background checks. Also, TSA requires personal appearance at an enrollment center for fingerprinting and ID checks as part of the TWIC process. Please see the TWIC rulemaking for clarification.</P>
                <P>One commenter wanted the Coast Guard to create an MMC that a mariner can carry in his or her pocket.</P>
                <P>The NMC began issuing the MMC in early 2009 as a mariner's professional qualifications document. It incorporates the legacy license, MMD and/or Certificate of Registry as well as a mariner's STCW endorsements. The TWIC now serves as the mariner's identity document. Please see the TWIC rulemaking for clarification.</P>
                <P>One commenter took issue with the Coast Guard issuing an interim rule without seeking comment from industry.</P>
                <P>Due to the immediate needs for heightened security measures to be implemented, the publication of an interim rule with a request for comments allowed the Coast Guard to immediately implement regulations needed to protect national security. However, the interim rule did allow for the public to comment on the rule before it became final. Those comments are summarized above. Since publication of the interim rule, the Coast Guard, TSA, and the Department of Homeland Security have considered and addressed the public's concerns in the regulations listed above in the “Background” section of this document, as these same concerns were raised upon promulgation of those other rules.</P>
                <HD SOURCE="HD1">Intent To Finalize; Request for Comments</HD>
                <P>
                    The Coast Guard invites further comments related to this Notice of Intent to finalize the one section of the January 13, 2006 interim rule that has remained unfinalized, 46 CFR 10.107(b): 
                    <E T="03">Definitions in subchapter B,</E>
                     specifically, the definition of “Dangerous drug”. Written comments and responses related to finalizing this definition will be added to the docket number for this rulemaking (USCG-2004-17455). Upon close of the comment period, the Coast Guard will consider all comments received. We anticipate that we will be able to finalize 46 CFR 10.107(b) soon thereafter.
                </P>
                <SIG>
                    <DATED>Dated: June 9, 2011.</DATED>
                    <NAME>F.J. Sturm,</NAME>
                    <TITLE>Acting Director of Commercial Regulations and Standards.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-14920 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 9110-04-P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
                <SUBAGY>Coast Guard</SUBAGY>
                <CFR>46 CFR Part 12</CFR>
                <DEPDOC>[Docket No. USCG-2003-14500]</DEPDOC>
                <RIN>RIN 1625-AA81</RIN>
                <SUBJECT>Validation of Merchant Mariners' Vital Information and Issuance of Coast Guard Merchant Mariner's Documents (MMDs)</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Coast Guard, DHS.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of intent with request for comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Coast Guard is advising the public of its intent to finalize regulations previously published as an interim rule on January 6, 2004. The interim rule (IR) was published to enhance the application procedures for the Merchant Mariner Licensing and Documentation program, which were necessary to improve maritime safety and promote the national security interest of the United States, but was never published as a final rule. Because of the lapse in time since the interim rule publication, the Coast Guard is seeking comments from the public on one remaining section of the interim rule that has remained unfinalized. The Coast Guard intends to finalize this one section of the interim rule.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be received on or before August 15, 2011.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may submit comments identified by docket number USCG-2003-14500 using any one of the following methods:</P>
                    <P>
                        (1) 
                        <E T="03">Federal eRulemaking Portal: http://www.regulations.gov.</E>
                    </P>
                    <P>
                        (2) 
                        <E T="03">Fax:</E>
                         202-493-2251.
                    </P>
                    <P>
                        (3) 
                        <E T="03">Mail:</E>
                         Docket Management Facility (M-30), U.S. Department of Transportation, West Building Ground Floor, Room W12-140, 1200 New Jersey Avenue, SE., Washington, DC 20590-0001.
                    </P>
                    <P>
                        (4) 
                        <E T="03">Hand delivery:</E>
                         Same as mail address above, between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays. The telephone number is 202-366-9329. To avoid duplication, please use only one of these four methods. See the “Public Participation and Request for Comments” portion of the 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                         section below for instructions on submitting comments.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        If you have questions on this proposed rule, call or e-mail Mr. Gerald Miante, Maritime Personnel Qualifications 
                        <PRTPAGE P="35174"/>
                        Division, Coast Guard; telephone 202-372-1407, e-mail 
                        <E T="03">Gerald.P.Miante@uscg.mil.</E>
                         If you have questions on viewing or submitting material to the docket, call Renee V. Wright, Program Manager, Docket Operations, telephone 202-366-9826.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Request for Comments</HD>
                <P>
                    If you submit a comment, please include the docket number for this rulemaking (USCG-2003-14500), indicate the specific section of this document to which each comment applies, and provide a reason for each suggestion or recommendation. You may submit your comments and material online (via 
                    <E T="03">http://www.regulations.gov</E>
                    ) or by fax, mail, or hand delivery, but please use only one of these means. If you submit a comment online via 
                    <E T="03">http://</E>
                    <E T="03">www.regulations.gov,</E>
                     it will be considered received by the Coast Guard when you successfully transmit the comment. If you fax, hand deliver, or mail your comment, it will be considered as having been received by the Coast Guard when it is received at the Docket Management Facility. We recommend that you include your name and a mailing address, an e-mail address, or a phone number in the body of your document so that we can contact you if we have questions regarding your submission.
                </P>
                <P>
                    To submit your comment online, go to 
                    <E T="03">http://www.regulations.gov,</E>
                     click on the “submit a comment” box, which will then become highlighted in blue. In the “Select Document Type” drop down menu select “Proposed Rule” and insert “USCG-2003-14500” in the “Enter Keyword or ID” box. Click “Search” then click on the balloon shape in the “Actions” column. If you submit your comments by mail or hand delivery, submit them in an unbound format, no larger than 8
                    <FR>1/2</FR>
                     by 11 inches, suitable for copying and electronic filing. If you submit comments by mail and would like to know that they reached the Facility, please enclose a stamped, self-addressed postcard or envelope.
                </P>
                <P>We will consider all comments and material received during the comment period and may change this proposed rule based on your comments.</P>
                <HD SOURCE="HD2">Viewing Comments and Documents</HD>
                <P>
                    To view comments, as well as documents mentioned in this preamble as being available in the docket, go to 
                    <E T="03">http://www.regulations.gov,</E>
                     click on the “read comments” box, which will then become highlighted in blue. In the “Enter Keyword or ID” box insert “USCG-2003-14500” and click “Search.” Click the “Open Docket Folder” in the “Actions” column. You may also visit the Docket Management Facility in Room W12-140 on the ground floor of the Department of Transportation West Building, 1200 New Jersey Avenue, SE., Washington, DC 20590, between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays. We have an agreement with the Department of Transportation to use the Docket Management Facility.
                </P>
                <HD SOURCE="HD2">Privacy Act</HD>
                <P>
                    Anyone can search the electronic form of 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 a Privacy Act notice regarding our public dockets in the January 17, 2008, issue of the 
                    <E T="04">Federal Register</E>
                     (73 FR 3316).
                </P>
                <HD SOURCE="HD2">Public Meeting</HD>
                <P>
                    We do not now plan to hold a public meeting. But you may submit a request for one on or before July 6, 2011 using one of the four methods specified under 
                    <E T="02">ADDRESSES</E>
                    . Please explain why you believe a public meeting would be beneficial. If we determine that one would aid this rulemaking, we will hold one at a time and place announced by a later notice in the 
                    <E T="04">Federal Register</E>
                    .
                </P>
                <P>
                    For information on facilities or services for individuals with disabilities or to request special assistance at the public meeting, contact Mr. Gerald Miante, Maritime Personnel Qualifications Division, Coast Guard; at the telephone number or e-mail address indicated under the 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                     section of this notice.
                </P>
                <HD SOURCE="HD1">Abbreviations</HD>
                <EXTRACT>
                    <FP SOURCE="FP-1">§ Section symbol</FP>
                    <FP SOURCE="FP-1">
                        FR 
                        <E T="04">Federal Register</E>
                    </FP>
                    <FP SOURCE="FP-1">MMD Merchant Mariner's Document</FP>
                    <FP SOURCE="FP-1">NMC National Maritime Center</FP>
                    <FP SOURCE="FP-1">REC Regional Examination Center</FP>
                    <FP SOURCE="FP-1">TSA Transportation Security Administration</FP>
                    <FP SOURCE="FP-1">TWIC Transportation Worker Identification Credential</FP>
                    <FP SOURCE="FP-1">U.S.C. U.S. Code</FP>
                </EXTRACT>
                <HD SOURCE="HD1">Basis and Purpose</HD>
                <P>
                    On January 6, 2004, the Coast Guard published in the 
                    <E T="04">Federal Register</E>
                     (69 FR 526) an interim rule with request for comments. The interim rule described enhancements to the application procedures for the Merchant Mariner Licensing and Documentation program, which were necessary to improve maritime safety and promote the national security interest of the United States. However, subsequent rulemakings have addressed the majority of the interim rule provisions. As a result, the Coast Guard intends to finalize the single remaining section that has not been addressed in subsequent rulemakings.
                </P>
                <P>
                    The most recent significant rulemaking documents for rulemakings addressing the interim rule provisions are as follows 
                    <SU>1</SU>
                    <FTREF/>
                    : (1) Transportation Worker Identification Credential (TWIC) Implementation in the Maritime Sector; Hazardous Materials Endorsement for a Commercial Driver's License (74 FR 13114); (2) Seafarer's Training, Certification and Watchkeeping Code (STCW Code) (75 FR 13715); (3) Maritime Identification Credentials (74 FR 2865); (4) Consolidation of Merchant Mariner Qualification Credentials (74 FR 11196); (5) Training and Service Requirements for Merchant Marine Officers (73 FR 52789); (6) Large Passenger Vessel Crew Requirements (74 FR 47729); and (7) Crewmember Identification Documents (74 FR 19135).
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         To find all the rulemaking documents associated with the rulemakings listed here, you can view each rulemaking's docket on 
                        <E T="03">http://www.regulations.gov.</E>
                    </P>
                </FTNT>
                <P>
                    The one section of the January 6, 2004 interim rule that has remained unfinalized is 46 CFR 12.01-1(a)(1): Purpose of rules in this part, which states the rules are to provide a “comprehensive and adequate means of determining and verifying the identity, citizenship, nationality, and professional qualifications an applicant must possess to be eligible for certification to serve on merchant vessels of the United States”. Our intent is to finalize this one remaining section of the interim rule, and we are asking for comment on this section only. You may submit a comment to the docket using one of the methods specified under 
                    <E T="02">ADDRESSES</E>
                    .
                </P>
                <HD SOURCE="HD2">Discussion of Comments</HD>
                <P>
                    As a result of our request for comments in the interim rule published on January 6, 2004 in the 
                    <E T="04">Federal Register</E>
                    , (69 FR 526), the Coast Guard heard from eight respondents representing mariners and the industry. The respondents submitted numerous comments addressing a wide range of issues related to the interim rule. A discussion of the comments follows.
                </P>
                <P>One commenter requested a public hearing in order to “develop a complete and accurate record regarding the provisions and consequences of the interim rule.”</P>
                <P>
                    The Coast Guard believes a public hearing is unnecessary. This rulemaking qualifies as an informal rulemaking 
                    <PRTPAGE P="35175"/>
                    under Sec. 553 of the Administrative Procedure Act, and as such does not require formal hearing procedures. The Coast Guard believes that the commenter's desire for a complete and accurate record of rulemaking actions related to this interim rule is available in the public docket USCG-2003-14500, available online by going to 
                    <E T="03">http://regulations.gov,</E>
                     inserting USCG-2003-14500 in the “Keyword” box, and then clicking “Search.”
                </P>
                <P>One commenter looked favorably on the removal of the term “shipping commissioner” and the removal of social security numbers from the Merchant Mariners Documents (MMDs).</P>
                <P>At each revision, the Coast Guard attempts to update terminology in its regulations. In this rulemaking specifically, we removed social security numbers from MMDs to safeguard mariners' personally identifiable information. We believe that changes such as these better serve the mariners.</P>
                <P>One commenter said that the Coast Guard does not understand and fails to communicate with lower-level mariners.</P>
                <P>The Coast Guard disagrees. The Coast Guard communicates with all branches of the maritime community through publications, Web sites, responses to inquiries, and other personal and mass media efforts. In fact, the Merchant Marine Personnel Advisory Committee has several “limited-service” mariners as members while several other members represent companies that employ these mariners. MERPAC periodically studies and discusses issues pertinent to limited-service mariner employment and advancement, such as Able Seamen Qualifications and ratings attaining Officer in Charge of a Navigational Watch and Officer in Charge of an Engineering Watch coming up through the hawsepipe.</P>
                <P>One commenter warned that “adding extra and vague requirements to the already burdensome ones” will only serve to drive more people away from the maritime industry.</P>
                <P>The Coast Guard agrees that excessive regulatory burdens must be avoided. However, extra security measures are a reality for all transportation sectors. Making ports, facilities, and vessels more secure is a part of doing business in today's world that cannot be avoided. New security measures take extra effort from all parties—government, industry, and the individual mariner—and we believe these measures are not excessive.</P>
                <P>The Coast Guard also agrees with the commenter that “vague requirements” should be avoided. To make our requirements more clear, we have provided definitions of “safe and suitable person”, “criminal record check”, and “National Driver Register (NDR)” with specific language in 46 CFR 10.107. Mariners who feel they were unfairly denied a credential can appeal under the process available from the Transportation Security Administration (TSA) (49 CFR 1515) and/or the Coast Guard (46 CFR 1.03). Those mariners who are not required to obtain a TWIC must still undergo another vetting process.</P>
                <P>Five commenters stated that, in addition to the current 17 Regional Examination Centers (RECs), additional locations were needed for mariners to show proof of identity and be fingerprinted.</P>
                <P>This comment has been overcome by events with the establishment of the TWIC rulemaking. Those mariners who are not required to obtain a TWIC must still undergo another vetting process, which requires a showing of proof of identity and provision of fingerprints. The Coast Guard agrees that maximizing the number of locations where this may be accomplished is best, and is evaluating the options available for how to best meet mariners' identification needs. However, this is beyond the scope of this rulemaking finalizing one remaining section: 46 CFR 12.01-1(a)(1): Purpose of rules in this part.</P>
                <P>One commenter said the RECs are unable to provide adequate services to mariners while performing current duties and that the RECs' attempt “to accomplish even more with fewer resources is the basis of the current problem with the RECs.”</P>
                <P>One commenter predicted that the RECs will be unable to provide timely identification and fingerprinting services.</P>
                <P>These comments have been overcome by events with the establishment of the TWIC rulemaking. Those mariners who are not required to obtain a TWIC must still undergo another vetting process.</P>
                <P>One of these commenters also stated that evaluators should be trained, temporary licenses and documents should be issued, a hotline should be set up to receive credential-related inquiries, and that the licensing procedures should be simplified.</P>
                <P>These subjects are not directly related to this rulemaking but were considered during subsequent revisions of the entire subchapter, 46 CFR subchapter B.</P>
                <P>As part of documentation centralization at the National Maritime Center (NMC) in West Virginia, evaluators are being trained, and extra evaluators may be applied to any surges that might occur.</P>
                <P>One commenter stated that 5-year renewals of MMDs and licenses should be good for 5 full years with renewal dates falling on the mariner's birthday, and that current documents should be extended as necessary to implement this change.</P>
                <P>Title 46 U.S.C. 7302(f) currently states that an MMD is valid for 5 years and may be renewed for an additional 5-year period. To help alleviate the problem created by the 5-year validity period, the NMC is issuing credentials that have a delayed start-date to coincide with the expiration date of the previous credential.</P>
                <P>One commenter pointed out that the interim rule is unrealistic because it focuses on only one aspect of security without addressing other areas where enhanced security is necessary.</P>
                <P>Two commenters expressed concern that mariners on deep-draft U.S. flag vessels pose the least risk to national security and that threats to national security lie in exceptions to documentation requirements for mariners on inland waters and/or those serving on vessels of less than 100 gross tons (GRT). The commenters recommended that persons on all types of vessels be required to undergo a security screening.</P>
                <P>These comments have been overcome by events with the establishment of the TWIC rulemaking. In addition, there are approved courses available for company, facility, and vessel security officer training as well as security familiarization for other crewmembers.</P>
                <P>One commenter pointed out that the Coast Guard should require criminal record disclosure in applications for mariner credentials, but should not continuously require repeated documentation of previously disclosed information.</P>
                <P>The Coast Guard agrees that the application process should be updated and simplified. As one major step, the Coast Guard has centralized all mariners' credential records at the NMC. This new process may, in the future, negate the need for repeated collection of established reporting.</P>
                <P>Two commenters called for a clear and workable appeals process in the event that a mariner is denied a credential. One of these commenters stated the Coast Guard can withhold any explanation of the reason for disproving an MMD.</P>
                <P>
                    The Coast Guard agrees with the commenters and has comprehensively revised the regulation. The Coast Guard has developed an appeals process for mariners who believe they were wrongly denied a credential. The appeal process is available from the TSA (See 49 CFR 1515) and/or the Coast Guard (See 46 CFR 1.03). Those mariners who 
                    <PRTPAGE P="35176"/>
                    are not required to obtain a TWIC must still undergo another vetting process.
                </P>
                <P>We received many comments relating to our estimates of costs in the interim final rule. Three commenters stated that applicant visits to an REC for the purposes of showing identification and fingerprinting could not be accomplished in 1 hour, and that the 1-hour approximation was underestimated.</P>
                <P>Two commenters stated that 1-day round-trip travel does not constitute close proximity to an REC, and that the 100-mile average was unreasonable for 1-day round-trip travel to an REC.</P>
                <P>Three commenters disagreed with the Coast Guard's travel cost estimate that most mariners live within 1-day round trip travel of an REC.</P>
                <P>One commenter stated that several mariners in the Great Lakes Basin did not live in close proximity to an REC.</P>
                <P>Another commenter stated that the assumptions used by the Coast Guard in calculating travel costs for applicants did not adequately reflect real travel costs in the Great Lakes.</P>
                <P>One commenter stated that the cost in the interim rule looked at the cost on a 5-year basis, but in the long term, there was an enormous cost impact for all mariners given the multiple renews required during the course of a career.</P>
                <P>One commenter stated that the Coast Guard's analysis was not correct to say, “not all mariners will incur costs from this rule.” The commenter further stated that every mariner seeking a new or reissue MMD was going to incur costs.</P>
                <P>One commenter stated that the hours spent traveling should be acknowledged as the opportunity cost of the individual's wages.</P>
                <P>Five commenters said the costs to mariners and the total cost of this rulemaking were underestimated.</P>
                <P>One commenter wanted clarification on the application of convictions for misdemeanors and was concerned about its effect on recruitment and retention.</P>
                <P>One commenter suggested that anyone who was denied a credential because of a safety and security check should be advised in writing as to the reason without exception.</P>
                <P>One commenter said that an administrative law judge should make final decisions on appeals.</P>
                <P>One commenter argued that the definition of the term “safety and security check” should include a statement on the extent of the check that may be performed.</P>
                <P>These comments have been overcome by events with the establishment of the TWIC rulemaking. Those mariners who are not required to obtain a TWIC must still undergo another vetting process. However, we note that the regulatory evaluations which accompanied the TWIC rulemaking considered many of the comments regarding cost estimation we received here.</P>
                <P>One commenter believed that regulations in effect prior to the interim rule create a presumption of adequacy, and that further safety and security checks were unnecessary.</P>
                <P>The Coast Guard does not agree. As part of the Coast Guard's goal of increasing security in all aspects of the maritime domain, all mariners who then held an MMD were screened to determine if they presented a potential security risk to our nation. As a result, the Coast Guard found instances where an applicant had been issued a credential and was later found to pose a threat to security. The prior regulations did not require mariners to have their fingerprints taken at the RECs, and it allowed a candidate to submit a fingerprint card from an uncontrolled location. Similarly, the prior regulations allowed renewal of documents by mail and an applicant's identity could not be verified. The new regulations require a candidate's presence before the Coast Guard or its authorized agent to be certain that the person applying for the document can validate his or her identity and the fingerprints are indeed those of the applicant.</P>
                <P>Three commenters believed that the regulation concerning a “safe and suitable person” and one's “character and habits of life” was vague, lacked criteria for making this determination, and did not provide adequate safeguards to the mariner. Additionally, one of these commenters added that the “character and habits of life” standard would infringe on the mariners' First Amendment rights and ignored the Supreme Court's limiting construction.</P>
                <P>The Coast Guard agrees and changes to the terms were made with the Consolidation of Merchant Mariner Qualification Credentials final rule. 74 FR 11196.</P>
                <P>One commenter believed that the requirement in 46 CFR 12.02-4(a) was too harsh.</P>
                <P>One commenter wanted clarification regarding 46 CFR 12.02-4(c) as it related to applicants who have been arrested but not convicted.</P>
                <P>One commenter suggested revising 46 CFR 12.02-9(a), which read, “The Coast Guard may refuse to process an incomplete MMC application.” by replacing the word “process” with the words “issue a credential based upon”.</P>
                <P>One commenter asked for a definition for the word “incomplete” in 46 CFR 12.02-9(a).</P>
                <P>These subjects are not directly related to this rulemaking but were addressed with the Consolidation of Merchant Mariner Qualification Credentials final rule, which removed and reserved 46 CFR 12.02-4 and 12.02-9. (74 FR 11196). Application regulations for all endorsements are now contained in 46 CFR 10.209.</P>
                <HD SOURCE="HD1">Intent To Finalize; Request for Comments</HD>
                <P>
                    The Coast Guard invites further comments related to this Notice of Intent to finalize the one section of the January 6, 2004 interim rule that has remained unfinalized, 46 CFR 12.01-1(a)(1): 
                    <E T="03">Purpose of rules in this part.</E>
                     Written comments and responses related to finalizing 46 CFR 12.01-1(a)(1) will be added to the docket number for this rulemaking (USCG-2003-14500). Upon close of the comment period, the Coast Guard will consider all comments received. We anticipate that we will be able to finalize 46 CFR 12.01-1(a)(1) soon thereafter.
                </P>
                <SIG>
                    <DATED>Dated: June 9, 2011.</DATED>
                    <NAME>F.J. Sturm,</NAME>
                    <TITLE>Acting Director of Commercial Regulations and Standards.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-14921 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 9110-04-P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="N">FEDERAL COMMUNICATIONS COMMISSION</AGENCY>
                <CFR>47 CFR Part 15</CFR>
                <DEPDOC>[ET Docket Nos. 11-90 and 10-28; FCC 11-79]</DEPDOC>
                <SUBJECT>Operation of Radar Systems in the 76-77 GHz Band</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Communications Commission.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Proposed rule.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        In this document the Commission proposes to amend rules to enable enhanced vehicular radar technologies in the 76-77 GHz band to improve collision avoidance and driver safety. Vehicular radars can determine the exact distance and relative speed of objects in front of, beside, or behind a car to improve the driver's ability to perceive objects under bad visibility conditions or objects that are in blind spots. These modifications to the rules will provide more efficient use of spectrum, and enable the automotive and fixed radar application industries to develop enhanced safety measures for drivers and the general public. The Commission takes this action in 
                        <PRTPAGE P="35177"/>
                        response to petitions for rulemaking filed by Toyota Motor Corporation (“TMC”) and Era Systems Corporation (“Era”)
                    </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be filed on or before July 18, 2011, and reply comments must be filed on or before August 1, 2011.</P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Aamer Zain, Office of Engineering and Technology, (202) 418-2437, 
                        <E T="03">e-mail: Aamer.Zain@fcc.gov</E>
                        , TTY (202) 418-2989.
                    </P>
                </FURINF>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may submit comments, identified by ET Docket Nos. 11-90 and 10-28, by any of the following methods:</P>
                    <P>
                        • 
                        <E T="03">Federal Communications Commission's Web Site: http://fjallfoss.fcc.gov/ecfs2/.</E>
                         Follow the instructions for submitting comments.
                    </P>
                    <P>
                        • 
                        <E T="03">Mail:</E>
                         Aamer Zain, Electronics Engineer, Office of Engineering and Technology, 445 12th Street, SW., Room 7-A110, Washington, 20554
                    </P>
                    <P>
                        • 
                        <E T="03">People with Disabilities:</E>
                         Contact the FCC to request reasonable accommodations (accessible format documents, sign language interpreters, CART, etc.) by 
                        <E T="03">e-mail: FCC504@fcc.gov</E>
                         or phone: 202-418-0530 or 
                        <E T="03">TTY:</E>
                         202-418-0432.
                    </P>
                    <P>
                        For detailed instructions for submitting comments and additional information on the rulemaking process, see the 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                         of this document.
                    </P>
                </ADD>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    This is a summary of the Commission's 
                    <E T="03">Notice of Proposed Rule Making,</E>
                     ET Docket No. 11-90, FCC 11-79, adopted May 24, 2011 and released May 25, 2011. The full text of this document is available for inspection and copying during normal business hours in the FCC Reference Center (Room CY-A257), 445 12th Street, SW., Washington, DC 20554. The complete text of this document also may be purchased from the Commission's copy contractor, Best Copy and Printing, Inc., 445 12th Street, SW., Room, CY-B402, Washington, DC 20554. The full text may also be downloaded at: 
                    <E T="03">http://www.fcc.gov</E>
                    .
                </P>
                <HD SOURCE="HD1">Comment Period and Procedures</HD>
                <P>
                    Pursuant to §§ 1.415 and 1.419 of the Commission's rules, 47 CFR 1.415, 1.419, interested parties may file comments and reply comments on or before the dates indicated on the first page of this document. Comments may be filed using: (1) The Commission's Electronic Comment Filing System (ECFS), (2) the Federal Government's eRulemaking Portal, or (3) by filing paper copies. 
                    <E T="03">See Electronic Filing of Documents in Rulemaking Proceedings,</E>
                     63 FR 24121 (1998).
                </P>
                <P>
                    • 
                    <E T="03">Electronic Filers:</E>
                     Comments may be filed electronically using the Internet by accessing the ECFS: 
                    <E T="03">http://fjallfoss.fcc.gov/ecfs2/.</E>
                </P>
                <P>
                    • 
                    <E T="03">Paper Filers:</E>
                     Parties who choose to file by paper must file an original and one copy of each filing. If more than one docket or rulemaking number appears in the caption of this proceeding, filers must submit two additional copies for each additional docket or rulemaking number.
                </P>
                <P>Filings can be sent by hand or messenger delivery, by commercial overnight courier, or by first-class or overnight U.S. Postal Service mail. All filings must be addressed to the Commission's Secretary, Office of the Secretary, Federal Communications Commission.</P>
                <P>
                    • All hand-delivered or messenger-delivered paper filings for the Commission's Secretary must be delivered to FCC Headquarters at 445 12th St., SW., Room TW-A325, Washington, DC 20554. The filing hours are 8 a.m. to 7 p.m. All hand deliveries must be held together with rubber bands or fasteners. Any envelopes and boxes must be disposed of 
                    <E T="03">before</E>
                     entering the building.
                </P>
                <P>• Commercial overnight mail (other than U.S. Postal Service Express Mail and Priority Mail) must be sent to 9300 East Hampton Drive, Capitol Heights, MD 20743.</P>
                <P>• U.S. Postal Service first-class, Express, and Priority mail must be addressed to 445 12th Street, SW., Washington DC 20554.</P>
                <P>
                    <E T="03">People with Disabilities:</E>
                     To request materials in accessible formats for people with disabilities (braille, large print, electronic files, audio format), send an e-mail to 
                    <E T="03">fcc504@fcc.gov</E>
                     or call the Consumer &amp; Governmental Affairs Bureau at 202-418-0530 (voice), 202-418-0432 (tty).
                </P>
                <HD SOURCE="HD1">Summary of Notice of Proposed Rulemaking</HD>
                <P>
                    1. In the 
                    <E T="03">Notice of Proposed Rule Making</E>
                     (NPRM), the Commission proposes to modify §§ 15.35 and 15.253 of its rules to enable enhanced vehicular radar technologies in the 76-77 GHz band to improve collision avoidance and driver safety. Vehicular radars can determine the exact distance and relative speed of objects in front of, beside, or behind a car to improve the driver's ability to perceive objects under bad visibility conditions or objects that are in blind spots. The Commission proposes to eliminate the existing requirement that vehicular radars decrease power when the vehicle on which the radar is mounted is stopped, or not in motion, and to expand the authorization for unlicensed 76-77 GHz band radars to allow their use in fixed infrastructure systems. These modifications to the rules will provide more efficient use of spectrum, and enable the automotive and fixed radar application industries to develop enhanced safety measures for drivers and the general public. This action is taken in response to petitions for rulemaking filed by Toyota Motor Corporation (TMC) and Era Systems Corporation (Era).
                </P>
                <P>2. The 76-77 GHz band offers advantages for vehicular and fixed radar systems, such as precise real-time monitoring of the position and speed of vehicles. The Commission's proposals are intended to foster the development of improved radar systems that offer significant safety benefits to the general public. The Commission also foresees economic benefits such as economies of scale and broader marketplace demand that may be attained if both the U.S. and other markets use the 76-77 GHz band for fixed and vehicular radar systems. Furthermore, the Commission believes that the changes in power levels and use suggested by TMC and Era will not result in any increased potential of interference to licensed services.</P>
                <P>3. TMC filed a petition for rulemaking requesting that the emission limits be modified for vehicular radar systems operating within the 76-77 GHz band. Specifically, TMC requested that the Commission eliminate the “in-motion” and “not-in-motion” distinctions in the emission limits for vehicular radar systems and establish a single emission limit that applies in all directions from a vehicle.</P>
                <P>
                    4. The Commission believes there is merit to TMC's request to modify the emissions limits for vehicular radar systems, and to eliminate the “in-motion” and “not-in-motion” distinction in limits for millimeter wave vehicular radar systems. Therefore, the Commission proposes to modify its rules for vehicular radar systems operating in the 76-77 GHz band as TMC requests. The Commission proposes to modify § 15.253 of its rules to increase the average power density limit to 50 dBm (88 μW/cm
                    <SU>2</SU>
                     at 3 m) and decrease the peak power density limit to 55 dBm (279 μW/cm
                    <SU>2</SU>
                     at 3m) for vehicular radar systems regardless of the illumination direction of the vehicular radar system as reflected in the proposed rules set forth in Appendix A. The Commission seeks comments on this proposal. The proposed emission limits would extend to vehicular radar systems illuminating in any of the mentioned directions (forward, rear or side). This action would make the rules 
                    <PRTPAGE P="35178"/>
                    governing the vehicular radar emission limit in United States to be more comparable to those set forth outside the United States and therefore benefit the automotive industry in terms of new product development and cost reduction.
                </P>
                <P>
                    5. The existing separate in-motion and not-in-motion emission limits were adopted to prevent unnecessary and prolonged harmful human exposure to RF radiation. The motion status of the vehicle was given special consideration due the fact that vehicles that are not in motion could result in human exposure to radiation for longer time durations than a moving vehicle. However, because the proposed emission limit of 88 μW/cm
                    <SU>2</SU>
                     is below the current average threshold limit of 1 mW/cm
                    <SU>2</SU>
                     adopted for human exposure to RF radiation, the in-motion and not-in-motion criteria become unnecessary for safety purposes. The Commission therefore proposes emission limits independent of the motion status of the vehicle. The Commission seeks comments on these proposals.
                </P>
                <P>6. In proposing the new emission limit, the Commission recognizes NRAO's concerns about possible interference, but note that the peak limit recommended by Toyota is lower than the current peak limit. This reduced limit will increase the level of interference protection afforded to RAS systems and other authorized users of the 76-77 GHz band. The Commission agrees with TMC's assessment that there is very little likelihood that vehicular radar systems operating at either the current or proposed limits would cause harmful interference to radio astronomy equipment. Accordingly, the Commission believes that there is no need to restrict vehicular radar systems based on coordination zones or to impose requirements for a GPS-aware automatic cut-off switch as proposed by NRAO. The Commission invites comment on this analysis.</P>
                <P>7. The Commission also seeks comment on TMC's request to modify § 15.253 of its rules to specify a limit on peak EIRP instead of average power density as an alternative to, or in addition to, the limits currently specified in the rules. Furthermore, it proposes to modify § 15.35(b) of the Commission's rules to reflect the fact that the proposed peak emission limit is not 20 dB above the average emission limit.</P>
                <P>8. In its petition, Era requests that the Commission amend § 15.253 of its rules to permit the use of 76-77 GHz unlicensed fixed radars at airports for monitoring terrestrial vehicle movements. Era contends that when the rules limiting operation to vehicle-mounted radars were adopted, there was no practical experience with vehicular radars in the 76-77 GHz band, and the rules were made very conservative to assure that such radars would not receive interference from other users of the band. Era contends that subsequent experience in other countries has shown that the requirement that radars operate only on moving vehicles is overly restrictive. It requests that the Commission relax this requirement and suggests several alternative approaches for modifying the rules to allow fixed radar use, primarily at airports. The suggested approaches are: (1) Limit fixed radars to airports and other applications that do not illuminate public roads; (2) require either compliance with the ETSI standard or strict compatibility testing for any system that illuminates public roads; or (3) mandate compliance with the ETSI standard for all 76 GHz radar systems. Era does not express a preference for which of these approaches it believes the Commission should adopt.</P>
                <P>9. The Commission agrees with Era that the current rules should be relaxed to allow the operation of fixed radars in the 76-77 GHz band on an unlicensed basis. It therefore proposes to permit fixed radars to operate in the 76-77 GHz band in addition to vehicular radar systems, and to require that such fixed radar systems meet the proposed limits for vehicular radar systems as well as the maximum permissible RF exposure levels set forth in the rules. The Commission believes that, based on Era's representations, use of the fixed radar devices in this band will enhance public safety by enabling applications such as monitoring vehicles on the ground at airports. However, the Commission is not proposing to limit operation to monitoring vehicles or to specific locations such as airports or other place's where fixed radars would not illuminate public roads. The Commission believes that Era's suggested alternative approaches and proposals may be overly restrictive and could cause unnecessary burdens for the public if implemented. Implementation of certain elements of these approaches could require licensing and/or coordination that would be burdensome for both users of the devices and the Commission with no corresponding benefits in terms of reduction of interference potential to licensed services or improved co-existence between unlicensed devices. The Commission's proposal to permit fixed radar applications is less restrictive and could be more beneficial to public than the proposals requested by Era. The Commission believes that fixed radars operating at the same maximum power levels as vehicle-mounted radars will be less likely to interfere with the RAS and Radiolocation services than vehicle-mounted radars because the location where they are used would not change. The Commission also believes that fixed radars should be able to co-exist with vehicular radars because they would both operate with the same power level and because both would use antennas with narrow beamwidths, thus reducing the chances that the signal from one radar would be within the main lobe of the receive antenna of the other. In a worst case scenario where two radars are aimed directly at each other, fixed radar should have no more impact on a vehicular radar system than another vehicular system would.</P>
                <P>
                    10. The Commission seeks comment on whether it should allow unlicensed fixed radar applications to operate within the 76-77 GHz band, and on the appropriateness of the proposed power levels. The Commission also seeks comment on whether there is a need to limit fixed radar applications to specific locations such as airports and/or locations where they are not aimed at publicly accessible roads as suggested by Era, or if some alternative criteria would be more appropriate. Commenters recommended operational restrictions such as these should also address how they could be practically enforced for unlicensed devices. In addition, the Commission seeks comment on whether specific technical requirements are necessary to allow co-existence of fixed and vehicular radars in the 76-77 GHz band (
                    <E T="03">e.g.,</E>
                     antenna height, operational frequency or power limits), and whether it should require fixed or vehicular radars to comply with a standard such as the ETSI EN 301 91 standard referenced by Era.
                </P>
                <HD SOURCE="HD1">Initial Regulatory Flexibility Analysis</HD>
                <P>
                    11. As required by the Regulatory Flexibility Act of 1980, as amended (RFA),
                    <SU>1</SU>
                    <FTREF/>
                     the Commission has prepared this present Initial Regulatory Flexibility Analysis (IRFA) of the possible significant economic impact on small entities by the policies and rules proposed in this Notice of Proposed Rule Making (NPRM). Written public comments are requested on this IRFA. Comments must be identified as responses to the IRFA and must be filed by the deadlines specified in the NPRM 
                    <PRTPAGE P="35179"/>
                    for comments. The Commission will send a copy of this NPRM, including this IRFA, to the Chief Counsel for Advocacy of the Small Business Administration (SBA).
                    <SU>2</SU>
                    <FTREF/>
                     In addition, the NPRM and IRFA (or summaries thereof) will be published in the 
                    <E T="04">Federal Register</E>
                    .
                    <SU>3</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         
                        <E T="03">See</E>
                         5 U.S.C. 603. The RFA, 
                        <E T="03">see</E>
                         5 U.S.C. 601-612, has been amended by the Small Business Regulatory Enforcement Fairness Act of 1996, (SBREFA) Public Law 104-121, Title II, 110 Stat. 857 (1996).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         
                        <E T="03">See</E>
                         5 U.S.C. 603(a).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         
                        <E T="03">See</E>
                         5 U.S.C. 603(a).
                    </P>
                </FTNT>
                <HD SOURCE="HD2">A. Need for, and Objectives of, the Proposed Rules</HD>
                <P>12. This NPRM responds to petitions for rulemaking filed by Toyota Motor Corporation (“TMC”) and Era Systems Corporation (“Era”) requesting modifications to § 15.253 of the Commission's rules for vehicular radar systems operating in the 76-77 GHz band. Vehicular radars can determine the exact distance and relative speed of objects in front of, beside, or behind a car to improve the driver's ability to perceive objects under bad visibility conditions or objects that are in blind spots. Some examples of vehicular radar systems include collision warning and mitigation systems, blind spot detection systems, lane change assist and parking aid systems. The NPRM proposes to eliminate the requirement that vehicular radars decrease power when the vehicle on which the radar is mounted is stopped, or not in motion, and to expand the use of unlicensed 76-77 GHz band radars to fixed infrastructure systems. These modifications to the rules will provide more efficient use of spectrum, and enable the automotive and fixed radar application industries to develop enhanced safety measures for drivers and the general public.</P>
                <HD SOURCE="HD2">B. Legal Basis</HD>
                <P>13. This action is authorized under sections 1, 4(i), 302, 303(f) and (r), 332, and 337 of the Communications Act of 1934, as amended, 47 U.S.C. 1, 4(i), 154(i), 302, 303(f) and (r), 332, 337.</P>
                <HD SOURCE="HD2">C. Description and Estimate of the Number of Small Entities to Which the Proposed Rule Will Apply</HD>
                <P>
                    14. The RFA directs agencies to provide a description of, and, where feasible, an estimate of, the number of small entities that may be affected by the rules adopted herein.
                    <SU>4</SU>
                    <FTREF/>
                     The RFA generally defines the term “small entity” as having the same meaning as the terms “small business,” “small organization,” and “small governmental jurisdiction.” 
                    <SU>5</SU>
                    <FTREF/>
                     In addition, the term “small business” has the same meaning as the term “small business concern” under the Small Business Act.
                    <SU>6</SU>
                    <FTREF/>
                     A “small business concern” is one which: (1) Is independently owned and operated; (2) is not dominant in its field of operation; and (3) satisfies any additional criteria established by the Small Business Administration (SBA).
                    <SU>7</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         5 U.S.C. 604(a)(3).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         5 U.S.C. 601(6).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         5 U.S.C. 601(3) (incorporating by reference the definition of “small-business concern” in the Small Business Act, 15 U.S.C. 632). Pursuant to 5 U.S.C. 601(3), the statutory definition of a small business applies “unless an agency, after consultation with the Office of Advocacy of the Small Business Administration and after opportunity for public comment, establishes one or more definitions of such term which are appropriate to the activities of the agency and publishes such definition(s) in the Federal Register.”
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         15 U.S.C. 632.
                    </P>
                </FTNT>
                <P>
                    15. 
                    <E T="03">Radio and Television Broadcasting and Wireless Communications Equipment Manufacturing.</E>
                     The Census Bureau defines this category as follows: “This industry comprises establishments primarily engaged in manufacturing radio and television broadcast and wireless communications equipment. Examples of products made by these establishments are: transmitting and receiving antennas, cable television equipment, GPS equipment, pagers, cellular phones, mobile communications equipment, and radio and television studio and broadcasting equipment.” 
                    <SU>8</SU>
                    <FTREF/>
                     The SBA has developed a small business size standard for Radio and Television Broadcasting and Wireless Communications Equipment Manufacturing, which is: all such firms having 750 or fewer employees.
                    <SU>9</SU>
                    <FTREF/>
                     According to Census Bureau data for 2002, there were a total of 1,041 establishments in this category that operated for the entire year.
                    <SU>10</SU>
                    <FTREF/>
                     Of this total, 1,010 had employment of under 500, and an additional 13 had employment of 500 to 999.
                    <SU>11</SU>
                    <FTREF/>
                     Thus, under this size standard, the majority of firms can be considered small.
                </P>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         U.S. Census Bureau, 2002 NAICS Definitions, “334220 Radio and Television Broadcasting and Wireless Communications Equipment Manufacturing”; 
                        <E T="03">http://www.census.gov/epcd/naics02/def/NDEF334.HTM#N3342</E>
                        .
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         13 CFR 121.201, NAICS code 334220.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         U.S. Census Bureau, American FactFinder, 2002 Economic Census, Industry Series, Industry Statistics by Employment Size, NAICS code 334220 (released May 26, 2005); 
                        <E T="03">http://factfinder.census.gov.</E>
                         The number of “establishments” is a less helpful indicator of small business prevalence in this context than would be the number of “firms” or “companies,” because the latter take into account the concept of common ownership or control. Any single physical location for an entity is an establishment, even though that location may be owned by a different establishment. Thus, the numbers given may reflect inflated numbers of businesses in this category, including the numbers of small businesses. In this category, the Census breaks-out data for firms or companies only to give the total number of such entities for 2002, which was 929.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         
                        <E T="03">Id.</E>
                         An additional 18 establishments had employment of 1,000 or more.
                    </P>
                </FTNT>
                <HD SOURCE="HD2">D. Description of Projected Reporting, Recordkeeping, and Other Compliance Requirements</HD>
                <P>16. Radars operating in the 76-77 GHz band are required to be authorized under the Commission's certification procedure as a prerequisite to marketing and importation, and the NPRM proposes no change to that requirement. However, it proposes to eliminate the requirement that a radar must reduce power when a vehicle is not in motion and to establish a single emission limit that applies in all directions from a vehicle. The NPRM also proposes to permit fixed radars to operate in the 76-77 GHz band under the same limits proposed for vehicular radar systems.</P>
                <HD SOURCE="HD2">E. Steps Taken To Minimize Significant Economic Impact on Small Entities, and Significant Alternatives Considered</HD>
                <P>
                    17. The RFA requires an agency to describe any significant alternatives that it has considered in reaching its proposed approach, which may include the following four alternatives (among others): (1) The establishment of differing compliance or reporting requirements or timetables that take into account the resources available to small entities; (2) the clarification, consolidation, or simplification of compliance or reporting requirements under the rule for small entities; (3) the use of performance, rather than design, standards; and (4) an exemption from coverage of the rule, or any part thereof, for small entities.
                    <SU>12</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         
                        <E T="03">See</E>
                         5 U.S.C. 603(c).
                    </P>
                </FTNT>
                <P>18. The proposals contained in this NPRM are deregulatory in nature, which we expect will simplify compliance requirements for all parties, particularly small entities, and permit the development of improved radar systems. Elimination of requirement for radars to reduce power when a vehicle is not in motion will simplify equipment design, and establishment of a single emission limit that applies in all directions from a vehicle would allow the development of omni-directional monitoring systems. Permitting fixed radar devices in the 76-77 GHz band would enable the development of applications such as monitoring the movement of vehicles on the ground at airports.</P>
                <HD SOURCE="HD2">F. Federal Rules That May Duplicate, Overlap, or Conflict With the Proposed Rule</HD>
                <P>
                    19. None.
                    <PRTPAGE P="35180"/>
                </P>
                <HD SOURCE="HD3">Ordering Clauses</HD>
                <P>
                    20. Pursuant to §§ 1, 4, 301, 302(a), and 303(b), (c) and (f) of the Communications Act of 1934, as amended, 47 U.S.C. 151, 154, 301, 302a(a), and 303(b), (c) and (f), the 
                    <E T="03">notice of proposed rulemaking</E>
                     is hereby 
                    <E T="03">adopted.</E>
                </P>
                <P>
                    21. The Commission's Consumer and Governmental Affairs Bureau, Reference Information Center, 
                    <E T="03">shall send</E>
                     a copy of the 
                    <E T="03">notice of proposed rulemaking,</E>
                     including the Initial Regulatory Flexibility Certification, to the Chief Counsel for Advocacy of the Small Business Administration.
                </P>
                <P>
                    22. Pursuant to sections 1, 2, 4(i), 301, 302, and 303(f) of the Communications Act of 1934, 47 U.S.C. 151, 152, 154(i), 301, 301, and 303(f), that this Notice of Proposed Rulemaking is hereby 
                    <E T="03">adopted.</E>
                </P>
                <P>
                    23. The Commission's Consumer and Governmental Affairs Bureau, Reference Information Center, 
                    <E T="03">shall send</E>
                     a copy of this Notice of Proposed Rulemaking, including the Initial Regulatory Flexibility Analysis, to the Chief Counsel for Advocacy of the Small Business Administration.
                </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 47 CFR Part 15</HD>
                    <P>Communications equipment, Radio.</P>
                </LSTSUB>
                <SIG>
                    <FP>Federal Communications Commission.</FP>
                    <NAME>Marlene H. Dortch,</NAME>
                    <TITLE>Secretary.</TITLE>
                </SIG>
                <P>For the reasons set forth in the preamble, the Federal Communications Commission proposes to amend 47 CFR part 15 as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 15—RADIO FREQUENCY DEVICES</HD>
                    <P>1. The authority citation for part 15 continues to read as follows:</P>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P> 47 U.S.C. 154, 302a, 303, 304, 307, 336 and 544a.</P>
                    </AUTH>
                    <P>2. Section 15.35 is amended by revising paragraph (b) to read as follows:</P>
                    <SECTION>
                        <SECTNO>§ 15.35 </SECTNO>
                        <SUBJECT>Measurement detector functions and bandwidths.</SUBJECT>
                        <STARS/>
                        <P>
                            (b) Unless otherwise specified, on any frequency or frequencies above 1000 MHz, the radiated emission limits are based on the use of measurement instrumentation employing an average detector function. Unless otherwise specified, measurements above 1000 MHz shall be performed using a minimum resolution bandwidth of 1 MHz. When average radiated emission measurements are specified in this part, including average emission measurements below 1000 MHz, there also is a limit on the peak level of the radio frequency emissions. Unless otherwise specified, 
                            <E T="03">e.g.,</E>
                             see §§ 15.250, 15.252, 15.253(b), 15.255, and 15.509 through 15.519, the limit on peak radio frequency emissions is 20 dB above the maximum permitted average emission limit applicable to the equipment under test. This peak limit applies to the total peak emission level radiated by the device, e.g., the total peak power level. Note that the use of a pulse desensitization correction factor may be needed to determine the total peak emission level. The instruction manual or application note for the measurement instrument should be consulted for determining pulse desensitization factors, as necessary.
                        </P>
                        <STARS/>
                        <P>3. Section 15.253 is revised to read as follows:</P>
                    </SECTION>
                    <SECTION>
                        <SECTNO>§ 15.253 </SECTNO>
                        <SUBJECT>Operation within the bands 46.7-46.9 GHz and 76.0-77.0 GHz.</SUBJECT>
                        <P>(a) Operation within the band 46.7-46.9 GHz is restricted to vehicle-mounted field disturbance sensors used as vehicle radar systems. The transmission of additional information, such as data, is permitted provided the primary mode of operation is as a vehicle-mounted field disturbance sensor. Operation under the provisions of this section is not permitted on aircraft or satellites.</P>
                        <P>(1) The radiated emission limits within the bands 46.7-46.9 GHz are as follows:</P>
                        <P>
                            (i) If the vehicle is not in motion, the power density of any emission within the bands specified in this section shall not exceed 200 nW/cm
                            <SU>2</SU>
                             at a distance of 3 meters from the exterior surface of the radiating structure.
                        </P>
                        <P>
                            (ii) For forward-looking vehicle mounted field disturbance sensors, if the vehicle is in motion the power density of any emission within the bands specified in this section shall not exceed 60 μW/cm
                            <SU>2</SU>
                             at a distance of 3 meters from the exterior surface of the radiating structure.
                        </P>
                        <P>
                            (iii) For side-looking or rear-looking vehicle-mounted field disturbance sensors, if the vehicle is in motion the power density of any emission within the bands specified in this section shall not exceed 30 μW/cm
                            <SU>2</SU>
                             at a distance of 3 meters from the exterior surface of the radiating structure.
                        </P>
                        <P>(iv) The provisions in § 15.35 limiting peak emissions apply.</P>
                        <P>(2) [Reserved]</P>
                        <P>(b) Operation within the band 76.0-77.0 GHz is restricted to vehicle-mounted field disturbance sensors used as vehicle radar systems and to fixed radar systems. The transmission of additional information, such as data, is permitted provided the primary mode of operation is as a vehicle-mounted field disturbance sensor or as a fixed field disturbance sensor. Operation under the provisions of this section is not permitted on aircraft or satellites.</P>
                        <P>(1) The radiated emission limits within the bands 76.0-77.0 GHz are as follows:</P>
                        <P>
                            (i) The average power density of any emission within the bands specified in this section shall not exceed 88 µW/cm
                            <SU>2</SU>
                             at a distance of 3 meters from the exterior surface of the radiating structure.
                        </P>
                        <P>
                            (ii) The peak power density of any emission within the bands specified in this section shall not exceed 279 µW/cm
                            <SU>2</SU>
                             at a distance of 3 meters from the exterior surface of the radiating structure.
                        </P>
                        <P>(2) [Reserved]</P>
                        <P>(c) The power density of any emissions outside the operating band shall consist solely of spurious emissions and shall not exceed the following:</P>
                        <P>(1) Radiated emissions below 40 GHz shall not exceed the general limits in § 15.209.</P>
                        <P>(2) Radiated emissions outside the operating band and between 40 GHz and 200 GHz shall not exceed the following:</P>
                        <P>(i) For field disturbance sensors operating in the band 46.7-46.9 GHz:</P>
                        <P>
                            2 pW/cm
                            <SU>2</SU>
                             at a distance of 3 meters from the exterior surface of the radiating structure.
                        </P>
                        <P>(ii) For field disturbance sensors operating in the band 76-77 GHz:</P>
                        <P>
                            600 pW/cm
                            <SU>2</SU>
                             at a distance of 3 meters from the exterior surface of the radiating structure.
                        </P>
                        <P>
                            (3) For radiated emissions above 200 GHz from field disturbance sensors operating in the 76-77 GHz band: The power density of any emission shall not exceed 1000 pW/cm
                            <SU>2</SU>
                             at a distance of 3 meters from the exterior surface of the radiating structure.
                        </P>
                        <P>(4) For field disturbance sensors operating in the 76-77 GHz band, the spectrum shall be investigated up to 231 GHz.</P>
                        <P>(d) Fundamental emissions must be contained within the frequency bands specified in this section during all conditions of operation. Equipment is presumed to operate over the temperature range −20 to +50 degrees Celsius with an input voltage variation of 85% to 115% of rated input voltage, unless justification is presented to demonstrate otherwise.</P>
                        <P>
                            (e) Regardless of the power density levels permitted under this section, devices operating under the provisions of this section are subject to the radiofrequency radiation exposure 
                            <PRTPAGE P="35181"/>
                            requirements specified in §§ 1.1307(b), 2.1091 and 2.1093 of this chapter, as appropriate. Applications for equipment authorization of devices operating under this section must contain a statement confirming compliance with these requirements for both fundamental emissions and unwanted emissions. Technical information showing the basis for this statement must be submitted to the Commission upon request.
                        </P>
                    </SECTION>
                </PART>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-14744 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6712-01-P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="S">FEDERAL COMMUNICATIONS COMMISSION </AGENCY>
                <CFR>47 CFR Parts 74, 78, and 101 </CFR>
                <DEPDOC>[WT Docket No. 10-153; DA 11-1011] </DEPDOC>
                <SUBJECT>Wireless Backhaul; Further Inquiry Into Fixed Service Sharing of the 6875-7125 and 12700-13200 MHz Bands </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Communications Commission. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Request for comments. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>In this document, the Commission seeks additional, focused comment on certain issues raised in its Wireless Backhaul proceeding to remove regulatory barriers to the use of spectrum for backhaul and other point-to-point and point-to-multipoint communications and to increase efficient use of spectrum for backhaul, by updating regulatory classifications that may not have kept pace with the evolution of converged digital technologies. Specifically, we seek to supplement the record in this proceeding on the feasibility of sharing in the 7 and 13 GHz bands, limiting the frequency ranges available for Fixed Service (FS) in order to ensure the continuation of electronic newsgathering operations, and the appropriate channelization scheme, coordination procedures, and capacity and loading requirements for the bands. </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Submit comments on or before June 27, 2011. </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Federal Communications Commission, 445 12th Street, SW., Washington, DC 20554. You may submit comments, identified by DA 11-1011, WT Docket No. 10-153, 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">Federal Communications Commission's Web Site: http://www.fcc.gov/cgb/ecfs/.</E>
                         Follow the instructions for submitting comments. 
                    </P>
                    <P>
                        <E T="03">People with Disabilities:</E>
                         Contact the FCC to request reasonable accommodations (accessible format documents, sign language interpreters, CART, etc.) by 
                        <E T="03">e-mail: FCC504@fcc.gov</E>
                         or 
                        <E T="03">phone:</E>
                         (202) 418-0530 or 
                        <E T="03">TTY:</E>
                         (202) 418-0432. 
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Charles Oliver, Broadband Division, Wireless Telecommunications Bureau, Federal Communications Commission, 445 12th Street, SW., Washington, DC 20554, at (202) 418-1325 or via the Internet to 
                        <E T="03">Charles.Oliver@fcc.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    This is a summary of a the Commission's document adopted and released by the FCC on June 7, 2011, in WT Docket No. 10-153. The full text of this document is available for inspection and copying during normal business hours in the FCC Reference Information Center, Room CY-A257, 445 12th Street, SW., Washington, DC 20554. The complete text may be purchased from the Commission's duplicating contractor, Best Copy and Printing, Inc. (BCPI), Portals II, 445 12th Street, SW., Room CY-B402, Washington, DC 20554, (202) 488-5300, facsimile (202) 488-5563, or via e-mail at 
                    <E T="03">fcc@bcpiweb.com.</E>
                     The complete text is also available on the Commission's Web site at 
                    <E T="03">http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-11-1011A1.doc</E>
                    . Alternative formats (computer diskette, large print, audio cassette, and Braille) are available by contacting Brian Millin at (202) 418-7426, TTY (202) 418-7365, or via e-mail to 
                    <E T="03">bmillin@fcc.gov.</E>
                </P>
                <HD SOURCE="HD1">Summary </HD>
                <P>1. On August 5, 2010, the Commission commenced a proceeding to remove regulatory barriers to the use of spectrum for wireless backhaul and other point-to-point and point-to-multipoint communications. The proceeding sought to increase efficient use of spectrum for backhaul, by updating regulatory classifications that may not have kept pace with the evolution of converged digital technologies. </P>
                <P>
                    2. 
                    <E T="03">Feasibility of FS Sharing in BAS and CARS Bands: The Wireless Backhaul NPRM/NOI</E>
                     proposed to allow FS operations to share the 6875-7125 MHz (7 GHz Band) and 12700-13200 MHz (13 GHz band) bands currently used by the Broadcast Auxiliary Service (BAS) and the Cable TV Relay Service (CARS). The Commission stated its intention to protect existing licensees, through use of existing frequency coordination procedures. There are currently both fixed and mobile BAS and CARS operations in the 7 and 13 GHz bands. Fixed BAS in those bands include television studio-to-transmitter links, television relay stations, and television translator relay stations. CARS stations are authorized to relay various types of signals intended for use by cable television systems or other eligible systems. Mobile BAS includes television pickup stations and CARS pickup stations (“TV pickup stations”), which are authorized to transmit program material, orders concerning such program material, and related communications from the scenes of events occurring in places other than a television studio to associated television stations. TV pickup stations in these bands are licensed either for a radius around a set of coordinates or in the vicinity of a given television market. In addition, there are a limited number of Local Television Transmission Service (LTTS) stations in the 7 and 13 GHz bands authorized pursuant to § 101.803(b) of the Commission's rules. 
                </P>
                <P>
                    3. In the 
                    <E T="03">Wireless Backhaul NPRM/NOI,</E>
                     the Commission proposed to require frequency coordination for new FS, BAS, and CARS applications in the 7 and 13 GHz bands. Under the current rules, all FS and fixed BAS and CARS stations above 2110 MHz must use the prior coordination notice procedure described in § 101.103(d) of the Commission's rules. LTTS licenses in the 7 and 13 GHz bands contain special conditions that require use of the prior coordination notice procedure before they operate in any given area. TV pickup stations and temporary fixed facilities may coordinate using less formal procedures, including using local frequency coordination committees. The Society of Broadcast Engineers (SBE) conducts a local frequency coordination program for BAS and CARS spectra. 
                </P>
                <P>4. A majority of commenters express qualified support for the proposal to open the 7 and 13 GHz bands to part 101 FS operators, while several broadcasting-affiliated entities oppose the proposal. Both supporters and opponents of the proposal express concerns about how to protect existing electronic news-gathering operations using TV pickup stations from interference due to FS operations, and whether meaningful FS operation in the bands will be possible given the potential for such interference. In contrast, there appears to be little concern about the ability of FS to coexist with fixed BAS and CARS. </P>
                <P>
                    5. WTB staff has conducted additional analysis of the 7 and 13 GHz bands. The results are depicted in several maps, which are available on the Commission's Web site at 
                    <E T="03">
                        http://hraunfoss.fcc.gov/edocs_public/
                        <PRTPAGE P="35182"/>
                        attachmatch/DA-11-1011A2.doc
                    </E>
                    , that show existing BAS and CARS operations in the 7 and 13 GHz bands. In light of this staff analysis, we seek additional comment to understand better the circumstances in which FS sharing of the 7 and 13 GHz bands with BAS and CARS might be practical. The analysis appears to indicate that, even if FS operations were totally excluded from the service areas of TV pickup stations and CARS facilities, there would be considerable areas where FS facilities could be licensed. For example, in the 7 GHz band in Minnesota, there is only one TV pickup station with a defined area of operation authorized in the entire state, and three additional stations authorized in adjacent states that have minimal overlapping area within the state of Minnesota. In comparison, the prevalence of fixed links in the adjacent 6525-6875 MHz bands shows much more extensive use of that band. It appears that opening the 7 and 13 GHz bands to FS operations could be of particular benefit in rural areas, where the spectrum is largely available. We also note that only one new BAS TV pickup license has been granted in the 7 GHz and 13 GHz bands in the last two years. Moreover, the Fixed Wireless Communications Coalition (FWCC) reports that BAS and CARS path and channel licensing, respectively, in the 13 GHz band have dropped sharply in the last decade. 
                </P>
                <P>6. We seek further input regarding whether imposing geographic restrictions on FS sharing in the 7 and 13 GHz bands would minimize interference potential between FS facilities and TV pickup stations. Specifically, the Commission could prohibit an FS station from locating its path within the service area of a co-channel TV pickup station. Additionally, the Commission could require FS operators to coordinate any new fixed links with TV pickup stations within the appropriate coordination zone of any new fixed link. </P>
                <P>7. We also seek comment on whether limiting new FS links in the 7 and 13 GHz bands to those areas outside the service areas of TV pickup stations would address commenters' concerns regarding the potential for harmful interference. We invite comment on the staff analysis and the data reported by FWCC on 13 GHz utilization. Are there other factors the Commission should consider regarding bands' suitability for FS use in areas where TV pickup stations are not operating? </P>
                <P>
                    8. 
                    <E T="03">Reserving Spectrum for Nationwide BAS Use.</E>
                     The 
                    <E T="03">Wireless Backhaul NPRM/NOI</E>
                     sought comment on making the 7 and 13 GHz band available for FS use and whether FS use would be compatible with existing uses in those bands. We now inquire whether the Commission should continue to reserve a portion of these bands exclusively for BAS and CARS operations, in order to enhance the ability of BAS and CARS to coexist with FS and facilitate nationwide use of BAS and CARS services. There are some differences in the rules governing BAS and CARS and those governing FS that might warrant such a reservation. For example, the Commission's rules authorize broadcasters to operate broadcast auxiliary facilities on a short-term basis on a secondary basis without prior Commission authorization. This provision may permit broadcasters to cover breaking news events in areas outside those covered by their TV pickup stations authorization. 
                </P>
                <P>
                    9. Consistent with the request for comment in the 
                    <E T="03">Wireless Backhaul NPRM/NOI</E>
                     on the ability of BAS and CARS to share with FS in the 7 and 13 GHz bands, we seek comment on whether the Commission should continue to exclude FS facilities from the 7075-7125 MHz and 13.15-13.2 GHz bands, and reserve two 25 megahertz channels for BAS and CARS use in each band. In the 7 GHz band, reserving 7075-7125 MHz for BAS would mean that FS sharing could occur in the 6875-7075 MHz frequency range, which is contiguous to the 6525-6875 MHz band where FS operations are already authorized. In the 13 GHz band, this proposal would maintain the status quo in the 13.15-13.2 GHz band, which is currently reserved for TV pickup stations inside a 50 kilometer basis of the top 100 television markets. We seek comment on whether this proposal will strike the appropriate balance between making FS spectrum available for backhaul and other uses and ensuring spectrum is available for critical newsgathering activities. We also seek comment on other alternatives for reserving capacity for BAS and CARS. We also seek comment on how alternative technologies for providing video coverage of live events may affect the need to exclude FS from a portion of these bands. 
                </P>
                <P>
                    10. 
                    <E T="03">Channelization Plans:</E>
                     In the 
                    <E T="03">Wireless Backhaul NPRM/NOI,</E>
                     noting that existing operations in the 7 and 13 GHz band used 25 megahertz bandwidth channels, the Commission proposed to make a variety of channel bandwidths available for both FS and BAS use, and to list such channel bandwidths in our rules, consistent with our practice in other FS bands. The Commission also sought comment on alternative channelization schemes. Several commenters, including FWCC and EIBASS, express concern that allowing 10 and 30 megahertz channels would preclude operation on multiple 25 megahertz channels used by BAS and result in wasted spectrum. EIBASS argues that the Commission already allows broadcasters to request signal bandwidths that are less than the standard channel bandwidth, and that there is no need to clutter the Commission's rules with a large list of arbitrarily chosen channel segments. With respect to the 13 GHz band, FWCC proposes a channel plan based on 28 megahertz channels. 
                </P>
                <P>11. In light of the concerns raised by FWCC and EIBASS, we seek comment on whether the Commission should allow a maximum channel bandwidth of 25 megahertz for FS in the 7 and 13 GHz bands. We invite comment on whether a maximum 25 megahertz channel bandwidth would be useful to FS operators and whether equipment manufacturers would develop equipment for such a band plan. </P>
                <P>12. For the 7 GHz band, we seek comment on the following band plan:</P>
                <HD SOURCE="HD2">25 MHz Bandwidth Channels </HD>
                <GPOTABLE COLS="2" OPTS="L2,tp0,i1" CDEF="10C,10C">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">
                            Transmit (receive) 
                            <LI>(MHz)</LI>
                        </CHED>
                        <CHED H="1">
                            Receive (transmit) 
                            <LI>(MHz)</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">6887.5 </ENT>
                        <ENT>6987.5</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">6912.5 </ENT>
                        <ENT>7012.5</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">6937.5 </ENT>
                        <ENT>7037.5</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">6962.5 </ENT>
                        <ENT>7062.5</ENT>
                    </ROW>
                </GPOTABLE>
                <P>For the 13 GHz band, we seek comment on the following channel plan based on 25 megahertz channels: </P>
                <HD SOURCE="HD2">25 MHz Bandwidth Channels </HD>
                <GPOTABLE COLS="02" OPTS="L2,tp0,i1" CDEF="10C,10C">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">
                            Transmit (receive)
                            <LI>(MHz)</LI>
                        </CHED>
                        <CHED H="1">
                            Receive (transmit)
                            <LI>(MHz)</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">12712.5</ENT>
                        <ENT> 12937.5</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">12737.5</ENT>
                        <ENT> 12962.5</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">12762.5</ENT>
                        <ENT> 12987.5</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">12787.5</ENT>
                        <ENT> 13012.5</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">12812.5</ENT>
                        <ENT> 13037.5</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">12837.5</ENT>
                        <ENT> 13062.5</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">12862.5</ENT>
                        <ENT> 13087.5</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">12887.5</ENT>
                        <ENT> 13112.5</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">12912.5</ENT>
                        <ENT> 13137.5</ENT>
                    </ROW>
                </GPOTABLE>
                <P>We also seek comment on the alternative band plan offered by FWCC based on 28 megahertz bandwidth channels, which it explains comes from the International Telecommunications Union: </P>
                <GPOTABLE COLS="02" OPTS="L2,tp0,i1" CDEF="10C,10C">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">
                            Transmit (receive)
                            <LI>(MHz)</LI>
                        </CHED>
                        <CHED H="1">
                            Receive (transmit)
                            <LI>(MHz)</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">12765</ENT>
                        <ENT> 13031</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">12793</ENT>
                        <ENT> 13059</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">12821</ENT>
                        <ENT> 13087</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="35183"/>
                        <ENT I="01">12849</ENT>
                        <ENT> 13115</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">12877</ENT>
                        <ENT> 13143</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">12905</ENT>
                        <ENT> 13171</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">12933</ENT>
                        <ENT> 13199</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">12961</ENT>
                        <ENT> 13227</ENT>
                    </ROW>
                </GPOTABLE>
                <P>13. We also seek comment on EIBASS” suggestion that FS operators be allowed to specify a lesser channel bandwidth without identifying such lesser channel bandwidths in our rules. We also seek comment on whether we should allow 50 megahertz channels in the 13 GHz band for FS, BAS, and CARS in order to allow systems to use wider channels to obtain higher data rates. </P>
                <P>
                    14. 
                    <E T="03">Coordination Procedures:</E>
                     Several commenters express concern that permitting FS operations in the 7 and 13 GHz bands, subject to frequency coordination, will inhibit mobile electronic newsgathering and temporary fixed operation for video coverage of newsworthy events. 
                </P>
                <P>15. If the Commission were to permit FS operations in the 7 and 13 GHz bands only outside of the authorized service areas of TV pickup stations, as discussed in paragraphs 2-7 above, it could likewise maintain the existing requirements that FS and fixed BAS and CARS applicants coordinate using the more formal part 101 procedures. The Commission, however, could allow TV pickup stations and other temporary fixed operators to continue to use informal frequency coordination procedures within the authorized service areas of TV pickup stations. We seek comment on appropriate coordination procedures for FS with fixed BAS, CARS stations, and TV pickup stations in shared frequencies, especially in light of geographic restrictions the Commission may adopt. </P>
                <P>
                    16. 
                    <E T="03">Capacity and Loading Requirements:</E>
                     The 
                    <E T="03">Wireless Backhaul NPRM/NOI</E>
                     proposed to apply the Fixed Services minimum capacity and loading requirements to the 6875-7125 MHz and 12700-13200 MHz bands. While several commenters support that proposal, SBE and EIBASS express concern. SBE states that BAS links in the 7 and 13 GHz bands are used for intercity relay backhaul from distant electronic news-gathering sites, and have no content and no modulation on them until a new live shot is tuned in and transmitting. SBE argues that such necessary usage would be prohibited by the proposed rule change. EIBASS echoes SBE's concern, and proposes certain exemptions to address the concern. 
                </P>
                <P>
                    17. With respect to this issue, we note that the 
                    <E T="03">NPRM</E>
                     did not propose to apply the capacity and loading criteria to operations authorized under part 74 and part 78, such as TV studio-transmitter links and intercity relays, but rather only to the FS operations authorized under part 101. In addition, § 101.141(a)(5) of the rules exempts transmitters carrying digital video motion material from the capacity and loading requirements of §§ 101.141(a)(2) and (3), provided that at least 50 percent of the payload is digital video motion material and the minimum bit rate specified in § 101.141(a)(1) is met, 
                    <E T="03">i.e.</E>
                    , that the bit rate, in bits per second, is equal to or greater than the bandwidth measured in Hertz. We seek comment on the extent to which this existing exemption addresses the concerns expressed by SBE and EIBASS. In what ways, if any, should this exemption be modified before it can be applied to the 6875-7125 MHz and 12700-13200 MHz bands? 
                </P>
                <HD SOURCE="HD1">Procedural Matters </HD>
                <P>
                    18. 
                    <E T="03">Ex Parte Rules—Permit-But-Disclose.</E>
                     This matter shall be treated as a “permit-but-disclose” proceeding in accordance with the 
                    <E T="03">ex parte</E>
                     rules. Persons making 
                    <E T="03">ex parte</E>
                     presentations must file a copy of any written presentation or a memorandum summarizing any oral presentation within two business days after the presentation (unless a different deadline applicable to the Sunshine period applies). Persons making oral 
                    <E T="03">ex parte</E>
                     presentations are reminded that memoranda summarizing the presentation must (1) List all persons attending or otherwise participating in the meeting at which the 
                    <E T="03">ex parte</E>
                     presentation was made, and (2) summarize all data presented and arguments made during the presentation. If the presentation consisted in whole or in part of the presentation of data or arguments already reflected in the presenter's written comments, memoranda or other filings in the proceeding, the presenter may provide citations to such data or arguments in his or her prior comments, memoranda, or other filings (specifying the relevant page and/or paragraph numbers where such data or arguments can be found) in lieu of summarizing them in the memorandum. Documents shown or given to Commission staff during 
                    <E T="03">ex parte</E>
                     meetings are deemed to be written 
                    <E T="03">ex parte</E>
                     presentations and must be filed consistent with rule 1.1206(b). In proceedings governed by rule 1.49(f) or for which the Commission has made available a method of electronic filing, written 
                    <E T="03">ex parte</E>
                     presentations and memoranda summarizing oral 
                    <E T="03">ex parte</E>
                     presentations, and all attachments thereto, must be filed through the electronic comment filing system available for that proceeding, and must be filed in their native format (
                    <E T="03">e.g.</E>
                    , .doc, .xml, .ppt, searchable .pdf). Participants in this proceeding should familiarize themselves with the Commission's 
                    <E T="03">ex parte</E>
                     rules. 
                </P>
                <HD SOURCE="HD1">Comment Period and Procedures </HD>
                <P>
                    19. The 
                    <E T="03">Wireless Backhaul NPRM/NOI</E>
                     included an Initial Regulatory Flexibility Analysis (IRFA) pursuant to 5 U.S.C. 603, exploring the potential impact on small entities of the Commission's proposal. We invite parties to file comments on the IRFA in light of this additional notice. 
                </P>
                <P>
                    20. Pursuant to §§ 1.415 and 1.419 of the Commission's rules, 47 CFR 1.415, 1.419, interested parties may file comments on or before June 27, 1011. Comments may be filed using: (1) The Commission's Electronic Comment Filing system (ECFS), (2) the Federal Government's eRulemaking Portal, or (3) by filing paper copies. 
                    <E T="03">See Electronic Filing of Documents in Rulemaking Proceedings,</E>
                     63 FR 24121 (1998). 
                </P>
                <P>
                    • 
                    <E T="03">Electronic Filers:</E>
                     Comments may be filed electronically using the Internet by accessing the ECFS: 
                    <E T="03">http://www.fcc.gov/cgb/ecfs/</E>
                     or 
                    <E T="03">the Federal eRulemaking Portal: http://www.regulations.gov.</E>
                     Filers should follow the instructions provided on the Web site for submitting comments. 
                </P>
                <P>
                    <E T="03">For ECFS filers,</E>
                     if multiple docket or rulemaking numbers appear in the caption of this proceeding, filers must transmit one electronic copy of the comments for each docket or rulemaking number referenced in the caption. In completing the transmittal screen, filers should include their full name, U.S. Postal Service mailing address, and the applicable docket or rulemaking number. Comments shall be sent as an electronic file via the Internet to 
                    <E T="03">http://www.fcc.gov/e-file/ecfs.html</E>
                    . In completing the transmittal screen, commenters should include their full name, Postal Service mailing address, and the applicable docket number. Parties may also submit an electronic comment by Internet e-mail. To get filing instructions for e-mail comments, commenters should send an e-mail to 
                    <E T="03">ecfs@fcc.gov,</E>
                     and include the following words in the body of the message, “get form.” A sample form and directions will be sent in response. 
                </P>
                <P>
                    • 
                    <E T="03">Paper filers:</E>
                     Parties who choose to file by paper must file an original and four copies of each filing. If more than one docket or rulemaking number 
                    <PRTPAGE P="35184"/>
                    appears in the caption of this proceeding, filers must submit two additional copies for each additional docket or rulemaking number. 
                </P>
                <P>• Filings can be sent by hand or messenger delivery, by commercial overnight courier, or by first-class or overnight U.S. Postal Service mail. All filings must be addressed to the Commission's Secretary, Office of the Secretary, Federal Communications Commission, 445 12th Street, SW., Washington, DC 20554. </P>
                <P>
                    • All hand-delivered or messenger-delivered paper filings for the Commission's Secretary must be delivered to FCC Headquarters at 445 12th Street, SW., Room TW-A325, Washington, DC 20554. All hand deliveries must be held together with rubber bands or fasteners. Any envelopes must be disposed of 
                    <E T="03">before</E>
                     entering the building. The filing hours at this location are 8 a.m. to 7 p.m. Commercial overnight mail (other than U.S. Postal Service Express Mail and Priority Mail) must be sent to 9300 East Hampton Drive, Capitol Heights, MD 20743. U.S. Postal Service first-class, Express, and Priority mail must be addressed to 445 12th Street, SW., Washington, DC 20554. 
                </P>
                <P>
                    • Parties shall also serve one copy with the Commission's copy contractor, Best Copy and Printing, Inc. (BCPI), Portals II, 445 12th Street, SW., Room CY-B402, Washington, DC 20554, (202) 488-5300, or via e-mail to 
                    <E T="03">fcc@bcpiweb.com.</E>
                </P>
                <P>
                    • 
                    <E T="03">People with Disabilities:</E>
                     To request materials in accessible formats for people with disabilities (braille, large print, electronic files, audio format), send an e-mail to 
                    <E T="03">fcc504@fcc.gov</E>
                     or call the Consumer &amp; Governmental Affairs Bureau at 202-418-0530 (voice), 202-418-0432 (tty). 
                </P>
                <P>
                    • 
                    <E T="03">Availability of Documents:</E>
                     Documents in WT Docket No. 10-153 will be available for public inspection and copying during business hours at the FCC Reference Information Center, Portals II, 445 12th Street, SW., Room CY-A257, Washington, DC 20554. The documents may also be purchased from BCPI, Portals II, 445 12th Street, SW., Room CY-B402, Washington, DC 20554, (202) 488-5300, (202) 488-5563 (fax), (202) 488-5562 (tty), or via to 
                    <E T="03">fcc@bcpiweb.com.</E>
                </P>
                <HD SOURCE="HD1">Ordering Clause </HD>
                <P>21. This action is taken under delegated authority pursuant to §§ 0.131 and 0.331 of the Commission's rules, 47 CFR 0.131, 0.331. </P>
                <SIG>
                    <FP>Federal Communications Commission. </FP>
                    <NAME>Blaise Scinto, </NAME>
                    <TITLE>Chief, Broadband Division, Wireless Telecommunications Bureau.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-14721 Filed 6-15-11; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 6712-01-P </BILCOD>
        </PRORULE>
    </PRORULES>
    <VOL>76</VOL>
    <NO>116</NO>
    <DATE>Thursday, June 16, 2011</DATE>
    <UNITNAME>Notices</UNITNAME>
    <NOTICES>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="35185"/>
                <AGENCY TYPE="F">DEPARTMENT OF AGRICULTURE</AGENCY>
                <SUBJECT>Submission for OMB Review; Comment Request</SUBJECT>
                <DATE>June 13, 2011.</DATE>
                <P>
                    The Department of Agriculture has submitted the following information collection requirement(s) to OMB for review and clearance under the Paperwork Reduction Act of 1995, Public Law 104-13. Comments regarding (a) 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; (b) the accuracy of the agency's estimate of burden including the validity of the methodology and assumptions used; (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 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 should be addressed to: Desk Officer for Agriculture, Office of Information and Regulatory Affairs, Office of Management and Budget (OMB), 
                    <E T="03">OIRA_Submission@OMB.EOP.GOV</E>
                     or fax (202) 395-5806 and to Departmental Clearance Office, USDA, OCIO, Mail Stop 7602, Washington, DC 20250-7602. Comments regarding these information collections are best assured of having their full effect if received within 30 days of this notification. Copies of the submission(s) may be obtained by calling (202) 720-8958.
                </P>
                <P>An agency may not conduct or sponsor a collection of information unless the collection of information displays a currently valid OMB control number and the agency informs potential persons who are to respond to the collection of information that such persons are not required to respond to the collection of information unless it displays a currently valid OMB control number.</P>
                <HD SOURCE="HD1">Food and Nutrition Service</HD>
                <P>
                    <E T="03">Title:</E>
                     Evaluation of the Summer Food Service Program Enhancement Demonstration Food Backs and Meal Delivery.
                </P>
                <P>
                    <E T="03">OMB Control Number:</E>
                     0584-NEW.
                </P>
                <P>
                    <E T="03">Summary of Collection:</E>
                     The Agriculture, Rural Development, Food and Drug Administration, and Related Agencies Appropriations Act of 2010 (Pub. L., 111-80), Section 749(g), directed that the Secretary of Agriculture shall carry out demonstration projects to develop and test methods of providing access to food for children in urban and rural areas during the summer months when schools are not in regular session to reduce or eliminate the food insecurity and hunger of children and to improve the nutritional status of children. These demonstrations will include the Home Delivery Demonstration and the Food Backpack Demonstration.
                </P>
                <P>
                    <E T="03">Need and Use of the Information:</E>
                     The data collected in this evaluation will be used by the Food and Nutrition Service (FNS) to provide policymakers with information to make decisions about potential changes in Federal summer food nutrition programs for children. The specific goals of the evaluation are to assess the following: (1) The impact of each Summer Food Service Program (SFSP) enhancement demonstration model on participation and meal service; (2) The food security status among recipients of the home delivered meals and backpack demonstration; (3) The “targeting accuracy” in the Meal Delivery and Backpack demonstrations; (4) The process of project implementation in each SFSP enhancement demonstration; and (5) The total and component specific costs of implementing and operating SFSP demonstrations. Data will be collected by telephone, face-to-face, electronically, and over the internet.
                </P>
                <P>
                    <E T="03">Description of Respondents:</E>
                     Individuals or household; State, Local or Tribal Government; Business or other for-profit.
                </P>
                <P>
                    <E T="03">Number of Respondents:</E>
                     1,181.
                </P>
                <P>
                    <E T="03">Frequency of Responses:</E>
                     Reporting: On occasion; Annually.
                </P>
                <P>
                    <E T="03">Total Burden Hours:</E>
                     652.
                </P>
                <SIG>
                    <NAME>Ruth Brown,</NAME>
                    <TITLE>Departmental Information Collection Clearance Officer.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-14994 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3410-30-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF AGRICULTURE</AGENCY>
                <SUBJECT>Deschutes Provincial Advisory Committee (DPAC)</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Forest Service, USDA.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of meeting.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Deschutes Provincial Advisory Committee will meet on June 10, 2011 to review the goals and objectives of the committee for the next two year period. The meeting will also provide updates on the forest restoration and sustainable recreation subcommittees. Members will meet at the Deschutes National Forest Supervisor's office, Upper Deschutes Conference Room (1001 SW. Emkay Drive, Bend, Oregon) from 9 a.m. until noon. All Deschutes Province Advisory Committee meetings are open to the public.</P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Michael Keown, Province Liaison, Sisters Ranger District, Pine Street and Highway 20, Sisters, Oregon 97759, Phone (541) 549-7735.</P>
                    <SIG>
                        <NAME>John Allen,</NAME>
                        <TITLE>Deschutes National Forest Supervisor.</TITLE>
                    </SIG>
                </FURINF>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-14793 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3410-11-M</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF AGRICULTURE</AGENCY>
                <SUBAGY>Animal and Plant Health Inspection Service</SUBAGY>
                <DEPDOC>[Docket No. APHIS-2011-0043]</DEPDOC>
                <SUBJECT>Notice of Request for Extension of Approval of an Information Collection; Bovine Spongiform Encephalopathy; Importation of Animals and Animal Products</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 
                        <PRTPAGE P="35186"/>
                        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 importation of animals and animal products and byproducts to protect against the introduction of bovine spongiform encephalopathy into the United States.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>We will consider all comments that we receive on or before August 15, 2011.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may submit comments by either of the following methods:</P>
                    <P>
                        • 
                        <E T="03">Federal eRulemaking Portal:</E>
                         Go to 
                        <E T="03">http://www.regulations.gov/#!documentDetail;D=APHIS-2011-0043-0001.</E>
                    </P>
                    <P>
                        • 
                        <E T="03">Postal Mail/Commercial Delivery:</E>
                         Send your comment to Docket No. APHIS-2011-0043, Regulatory Analysis and Development, PPD, APHIS, Station 3A-03.8, 4700 River Road Unit 118, Riverdale, MD 20737-1238.
                    </P>
                    <P>
                        Supporting documents and any comments we receive on this docket may be viewed at 
                        <E T="03">http://www.regulations.gov/#!docketDetail;D=APHIS-2011-0043</E>
                         or in our reading room, which 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 regulations for the importation of animals and animal products and byproducts to prevent the introduction of bovine spongiform encephalopathy into the United States, contact Dr. Langston Hull, Staff Veterinarian, Live Animal Imports, National Center for Import and Export, VS, APHIS, 4700 River Road, Unit 39, Riverdale, MD 20737; (301) 734-8364. For copies of more detailed information on the information collection, contact Mrs. Celeste Sickles, APHIS' Information Collection Coordinator, at (301) 851-2908.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    <E T="03">Title:</E>
                     Bovine Spongiform Encephalopathy; Importation of Animals and Animal Products.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     0579-0234.
                </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 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 of animals and animal products into the United States to guard against the introduction of animal diseases. The regulations in 9 CFR parts 93, 94, 95, and 96 (referred to below as the regulations) govern the importation of certain animals, birds, poultry, meat, other animal products and byproducts, hay, and straw into the United States in order to prevent the introduction of various animal diseases, including bovine spongiform encephalopathy (BSE), a chronic degenerative disease affecting the central nervous system of cattle.
                </P>
                <P>To help ensure that BSE is not introduced into the United States, the regulations allow, under specified conditions, the importation of certain live ruminants and ruminant products and byproducts. These requirements necessitate the use of several information collection activities, including VS Form 16-3, permit application; certification statements for the importation of ruminants and ruminant products; certificate for inedible processed animal origin materials and products from BSE-free regions; cooperative agreements with foreign facilities that process and store regulated materials and products destined for importation into the United States; VS Form 17-33, Animals Imported for Immediate Slaughter; the placing of seals on conveyances from the exporting region; agreement with slaughter facilities on use of seals on conveyances transporting animals from BSE minimal-risk regions; and notification of designated individuals authorized to break seals.</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 collection of information, 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.6039374 hours per response.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     U.S. importers; herd owners; foreign exporters; foreign salaried veterinary officials of exporting regions; APHIS accredited veterinarians; slaughter facility personnel.
                </P>
                <P>
                    <E T="03">Estimated annual number of respondents:</E>
                     5,949.
                </P>
                <P>
                    <E T="03">Estimated annual number of responses per respondent:</E>
                     21.695747.
                </P>
                <P>
                    <E T="03">Estimated annual number of responses:</E>
                     129,068.
                </P>
                <P>
                    <E T="03">Estimated total annual burden on respondents:</E>
                     77,949 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 10th day of June 2011.</DATED>
                    <NAME>Kevin Shea,</NAME>
                    <TITLE>Acting Administrator, Animal and Plant Health Inspection Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-14989 Filed 6-15-11; 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-2011-0037]</DEPDOC>
                <SUBJECT>Notice of Availability of a Pest Risk Analysis for Interstate Movement of Rambutan From Puerto Rico Into the Continental United States</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Animal and Plant Health Inspection Service, USDA.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>We are advising the public that we have prepared a pest risk analysis that evaluates the risks associated with the interstate movement into the continental United States of fresh rambutan fruit from Puerto Rico. Based on that analysis, we believe that the application of one or more designated phytosanitary measures will be sufficient to mitigate the risks of introducing or disseminating plant pests or noxious weeds via the interstate movement of rambutan from Puerto Rico. We are making the pest risk analysis available to the public for review and comment.</P>
                </SUM>
                <DATES>
                    <PRTPAGE P="35187"/>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>We will consider all comments that we receive on or before August 15, 2011.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may submit comments by either of the following methods:</P>
                    <P>
                        • 
                        <E T="03">Federal eRulemaking Portal:</E>
                         Go to 
                        <E T="03">http://www.regulations.gov/#!documentDetail;D=APHIS-2011-0037-0001.</E>
                    </P>
                    <P>
                        • 
                        <E T="03">Postal Mail/Commercial Delivery:</E>
                         Send your comment to Docket No. APHIS-2011-0037, Regulatory Analysis and Development, PPD, APHIS, Station 3A-03.8, 4700 River Road Unit 118, Riverdale, MD 20737-1238.
                    </P>
                    <P>
                        Supporting documents and any comments we receive on this docket may be viewed at 
                        <E T="03">http://www.regulations.gov/#!docketDetail;D=APHIS-2011-0037</E>
                         or in our reading room, which 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>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Mr. Philip Grove, Regulatory Coordinator, PPQ, APHIS, 4700 River Road Unit 156, Riverdale, MD 20737-1231; (301) 734-6280.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Background</HD>
                <P>Under the regulations in “Subpart—Regulated Articles From Hawaii and the Territories” (7 CFR 318.13-1 through 318.13-26, referred to below as the regulations), the Animal and Plant Health Inspection Service (APHIS) of the U.S. Department of Agriculture prohibits or restricts the interstate movement of fruits and vegetables into the continental United States from Hawaii, Puerto Rico, the U.S. Virgin Islands, Guam, and the Commonwealth of the Northern Mariana Islands to prevent plant pests and noxious weeds from being introduced into and spread within the continental United States. (The continental United States is defined in § 318.13-2 of the regulations as the 48 contiguous States, Alaska, and the District of Columbia.)</P>
                <P>Section 318.13-4 contains a performance-based process for approving the interstate movement of commodities that, based on the findings of a pest risk analysis, can be safely moved subject to one or more of the designated phytosanitary measures listed in paragraph (b) of that section.</P>
                <P>
                    APHIS received a request from the Commonwealth of Puerto Rico to allow the interstate movement of fresh rambutan fruit (
                    <E T="03">Nephelium lappaceum</E>
                     L.) from Puerto Rico to the continental United States. We have completed a pest list to identify pests of quarantine significance that could follow the pathway of interstate movement into the continental United States and, based on that pest list, have prepared a risk management analysis to identify phytosanitary measures that could be applied to the commodity to mitigate the pest risk. We have concluded that rambutan can be safely moved from Puerto Rico to the continental United States using one or more of the six designated phytosanitary measures listed in § 318.13-4(b). These measures are:
                </P>
                <P>• Inspection and certification by an inspector in Puerto Rico that the rambutan are free of all quarantine pests likely to follow the pathway of interstate movement of the rambutan;</P>
                <P>• Movement of the rambutan as commercial consignments only; and</P>
                <P>• Distribution of the rambutan only within a defined area (a prohibition on movement to Hawaii, the Virgin Islands, or Guam) and marking of the boxes or containers in which the rambutan is distributed to indicate those distribution restrictions.</P>
                <P>
                    Therefore, in accordance with § 318.13-4(c), we are announcing the availability of our pest risk analysis for public review and comment. The pest risk analysis may be viewed on the Regulations.gov Web site or in our reading room (see 
                    <E T="02">ADDRESSES</E>
                     above for instructions for accessing Regulations.gov and information on the location and hours of the reading room). You may request paper copies of the pest risk analysis by calling or writing to the person listed under 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                    . Please refer to the subject of the pest risk analysis when requesting copies.
                </P>
                <P>After reviewing the comments we receive, we will announce our decision regarding the interstate movement of rambutan from Puerto Rico to the continental United States in a subsequent notice. If the overall conclusions of the analysis and the Administrator's determination of risk remain unchanged following our consideration of the comments, then we will begin allowing the interstate movement of rambutan from Puerto Rico to the continental United States subject to the requirements specified in the risk management document.</P>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P>7 U.S.C. 7701-7772, and 7781-7786; 7 CFR 2.22, 2.80, and 371.3.</P>
                </AUTH>
                <SIG>
                    <DATED>Done in Washington, DC, this 10th day of June 2011.</DATED>
                    <NAME>Kevin Shea,</NAME>
                    <TITLE>Acting Administrator, Animal and Plant Health Inspection Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-14992 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3410-34-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF AGRICULTURE</AGENCY>
                <SUBAGY>Forest Service</SUBAGY>
                <SUBJECT>Fremont and Winema Resource Advisory Committee</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Forest Service, USDA.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of meeting.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Fremont and Winema Resource Advisory Committee will meet in Lakeview Oregon, for the purpose of evaluating and recommending resource management projects for funding in FY 2012, under the provisions of Title II of the Secure Rural Schools and Community Self-Determination Act of 2000 (reauthorized in 2008).</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The meeting will be held on July 19 and 20, 2011.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>The meeting will take place at the Lakeview Interagency Office, 1301 South G Street, Lakeview, OR 97630.</P>
                    <P>
                        Send written comments to Fremont and Winema Resource Advisory Committee, c/o USDA Forest Service, Klamath Ranger District, 2819 Dahlia, Suite A, Klamath Falls, Oregon or electronically to 
                        <E T="03">agowan@fs.fed.us</E>
                        .
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Amy Gowan, Designated Federal Official, c/o Klamath Ranger District, 2819 Dahlia, Suite A, Klamath Falls, Oregon, telephone (541) 883-6741.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The agenda will include a review and evaluation of FY 2012 Title II proposals including presentations by project proponents. Business items will include the prioritization and ranking of proposals by the RAC, including final recommendations for funding of fiscal year 2012 projects.</P>
                <P>All Fremont and Winema Resource Advisory Committee Meetings are open to the public. There will be a time for public input and comment. Interested citizens are encouraged to attend.</P>
                <SIG>
                    <DATED>Dated: June 10, 2011.</DATED>
                    <NAME>Amy Gowan,</NAME>
                    <TITLE>Designated Federal Official.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-14939 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3410-11-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="35188"/>
                <AGENCY TYPE="N">DEPARTMENT OF DEFENSE</AGENCY>
                <SUBAGY>Office of the Secretary</SUBAGY>
                <DEPDOC>[Transmittal Nos. 11-22]</DEPDOC>
                <SUBJECT>36(b)(1) Arms Sales Notification</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Defense Security Cooperation Agency, Department of Defense.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Department of Defense is publishing the unclassified text of a section 36(b)(1) arms sales notification. This is published to fulfill the requirements of section 155 of Public Law 104-164 dated July 21, 1996.</P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Ms. B. English, DSCA/DBO/CFM, (703) 601-3740.</P>
                    <P>The following is a copy of a letter to the Speaker of the House of Representatives, Transmittals 11-22 with attached transmittal, and policy justification.</P>
                    <SIG>
                        <DATED>Dated: June 10, 2011.</DATED>
                        <NAME>Aaron Siegel,</NAME>
                        <TITLE>Alternate OSD Federal Register Liaison Officer, Department of Defense.</TITLE>
                    </SIG>
                    <BILCOD>BILLING CODE 5001-06-P</BILCOD>
                    <GPH SPAN="3" DEEP="532">
                        <GID>EN16JN11.003</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="403">
                        <PRTPAGE P="35189"/>
                        <GID>EN16JN11.004</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="368">
                        <PRTPAGE P="35190"/>
                        <GID>EN16JN11.005</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="284">
                        <PRTPAGE P="35191"/>
                        <GID>EN16JN11.006</GID>
                    </GPH>
                </FURINF>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-14942 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 5001-06-C</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF DEFENSE</AGENCY>
                <SUBAGY>Office of the Secretary</SUBAGY>
                <SUBJECT>Reserve Forces Policy Board (RFPB)</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Department of Defense, Office of the Secretary of Defense Reserve Forces Policy Board.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of Advisory Committee meeting.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>Pursuant to the Federal Advisory Committee Act of 1972 (5 U.S.C. Appendix, as amended), the Sunshine in the Government Act of 1976 (5 U.S.C. 552b, as amended), and 41 CFR 102-3.150, the Department of Defense announces the following Federal advisory committee meeting of the Reserve Forces Policy Board (RFPB):</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Tuesday, July 26, 2011 from 7:30 a.m. to 4:30 p.m. and Wednesday, July 27, 2011 from 7:30 a.m. to 4:30 p.m.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Meeting address is Pentagon, Conference Room 3E863, Arlington, VA. Mailing address is Reserve Forces Policy Board, 7300 Defense Pentagon, Washington, DC 20301-7300.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Lt. Col. Julie A. Small, Designated Federal Officer, (703) 697-4486 (Voice), (703) 693-5371 (Facsimile), RFPB@osd.mil. Mailing address is Reserve Forces Policy Board, 7300 Defense Pentagon, Washington, DC 20301-7300. Web site: http://ra.defense.gov/rfpb/.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P SOURCE="NPAR">
                    <E T="03">Purpose of the Meeting:</E>
                     An open meeting of the Reserve Forces Policy Board.
                </P>
                <P>
                    <E T="03">Agenda:</E>
                     Total Force Readiness, Care for Our People, and Culture of Relevance, Effectiveness, and Efficiency.
                </P>
                <P>
                    <E T="03">Meeting Accessibility:</E>
                     Pursuant to 5 U.S.C. 552b, as amended, and 41 CFR 102-3.140 through 102-3.165, and the availability of space, this meeting is open to the public. To request a seat, contact the Designated Federal Officer not later than 06/27/11 at 703-697-4486, or by e-mail, 
                    <E T="03">RFPB@osd.mil.</E>
                </P>
                <P>
                    <E T="03">Written Statements:</E>
                     Pursuant to 41 CFR 102-3.105(j) and 102-3.140, the public or interested organizations may submit written statements to the membership of the Reserve Forces Policy Board at any time or in response to the stated agenda of a planned meeting. Written statements should be submitted to the Reserve Forces Policy Board's Designated Federal Officer. The Designated Federal Officer's contact information can be obtained from the GSA's FACA Database—
                    <E T="03">https://www.fido.gov/facadatabase/public.asp</E>
                    .
                </P>
                <P>Written statements that do not pertain to a scheduled meeting of the Reserve Forces Policy Board may be submitted at any time. However, if individual comments pertain to a specific topic being discussed at a planned meeting then these statements must be submitted no later than five business days prior to the meeting in question. The Designated Federal Officer will review all submitted written statements and provide copies to all the committee members.</P>
                <SIG>
                    <DATED>Dated: June 8, 2011.</DATED>
                    <NAME>Aaron Siegel,</NAME>
                    <TITLE>Alternate OSD Federal Register Liaison Officer, Department of Defense.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-14936 Filed 6-15-11; 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>
                <DEPDOC>[Docket ID: DOD-2011-OS-0067]</DEPDOC>
                <SUBJECT>Privacy Act of 1974; System of Records</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Defense Intelligence Agency, DoD.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice to alter a system of records.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Defense Intelligence Agency is proposing to alter a system to its existing inventory of records systems subject to the Privacy Act of 1974, (5 U.S.C. 552a), as amended.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>This proposed action will be effective further notice on July 18, 2011 unless comments are received which in a contrary.</P>
                </DATES>
                <ADD>
                    <PRTPAGE P="35192"/>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may submit comments, identified by docket number and/Regulatory Information Number (RIN) and title, by any of the following methods:</P>
                    <P>
                        * 
                        <E T="03">Federal Rulemaking Portal: http://www.regulations.gov</E>
                        .
                    </P>
                    <P>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://www.regulations.gov</E>
                         as they are received without change, including any personal identifiers or contact information.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Ms. Theresa Lowery, Defense Intelligence Agency, DAN 1-C, 600 McDill Blvd., Washington, DC 20340-0001 or by phone at (202) 231-1193.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    The Defense Intelligence Agency system 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 in 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                    .
                </P>
                <P>The proposed system report, as required by 5 U.S.C. 552a of the Privacy Act of 1974, as amended, was submitted on June 8, 2011 to the House Committee on Oversight and 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>
                <SIG>
                    <DATED>Dated: June 9, 2011.</DATED>
                    <NAME>Aaron Siegel,</NAME>
                    <TITLE>Alternate OSD Federal Register Liaison Officer, Department of Defense.</TITLE>
                </SIG>
                <PRIACT>
                    <HD SOURCE="HD1">LDIA 0660</HD>
                    <P>Security Files (July 24, 2006, 71 FR 41784)</P>
                    <STARS/>
                    <HD SOURCE="HD2">Changes:</HD>
                    <HD SOURCE="HD2">System name: </HD>
                    <P>Delete entry and replace with “Security and Counterintelligence Records”.</P>
                    <STARS/>
                    <HD SOURCE="HD2">Categories of individuals covered by the system: </HD>
                    <P>Delete entry and replace with “Current and former Defense Intelligence Agency (DIA) civilian, military and contractor personnel, nominees for employment with DIA, all persons with access to DIA facilities and infrastructure, all persons under the security cognizance of DIA. Persons about whom other U.S. government agencies have requested investigative assistance from DIA as part of lawful investigations by their agency. Individuals identified as the result of an administrative, security and/or investigative function who could pose a threat to DIA operations, data, personnel, facilities and systems.” </P>
                    <HD SOURCE="HD2">Categories of records in the system: </HD>
                    <P>Delete entry and replace with “Personnel: Name, date and place of birth, Social Security Number (SSN), gender, race, home address, family and dependent information, biometric data, medical/psychological information, financial, employment, training records, test results and education history, statements of personal history.</P>
                    <P>Administrative: Case control number, forms, documents and correspondence relating to security files, personnel security, investigative and employment records, personnel security functions, nomination notices, indoctrination/debriefing memoranda, secrecy and nondisclosure agreements, certificates of clearance.</P>
                    <P>Adjudication memoranda and supporting documentation, in-house investigations, security violations, security threats and incidents, investigations and inquiries of criminal and counterintelligence matters, investigative referrals, counterintelligence reporting, foreign travel, foreign contacts, identification badge records, retrieval indices, clearance status records, facility and access control records.”</P>
                    <HD SOURCE="HD2">Authority for maintenance of the system: </HD>
                    <P>Delete entry and replace with “National Security Act of 1947; Executive Order 12333, United States Intelligence Activities; DoDD 5105.21, Defense Intelligence Agency; DoDI 5240.06, Counterintelligence Awareness, Briefing, and Reporting Programs; DoDI 5200.08, Security of DoD Installations and Resources; DoD 5200.2.R, Personnel Security Program; DIA Directive 3020.400, DIA Critical Infrastructure Program; Intelligence Community Directive (ICD) 704, Personnel Security Standards and Procedures Governing Eligibility for Access to Special Compartmented Information and Other Controlled Access Program Information; DIA Manual 50-8, Personnel Security Program; DIA Manual 50-14, Security Investigations; DIA Regulation 50-17, Reporting Foreign Contact and Foreign Travel; DIA Instruction 5200.002, Credibility Assessment Program and E.O. 9397 (SSN), as amended.”</P>
                    <HD SOURCE="HD2">Purpose(s): </HD>
                    <P>Delete entry and replace with “The system will manage records used to accomplish security and counterintelligence functions. Information is used to comply with regulatory requirements related to initial and continued employment, to determine eligibility for access to classified information, to protect the agency's operations, data, personnel, facilities and systems (by using administrative, security and investigative functions to detect actual or potential threats and risks) and to document training and education”.</P>
                    <STARS/>
                    <HD SOURCE="HD2">Storage: </HD>
                    <P>Delete entry and replace with “Paper and Electronic storage media”.</P>
                    <HD SOURCE="HD2">Retrievability: </HD>
                    <P>Delete entry and replace with “By last name, Social Security Number (SSN), and applicable case control number”.</P>
                    <HD SOURCE="HD2">Safeguards: </HD>
                    <P>Delete entry and replace with “Records are stored in office buildings protected by guards, controlled screenings, use of visitor registers, electronic access, and/or locks. Access to records is limited to individuals who are properly screened and cleared on a need-to-know basis in the performance of their duties. Passwords and User IDs are used to control access to the system data, and procedures are in place to deter and detect browsing and unauthorized access. Physical and electronic access are limited to persons responsible for servicing and authorized to use the system”.</P>
                    <HD SOURCE="HD2">Retention and disposal: </HD>
                    <P>
                        Delete entry and replace with “Security Files: Personnel Security Records. Case files documenting the processing of investigations on Federal employees or applicants for Federal employment, whether or not a security clearance is granted, and other persons, such as those performing work for a Federal agency under contract, who require an approval before having access to Government facilities or to sensitive data. These files include questionnaires, summaries of reports prepared by the 
                        <PRTPAGE P="35193"/>
                        investigating agency, and other records reflecting the processing of the investigation and the status of the clearance, exclusive of copies of investigative reports furnished by the investigating agency. Temporary-Destroy upon notification of death or 5 years after separation or transfer of employee or no later than 5 years after contract relationship expires.
                    </P>
                    <P>Security Files: Polygraph examinations, favorable examinations; Temporary-Destroy 90 days. Unfavorable Examinations; examinations considered as part of an investigation action necessary for security adjudicative purposes and includes the Medical/Psychiatric Condition Statement-Temporary-Destroy when 15 years old.</P>
                    <P>Medical and Psychiatric Condition Statement (Favorable), Temporary-Destroy when 1 year old; (Unfavorable), Temporary-Destroy when 15 years old. </P>
                    <P>Examinations considered records of major significance, congressional interest, national security or upon which significant action was taken (trial, courts-martial, employment termination). PERMANENT—Offer to National Archives and Records Administration (NARA) when 25-30 years old. Final disposition determinations of individual cases are made by NARA.</P>
                    <P>Security Violations: Temporary-Destroy 5 years after close of case. Files referred for prosecution determination; Temporary-Destroy 3 years after close of case.</P>
                    <P>Orientation and Training: Temporary-Destroy when no longer required for current operations (documents reflecting training, security orientation, and compliance with security regulations).</P>
                    <P>Non-Disclosure Agreements: Temporary-Destroy when 70 years old.</P>
                    <P>Logs and Registers: Temporary-Destroy 2 years after final entry.”</P>
                    <HD SOURCE="HD2">System manager(s) and address: </HD>
                    <P>Delete entry and replace with “Counterintelligence and Security Office, Defense Intelligence Agency, 200 MacDill Blvd, Washington DC 20340-5100”.</P>
                    <HD SOURCE="HD2">Notification procedure: </HD>
                    <P>Delete entry and replace with “Individuals seeking to determine whether information about themselves is contained in this system of records should address written inquiries to the DIA Freedom of Information Office (DAN-1A), Defense Intelligence Agency, 200 MacDill Blvd, Washington, DC 20340-5100.</P>
                    <P>Request should contain the individual's full name, current address, and telephone number”.</P>
                    <HD SOURCE="HD2">Record access procedures: </HD>
                    <P>Delete entry and replace with “Individuals seeking access to information about themselves, contained in this system of records, should address written inquiries to the DIA Freedom of Information Office (DAN-1A), 200 MacDill Blvd, Washington, DC 20340-5100.</P>
                    <P>Request should contain the individual's full name, current address, and telephone number”.</P>
                    <HD SOURCE="HD2">Contesting record procedures: </HD>
                    <P>Delete entry and replace with “DIA's rules for accessing records, for contesting contents and appealing initial agency determinations are published in DIA Instruction 5400.001 “Defense Intelligence Agency Privacy Program”; or may be obtained from the system manager”.</P>
                    <HD SOURCE="HD2">Record source categories:</HD>
                    <P>Delete entry and replace with “Subject individuals, agency and other government officials as well as open source information”.</P>
                    <HD SOURCE="HD2">Exemptions claimed for the system: </HD>
                    <P>Delete entry and replace with “Investigatory material compiled for law enforcement purposes, other than material within the scope of subsection 5 U.S.C 552a(j)(2), may be exempt pursuant to 5 U.S.C 552(k)(2). However, if an individual is denied any right, privilege, or benefit for which he would otherwise be entitled by Federal law or which he would otherwise be eligible, as a result of maintenance of the information, the individual will 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>(k)(5) Investigatory material complied 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>(k)(6) Testing or examination material used to determine individual qualifications for appointment or promotion in the Federal or military service, if the disclosure of such material would compromise the objectivity or fairness of the test or examination process.</P>
                    <P>An exemption rule for this system has been promulgated in accordance with the requirements of 5 U.S.C 553(b)(1),(2), and (3), (c) and (e) and published in 32 CFR part 319”.</P>
                    <STARS/>
                    <HD SOURCE="HD1">LDIA 0660</HD>
                    <HD SOURCE="HD2">System name: </HD>
                    <P>Security and Counterintelligence Records.</P>
                    <HD SOURCE="HD2">System location: </HD>
                    <P>Defense Intelligence Agency, 200 MacDill Boulevard, Washington, DC 20304-5100.</P>
                    <HD SOURCE="HD2">Categories of individuals covered by the system: </HD>
                    <P>Current and former Defense Intelligence Agency (DIA) civilian, military and contractor personnel, nominees for employment with DIA, all persons with access to DIA facilities and infrastructure, all persons under the security cognizance of DIA. Persons about whom other U.S. government agencies have requested investigative assistance from DIA as part of lawful investigations by their agency. Individuals identified as the result of an administrative, security and/or investigative function who could pose a threat to DIA operations, data, personnel, facilities and systems. </P>
                    <HD SOURCE="HD2">Categories of records in the system: </HD>
                    <P>Personnel: Name, date and place of birth, Social Security Number (SSN), gender, race, home address, family and dependent information, biometric data, medical/psychological information, financial, employment, training records, test results and education history, statements of personal history.</P>
                    <P>Administrative: Case control number, forms, documents and correspondence relating to security files, personnel security, investigative and employment records, personnel security functions, nomination notices, indoctrination/debriefing memoranda, secrecy and nondisclosure agreements, certificates of clearance.</P>
                    <P>Adjudication memoranda and supporting documentation, in-house investigations, security violations, security threats and incidents, investigations and inquiries of criminal and counterintelligence matters, investigative referrals, counterintelligence reporting, foreign travel, foreign contacts, identification badge records, retrieval indices, clearance status records, facility and access control records.</P>
                    <HD SOURCE="HD2">Authority for maintenance of the system: </HD>
                    <P>
                        National Security Act of 1947; Executive Order 12333; United States 
                        <PRTPAGE P="35194"/>
                        Intelligence Activities; DoDD 5105.21, Defense Intelligence Agency; DoDI 5240.06, Counterintelligence Awareness, Briefing, and Reporting Programs; DoDI 5200.08, Security of DoD Installations and Resources; DoD 5200.2.R, Personnel Security Program; DIA Directive 3020.400, DIA Critical Infrastructure Program; Intelligence Community Directive (ICD) 704, Personnel Security Standards and Procedures Governing Eligibility for Access to Special Compartmented Information and Other Controlled Access Program Information; DIA Manual 50-8, Personnel Security Program; DIA Manual 50-14, Security Investigations; DIA Regulation 50-17, Reporting Foreign Contact and Foreign Travel; DIA Instruction 5200.002, Credibility Assessment Program and E.O. 9397 (SSN), as amended.
                    </P>
                    <HD SOURCE="HD2">Purpose(s): </HD>
                    <P>The system will manage records used to accomplish security and counterintelligence functions. Information is used to comply with regulatory requirements related to initial and continued employment, to determine eligibility for access to classified information, to protect the agency's operations, data, personnel, facilities and systems (by using administrative, security and investigative functions to detect actual or potential threats and risks) and to document training and education.</P>
                    <HD SOURCE="HD2">Routine uses of records maintained in the system, including categories of users and the purposes of such uses:</HD>
                    <P>In addition to those disclosures generally permitted under 5 U.S.C. 552a(b) of the Privacy Act of 1974, these records 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>Information may be disclosed to other Federal agencies, state and local governments, as may have an official need for such information and agree to apply appropriate safeguards to protect the data in a manner consistent with the conditions or expectations under which the information was provided, collected or obtained.</P>
                    <P>The DoD ‘Blanket Routine Uses’ set forth at the beginning of the Defense Intelligence Agency's compilation of systems records notices apply to this system.</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>Paper and Electronic storage media.</P>
                    <HD SOURCE="HD2">Retrievability:</HD>
                    <P>By last name, Social Security Number (SSN), and applicable case control number.</P>
                    <HD SOURCE="HD2">Safeguards:</HD>
                    <P>Records are stored in office buildings protected by guards, controlled screenings, use of visitor registers, electronic access, and/or locks. Access to records is limited to individuals who are properly screened and cleared on a need-to-know basis in the performance of their duties. Passwords and User IDs are used to control access to the system data, and procedures are in place to deter and detect browsing and unauthorized access. Physical and electronic access are limited to persons responsible for servicing and authorized to use the system.</P>
                    <HD SOURCE="HD2">Retention and disposal:</HD>
                    <P>Security Files: Personnel Security Records. Case files documenting the processing of investigations on Federal employees or applicants for Federal employment, whether or not a security clearance is granted, and other persons, such as those performing work for a Federal agency under contract, who require an approval before having access to Government facilities or to sensitive data. These files include questionnaires, summaries of reports prepared by the investigating agency, and other records reflecting the processing of the investigation and the status of the clearance, exclusive of copies of investigative reports furnished by the investigating agency; Temporary-Destroy upon notification of death or 5 years after separation or transfer of employee or no later than 5 years after contract relationship expires.</P>
                    <P>Security Files: Polygraph examinations, favorable examinations; Temporary-Destroy 90 days. Unfavorable Examinations; examinations considered as part of an investigation action necessary for security adjudicative purposes and includes the Medical/Psychiatric Condition Statement-Temporary-Destroy when 15 years old.</P>
                    <P>Medical and Psychiatric Condition Statement (Favorable), Temporary-Destroy when 1 year old; (Unfavorable), Temporary-Destroy when 15 years old. </P>
                    <P>Examinations considered records of major significance, congressional interest, national security or upon which significant action was taken (trial, courts-martial, employment termination). PERMANENT—Offer to National Archives and Records Administration (NARA) when 25-30 years old. Final disposition determinations of individual cases are made by NARA.</P>
                    <P>Security Violations: Temporary-Destroy 5 years after close of case. Files referred for prosecution determination; Temporary- Destroy 3 years after close of case.</P>
                    <P>Orientation and Training: Temporary-Destroy when no longer required for current operations (documents reflecting training, security orientation, and compliance with security regulations).</P>
                    <P>Non-Disclosure Agreements: Temporary—Destroy when 70 years old.</P>
                    <P>Logs and Registers: Temporary-Destroy 2 years after final entry.</P>
                    <HD SOURCE="HD2">System manager(s) and address:</HD>
                    <P>Counterintelligence and Security Office, Defense Intelligence Agency, 200 MacDill Blvd., Washington, DC 20340-5100.</P>
                    <HD SOURCE="HD2">Notification procedure: </HD>
                    <P>Individuals seeking to determine whether information about themselves is contained in this system of records should address written inquiries to the DIA Freedom of Information Office (DAN-1A), Defense Intelligence Agency, 200 MacDill Blvd, Washington, DC 20340-5100.</P>
                    <P>Request should contain the individual's full name, current address, and telephone number.</P>
                    <HD SOURCE="HD2">Record access procedures: </HD>
                    <P>Individuals seeking access to information about themselves, contained in this system of records, should address written inquiries to the DIA Freedom of Information Office (DAN-1A), 200 MacDill Blvd., Washington, DC 20340-5100.</P>
                    <P>Request should contain the individual's full name, current address, and telephone number.</P>
                    <HD SOURCE="HD2">Contesting record procedures: </HD>
                    <P>DIA's rules for accessing records, for contesting contents and appealing initial agency determinations are published in DIA Instruction 5400.001 “Defense Intelligence Agency Privacy Program”; or may be obtained from the system manager.</P>
                    <HD SOURCE="HD2">Record source categories:</HD>
                    <P>Subject individuals, agency and other government officials as well as open source information.</P>
                    <HD SOURCE="HD2">Exemptions claimed for the system:</HD>
                    <P>
                        Investigatory material compiled for law enforcement purposes, other than material within the scope of subsection 5 U.S.C 552a(j)(2), may be exempt pursuant to 5 U.S.C 552(k)(2). However, if an individual is denied any right, 
                        <PRTPAGE P="35195"/>
                        privilege, or benefit for which he would otherwise be entitled by Federal law or which he would otherwise be eligible, as a result of maintenance of the information, the individual will 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>(k)(5) Investigatory material complied 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>(k)(6) Testing or examination material used to determine individual qualifications for appointment or promotion in the Federal or military service, if the disclosure of such material would compromise the objectivity or fairness of the test or examination process.</P>
                    <P>An exemption rule for this system has been promulgated in accordance with the requirements of 5 U.S.C 553(b)(1), (2), and (3), (c) and (e) and published in 32 CFR part 319.</P>
                </PRIACT>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-14941 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 5001-06-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF DEFENSE</AGENCY>
                <SUBAGY>Department of the Air Force</SUBAGY>
                <DEPDOC>[Docket ID: USAF-2011-0016]</DEPDOC>
                <SUBJECT>Privacy Act of 1974; System of Records</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Department of the Air Force, DoD.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice to Add a System of Records.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Department of the Air Force 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.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The proposed action will be effective on July 18, 2011 unless comments are received that would result in a contrary determination.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may submit comments, identified by dock number and/RIN number and title, by any of the following methods:</P>
                    <P>
                        * 
                        <E T="03">Federal Rulemaking Portal:</E>
                          
                        <E T="03">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 Federal Register 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://www.regulations.gov</E>
                         as they are received without change, including any personal identifiers or contact information
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Mr. Charles J. Shedrick, Department of the Air Force Privacy Office, Air Force Privacy Act Office, Office of Warfighting Integration and Chief Information officer, ATTN: SAF/XCPPI, 1800 Air Force Pentagon, Washington DC 20330-1800, or by phone at 703-696-6488.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    The Department of the Air Force's 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 in 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                    .
                </P>
                <P>The proposed systems reports, as required by 5 U.S.C. 552a(r) of the Privacy Act, were submitted on June 8, 2011 to the House Committee on Oversight and 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>
                <SIG>
                    <DATED>Dated: June 8, 2011.</DATED>
                    <NAME>Aaron Siegel,</NAME>
                    <TITLE>Alternate OSD Federal Register Liaison Officer, Department of Defense.</TITLE>
                </SIG>
                <PRIACT>
                    <HD SOURCE="HD1">F036 AFMC L</HD>
                    <HD SOURCE="HD2">System name:</HD>
                    <P>Air Force Integrated Personnel and Pay System (AF-IPPS).</P>
                    <HD SOURCE="HD2">System location:</HD>
                    <P>Command, Control, Communications and Computers Enterprise Integration Facility (CEIF), 15 Elgin St., Hanscom Air Force Base, MA 01731-3000.</P>
                    <HD SOURCE="HD2">Categories of individuals covered by the system:</HD>
                    <P>Active Duty Air Force, Air Force Reserve, and Air National Guard personnel.</P>
                    <HD SOURCE="HD2">Categories of records in the system:</HD>
                    <P>Personal Information: Individual's name, rank/grade, address, date of birth, eye color, height, weight, place of birth, Social Security Number (SSN), and similar personal identifiers for beneficiary/dependant purposes; driver's license number, security clearance level, office location, assigned user name and security questions, local and home of record addresses, phone numbers and emergency contact information.</P>
                    <P>Personnel Information: Evaluation and review history, enrollment, participation, status and outcome information for personnel programs, service qualification and performance measures, types of orders, accomplishments, skills and competencies, career preferences, contract information related to accession and Oath of Office, enlistment and re-enlistment, and separation information, benefits eligibility, enrollment, designations and status information, Uniform Code of Military Justice (UCMJ) actions summarizing court martial, non-judicial punishments, and similar or related documents. Circumstances of an incident the member was involved in and whether he or she is in an injured, wounded, seriously wounded, or ill duty status from the incident.</P>
                    <P>Duty related information: Duty station, employment and job related information and history, deployment information, work title, work address and related work contact information (e.g., phone and fax numbers, E-mail address), supervisor's name and related contact information.</P>
                    <P>Education and training: Graduation dates and locations, highest level of education, other education, training and school information including courses and training completion dates.</P>
                    <P>Pay Entitlement and Allowances: Pay information including earnings and allowances, additional pay (bonuses, special, and incentive pays), payroll computation, balances and history with associated accounting elements, leave balances and leave history.</P>
                    <P>Deductions from Pay: Tax information (federal, state and local) based on withholding options, payroll deductions, garnishments, savings bond information including designated owner, deductions, and purchase dates, thrift savings plan participation.</P>
                    <P>
                        Other pay-related information: Direct deposit information including financial institution name, routing number, and account information.
                        <PRTPAGE P="35196"/>
                    </P>
                    <HD SOURCE="HD2">Authority for maintenance of the system:</HD>
                    <P>10 U.S.C. 113 note, Secretary of Defense; 10 U.S.C. 8013, Secretary of the Air Force; 37 U.S.C Pay and Allowances of the Uniformed Services; 10 U.S.C., Armed Forces; Under Secretary of Defense for Personnel and Readiness; E.O. 9397 (SSN), as amended.</P>
                    <HD SOURCE="HD2">Purpose(s):</HD>
                    <P>The Air Force Integrated Personnel and Pay System (AF-IPPS) fully integrates military personnel and pay capabilities for all Active Duty Air Force, Air National Guard, and Air Force Reserves. The system provides a single record of service for each officer/enlisted member and will provide Combatant Commanders real-time accurate force strength and readiness, better tracking of personnel into and out of theaters of operations, enhanced mission planning and support. This single record of service and will become the Air Force's authoritative source of data used to populate the Department of Defense's data bases via the Enterprise Information Web (EIW). AF-IPPS will also allow Air Force Manpower and Personnel office to be aligned with the Air Force's strategic vision and provide a solution with the adaptability to effectively manage Air Force personnel in operational concepts of mobilization, activation, contingency operations, requirements, and assignment actions.</P>
                    <P>In addition to those disclosures generally permitted under 5 U.S.C. 552a(b) of the Privacy Act of 1974, these records contained therein may specifically be disclosed outside the Department of Defense (DoD) as a routine use pursuant to 5 U.S.C. 552a(b)(3) as follows:</P>
                    <P>To officials and employees of the Department of Health and Human Services, and Selective Service Administration in the performance of their official duties related to eligibility, notification, and assistance in obtaining benefits for which members, former members or retiree may be eligible.</P>
                    <P>To officials and employees of the Department of Veterans Affairs in the performance of their official duties related to approved research projects, and for processing and adjudicating claims, determining eligibility, notification, and assistance in obtaining benefits and medical care for which members, former members, retiree and family members/annuitants may be eligible. To the Department of Veterans Affairs to provide information regarding a service-member's record or family member for the purposes of supporting eligibility processing for the Service-member's Group Life Insurance program.</P>
                    <P>To state and local agencies in the performance of their official duties related to verification of status for determination of eligibility for Veterans bonuses and other benefits and entitlements.</P>
                    <P>To officials and employees of the American Red Cross in the performance of their duties relating to the assistance of the members and their dependents and relatives, or related to assistance previously furnished such individuals, without regard to whether the individual assisted or his/her sponsor continues to be a member of the Military Service. Access will be limited to those portions of the member's record required to effectively assist the member.</P>
                    <P>To the U.S. Citizenship and Immigration Services for use in making alien admission and naturalization inquiries. To the Social Security Administration to obtain or verify Social Security Numbers or to substantiate applicant's credit for social security compensation.</P>
                    <P>To officials and employees of the Office of the Sergeant at Arms of the United States House of Representatives in the performance of their official duties related to the verification of the active duty military service of Members of Congress. Access is limited to those portions of the member's record required to verify time in service.</P>
                    <P>To the widow or widower, dependent, or next-of-kin of deceased members to settle the affairs of the deceased member. The individuals will have to verify relationship by providing a birth certificate, marriage license, death certificate, or court document as requested/required to prove identity.</P>
                    <P>To governmental agencies for the conduct of computer matching agreements for the purpose(s) of determining eligibility for Federal benefit programs, to determine compliance with benefit program requirements and to recover improper payments or delinquent debts under a federal benefit program. To Federal and state licensing authorities and civilian certification boards, committees and/or ecclesiastical endorsing organizations for the purposes of professional credentialing (licensing and certification) of lawyers, chaplains and health professionals.</P>
                    <P>To Federal agencies such as the National Academy of Sciences, for the purposes of conducting personnel and/or health-related research in the interest of the Federal government and the public. When not considered mandatory, the names and other identifying data will be eliminated from records used for such research studies.</P>
                    <P>To the officials and employees of the Department of Labor in the performance of their official duties related to employment and compensation.</P>
                    <NOTE>
                        <HD SOURCE="HED">Note: </HD>
                        <P> Disclosure to consumer reporting agencies.</P>
                        <P>Disclosures pursuant to 5 U.S.C. 552a(b)(12) may be made from this system to `consumer reporting agencies' as defined in the Fair Credit Reporting Act (14 U.S.C. 1681a(f)) or the Federal Claims Collection Act of 1966 (31 U.S.C. 3701(a)(3)). The purpose of this disclosure is to aid in the collection of outstanding debts owed to the Federal government, typically to provide an incentive for debtors to repay delinquent Federal government debts by making these debts part of their credit records.</P>
                    </NOTE>
                    <P>The disclosure is limited to information necessary to establish the identity of the individual, including name, address, and taxpayer identification number (Social Security Number (SSN)); the amount, status and history of the claim, and the agency or program under which the claim arose for the sole purpose of allowing the consumer reporting agency to prepare a commercial credit report.</P>
                    <P>The DoD “Blanket Routine Uses” set forth at the beginning of the Air Force's compilation of the System of Records Notices apply to this system.</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>Electronic storage media.</P>
                    <HD SOURCE="HD2">Retrievability:</HD>
                    <P>Individual's name, Social Security Number (SSN), and date of birth.</P>
                    <HD SOURCE="HD2">Safeguards:</HD>
                    <P>Physical entry will be restricted by the use of locks, guards, and will be accessible only to authorized personnel with a need-to-know. Access to personal data will be limited to person(s) responsible for maintaining and servicing AF-IPPS data in performance of their official duties and who are properly trained, screened and cleared for a need-to-know. Access to personal data will be further restricted by encryption and the use of Common Access Card (CAC) and/or strong password, which are changed periodically according to DoD and Air Force policies.</P>
                    <HD SOURCE="HD2">Retention and disposal:</HD>
                    <P>
                        Those records designated as temporary in the prescribing directive remain in the records until their obsolescence (superseded, member terminates status or retires) when they are removed and provided to the individual.
                        <PRTPAGE P="35197"/>
                    </P>
                    <P>Unfavorable communications in the Open Systems Research Group (OSRG) are transferred to the Air Reserve Component and retained for one year following an officer's termination of status or destroyed if the officer retires or dies.</P>
                    <P>Those documents designated as permanent remain in the military personnel records system permanently and are retired with the master personnel record group.</P>
                    <HD SOURCE="HD2">System manager(s) and address:</HD>
                    <P>Program Director, AFMC/ESC/HIS/AF-IPPS, Bldg 1102C, 3rd Floor 29 Randolph Rd., Hanscom AFB, MA 01731-3000.</P>
                    <HD SOURCE="HD2">Notification procedure:</HD>
                    <P>Individuals seeking to determine whether this system of records contains information on themselves should address written inquiries to Program Director, AFMC/ESC/HIS/AF-IPPS, Bldg 1102C, 29 Randolph Rd., Hanscom AFB, MA 01731-3000.</P>
                    <P>For verification purposes, individuals should provide their full name, Social Security Number (SSN), any details which may assist in locating records, and their signature.</P>
                    <P>In addition, the requester must provide a notarized statement or an unsworn declaration made in accordance with 28 U.S.C. 1746, in the following format:</P>
                    <P>If executed outside the United States:</P>
                    <P>‘I declare (or certify, verify, or state) under penalty of perjury under the laws of the United State of America that the foregoing is true and correct. Executed on (date). (Signature)'. If executed within the United States, its territories, possessions, or commonwealths: ‘I declare (or certify, verify, or state) under penalty of perjury that the foregoing is true and correct. Executed on (date). (Signature)'.</P>
                    <HD SOURCE="HD2">Record access procedures:</HD>
                    <P>Individuals seeking access to information about themselves contained in this system of records should address written inquiries to Air Force Records—Air Force Personnel Center, HQ AFPC/DPSSRP, 550 C Street West, Suite 19, Randolph AFB, TX 78150-4721.</P>
                    <P>For verification purposes, individuals should provide their full name, Social Security Number (SSN), any details which may assist in locating records, and their signature.</P>
                    <P>In addition, the requester must provide a notarized statement or an unsworn declaration made in accordance with 28 U.S.C. 1746, in the following format:</P>
                    <P>If executed outside the United States:</P>
                    <P>‘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)'. If executed within the United States, its territories, possessions, or commonwealths: `I declare (or certify, verify, or state) under penalty of perjury that the foregoing is true and correct. Executed on (date). (Signature)'.</P>
                    <HD SOURCE="HD2">Contesting record procedures:</HD>
                    <P>The Air Force rules for accessing records, and for contesting contents and appealing initial agency determinations are published in Air Force Instruction 37-132; 32 CFR Part 806b; or may be obtained from the system manager.</P>
                    <HD SOURCE="HD2">Record source categories:</HD>
                    <P>Data contained in this system is collected from the individuals and current Air Force Human Resource Offices and integrated pay systems.</P>
                    <HD SOURCE="HD2">Exemptions claimed for the system:</HD>
                    <P>None.</P>
                </PRIACT>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-14940 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 5001-06-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF DEFENSE</AGENCY>
                <SUBAGY>Department of the Army</SUBAGY>
                <DEPDOC>[Docket ID: USA-2011-0012]</DEPDOC>
                <SUBJECT>Privacy Act of 1974; System of Records</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Department of the Army, DoD.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice to alter a system of records.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>Department of the Army is altering a system of records notice in its existing inventory of record systems subject to the Privacy Act of 1974 (5 U.S.C. 552a), as amended.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>This proposed action will be effective without further notice on July 18, 2011 unless comments are received which result in a contrary determination.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may submit comments, identified by docket number and/Regulatory Information Number (RIN) and title, by any of the following methods:</P>
                    <P>
                        * 
                        <E T="03">Federal Rulemaking 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://www.regulations.gov</E>
                         as they are received without change, including any personal identifiers or contact information.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Mr. Leroy Jones, Department of the Army, Privacy Office, U.S. Army Records Management and Declassification Agency, 7701 Telegraph Road, Casey Building, Suite 144, Alexandria, VA 22325-3905, or by phone at (703) 428-6185.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    Department of the Army 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 in 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                    .
                </P>
                <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 June 7, 2011 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,” February 20, 1996, 61 FR 6427.</P>
                <SIG>
                    <DATED>Dated: June 7, 2011.</DATED>
                    <NAME>Aaron Siegel,</NAME>
                    <TITLE>Alternate OSD Federal Register Liaison Officer, Department of Defense.</TITLE>
                </SIG>
                <PRIACT>
                    <HD SOURCE="HD1">A0351b TRADOC DoD</HD>
                    <HD SOURCE="HD2">System name:</HD>
                    <P>Army Correspondence Course Program (ACCP) (July 25, 2008, 73 FR 43420).</P>
                    <HD SOURCE="HD2">Changes:</HD>
                    <HD SOURCE="HD2">System Name:</HD>
                    <P>Delete entry and replace with “Army Training Information Architecture—Learning Management System (ATIA-LMS).”</P>
                    <STARS/>
                    <HD SOURCE="HD2">Authority for maintenance of the system:</HD>
                    <P>
                        Delete entry and replace with “10 U.S.C. 3013, Secretary of the Army; Army Regulation 350-1, Army Training and Leader Development; Army Regulation 350-10, Management of Army Individual Training Requirements 
                        <PRTPAGE P="35198"/>
                        and Resources; and E.O. 9397 (SSN), as amended.”
                    </P>
                    <STARS/>
                    <HD SOURCE="HD2">Safeguards:</HD>
                    <P>Delete entry and replace with “The system is hosted on an Army installation, in a secure environment at the Training Capability Manager—Army Training Information System (TCM-ATIS). Building security is through Police patrols, installation fences, key card access, building-server room alarms and cameras. System access is through the Directorate of Information Management's (DOIM's) firewall. Servers are frequently scanned and comply with current Security Technical Implementation Guides (STIGS) which ensures proper security settings. Each user requires a user ID and password (which has to be changed each 90 days). Direct access to the database is restricted to authorized System Administrators (SAs) only. Server access is controlled by IP address. System is accessible world-wide. Servers are located in a cipher locked room and access is controlled by the SA.”</P>
                    <STARS/>
                    <HD SOURCE="HD2">System manager(s) and address:</HD>
                    <P>Delete entry and replace with “Commander, Army Training Support Center, Building 2114, Pershing Avenue, Fort Eustis, VA 23604-5166.”</P>
                    <HD SOURCE="HD2">Notification procedure:</HD>
                    <P>Delete entry and replace with “Individuals seeking to determine whether information about themselves is contained in this system should address written inquiries to the Commander, U.S. Army Training Support Center, Building 2114, Pershing Avenue, Fort Eustis, VA 23604-5166.</P>
                    <P>Individual must furnish his/her full name, Social Security Number (SSN), current address and telephone number, and military status or other information verifiable from the record itself which may assist in locating the record, and their signature.</P>
                    <P>In addition, the requester must provide a notarized statement or an unsworn declaration made in accordance with 28 U.S.C. 1746, in the following format:</P>
                    <P>If executed outside the United States:</P>
                    <P>`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>If executed within the United States, its territories, possessions, or commonwealths: `I declare (or certify, verify, or state) under penalty of perjury that the foregoing is true and correct. Executed on (date). (Signature)'.”</P>
                    <HD SOURCE="HD2">Record access procedures:</HD>
                    <P>Delete entry and replace with “Individuals seeking access to information about themselves contained in this system should address written inquiries to the Commander, U.S. Army Training Support Center, Building 2114, Pershing Avenue, Fort Eustis, VA 23604-5166.</P>
                    <P>Individual must furnish his/her full name, Social Security Number (SSN), current address and telephone number, and military status or other information verifiable from the record itself which may assist in locating the record, and their signature.</P>
                    <P>In addition, the requester must provide a notarized statement or an unsworn declaration made in accordance with 28 U.S.C. 1746, in the following format:</P>
                    <P>If executed outside the United States:</P>
                    <P>`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>If executed within the United States, its territories, possessions, or commonwealths: `I declare (or certify, verify, or state) under penalty of perjury that the foregoing is true and correct. Executed on (date). (Signature)'.”</P>
                    <STARS/>
                    <HD SOURCE="HD1">A0351b TRADOC DoD</HD>
                    <HD SOURCE="HD2">System name:</HD>
                    <P>Army Training Information Architecture—Learning Management System (ATIA-LMS).</P>
                    <HD SOURCE="HD2">System location:</HD>
                    <P>Commander, U.S. Army Training Support Center, 3308 Wilson Avenue, Fort Eustis, VA 23604-5166.</P>
                    <HD SOURCE="HD2">Categories of individuals covered by the system:</HD>
                    <P>Members of the Army, Navy, Marine Corps, and Air Force, Reserve Officer Training Corps and National Defense Cadet Corps students, Department of Defense civilian employees, and approved foreign military personnel enrolled in a non-resident course administered by the Army Institute for Professional Development.</P>
                    <HD SOURCE="HD2">Categories of records in the system:</HD>
                    <P>Files contain name, grade/rank, Social Security Number (SSN), address, service component, branch, personnel classification, military occupational specialty, credit hours accumulated, examination and lesson grades, student academic status, curricula, course description.</P>
                    <HD SOURCE="HD2">Authority for maintenance of the system:</HD>
                    <P>10 U.S.C. 3013, Secretary of the Army; Army Regulation 350-1, Army Training and Leader Development; Army Regulation 350-10, Management of Army Individual Training Requirements and Resources; and E.O. 9397 (SSN), as amended.</P>
                    <HD SOURCE="HD2">Purpose(s):</HD>
                    <P>To record lessons and/or exam grades; maintain student academic status; course and sub-course descriptions; produce course completion certificates and reflect credit hours earned; and produce management summary reports.</P>
                    <HD SOURCE="HD2">Routine uses of records maintained in the system, including categories of users and the purposes of such uses:</HD>
                    <P>In addition to those disclosures generally permitted under 5 U.S.C. 552a(b) of the Privacy Act of 1974, these records 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>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>
                    <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>Electronic storage media.</P>
                    <HD SOURCE="HD2">Retrievability:</HD>
                    <P>By name and Social Security Number (SSN).</P>
                    <HD SOURCE="HD2">Safeguards:</HD>
                    <P>The system is hosted on an Army installation, in a secure environment at the Training Capability Manager—Army Training Information System (TCM-ATIS). Building security is through Police patrols, installation fences, key card access, building-server room alarms and cameras. System access is through the Directorate of Information Management's (DOIM's) firewall. Servers are frequently scanned and comply with current Security Technical Implementation Guides (STIGS) which ensures proper security settings. Each user requires a user ID and password (which has to be changed each 90 days). Direct access to the database is restricted to authorized System Administrators (SAs) only. Server access is controlled by IP address. System is accessible world-wide. Servers are located in a cipher locked room and access is controlled by the SA.</P>
                    <HD SOURCE="HD2">Retention and disposal:</HD>
                    <P>
                        Student records indicating courses attended, course length, extent of 
                        <PRTPAGE P="35199"/>
                        completion, results, aptitudes and personal qualities, grade, rating attained and related information destroy after 40 years. Records of extension courses will be held for 3 years in current file area and 2 years in records holding area before retirement to National Personnel Records Center, 9700 Page Avenue, St. Louis, MO 63132-5100.
                    </P>
                    <HD SOURCE="HD2">System manager(s) and address:</HD>
                    <P>Commander, Army Training Support Center, Building 2114, Pershing Avenue, Fort Eustis, VA 23604-5166.</P>
                    <HD SOURCE="HD2">Notification procedure:</HD>
                    <P>Individuals seeking to determine whether information about themselves is contained in this system should address written inquiries to the Commander, U.S. Army Training Support Center, Building 2114, Pershing Avenue, Fort Eustis, VA 23604-5166.</P>
                    <P>Individual must furnish his/her full name, Social Security Number (SSN), current address and telephone number, and military status or other information verifiable from the record itself which may assist in locating the record, and their signature.</P>
                    <P>In addition, the requester must provide a notarized statement or an unsworn declaration made in accordance with 28 U.S.C. 1746, in the following format:</P>
                    <P>If executed outside the United States:</P>
                    <P>‘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>If executed within the United States, its territories, possessions, or commonwealths: `I declare (or certify, verify, or state) under penalty of perjury that the foregoing is true and correct. Executed on (date). (Signature)'.</P>
                    <HD SOURCE="HD2">Record access procedures:</HD>
                    <P>Individuals seeking access to information about themselves contained in this system should address written inquiries to the Commander, U.S. Army Training Support Center, Building 2114, Pershing Avenue, Fort Eustis, VA 23604-5166.</P>
                    <P>Individual must furnish his/her full name, Social Security Number (SSN), current address and telephone number, and military status or other information verifiable from the record itself which may assist in locating the record, and their signature.</P>
                    <P>In addition, the requester must provide a notarized statement or an unsworn declaration made in accordance with 28 U.S.C. 1746, in the following format:</P>
                    <P>If executed outside the United States:</P>
                    <P>‘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>If executed within the United States, its territories, possessions, or commonwealths: `I declare (or certify, verify, or state) under penalty of perjury that the foregoing is true and correct. Executed on (date). (Signature)'.</P>
                    <HD SOURCE="HD2">Contesting record procedures:</HD>
                    <P>The Army's rules for accessing records, contesting content, 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>
                    <HD SOURCE="HD2">Record source categories:</HD>
                    <P>From individual upon enrollment, from class records and instructors, and from graded examinations.</P>
                    <HD SOURCE="HD2">Exemptions claimed for the system:</HD>
                    <P>None. </P>
                </PRIACT>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-14935 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 5001-06-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF DEFENSE</AGENCY>
                <SUBAGY>Department of the Navy</SUBAGY>
                <SUBJECT>Notice of Intent To Grant Partially-Exclusive Patent License; Sound Metrics Corp.</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Department of the Navy, DoD.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Department of the Navy hereby gives notice of its intent to grant to Sound Metrics Corp. a revocable, non-assignable, partially-exclusive license to practice in the United States, the Government-owned invention described in U.S. Patent No. 12/806,258, Navy Case No. 100,287: Facemask Display.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Anyone wishing to object to the grant of this license must file written objections along with supporting evidence, if any, not later than July 1, 2011.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Written objections are to be filed with the Office of Counsel, Naval Surface Warfare Center Panama City, 110 Vernon Ave., Code CDL, Panama City, FL 32407-7001.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Mr. James Shepherd, Patent Counsel, Naval Surface Warfare Center Panama City, 110 Vernon Ave., Panama City, FL 32407-7001, telephone 850-234-4646, fax 850-235-5497, or 
                        <E T="03">james.t.shepherd@navy.mil.</E>
                    </P>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P> 35 U.S.C. 207, 37 CFR Part 404.</P>
                    </AUTH>
                    <SIG>
                        <DATED>Dated: June 9, 2011.</DATED>
                        <NAME>L.M. Senay,</NAME>
                        <TITLE>Lieutenant, Judge Advocate General's Corps, U.S. Navy, Federal Register Liaison Officer.</TITLE>
                    </SIG>
                </FURINF>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-14930 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3810-FF-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF ENERGY</AGENCY>
                <SUBAGY>Office of Energy Efficiency and Renewable Energy</SUBAGY>
                <SUBJECT>Proposed Agency Information Collection</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of Energy Efficiency and Renewable Energy, Department of Energy.</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 Energy (DOE) has submitted to the Office of Management and Budget (OMB) for clearance a proposal for collection of information under the provisions of the Paperwork Reduction Act of 1995. The proposed collection will support the Weatherization Assistance Program Evaluation for the American Recovery and Reinvestment Act (ARRA) Period covering Program Years 2009, 2010, and 2011. A 60-day notice and request for comments was published in the 
                        <E T="04">Federal Register</E>
                         on March 11, 2011, 76FR 13398. No comments were received. This subsequent 30-day notice allows public comment on the final version of this information collection request. 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, 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 respondents, including through the use of automated collection techniques or other forms of information technology. Please note that in the final version the estimated burden has increased, primarily due to the collection of utility bill data on multiple instances instead of once as previously planned.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        Comments regarding this proposed information collection must be received on or before July 18, 2011. If you anticipate difficulty in submitting comments within that period, contact 
                        <PRTPAGE P="35200"/>
                        the person listed in 
                        <E T="02">ADDRESSES</E>
                         as soon as possible.
                    </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Written comments may be sent to DOE Desk Officer, Office of Information and Regulatory Affairs, Office of Management and Budget, New Executive Office Building, Room 10102, 725 17th Street, NW., Washington, DC 20503; and Bruce Tonn, Environmental Sciences Division, Oak Ridge National Laboratory, One Bethel Valley Road, P.O. Box 2008, MS-6038, Oak Ridge, TN 37831-6038, 
                        <E T="03">Fax #:</E>
                         (865) 576-8646, 
                        <E T="03">tonnbe@ornl.gov.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Requests for additional information or copies of the information collection instrument and instructions should be directed to Bruce Tonn, Environmental Sciences Division, Oak Ridge National Laboratory, One Bethel Valley Road, P.O. Box 2008, MS-6038, Oak Ridge, TN 37831-6038, 
                        <E T="03">Fax #:</E>
                         (865) 576-8646, 
                        <E T="03">tonnbe@ornl.gov.</E>
                    </P>
                    <P>
                        The plan for this evaluation can be found at 
                        <E T="03">http://weatherization.ornl.gov/evaluation_period.shtml</E>
                        . The surveys and data forms that comprise this information request can also be found at that Web page.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    This package contains: (1) 
                    <E T="03">OMB No.:</E>
                     1910-NEW; (2) 
                    <E T="03">Package Title:</E>
                     The Weatherization Assistance Program ARRA-Period Evaluation; (3) 
                    <E T="03">Type of Review:</E>
                     Regular; (4) 
                    <E T="03">Purpose:</E>
                     This collection of information is necessary for a complete evaluation of the program that will weatherize approximately 600,000 low-income homes in Program Years 2009, 2010 and 2011; (5) 
                    <E T="03">Estimated Number of Total Respondents:</E>
                     6,604. Information will be collected from seventy-four grantees (fifty states, five U.S. territories, Washington DC, two Native American tribes, and sixteen Weatherization Innovation grantees); thirty-four weatherization training centers; approximately 1,000 local weatherization agencies; approximately 1,200 utilities; approximately 1,240 occupants/clients of weatherization; and approximately 3,056 individuals working in the weatherization field; (6) 
                    <E T="03">Estimated Number of Total Responses:</E>
                     9,012; (7) 
                    <E T="03">Estimated Number of Total Burden Hours:</E>
                     The estimated burden is 83,527 hours; (8) 
                    <E T="03">Estimated Reporting and Recordkeeping Cost Burden:</E>
                     There is no reporting or recordkeeping cost burden associated with this request.
                </P>
                <P>Authority: Section 6861 of title 42 of the United States Code and 10 CFR 440.25 authorize the collection of this information.</P>
                <SIG>
                    <DATED>Issued in Washington, DC, on June 9, 2011. </DATED>
                    <NAME>Henry Kelly,</NAME>
                    <TITLE>Acting Assistant Secretary, Energy Efficiency and Renewable Energy.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-14997 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6450-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF ENERGY</AGENCY>
                <SUBAGY>Federal Energy Regulatory Commission</SUBAGY>
                <DEPDOC>[Docket No. CP10-43-001]</DEPDOC>
                <SUBJECT>High Island Offshore System, L.L.C.; Notice of Amendment</SUBJECT>
                <P>Take notice that on June 6, 2011, High Island Offshore System, L.L.C. (HIOS), 1100 Louisiana St., Houston, Texas 77002, filed in Docket No. CP10-43-001, to amend its application filed in Docket No. CP10-43-000 pursuant to section 7(b) of the Natural Gas Act (NGA) and Part 157 of the Commission's regulations, by requesting authorization to establish its system's firm, certificated capacity at 500 MMcf per day rather than the originally requested 350 MMcf per day. The requested reduction in firm, certificated capacity is related to HIOS's request to abandon three compressor units on a platform at High Island Area Block 264, located offshore Texas, all as more fully set forth in the application as amended which is on file with the Commission and open to public inspection.</P>
                <P>
                    Any questions regarding this application should be directed to Jeff Molinaro, High Island Offshore System, L.L.C., 1100 Louisiana St., Houston, Texas 77002, or (telephone) 713-381-2526, or 
                    <E T="03">JMolinaro@epco.com,</E>
                     or (Fax) 713-803-2534.
                </P>
                <P>There are two ways to become involved in the Commission's review of this project. First, any person wishing to obtain legal status by becoming a party to the proceedings for this project should, on or before the comment date stated below, file with the Federal Energy Regulatory Commission, 888 First Street, NE., Washington, DC 20426, a motion to intervene in accordance with the requirements of the Commission's Rules of Practice and Procedure (18 CFR 385.214 or 385.211) and the Regulations under the NGA (18 CFR 157.10). A person obtaining party status will be placed on the service list maintained by the Secretary of the Commission and will receive copies of all documents filed by the applicant and by all other parties. A party must submit seven copies of filings made with the Commission and must mail a copy to the applicant and to every other party in the proceeding. Only parties to the proceeding can ask for court review of Commission orders in the proceeding.</P>
                <P>However, a person does not have to intervene in order to have comments considered. The second way to participate is by filing with the Secretary of the Commission, as soon as possible, an original and two copies of comments in support of or in opposition to this project. The Commission will consider these comments in determining the appropriate action to be taken, but the filing of a comment alone will not serve to make the filer a party to the proceeding. The Commission's rules require that persons filing comments in opposition to the project provide copies of their protests only to the party or parties directly involved in the protest.</P>
                <P>
                    The Commission encourages electronic submission of protests and interventions in lieu of paper using the “eFiling” link at 
                    <E T="03">http://www.ferc.gov</E>
                    . Persons unable to file electronically should submit an original and seven copies of the protest or intervention to the Federal Energy Regulatory Commission, 888 First Street, NE., Washington, DC 20426. This filing is accessible on-line at 
                    <E T="03">http://www.ferc.gov</E>
                     using the “eLibrary” link and is available for review in the Commission's Public Reference Room in Washington, DC. There is an “eSubscription” link on the Web site that enables subscribers to receive e-mail notification when a document is added to a subscribed docket(s). For assistance with any FERC Online service, please e-mail 
                    <E T="03">FERCOnlineSupport@ferc.gov,</E>
                     or call (866) 208-3676 (toll free). For TTY, call (202) 502-8659.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     June 24, 2011.
                </P>
                <SIG>
                    <DATED>Dated: June 9, 2011.</DATED>
                    <NAME>Kimberly D. Bose,</NAME>
                    <TITLE>Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-14899 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6717-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="35201"/>
                <AGENCY TYPE="S">DEPARTMENT OF ENERGY</AGENCY>
                <SUBAGY>Federal Energy Regulatory Commission</SUBAGY>
                <DEPDOC>[Project No. 2309-019]</DEPDOC>
                <SUBJECT>Jersey Central Power and Light; PSEG Fossil LLC; Notice of Application Accepted for Filing, Soliciting Motions To Intervene and Protests, Ready for Environmental Analysis, and Soliciting Comments, Recommendations, Preliminary Terms and Conditions, and Preliminary Fishway Prescriptions</SUBJECT>
                <P>Take notice that the following hydroelectric application has been filed with the Commission and is available for public inspection.</P>
                <P>
                    a. 
                    <E T="03">Type of Application:</E>
                     New Major License.
                </P>
                <P>
                    b. 
                    <E T="03">Project No.:</E>
                     2309-019.
                </P>
                <P>
                    c. 
                    <E T="03">Date Filed:</E>
                     February 18, 2011.
                </P>
                <P>
                    d. 
                    <E T="03">Applicant:</E>
                     Jersey Central Power and Light and PSEG Fossil LLC.
                </P>
                <P>
                    e. 
                    <E T="03">Name of Project:</E>
                     Yards Creek Pumped Storage Project.
                </P>
                <P>
                    f. 
                    <E T="03">Location:</E>
                     The existing project is located on Yards Creek, in the townships of Hardwick and Blairstown, Warren County, New Jersey. No Federal lands are involved.
                </P>
                <P>
                    g. 
                    <E T="03">Filed pursuant to:</E>
                     Federal Power Act, 16 U.S.C. 791(a)-825(r).
                </P>
                <P>
                    h. 
                    <E T="03">Applicant Contact:</E>
                     Timothy Oakes, Project Manager, Kleinschmidt Associates, 2 East Main Street, Strasburg, PA 17579; Telephone (717) 687-7211.
                </P>
                <P>
                    i. 
                    <E T="03">FERC Contact:</E>
                     Allyson Conner, (202) 502-6082 or 
                    <E T="03">allyson.conner@ferc.gov.</E>
                </P>
                <P>
                    j. 
                    <E T="03">Deadline for filing motions to intervene and protests, comments, recommendations, preliminary terms and conditions, and preliminary prescriptions:</E>
                     60 days from the issuance date of this notice; reply comments are due 105 days from the issuance date of this notice.
                </P>
                <P>
                    Motions to intervene, protests, comments, recommendations, preliminary terms and conditions, and preliminary fishway prescriptions may be filed electronically via the Internet. See 18 CFR 385.2001(a)(1)(iii) and the instructions on the Commission's Web site 
                    <E T="03">http://www.ferc.gov/docs-filing/efiling.asp</E>
                    . Commenters can submit brief comments up to 6,000 characters, without prior registration, using the eComment system at 
                    <E T="03">http://www.ferc.gov/docs-filing/ecomment.asp</E>
                    . You must include your name and contact information at the end of your comments. For assistance, please contact FERC Online Support at 
                    <E T="03">FERCOnlineSupport@ferc.gov</E>
                     or toll free at 1-866-208-3676, or for TTY, (202) 502-8659. Although the Commission strongly encourages electronic filing, documents may also be paper-filed. To paper-file, mail an original and seven copies to: Kimberly D. Bose, Secretary, Federal Energy Regulatory Commission, 888 First Street, NE., Washington, DC 20426.
                </P>
                <P>The Commission's Rules of Practice require all intervenors filing documents with the Commission to serve a copy of that document on each person on the official service list for the project. Further, if an intervenor files comments or documents with the Commission relating to the merits of an issue that may affect the responsibilities of a particular resource agency, they must also serve a copy of the document on that resource agency.</P>
                <P>k. This application has been accepted for filing and is now ready for environmental analysis.</P>
                <P>l. The Yards Creek Pumped Storage Project consists of: (1) An upper reservoir with a total usable storage capacity of 4,763 acre-feet; (2) a lower reservoir with a total usable storage capacity of 5,452 acre-feet; (3) an auxiliary reservoir with seasonal storage of 412 acre-feet formed by the auxiliary reservoir dam, which is 1,000 feet long and 20 feet high; (4) a main, earthfill dam at the lower reservoir that is 1,404 feet long and 52 feet high; (5) an auxiliary dike at the lower reservoir that is 2,091 feet long and 35 feet high; (6) a 2,116-foot, 35-foot-wide intake channel in the floor of the upper reservoir; (7) a 95-foot-high concrete intake structure with trashracks and stop logs; (8) a 1,130-foot-long, 20-foot-diameter concrete-lined pressure tunnel; (9) a 210-foot-long, 19-foot-diameter steel-lined pressure tunnel; (10) a 144-foot-long, 19-foot-diameter concrete encased steel-lined transition section; (11) a 478-foot-long, 19-foot-diameter steel penstock; (12) an 8-foot-long reducer from a 19-foot-diameter to 18-foot-diameter penstock; (13) a 1,582-foot-long, 18-foot-diameter steel penstock; (14) a 325-foot-long trifurcated penstock, one penstock per pumping-generating unit that tapers from 10-foot-diameter to 7-foot 2.5-inch-diameter; (15) 86.5-inch spherical guard valves at the entrance to each pump-turbine spiral case; (16) three vertical shaft, Francis-type, reversible pump-turbine engine units, each with a nameplate generating capacity of 140 megawatts; (17) a 140-foot-long by 63.5-foot-wide underground concrete powerhouse; and (18) appurtenant facilities.</P>
                <P>The licensee proposes to raise the preliminary spillway crest at the lower reservoir by 1 foot, to 819.5 feet, to provide for additional storage by adding wooden flashboards. The licensee also proposes raising the upper reservoir pool elevation 2 feet, from 1,555 feet to 1,557 feet, allowing only 4 feet of freeboard to the crest elevation of 1,561 feet. As an additional precaution to existing monitors and controls, the licensee is proposing to install an overflow structure at the upper reservoir to prevent overtopping the non-overflow structures (dikes) in the event of high water levels.</P>
                <P>
                    m. A copy of the application is available for review at the Commission in the Public Reference Room or may be viewed on the Commission's Web site at 
                    <E T="03">http://www.ferc.gov</E>
                     using the “eLibrary” link. Enter the docket number excluding the last three digits in the docket number field to access the document. For assistance, contact FERC Online Support. A copy is also available for inspection and reproduction at the address in item h above.
                </P>
                <P>
                    Register online at 
                    <E T="03">http://www.ferc.gov/docs-filing/esubscription.asp</E>
                     to be notified via e-mail of new filings and issuances related to this or other pending projects. For assistance, contact FERC Online Support.
                </P>
                <P>n. Anyone may submit comments, a protest, or a motion to intervene in accordance with the requirements of Rules of Practice and Procedure, 18 CFR 385.210, .211, .214. In determining the appropriate action to take, the Commission will consider all protests or other comments filed, but only those who file a motion to intervene in accordance with the Commission's Rules may become a party to the proceeding. Any comments, protests, or motions to intervene must be received on or before the specified comment date for the particular application.</P>
                <P>
                    All filings must (1) bear in all capital letters the title “PROTEST,” “MOTION TO INTERVENE,” “COMMENTS,” “REPLY COMMENTS,” “RECOMMENDATIONS,” “PRELIMINARY TERMS AND CONDITIONS,” or “PRELIMINARY FISHWAY PRESCRIPTIONS;” (2) set forth in the heading the name of the applicant and the project number of the application to which the filing responds; (3) furnish the name, address, and telephone number of the person protesting or intervening; and (4) otherwise comply with the requirements of 18 CFR 385.2001 through 385.2005. All comments, recommendations, terms and conditions or prescriptions must set forth their evidentiary basis and otherwise comply with the requirements of 18 CFR 4.34(b). Agencies may obtain copies of the application directly from 
                    <PRTPAGE P="35202"/>
                    the applicant. A copy of any protest or motion to intervene must be served upon each representative of the applicant specified in the particular application. A copy of all other filings in reference to this application must be accompanied by proof of service on all persons listed in the service list prepared by the Commission in this proceeding, in accordance with 18 CFR 4.34(b) and 385.2010.
                </P>
                <P>
                    o. 
                    <E T="03">Procedural Schedule:</E>
                     The application will be processed according to the following revised Hydro Licensing Schedule. Revisions to the schedule may be made as appropriate.
                </P>
                <GPOTABLE COLS="2" OPTS="L2,tp0,i1" CDEF="s100,xs80">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Milestone </CHED>
                        <CHED H="1">Target date</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Filing of recommendations, preliminary terms and conditions, and preliminary fishway prescriptions</ENT>
                        <ENT>August 9, 2011.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Commission issues Single EA</ENT>
                        <ENT>December 7, 2011.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Comments on EA</ENT>
                        <ENT>January 6, 2011.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Modified terms and conditions</ENT>
                        <ENT>March 5, 2012.</ENT>
                    </ROW>
                </GPOTABLE>
                <P>p. Final amendments to the application must be filed with the Commission no later than 30 days from the issuance date of this notice.</P>
                <P>q. A license applicant must file no later than 60 days following the date of issuance of the notice of acceptance and ready for environmental analysis provided for in 5.22: (1) A copy of the water quality certification; (2) a copy of the request for certification, including proof of the date on which the certifying agency received the request; or (3) evidence of waiver of water quality certification.</P>
                <SIG>
                    <DATED>Dated: June 10, 2011.</DATED>
                    <NAME>Kimberly D. Bose,</NAME>
                    <TITLE>Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-14967 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6717-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF ENERGY</AGENCY>
                <SUBAGY>Federal Energy Regulatory Commission</SUBAGY>
                <DEPDOC>[Docket No. CP11-495-000]</DEPDOC>
                <SUBJECT>Piedmont Natural Gas Company, Inc.; Notice of Application</SUBJECT>
                <P>
                    On June 3, 2011, Piedmont Natural Gas Company, Inc. (Piedmont) filed with the Federal Energy Regulatory Commission (Commission) an application pursuant to section 7(f) of the Natural Gas Act (NGA), as amended, and section 157 of the Commission's Regulations, for service area determination for their Charlotte, North Carolina and Fort Mill, South Carolina service areas, all as more fully set forth in the application, which is on file with the Commission and open to public inspection. The filing may also be viewed on the Web at 
                    <E T="03">http://www.ferc.gov</E>
                     using the “eLibrary” link. Enter the docket number excluding the last three digits in the docket number field to access the document. There is an “eSubscription” link on the Web site that enables subscribers to receive e-mail notification when a document is added to a subscribed docket(s). For assistance, contact FERC at 
                    <E T="03">FERCOnlineSupport@ferc.gov</E>
                     or call toll-free, (886) 208-3676 or TTY, (202) 502-8659.
                </P>
                <P>
                    Questions regarding this application should be directed to Michelle R. Mendoza, Piedmont Natural Gas Company, Inc., Post Office Box 33068, Charlotte, NC 28233 or by e-mailing 
                    <E T="03">michelle.mendoza@piedmontng.com</E>
                     or to James H. Jeffries IV, Moore &amp; Van Allen PLLC, 100 North Tryon Street, Suite 4700, Charlotte, NC 28202-4003 or by calling 704-331-1079 or by e-mailing 
                    <E T="03">mvaferc@mvalaw.com.</E>
                </P>
                <P>Pursuant to section 157.9 of the Commission's rules, within 90 days of this Notice the Commission staff will either: complete its environmental assessment (EA) and place it into the Commission's public record (eLibrary) for this proceeding; or issue a Notice of Schedule for Environmental Review. If a Notice of Schedule for Environmental Review is issued, it will indicate, among other milestones, the anticipated date for the Commission staff's issuance of the final environmental impact statement (FEIS) or EA for this proposal. The filing of the EA in the Commission's public record for this proceeding or the issuance of a Notice of Schedule for Environmental Review will serve to notify Federal and state agencies of the timing for the completion of all necessary reviews, and the subsequent need to complete all Federal authorizations within 90 days of the date of issuance of the Commission staff's FEIS or EA.</P>
                <P>There are two ways to become involved in the Commission's review of this project. First, any person wishing to obtain legal status by becoming a party to the proceedings for this project should, on or before the comment date stated below, file with the Federal Energy Regulatory Commission, 888 First Street, NE., Washington, DC 20426, a motion to intervene in accordance with the requirements of the Commission's Rules of Practice and Procedure (18 CFR 385.214 or 385.211) and the Regulations under the NGA (18 CFR 157.10). A person obtaining party status will be placed on the service list maintained by the Secretary of the Commission and will receive copies of all documents filed by the applicant and by all other parties. A party must submit seven copies of filings made with the Commission and must mail a copy to the applicant and to every other party in the proceeding. Only parties to the proceeding can ask for court review of Commission orders in the proceeding.</P>
                <P>However, a person does not have to intervene in order to have comments considered. The second way to participate is by filing with the Secretary of the Commission, as soon as possible, an original and two copies of comments in support of or in opposition to this project. The Commission will consider these comments in determining the appropriate action to be taken, but the filing of a comment alone will not serve to make the filer a party to the proceeding. The Commission's rules require that persons filing comments in opposition to the project provide copies of their protests only to the party or parties directly involved in the protest.</P>
                <P>
                    Persons who wish to comment only on the environmental review of this project should submit an original and two copies of their comments to the Secretary of the Commission. Environmental commenters will be placed on the Commission's environmental mailing list, will receive copies of the environmental documents, and will be notified of meetings associated with the Commission's environmental review process. Environmental commenters will not be required to serve copies of filed documents on all other parties. However, the non-party commenters will not receive copies of all documents filed by other parties or issued by the Commission (except for the mailing of environmental documents issued by the Commission) and will not have the right to seek court review of the Commission's final order.
                    <PRTPAGE P="35203"/>
                </P>
                <P>
                    The Commission strongly encourages electronic filings of comments, protests and interventions in lieu of paper using the “eFiling” link at 
                    <E T="03">http://www.ferc.gov</E>
                    . Persons unable to file electronically should submit original and seven copies of the protest or intervention to the Federal Energy Regulatory Commission, 888 First Street, NE., Washington, DC 20426.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     July 1, 2011.
                </P>
                <SIG>
                    <DATED>Dated: June 10, 2011.</DATED>
                    <NAME>Kimberly D. Bose,</NAME>
                    <TITLE>Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-14964 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6717-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF ENERGY</AGENCY>
                <SUBAGY>Federal Energy Regulatory Commission</SUBAGY>
                <DEPDOC>[Docket No. CP11-493-000]</DEPDOC>
                <SUBJECT>Dominion Transmission, Inc.; Notice Application</SUBJECT>
                <P>Take notice that on May 27, 2011, Dominion Transmission, Inc. (Dominion), filed an application in Docket No. CP11-493-000 pursuant to section 7(c) of the Natural Gas Act (NGA) and Part 157 of the Commission's Regulations, for a certificate of public convenience and necessity to: (1) Revise the active storage boundary; and (2) establish a protective boundary for the Woodhull Storage Pool located in Steuben County, New York, all as more fully set forth in the applications which is on file with the Commission and open for public inspection.</P>
                <P>Any questions regarding this application should be directed to Amanda K. Prestage, Regulatory and Certificates Analyst III, Dominion Transmission, Inc., 701 East Cary Street, Richmond, Virginia 23219, or call at (804) 771-4416.</P>
                <P>Pursuant to section 157.9 of the Commission's rules, 18 CFR 157.9, within 90 days of this Notice the Commission staff will either: complete its environmental assessment (EA) and place it into the Commission's public record (eLibrary) for this proceeding; or issue a Notice of Schedule for Environmental Review. If a Notice of Schedule for Environmental Review is issued, it will indicate, among other milestones, the anticipated date for the Commission staff's issuance of the final environmental impact statement (FEIS) or EA for this proposal. The filing of the EA in the Commission's public record for this proceeding or the issuance of a Notice of Schedule for Environmental Review will serve to notify Federal and State agencies of the timing for the completion of all necessary reviews, and the subsequent need to complete all Federal authorizations within 90 days of the date of issuance of the Commission staff's FEIS or EA.</P>
                <P>There are two ways to become involved in the Commission's review of this project. First, any person wishing to obtain legal status by becoming a party to the proceedings for this project should, on or before the comment date stated below, file with the Federal Energy Regulatory Commission, 888 First Street, NE., Washington, DC 20426, a motion to intervene in accordance with the requirements of the Commission's Rules of Practice and Procedure (18 CFR 385.214 or 385.211) and the Regulations under the NGA (18 CFR 157.10). A person obtaining party status will be placed on the service list maintained by the Secretary of the Commission and will receive copies of all documents filed by the applicant and by all other parties. A party must submit 7 copies of filings made with the Commission and must mail a copy to the applicant and to every other party in the proceeding. Only parties to the proceeding can ask for court review of Commission orders in the proceeding.</P>
                <P>However, a person does not have to intervene in order to have comments considered. The second way to participate is by filing with the Secretary of the Commission, as soon as possible, an original and two copies of comments in support of or in opposition to this project. The Commission will consider these comments in determining the appropriate action to be taken, but the filing of a comment alone will not serve to make the filer a party to the proceeding. The Commission's rules require that persons filing comments in opposition to the project provide copies of their protests only to the party or parties directly involved in the protest.</P>
                <P>Persons who wish to comment only on the environmental review of this project should submit an original and two copies of their comments to the Secretary of the Commission. Environmental commentors will be placed on the Commission's environmental mailing list, will receive copies of the environmental documents, and will be notified of meetings associated with the Commission's environmental review process. Environmental commentors will not be required to serve copies of filed documents on all other parties. However, the non-party commentors will not receive copies of all documents filed by other parties or issued by the Commission (except for the mailing of environmental documents issued by the Commission) and will not have the right to seek court review of the Commission's final order.</P>
                <P>
                    The Commission strongly encourages electronic filings of comments, protests and interventions in lieu of paper using the “eFiling” link at 
                    <E T="03">http://www.ferc.gov</E>
                    . Persons unable to file electronically should submit an original and 7 copies of the protest or intervention to the Federal Energy Regulatory Commission, 888 First Street, NE., Washington, DC 20426.
                </P>
                <P>
                    This filing is accessible on-line at 
                    <E T="03">http://www.ferc.gov,</E>
                     using the “eLibrary” link and is available for review in the Commission's Public Reference Room in Washington, DC. There is an “eSubscription” link on the Web site that enables subscribers to receive e-mail notification when a document is added to a subscribed docket(s). For assistance with any FERC Online service, please e-mail 
                    <E T="03">FERCOnlineSupport@ferc.gov,</E>
                     or call (866) 208-3676 (toll free). For TTY, call (202) 502-8659.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     July 1, 2011.
                </P>
                <SIG>
                    <DATED>Dated: June 10, 2011.</DATED>
                    <NAME>Kimberly D. Bose,</NAME>
                    <TITLE>Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-14963 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6717-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF ENERGY</AGENCY>
                <SUBAGY>Federal Energy Regulatory Commission</SUBAGY>
                <SUBJECT>Combined Notice of Filings #1</SUBJECT>
                <P>Take notice that the Commission received the following electric rate filings:</P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER05-644-013.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     PSEG Energy Resources &amp; Trade LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Informational Filing with a list of planned Additional Project Investments of the PSEG Companies.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     06/03/2011.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20110603-5417.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. Eastern Time on Friday, June 24, 2011.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER11-2617-002.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     ISO New England Inc., Vermont Electric Power Company, Inc.
                </P>
                <P>
                    <E T="03">Description:</E>
                     ISO New England Inc. submits tariff filing per 35: PTO Compliance Filing—ER11-2617, to be effective 4/1/2011.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     06/09/2011.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20110609-5014.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. Eastern Time on Thursday, June 30, 2011.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER11-2999-003.
                    <PRTPAGE P="35204"/>
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Arizona Public Service Company.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Arizona Public Service Company submits tariff filing per 35: Compliance Filing to Maintain Waiver Previously Accepted by the Commission to be effective N/A.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     06/08/2011.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20110608-5095.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. Eastern Time on Wednesday, June 29, 2011.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER11-3378-001.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     South Hurlburt Wind, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Revised Amendment to Application for Market-Based Rates of South Hurlburt Wind, LLC.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     06/08/2011.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20110608-5195.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. Eastern Time on Wednesday, June 29, 2011.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER11-3642-001.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Tanner Street Generation, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Tanner Street Generation, LLC submits tariff filing per 35.17(b): Supplement to MBR Filing to be effective 5/26/2011.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     06/09/2011.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20110609-5000.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. Eastern Time on Friday, June 24, 2011.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER11-3761-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Palmco Power DC, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Palmco Power DC, LLC submits tariff filing per 35.12: Palmco Power DC FERC Electric Tariff Original Volume No 1 to be effective 8/8/2011.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     06/08/2011.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20110608-5139.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. Eastern Time on Wednesday, June 29, 2011.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER11-3762-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Fulgora Arbitrage Fund, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Fulgora Arbitrage Fund, LLC submits tariff filing per 35.15: Fulgora Arbitrage Fund. LLC's Notice of Cancellation to be effective 6/9/2011.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     06/08/2011.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20110608-5179.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. Eastern Time on Wednesday, June 29, 2011.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER11-3763-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     ISO New England Inc.
                </P>
                <P>
                    <E T="03">Description:</E>
                     ISO New England Inc. submits tariff filing per 35: Docket No. ER09-938-003 eTariff Compliance to be effective 6/1/2011.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     06/09/2011.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20110609-5011.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. Eastern Time on Thursday, June 30, 2011.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER11-3764-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Midwest Independent Transmission System Operator, Inc.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Midwest Independent Transmission System Operator, Inc. submits tariff filing per 35.13(a)(2)(iii: G809 Amended GIA Filing to be effective 6/10/2011.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     06/09/2011.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20110609-5016.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. Eastern Time on Thursday, June 30, 2011.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER11-3765-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Southern California Edison Company.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Southern California Edison Company submits tariff filing per 35.13(a)(2)(iii: Letter Agreement for Alta WindPower Development, Suncreek and Alta 6 Projects to be effective 6/6/2011.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     06/09/2011.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20110609-5021.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. Eastern Time on Thursday, June 30, 2011.
                </P>
                <P>Any person desiring to intervene or to protest in any of the above proceedings must file in accordance with Rules 211 and 214 of the Commission's Rules of Practice and Procedure (18 CFR 385.211 and 385.214) on or before 5 p.m. Eastern time on the specified comment date. It is not necessary to separately intervene again in a subdocket related to a compliance filing if you have previously intervened in the same docket. Protests will be considered by the Commission in determining the appropriate action to be taken, but will not serve to make protestants parties to the proceeding. Anyone filing a motion to intervene or protest must serve a copy of that document on the Applicant. In reference to filings initiating a new proceeding, interventions or protests submitted on or before the comment deadline need not be served on persons other than the Applicant.</P>
                <P>As it relates to any qualifying facility filings, the notices of self-certification [or self-recertification] listed above, do not institute a proceeding regarding qualifying facility status. A notice of self-certification [or self-recertification] simply provides notification that the entity making the filing has determined the facility named in the notice meets the applicable criteria to be a qualifying facility. Intervention and/or protest do not lie in dockets that are qualifying facility self-certifications or self-recertifications. Any person seeking to challenge such qualifying facility status may do so by filing a motion pursuant to 18 CFR 292.207(d)(iii). Intervention and protests may be filed in response to notices of qualifying facility dockets other than self-certifications and self-recertifications.</P>
                <P>
                    The Commission encourages electronic submission of protests and interventions in lieu of paper, using the FERC Online links at 
                    <E T="03">http://www.ferc.gov</E>
                    . To facilitate electronic service, persons with Internet access who will eFile a document and/or be listed as a contact for an intervenor must create and validate an eRegistration account using the eRegistration link. Select the eFiling link to log on and submit the intervention or protests.
                </P>
                <P>Persons unable to file electronically should submit an original and 14 copies of the intervention or protest to the Federal Energy Regulatory Commission, 888 First St., NE., Washington, DC 20426.</P>
                <P>
                    The filings in the above proceedings are accessible in the Commission's eLibrary system by clicking on the appropriate link in the above list. They are also available for review in the Commission's Public Reference Room in Washington, DC. There is an eSubscription link on the Web site that enables subscribers to receive e-mail notification when a document is added to a subscribed docket(s). For assistance with any FERC Online service, please e-mail 
                    <E T="03">FERCOnlineSupport@ferc.gov,</E>
                     or call (866) 208-3676 (toll free). For TTY, call (202) 502-8659.
                </P>
                <SIG>
                    <DATED>Dated: June 9, 2011.</DATED>
                    <NAME>Nathaniel J. Davis, Sr.,</NAME>
                    <TITLE>Deputy Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-14880 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6717-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF ENERGY</AGENCY>
                <SUBAGY>Federal Energy Regulatory Commission</SUBAGY>
                <SUBJECT>Combined Notice of Filings</SUBJECT>
                <P>Take notice that the Commission has received the following Natural Gas Pipeline Rate and Refund Report filings:</P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     RP11-2177-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Texas Gas Transmission, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Texas Gas Transmission, LLC submits tariff filing per 154.204: Backhaul-Related Language Revisions to be effective 7/7/2011.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     06/06/2011.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20110606-5038.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. Eastern Time on Monday, June 20, 2011.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     RP11-2178-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Gulf South Pipeline Company, LP.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Gulf South Pipeline Company, LP submits tariff filing per 154.204: Open Season Clarification to be effective 7/7/2011.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     06/06/2011.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20110606-5048.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. Eastern Time on Monday, June 20, 2011.
                </P>
                <PRTPAGE P="35205"/>
                <P>
                    <E T="03">Docket Numbers:</E>
                     RP11-2179-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     El Paso Natural Gas Company.
                </P>
                <P>
                    <E T="03">Description:</E>
                     El Paso Natural Gas Company submits tariff filing per 154.204: Pressure Commitment Update to be effective 7/7/2011.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     06/06/2011.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20110606-5099.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. Eastern Time on Monday, June 20, 2011.
                </P>
                <P>Any person desiring to intervene or to protest in any of the above proceedings must file in accordance with Rules 211 and 214 of the Commission's Rules of Practice and Procedure (18 CFR 385.211 and 385.214) on or before 5 p.m. Eastern time on the specified comment date. It is not necessary to separately intervene again in a sub-docket related to a compliance filing if you have previously intervened in the same docket. Protests will be considered by the Commission in determining the appropriate action to be taken, but will not serve to make protestants parties to the proceeding. Anyone filing a motion to intervene or protest must serve a copy of that document on the Applicant. In reference to filings initiating a new proceeding, interventions or protests submitted on or before the comment deadline need not be served on persons other than the Applicant.</P>
                <P>
                    The Commission encourages electronic submission of protests and interventions in lieu of paper, using the FERC Online links at 
                    <E T="03">http://www.ferc.gov</E>
                    . To facilitate electronic service, persons with Internet access who will eFile a document and/or be listed as a contact for an intervenor must create and validate an eRegistration account using the eRegistration link. Select the eFiling link to log on and submit the intervention or protests.
                </P>
                <P>Persons unable to file electronically should submit an original and 14 copies of the intervention or protest to the Federal Energy Regulatory Commission, 888 First St., NE., Washington, DC 20426.</P>
                <P>
                    The filings in the above proceedings are accessible in the Commission's eLibrary system by clicking on the appropriate link in the above list. They are also available for review in the Commission's Public Reference Room in Washington, DC. There is an eSubscription link on the Web site that enables subscribers to receive e-mail notification when a document is added to a subscribed docket(s). For assistance with any FERC Online service, please e-mail 
                    <E T="03">FERCOnlineSupport@ferc.gov,</E>
                     or call (866) 208-3676 (toll free). For TTY, call (202) 502-8659.
                </P>
                <SIG>
                    <DATED>Dated: June 8, 2011.</DATED>
                    <NAME>Nathaniel J. Davis, Sr.,</NAME>
                    <TITLE>Deputy Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-14881 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6717-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF ENERGY</AGENCY>
                <SUBAGY>Federal Energy Regulatory Commission</SUBAGY>
                <SUBJECT>Combined Notice of Filings #1</SUBJECT>
                <P>Take notice that the Commission received the following electric corporate filings:</P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     EC11-88-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     NorthWestern Corporation.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Application of Northwestern Corporation for Authorization for Acquistion of an Existing Generation Facility.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     06/06/2011.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20110606-5209.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. Eastern Time on Monday, June 27, 2011.
                </P>
                <P>Take notice that the Commission received the following electric rate filings:</P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER97-3359-018.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Florida Power &amp; Light Company.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Florida Power &amp; Light Company Notice of Change in Status.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     05/27/2011.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20110527-5202.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. Eastern Time on Friday, June 17, 2011.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER10-2923-002.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Sunbury Generation LP.
                </P>
                <P>
                    <E T="03">Description:</E>
                     On 6/6/2011 Sunbury Generation LP submitted a notice of Non-Material Change in Status and on 6/7/2011 submitted an Errata Filing.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     06/06/2011, 06/07/2011.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20110606-5213; 20110607-5158.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. Eastern Time on Monday, June 27, 2011.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER11-2715-002.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Interstate Power and Light Company, ITC Midwest, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Interstate Power and Light Co. Resubmits OTA Exhibit 1.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     06/06/2011.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20110606-5212.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. Eastern Time on Monday, June 27, 2011.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER11-2544-001.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     New York Independent System Operator, Inc.
                </P>
                <P>
                    <E T="03">Description:</E>
                     New York Independent System Operator, Inc. submits tariff filing per 35: Compliance re: Effective date 4 sections MMM to be effective 6/23/2011.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     06/07/2011.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20110607-5012.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. Eastern Time on Tuesday, June 28, 2011.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER11-3631-001.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Interstate Power and Light Company.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Interstate Power and Light Company submits tariff filing per 35: IPL RES-5 Baseline Tariff Compliance Filing to be effective 8/26/2010.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     06/07/2011.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20110607-5023.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. Eastern Time on Tuesday, June 28, 2011.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER11-3740-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Florida Power &amp; Light Company.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Florida Power &amp; Light Company submits tariff filing per 35.13(a)(2)(iii: FPL Revisions to FKEC Rate Schedule FERC No. 322 to be effective 5/1/2011.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     06/07/2011.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20110607-5065.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. Eastern Time on Tuesday, June 28, 2011.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER11-3741-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Florida Power &amp; Light Company.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Florida Power &amp; Light Company submits tariff filing per 35.13(a)(2)(iii: FPL Revisions to LCEC Rate Schedule FERC No. 312 to be effective 8/10/2010.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     06/07/2011.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20110607-5067.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. Eastern Time on Tuesday, June 28, 2011.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER11-3742-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Florida Power &amp; Light Company.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Florida Power &amp; Light Company submits tariff filing per 35.13(a)(2)(iii: FPL Revisions to LCEC Rate Schedule FERC No. 317 to be effective 1/1/2014.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     06/07/2011.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20110607-5068.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. Eastern Time on Tuesday, June 28, 2011.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER11-3743-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     PJM Interconnection, L.L.C.
                </P>
                <P>
                    <E T="03">Description:</E>
                     PJM Interconnection, L.L.C. submits tariff filing per 35.13(a)(2)(iii: Queue No. W2-082; Original Service Agreement No. 2935 to be effective 5/10/2011.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     06/07/2011.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20110607-5079.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. Eastern Time on Tuesday, June 28, 2011.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER11-3744-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     PJM Interconnection, L.L.C.
                    <PRTPAGE P="35206"/>
                </P>
                <P>
                    <E T="03">Description:</E>
                     PJM Interconnection, L.L.C. submits tariff filing per 35.13(a)(2)(iii: Queue No. W2-080; Original Service Agreement No. 2934 to be effective 5/10/2011.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     06/07/2011.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20110607-5086.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. Eastern Time on Tuesday, June 28, 2011.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER11-3746-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     NSTAR Electric Company.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Tariff Filing of NSTAR Electric Company.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     06/03/2011.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20110603-5409.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. Eastern Time on Friday, June 24, 2011.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER11-3747-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     PJM Interconnection, L.L.C.
                </P>
                <P>
                    <E T="03">Description:</E>
                     PJM Interconnection, L.L.C. submits tariff filing per 35.13(a)(2)(iii: Queue No. W2-061; Original Service Agreement No. 2932 to be effective 5/10/2011.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     06/07/2011.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20110607-5096.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. Eastern Time on Tuesday, June 28, 2011.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER11-3748-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     CES Placerita, Incorporated.
                </P>
                <P>
                    <E T="03">Description:</E>
                     CES Placerita, Incorporated submits tariff filing per 35.13(a)(2)(iii: Notice of Succession to be effective 3/24/2011.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     06/07/2011.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20110607-5098.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. Eastern Time on Tuesday, June 28, 2011.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER11-3749-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     PJM Interconnection, L.L.C.
                </P>
                <P>
                    <E T="03">Description:</E>
                     PJM Interconnection, L.L.C. submits tariff filing per 35.13(a)(2)(iii) Queue No. W1-115; Original Service Agreement No. 2938 to be effective 5/10/2011.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     06/07/2011.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20110607-5109.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. Eastern Time on Tuesday, June 28, 2011.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER11-3750-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Southwestern Electric Power Company.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Southwestern Electric Power Company Actuarial Reports.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     06/03/2011.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20110603-5413.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. Eastern Time on Friday, June 24, 2011.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER11-3751-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Public Service Company of New Mexico.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Public Service Company of New Mexico submits a Notice of cancellation of FERC Electric Rate Schedule 37.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     06/06/2011.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20110607-0207.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. Eastern Time on Monday, June 27, 2011.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER11-3752-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Midwest Independent Transmission System Operator, Inc.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Midwest Independent Transmission System Operator, Inc. submits tariff filing per 35.13(a)(2)(iii) 06-07-11 GRE Attachment GG Filing to be effective 7/29/2011.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     06/07/2011.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20110607-5134.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. Eastern Time on Tuesday, June 28, 2011.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER11-3753-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     People's Power &amp; Gas, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     People's Power &amp; Gas, LLC submits tariff filing per 35.1: Market-Based Rate Tariff to be effective 6/8/2011.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     06/08/2011.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20110608-5002.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. Eastern Time on Wednesday, June 29, 2011.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER11-3754-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Horsehead Corp.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Notice of Cancellation of Horsehead Corp.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     06/07/2011.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20110607-5159.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. Eastern Time on Tuesday, June 28, 2011.
                </P>
                <P>Take notice that the Commission received the following electric reliability filings:</P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     RR11-4-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     North American Electric Reliability Corporation.
                </P>
                <P>
                    <E T="03">Description:</E>
                     North American Electric Reliability Corporation's Report of Comparisons of Budgeted to Actual Costs for 2010 for NERC and the Regional Entities.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     05/31/2011.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20110531-5154.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. Eastern Time on Wednesday, June 29, 2011.
                </P>
                <P>Any person desiring to intervene or to protest in any of the above proceedings must file in accordance with Rules 211 and 214 of the Commission's Rules of Practice and Procedure (18 CFR 385.211 and 385.214) on or before 5 p.m. Eastern time on the specified comment date. It is not necessary to separately intervene again in a subdocket related to a compliance filing if you have previously intervened in the same docket. Protests will be considered by the Commission in determining the appropriate action to be taken, but will not serve to make protestants parties to the proceeding. Anyone filing a motion to intervene or protest must serve a copy of that document on the Applicant. In reference to filings initiating a new proceeding, interventions or protests submitted on or before the comment deadline need not be served on persons other than the Applicant.</P>
                <P>As it relates to any qualifying facility filings, the notices of self-certification [or self-recertification] listed above, do not institute a proceeding regarding qualifying facility status. A notice of self-certification [or self-recertification] simply provides notification that the entity making the filing has determined the facility named in the notice meets the applicable criteria to be a qualifying facility. Intervention and/or protest do not lie in dockets that are qualifying facility self-certifications or self-recertifications. Any person seeking to challenge such qualifying facility status may do so by filing a motion pursuant to 18 CFR 292.207(d)(iii). Intervention and protests may be filed in response to notices of qualifying facility dockets other than self-certifications and self-recertifications.</P>
                <P>
                    The Commission encourages electronic submission of protests and interventions in lieu of paper, using the FERC Online links at 
                    <E T="03">http://www.ferc.gov</E>
                    . To facilitate electronic service, persons with Internet access who will eFile a document and/or be listed as a contact for an intervenor must create and validate an eRegistration account using the eRegistration link. Select the eFiling link to log on and submit the intervention or protests.
                </P>
                <P>Persons unable to file electronically should submit an original and 14 copies of the intervention or protest to the Federal Energy Regulatory Commission, 888 First St., NE., Washington, DC 20426.</P>
                <P>
                    The filings in the above proceedings are accessible in the Commission's eLibrary system by clicking on the appropriate link in the above list. They are also available for review in the Commission's Public Reference Room in Washington, DC. There is an eSubscription link on the Web site that enables subscribers to receive e-mail notification when a document is added to a subscribed docket(s). For assistance with any FERC Online service, please e-mail 
                    <E T="03">FERCOnlineSupport@ferc.gov,</E>
                     or call (866) 208-3676 (toll free). For TTY, call (202) 502-8659.
                </P>
                <SIG>
                    <DATED>Dated: June 8, 2011.</DATED>
                    <NAME>Nathaniel J. Davis, Sr.,</NAME>
                    <TITLE>Deputy Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-14888 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6717-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="35207"/>
                <AGENCY TYPE="S">DEPARTMENT OF ENERGY</AGENCY>
                <SUBAGY>Federal Energy Regulatory Commission</SUBAGY>
                <SUBJECT>Combined Notice of Filings #2</SUBJECT>
                <P>Take notice that the Commission received the following electric rate filings:</P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER11-3173-001.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Arizona Public Service Company.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Arizona Public Service Company submits tariff filing per 35: Compliance Filing To Make Footnotes Viewable in eTariff Viewer to be effective 11/15/2010.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     06/08/2011.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20110608-5096.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. Eastern Time on Wednesday, June 29, 2011.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER11-3755-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Wabash Valley Power Association, Inc.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Wabash Valley Power Association, Inc. submits tariff filing per 35.13(a)(2)(iii: Amendments to WVPA FERC Electric Tariff Volume 1—Section 1—Formulary Rate to be effective 1/1/2012.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     06/08/2011.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20110608-5023.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. Eastern Time on Wednesday, June 29, 2011.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER11-3756-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     California Independent System Operator Corporation.
                </P>
                <P>
                    <E T="03">Description:</E>
                     California Independent System Operator Corporation submits tariff filing per 35.13(a)(2)(iii: 2011-06-08 CAISO Non Conforming SCA with WAPA to be effective 7/28/2010.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     06/08/2011.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20110608-5065.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. Eastern Time on Wednesday, June 29, 2011.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER11-3757-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     California Independent System Operator Corporation.
                </P>
                <P>
                    <E T="03">Description:</E>
                     California Independent System Operator Corporation submits tariff filing per 35.13(a)(2)(iii: 2011-06-08 Amendment to CAISO Service Agreement 784 WAPA DSR to be effective 6/15/2011.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     06/08/2011.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20110608-5070.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. Eastern Time on Wednesday, June 29, 2011.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER11-3758-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     California Independent System Operator Corporation.
                </P>
                <P>
                    <E T="03">Description:</E>
                     California Independent System Operator Corporation submits tariff filing per 35.13(a)(2)(iii: 2011-06-08 CAISO Non-Conforming MSA with WAPA DSR to be effective 7/28/2010.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     06/08/2011.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20110608-5071.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. Eastern Time on Wednesday, June 29, 2011.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER11-3759-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     California Independent System Operator Corporation.
                </P>
                <P>
                    <E T="03">Description:</E>
                     California Independent System Operator Corporation submits tariff filing per 35.13(a)(2)(iii: 2011-06-08 Amendment to CAISO Non-Conforming MSA with WAPA DSR to be effective 6/15/2011.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     06/08/2011.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20110608-5082.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. Eastern Time on Wednesday, June 29, 2011.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER11-3760-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Deseret Generation &amp; Transmission Co-operative, Inc.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Deseret Generation &amp; Transmission Co-operative, Inc. submits tariff filing per 35.13(a)(2)(ii): Tier 2 Rate Schedule A 205 Filing to be effective 8/1/2011.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     06/08/2011.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20110608-5092.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. Eastern Time on Wednesday, June 29, 2011.
                </P>
                <P>Take notice that the Commission received the following qualifying facility filings:</P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     QF11-290-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Equistar Chemicals, L.P.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Form 556—Notice of Self-Certification of Equistar Chemicals, L.P.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     06/07/2011.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20110607-5105.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     None Applicable.
                </P>
                <P>Any person desiring to intervene or to protest in any of the above proceedings must file in accordance with Rules 211 and 214 of the Commission's Rules of Practice and Procedure (18 CFR 385.211 and 385.214) on or before 5 p.m. Eastern time on the specified comment date. It is not necessary to separately intervene again in a subdocket related to a compliance filing if you have previously intervened in the same docket. Protests will be considered by the Commission in determining the appropriate action to be taken, but will not serve to make protestants parties to the proceeding. Anyone filing a motion to intervene or protest must serve a copy of that document on the Applicant. In reference to filings initiating a new proceeding, interventions or protests submitted on or before the comment deadline need not be served on persons other than the Applicant.</P>
                <P>As it relates to any qualifying facility filings, the notices of self-certification [or self-recertification] listed above, do not institute a proceeding regarding qualifying facility status. A notice of self-certification [or self-recertification] simply provides notification that the entity making the filing has determined the facility named in the notice meets the applicable criteria to be a qualifying facility. Intervention and/or protest do not lie in dockets that are qualifying facility self-certifications or self-recertifications. Any person seeking to challenge such qualifying facility status may do so by filing a motion pursuant to 18 CFR 292.207(d)(iii). Intervention and protests may be filed in response to notices of qualifying facility dockets other than self-certifications and self-recertifications.</P>
                <P>
                    The Commission encourages electronic submission of protests and interventions in lieu of paper, using the FERC Online links at 
                    <E T="03">http://www.ferc.gov</E>
                    . To facilitate electronic service, persons with Internet access who will eFile a document and/or be listed as a contact for an intervenor must create and validate an eRegistration account using the eRegistration link. Select the eFiling link to log on and submit the intervention or protests.
                </P>
                <P>Persons unable to file electronically should submit an original and 14 copies of the intervention or protest to the Federal Energy Regulatory Commission, 888 First St., NE., Washington, DC 20426.</P>
                <P>
                    The filings in the above proceedings are accessible in the Commission's eLibrary system by clicking on the appropriate link in the above list. They are also available for review in the Commission's Public Reference Room in Washington, DC. There is an eSubscription link on the Web site that enables subscribers to receive e-mail notification when a document is added to a subscribed docket(s). For assistance with any FERC Online service, please e-mail 
                    <E T="03">FERCOnlineSupport@ferc.gov</E>
                     or call (866) 208-3676 (toll free). For TTY, call (202) 502-8659.
                </P>
                <SIG>
                    <DATED>Dated: June 8, 2011.</DATED>
                    <NAME>Nathaniel J. Davis, Sr.,</NAME>
                    <TITLE>Deputy Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-14884 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6717-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="35208"/>
                <AGENCY TYPE="S">DEPARTMENT OF ENERGY</AGENCY>
                <SUBAGY>Federal Energy Regulatory Commission</SUBAGY>
                <DEPDOC>[ Project No. 2790-055]</DEPDOC>
                <SUBJECT>Boott Hydropower, Inc.; Notice of Availability of Draft Environmental Assessment</SUBJECT>
                <P>In accordance with the National Environmental Policy Act of 1969 and the Federal Energy Regulatory Commission's (Commission or FERC) regulations, 18 CFR part 380, Commission staff has reviewed the application for amendment of license for the Lowell Hydroelectric Project (FERC No. 2790-055) and has prepared a draft environmental assessment (draft EA). The project is located on the Merrimack River in Middlesex County, Massachusetts.</P>
                <P>The draft EA contains the Commission staff's analysis of the potential environmental effects of the proposed replacement of the wooden flashboards with a pneumatic crest gate system of the same height and interim modifications to the existing flashboard system and concludes that authorizing the amendment, with appropriate environmental protective measures, would not constitute a major Federal action that would significantly affect the quality of the human environment.</P>
                <P>
                    A copy of the draft EA is available for review at the Commission in the Public Reference Room, or it may be viewed on the Commission's Web site at 
                    <E T="03">http://www.ferc.gov</E>
                     using the e-Library link. Enter the docket number (P-2790) in the docket number field to access the document. For assistance, contact FERC Online Support at 
                    <E T="03">FERCOnlineSupport@ferc.gov</E>
                     or call toll-free at 1-866-208-3676 or (202) 502-8659 (for TTY).
                </P>
                <P>
                    Any comments should be filed within 30 days from the issuance date of this notice, and should be addressed to the Secretary, Federal Energy Regulatory Commission, 888 First Street, NE., Washington, DC 20426. Please reference the Lowell Project No. 2790 on all comments. For further information on this notice, please contact Holly Frank at (202) 502-6833. Comments may be filed electronically via the Internet in lieu of paper. See 18 CFR 385.2001 (a)(1)(iii) and the instructions on the Commission's Web site at 
                    <E T="03">http://www.ferc.gov</E>
                     under the e-Filing link. The Commission strongly encourages electronic filing.
                </P>
                <SIG>
                    <DATED>Dated: June 10, 2011.</DATED>
                    <NAME>Kimberly D. Bose,</NAME>
                    <TITLE>Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-14970 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6717-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF ENERGY</AGENCY>
                <SUBAGY>Federal Energy Regulatory Commission</SUBAGY>
                <DEPDOC>[Docket No. CP10-480-000]</DEPDOC>
                <SUBJECT>Central New York Oil and Gas Company, LLC; Notice Extending Comment Period</SUBJECT>
                <P>On May 27, 2011, the Federal Energy Regulatory Commission (FERC or Commission) issued its environmental assessment (EA) for Central New York Oil and Gas Company, LLC's MARC I Hub Line Project proposed in the above-referenced docket. The EA was placed in the public record and was available via the FERC's eLibrary on that date. However, the Commission experienced technical problems reproducing the copies of the EA that were to be mailed to interested stakeholders. As a result, the compact disk copies of the EA were not mailed until June 7, 2011. Therefore, the deadline for filing comments on the EA has been extended for two weeks, and will end on July 11, 2011.</P>
                <SIG>
                    <DATED>Dated: June 10, 2011.</DATED>
                    <NAME>Kimberly D. Bose,</NAME>
                    <TITLE>Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-14962 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6717-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF ENERGY</AGENCY>
                <SUBAGY>Federal Energy Regulatory Commission</SUBAGY>
                <DEPDOC>[ Project No. 2310-193—California; Project No. 2266-102—California]</DEPDOC>
                <SUBJECT>Pacific Gas and Electric Company; Nevada Irrigation District; Notice of Environmental Site Review</SUBJECT>
                <P>On July 6-8, 2011, the Federal Energy Regulatory Commission (Commission) staff and the Pacific Gas and Electric Company (PG&amp;E) and Nevada Irrigation District (NID) (applicants) will conduct an environmental site review of the Drum-Spaulding and Yuba-Bear Projects. The Drum-Spaulding Project is located on the west slope of the Sierra Nevada on the South Yuba River, Bear River, North Fork of the North Fork American River, and tributaries in the Sacramento River watershed in Nevada and Placer Counties, California. The Yuba-Bear Hydroelectric Project is located on the west slope of the Sierra Nevada in the Middle Yuba River, Canyon Creek, Rucker Creek and Bear River watersheds in Nevada, Placer and Sierra Counties, California.</P>
                <P>The site visit is open to the public and resource agencies, and will occur from 8 a.m. to about 5 p.m. (Pacific Daylight Time) on each of three days. Participants will meet no later than the start time at Discovery Trail near Bear Valley on the first day, at PG&amp;E's Alta Service Center on the second day, and at PG&amp;E's Halsey forebay on the third day. Each day will start with a brief safety talk, review of the facilities that will be visited that day, and discussion of logistics. The tour will depart the meeting location no later than 15 minutes after the start time. We will try to return to the meeting location by 5 p.m. each day.</P>
                <P>Participants are responsible to provide their own transportation (recommend a 4-wheel drive vehicle), but car pooling to the extent possible is encouraged. We do not anticipate hiking in any difficult terrain or entering private property that requires special permission, but some brief walking over dirt trails might be needed. Cell phone coverage in the upper and mid elevation sites is limited.</P>
                <P>
                    Safety is a prime concern. Many of the sites that will be visited require wearing hardhats, safety eyewear, and safety vests that licensees will provide. Participants must wear appropriate footwear (
                    <E T="03">i.e.</E>
                     no sandals or open-toed shoes).
                </P>
                <P>The schedule below is provided for general guidance only and is not intended to be a strict schedule. We may proceed through the schedule for each day at a slower or faster pace than anticipated in the schedule below, or may decide to delete or add project facilities. For these reasons and because of poor electronic communications in some areas, it will be difficult for a participant to join the site visit after it departs the initial meeting location. Project facilities listed below are indicated as either “YB” for NID's Yuba-Bear Hydroelectric Project or “DS” for PG&amp;E's Drum-Spaulding Project.</P>
                <HD SOURCE="HD3">Wednesday, July 6, 2011</HD>
                <P>• Meet at Discovery Trail in Bear Valley at 8 a.m.;</P>
                <P>• Bowman Lake (YB);</P>
                <P>• Bowman/Spaulding canal at Fall Creek (YB);</P>
                <P>• Fuller Lake (DS);</P>
                <P>• Lake Spaulding dam (DS);</P>
                <P>
                    • Bear Valley—Drum canal and South Yuba canal (DS).
                    <PRTPAGE P="35209"/>
                </P>
                <HD SOURCE="HD3">Thursday, July 7, 2011</HD>
                <P>• Meet at Alta Service Center at 8 a.m.;</P>
                <P>• Drum powerhouse (DS);</P>
                <P>• Dutch Flat #2 powerhouse (YB);</P>
                <P>• Dutch Flat afterbay (YB);</P>
                <P>• Rollins dam (YB);</P>
                <P>• Bear River Head dam (DS).</P>
                <HD SOURCE="HD3">Friday, July 8, 2011</HD>
                <P>• Meet at Halsey forebay at 8 a.m.;</P>
                <P>• Halsey afterbay (DS);</P>
                <P>• Rock Creek reservoir (DS),</P>
                <P> Wise canal, Rock Creek, delivery to North Auburn Water Treatment Plant;</P>
                <P>• Auburn Ravine,</P>
                <P> Delivery to Auburn Ravine at YB-259, PCWA Pump Station into South canal;</P>
                <P>• Newcastle forebay and powerhouse (DS).</P>
                <P>
                    If you plan to attend, please notify Alan Mitchnick, FERC Team Leader, at (202) 502-6074 or 
                    <E T="03">alan.mitchnick@ferc.gov,</E>
                     no later than June 30, 2011.
                </P>
                <SIG>
                    <DATED>Dated: June 10, 2011.</DATED>
                    <NAME>Kimberly D. Bose,</NAME>
                    <TITLE>Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-14969 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6717-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF ENERGY</AGENCY>
                <SUBAGY>Federal Energy Regulatory Commission</SUBAGY>
                <DEPDOC>[Docket No. NJ11-12-001]</DEPDOC>
                <SUBJECT>Orlando Utilities Commission; Notice of Filing</SUBJECT>
                <P>Take notice that on May 26, 2011, Orlando Utilities Commission submitted its tariff filing per 35.17(b): Amendment to Compliance Filing to be effective 4/15/2011.</P>
                <P>Any person desiring to intervene or to protest this filing must file in accordance with Rules 211 and 214 of the Commission's Rules of Practice and Procedure (18 CFR 385.211, 385.214). Protests will be considered by the Commission in determining the appropriate action to be taken, but will not serve to make protestants parties to the proceeding. Any person wishing to become a party must file a notice of intervention or motion to intervene, as appropriate. Such notices, motions, or protests must be filed on or before the comment date. On or before the comment date, it is not necessary to serve motions to intervene or protests on persons other than the Applicant.</P>
                <P>
                    The Commission encourages electronic submission of protests and interventions in lieu of paper using the “eFiling” link at 
                    <E T="03">http://www.ferc.gov</E>
                    . Persons unable to file electronically should submit an original and 14 copies of the protest or intervention to the Federal Energy Regulatory Commission, 888 First Street, NE., Washington, DC 20426.
                </P>
                <P>
                    This filing is accessible on-line at 
                    <E T="03">http://www.ferc.gov,</E>
                     using the “eLibrary” link and is available for review in the Commission's Public Reference Room in Washington, DC. There is an “eSubscription” link on the Web site that enables subscribers to receive e-mail notification when a document is added to a subscribed docket(s). For assistance with any FERC Online service, please e-mail 
                    <E T="03">FERCOnlineSupport@ferc.gov,</E>
                     or call (866) 208-3676 (toll free). For TTY, call (202) 502-8659.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 pm Eastern Time on June 20, 2011.
                </P>
                <SIG>
                    <DATED>Dated: June 10, 2011.</DATED>
                    <NAME>Kimberly D. Bose,</NAME>
                    <TITLE>Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-14965 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6717-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF ENERGY</AGENCY>
                <SUBAGY>Federal Energy Regulatory Commission</SUBAGY>
                <DEPDOC>[Project No. 13579-001]</DEPDOC>
                <SUBJECT>FFP Qualified Hydro 14 LLC; Notice of Intent To File License Application, Filing of Pre-Application Document, and Approving Use of the Traditional Licensing Process</SUBJECT>
                <P>
                    a. 
                    <E T="03">Type of Filing:</E>
                     Notice of Intent to File License Application and Request to Use the Traditional Licensing Process.
                </P>
                <P>
                    b. 
                    <E T="03">Project No.:</E>
                     13579-001.
                </P>
                <P>
                    c. 
                    <E T="03">Dated Filed:</E>
                     April 4, 2011.
                </P>
                <P>
                    d. 
                    <E T="03">Submitted by:</E>
                     Free Flow Power Qualified Hydro 14 LLC (Qualified Power 14 LLC), a subsidiary of Free Flow Power Corporation.
                </P>
                <P>
                    e. 
                    <E T="03">Name of Project:</E>
                     Saylorville Dam Water Power Project.
                </P>
                <P>
                    f. 
                    <E T="03">Location:</E>
                     At the U.S. Army Corps of Engineers' (Corps) Saylorville Dam on the Des Moines River in Polk County, Iowa. The project would occupy 1.5 acres of United States lands administered by Corps' Rock Island District.
                </P>
                <P>
                    g. 
                    <E T="03">Filed Pursuant to:</E>
                     18 CFR 5.3 of the Commission's regulations.
                </P>
                <P>
                    h. 
                    <E T="03">Potential Applicant Contact:</E>
                     Ramya Swaminathan, Free Flow Power Corporation, 239 Causeway Street, Suite 300, Boston, MA 02114; (978) 226-1531; or e-mail 
                    <E T="03">rswaminathan@free-flow-power.com.</E>
                </P>
                <P>
                    i. 
                    <E T="03">FERC Contact:</E>
                     Sergiu Serban at (202) 502-6211; or e-mail at 
                    <E T="03">sergiu.serban@ferc.gov.</E>
                </P>
                <P>j. Qualified Power 14 LLC filed its request to use the Traditional Licensing Process on April 4, 2011. Qualified Power 14 LLC provided public notice of its request on March 16, 2011. In a letter issued on June 6, 2011, the Director of the Office of Energy Projects approved Qualified Power 14 LLC's request to use the Traditional Licensing Process.</P>
                <P>
                    k. 
                    <E T="03">With this notice, we are initiating informal consultation with:</E>
                     (a) The U.S. Fish and Wildlife Service under section 7 of the Endangered Species Act and the joint agency regulations thereunder at 50 CFR part 402; and (b) the Iowa State Historic Preservation Officer, as required by section 106, National Historical Preservation Act, and the implementing regulations of the Advisory Council on Historic Preservation at 36 CFR 800.2.
                </P>
                <P>l. With this notice, we are designating Qualified Power 14 LLC as the Commission's non-federal representative for carrying out informal consultation, pursuant to section 7 of the Endangered Species Act and section 106 of the National Historic Preservation Act.</P>
                <P>m. Qualified Power 14 LLC filed a Pre-Application Document (PAD; including a proposed process plan and schedule) with the Commission, pursuant to 18 CFR 5.6 of the Commission's regulations.</P>
                <P>
                    n. A copy of the PAD is available for review at the Commission in the Public Reference Room or may be viewed on the Commission's Web site (
                    <E T="03">http://www.ferc.gov</E>
                    ), using the “eLibrary” link. Enter the docket number, excluding the last three digits in the docket number field to access the document. For assistance, contact FERC Online Support at 
                    <E T="03">FERCONlineSupport@ferc.gov</E>
                     or toll free at 1-866-208-3676, or for TTY, (202) 502-8659. A copy is also available for inspection and reproduction at the address in paragraph h.
                </P>
                <P>
                    o. Register online at 
                    <E T="03">http://www.ferc.gov/docs-filing/esubscription.asp</E>
                     to be notified via e-mail of new filing and issuances related to this or other pending projects. For assistance, contact FERC Online Support.
                </P>
                <SIG>
                    <DATED>Dated: June 10, 2011.</DATED>
                    <NAME>Kimberly D. Bose,</NAME>
                    <TITLE> Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-14971 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6717-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="35210"/>
                <AGENCY TYPE="S">DEPARTMENT OF ENERGY</AGENCY>
                <SUBAGY>Federal Energy Regulatory Commission</SUBAGY>
                <DEPDOC>[Docket No. ER11-2970-000]</DEPDOC>
                <SUBJECT>Peetz Logan Interconnect, LLC; Notice of Filing</SUBJECT>
                <P>Take notice that on June 3, 2011, Peetz Logan Interconnect, LLC (PLI) filed a response to a staff deficiency letter issued on April 29, 2011, providing additional information with respect to a proposed open access transmission tariff (OATT) filed by PLI on February 28, 2011 in this proceeding.</P>
                <P>Any person desiring to intervene or to protest this filing must file in accordance with Rules 211 and 214 of the Commission's Rules of Practice and Procedure (18 CFR 385.211, 385.214). Protests will be considered by the Commission in determining the appropriate action to be taken, but will not serve to make protestants parties to the proceeding. Any person wishing to become a party must file a notice of intervention or motion to intervene, as appropriate. Such notices, motions, or protests must be filed on or before the comment date. On or before the comment date, it is not necessary to serve motions to intervene or protests on persons other than the Applicant.</P>
                <P>
                    The Commission encourages electronic submission of protests and interventions in lieu of paper using the “eFiling” link at 
                    <E T="03">http://www.ferc.gov</E>
                    . Persons unable to file electronically should submit an original and 14 copies of the protest or intervention to the Federal Energy Regulatory Commission, 888 First Street, NE., Washington, DC 20426.
                </P>
                <P>
                    This filing is accessible on-line at 
                    <E T="03">http://www.ferc.gov,</E>
                     using the “eLibrary” link and is available for review in the Commission's Public Reference Room in Washington, DC. There is an “eSubscription” link on the Web site that enables subscribers to receive e-mail notification when a document is added to a subscribed docket(s). For assistance with any FERC Online service, please e-mail 
                    <E T="03">FERCOnlineSupport@ferc.gov,</E>
                     or call (866) 208-3676 (toll free). For TTY, call (202) 502-8659.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. Eastern Time on June 24, 2011.
                </P>
                <SIG>
                    <DATED>Dated: June 8, 2011.</DATED>
                    <NAME>Nathaniel J. Davis, Sr.,</NAME>
                    <TITLE>Deputy Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-14885 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6717-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF ENERGY</AGENCY>
                <SUBAGY>Federal Energy Regulatory Commission</SUBAGY>
                <DEPDOC>[Docket No. ER11-3753-000]</DEPDOC>
                <SUBJECT>People's Power &amp; Gas, LLC; Supplemental Notice That Initial Market-Based Rate Filing Includes Request for Blanket Section 204 Authorization</SUBJECT>
                <P>This is a supplemental notice in the above-referenced proceeding of People's Power &amp; Gas, LLC's application for market-based rate authority, with an accompanying rate tariff, noting that such application includes a request for blanket authorization, under 18 CFR part 34, of future issuances of securities and assumptions of liability.</P>
                <P>Any person desiring to intervene or to protest should file with the Federal Energy Regulatory Commission, 888 First Street, NE., Washington, DC 20426, in accordance with Rules 211 and 214 of the Commission's Rules of Practice and Procedure (18 CFR 385.211 and 385.214). Anyone filing a motion to intervene or protest must serve a copy of that document on the Applicant.</P>
                <P>Notice is hereby given that the deadline for filing protests with regard to the applicant's request for blanket authorization, under 18 CFR part 34, of future issuances of securities and assumptions of liability, is June 28, 2011.</P>
                <P>
                    The Commission encourages electronic submission of protests and interventions in lieu of paper, using the FERC Online links at 
                    <E T="03">http://www.ferc.gov</E>
                    . To facilitate electronic service, persons with Internet access who will eFile a document and/or be listed as a contact for an intervenor must create and validate an eRegistration account using the eRegistration link. Select the eFiling link to log on and submit the intervention or protests.
                </P>
                <P>Persons unable to file electronically should submit an original and 14 copies of the intervention or protest to the Federal Energy Regulatory Commission, 888 First Street, NE., Washington, DC 20426.</P>
                <P>
                    The filings in the above-referenced proceeding are accessible in the Commission's eLibrary system by clicking on the appropriate link in the above list. They are also available for review in the Commission's Public Reference Room in Washington, DC. There is an eSubscription link on the Web site that enables subscribers to receive e-mail notification when a document is added to a subscribed docket(s). For assistance with any FERC Online service, please e-mail 
                    <E T="03">FERCOnlineSupport@ferc.gov</E>
                     or call (866) 208-3676 (toll free). For TTY, call (202) 502-8659.
                </P>
                <SIG>
                    <DATED>Dated: June 8, 2011.</DATED>
                    <NAME>Nathaniel J. Davis, Sr.,</NAME>
                    <TITLE>Deputy Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-14883 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6717-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF ENERGY</AGENCY>
                <SUBAGY>Federal Energy Regulatory Commission</SUBAGY>
                <DEPDOC>[Docket No. ER11-3736-000]</DEPDOC>
                <SUBJECT>Pocahontas Prairie Wind, LLC; Supplemental Notice That Initial Market-Based Rate Filing Includes Request for Blanket Section 204 Authorization</SUBJECT>
                <P>This is a supplemental notice in the above-referenced proceeding of Pocahontas Prairie Wind, LLC's application for market-based rate authority, with an accompanying rate tariff, noting that such application includes a request for blanket authorization, under 18 CFR Part 34, of future issuances of securities and assumptions of liability.</P>
                <P>Any person desiring to intervene or to protest should file with the Federal Energy Regulatory Commission, 888 First Street, NE., Washington, DC 20426, in accordance with Rules 211 and 214 of the Commission's Rules of Practice and Procedure (18 CFR 385.211 and 385.214). Anyone filing a motion to intervene or protest must serve a copy of that document on the Applicant.</P>
                <P>Notice is hereby given that the deadline for filing protests with regard to the applicant's request for blanket authorization, under 18 CFR part 34, of future issuances of securities and assumptions of liability, is June 28, 2011.</P>
                <P>
                    The Commission encourages electronic submission of protests and interventions in lieu of paper, using the FERC Online links at 
                    <E T="03">http://www.ferc.gov.</E>
                     To facilitate electronic service, persons with Internet access who will eFile a document and/or be listed as a contact for an intervenor must create and validate an eRegistration account using the eRegistration link. Select the eFiling link to log on and submit the intervention or protests.
                </P>
                <P>
                    Persons unable to file electronically should submit an original and 14 copies of the intervention or protest to the Federal Energy Regulatory Commission, 888 First Street, NE., Washington, DC 20426.
                    <PRTPAGE P="35211"/>
                </P>
                <P>
                    The filings in the above-referenced proceeding are accessible in the Commission's eLibrary system by clicking on the appropriate link in the above list. They are also available for review in the Commission's Public Reference Room in Washington, DC. There is an eSubscription link on the Web site that enables subscribers to receive e-mail notification when a document is added to a subscribed docket(s). For assistance with any FERC Online service, please e-mail 
                    <E T="03">FERCOnlineSupport@ferc.gov.</E>
                     or call (866) 208-3676 (toll free). For TTY, call (202) 502-8659.
                </P>
                <SIG>
                    <DATED>Dated: June 8, 2011.</DATED>
                    <NAME>Nathaniel J. Davis, Sr.,</NAME>
                    <TITLE>Deputy Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-14882 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6717-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF ENERGY</AGENCY>
                <SUBAGY>Federal Energy Regulatory Commission</SUBAGY>
                <DEPDOC>[Docket No. ER11-3727-000]</DEPDOC>
                <SUBJECT>El Segundo Energy Center LLC; Supplemental Notice that Initial Market-Based Rate Filing Includes Request for Blanket Section 204 Authorization</SUBJECT>
                <P>This is a supplemental notice in the above-referenced proceeding of El Segundo Energy Center, LLC's application for market-based rate authority, with an accompanying rate tariff, noting that such application includes a request for blanket authorization, under 18 CFR part 34, of future issuances of securities and assumptions of liability.</P>
                <P>Any person desiring to intervene or to protest should file with the Federal Energy Regulatory Commission, 888 First Street, NE., Washington, DC 20426, in accordance with Rules 211 and 214 of the Commission's Rules of Practice and Procedure (18 CFR 385.211 and 385.214). Anyone filing a motion to intervene or protest must serve a copy of that document on the Applicant.</P>
                <P>Notice is hereby given that the deadline for filing protests with regard to the applicant's request for blanket authorization, under 18 CFR part 34, of future issuances of securities and assumptions of liability, is June 28, 2011.</P>
                <P>
                    The Commission encourages electronic submission of protests and interventions in lieu of paper, using the FERC Online links at 
                    <E T="03">http://www.ferc.gov</E>
                    . To facilitate electronic service, persons with Internet access who will eFile a document and/or be listed as a contact for an intervenor must create and validate an eRegistration account using the eRegistration link. Select the eFiling link to log on and submit the intervention or protests.
                </P>
                <P>Persons unable to file electronically should submit an original and 14 copies of the intervention or protest to the Federal Energy Regulatory Commission, 888 First Street, NE., Washington, DC 20426.</P>
                <P>
                    The filings in the above-referenced proceeding are accessible in the Commission's eLibrary system by clicking on the appropriate link in the above list. They are also available for review in the Commission's Public Reference Room in Washington, DC. There is an eSubscription link on the Web site that enables subscribers to receive e-mail notification when a document is added to a subscribed docket(s). For assistance with any FERC Online service, please e-mail 
                    <E T="03">FERCOnlineSupport@ferc.gov</E>
                    . or call (866) 208-3676 (toll free). For TTY, call (202) 502-8659.
                </P>
                <SIG>
                    <DATED>Dated: June 8, 2011.</DATED>
                    <NAME>Nathaniel J. Davis, Sr.,</NAME>
                    <TITLE>Deputy Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-14886 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6717-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF ENERGY</AGENCY>
                <SUBAGY>Federal Energy Regulatory Commission</SUBAGY>
                <DEPDOC>[Docket No. ER11-3761-000]</DEPDOC>
                <SUBJECT>Palmco Power DC, LLC; Supplemental Notice THAT Initial Market-Based Rate Filing Includes Request for Blanket Section 204 Authorization</SUBJECT>
                <P>This is a supplemental notice in the above-referenced proceeding of Palmco Power DC, LLC's application for market-based rate authority, with an accompanying rate tariff, noting that such application includes a request for blanket authorization, under 18 CFR part 34, of future issuances of securities and assumptions of liability.</P>
                <P>Any person desiring to intervene or to protest should file with the Federal Energy Regulatory Commission, 888 First Street, NE., Washington, DC 20426, in accordance with Rules 211 and 214 of the Commission's Rules of Practice and Procedure (18 CFR 385.211 and 385.214). Anyone filing a motion to intervene or protest must serve a copy of that document on the Applicant.</P>
                <P>Notice is hereby given that the deadline for filing protests with regard to the applicant's request for blanket authorization, under 18 CFR part 34, of future issuances of securities and assumptions of liability, is June 29, 2011.</P>
                <P>
                    The Commission encourages electronic submission of protests and interventions in lieu of paper, using the FERC Online links at 
                    <E T="03">http://www.ferc.gov</E>
                    . To facilitate electronic service, persons with Internet access who will eFile a document and/or be listed as a contact for an intervenor must create and validate an eRegistration account using the eRegistration link. Select the eFiling link to log on and submit the intervention or protests.
                </P>
                <P>Persons unable to file electronically should submit an original and 14 copies of the intervention or protest to the Federal Energy Regulatory Commission, 888 First Street, NE., Washington, DC 20426.</P>
                <P>
                    The filings in the above-referenced proceeding are accessible in the Commission's eLibrary system by clicking on the appropriate link in the above list. They are also available for review in the Commission's Public Reference Room in Washington, DC. There is an eSubscription link on the Web site that enables subscribers to receive e-mail notification when a document is added to a subscribed docket(s). For assistance with any FERC Online service, please e-mail 
                    <E T="03">FERCOnlineSupport@ferc.gov</E>
                    . or call (866) 208-3676 (toll free). For TTY, call (202) 502-8659.
                </P>
                <SIG>
                    <DATED>Dated: June 9, 2011.</DATED>
                    <NAME>Nathaniel J. Davis, Sr.,</NAME>
                    <TITLE>Deputy Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-14889 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6717-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF ENERGY</AGENCY>
                <SUBAGY>Federal Energy Regulatory Commission</SUBAGY>
                <DEPDOC>[Docket No. ER11-3731-000]</DEPDOC>
                <SUBJECT>LWP Lessee, LLC; Supplemental Notice That Initial Market-Based Rate Filing Includes Request for Blanket Section 204 Authorization</SUBJECT>
                <P>This is a supplemental notice in the above-referenced proceeding of LWP Lessee, LLC's application for market-based rate authority, with an accompanying rate tariff, noting that such application includes a request for blanket authorization, under 18 CFR part 34, of future issuances of securities and assumptions of liability.</P>
                <P>
                    Any person desiring to intervene or to protest should file with the Federal 
                    <PRTPAGE P="35212"/>
                    Energy Regulatory Commission, 888 First Street, NE., Washington, DC 20426, in accordance with Rules 211 and 214 of the Commission's Rules of Practice and Procedure (18 CFR 385.211 and 385.214). Anyone filing a motion to intervene or protest must serve a copy of that document on the Applicant.
                </P>
                <P>Notice is hereby given that the deadline for filing protests with regard to the applicant's request for blanket authorization, under 18 CFR part 34, of future issuances of securities and assumptions of liability, is June 28, 2011.</P>
                <P>
                    The Commission encourages electronic submission of protests and interventions in lieu of paper, using the FERC Online links at 
                    <E T="03">http://www.ferc.gov</E>
                    . To facilitate electronic service, persons with Internet access who will eFile a document and/or be listed as a contact for an intervenor must create and validate an eRegistration account using the eRegistration link. Select the eFiling link to log on and submit the intervention or protests.
                </P>
                <P>Persons unable to file electronically should submit an original and 14 copies of the intervention or protest to the Federal Energy Regulatory Commission, 888 First Street, NE., Washington, DC 20426.</P>
                <P>
                    The filings in the above-referenced proceeding are accessible in the Commission's eLibrary system by clicking on the appropriate link in the above list. They are also available for review in the Commission's Public Reference Room in Washington, DC. There is an eSubscription link on the Web site that enables subscribers to receive e-mail notification when a document is added to a subscribed docket(s). For assistance with any FERC Online service, please e-mail 
                    <E T="03">FERCOnlineSupport@ferc.gov</E>
                     or call (866) 208-3676 (toll free). For TTY, call (202) 502-8659.
                </P>
                <SIG>
                    <DATED>Dated: June 8, 2011.</DATED>
                    <NAME>Nathaniel J. Davis, Sr.,</NAME>
                    <TITLE>Deputy Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-14887 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6717-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF ENERGY</AGENCY>
                <SUBAGY>Federal Energy Regulatory Commission</SUBAGY>
                <DEPDOC>[Project No. 2056-052]</DEPDOC>
                <SUBJECT>Northern States Power Company (Xcel Energy); Notice of Application To Amend License and Accepted for Filing, Soliciting Comments, Motions To Intervene, and Protests</SUBJECT>
                <P>Take notice that the following hydroelectric application has been filed with the Commission and is available for public inspection:</P>
                <P>
                    a. 
                    <E T="03">Type of Application:</E>
                     Amendment to License.
                </P>
                <P>
                    b. 
                    <E T="03">Project No:</E>
                     2056-052.
                </P>
                <P>
                    c. 
                    <E T="03">Date Filed:</E>
                     May 25, 2011.
                </P>
                <P>
                    d. 
                    <E T="03">Applicant:</E>
                     Northern States Power Company (Xcel Energy).
                </P>
                <P>
                    e. 
                    <E T="03">Name of Project:</E>
                     St. Anthony Falls Hydroelectric Project.
                </P>
                <P>
                    f. 
                    <E T="03">Location:</E>
                     On the Mississippi River in the city of Minneapolis in Hennepin County, Minnesota.
                </P>
                <P>
                    g. 
                    <E T="03">Filed Pursuant to:</E>
                     Federal Power Act, 16 U.S.C. 791(a)-825(r).
                </P>
                <P>
                    h. 
                    <E T="03">Applicant Contact:</E>
                     William P. Zawacki, Director of Hydro Plants, Xcel Energy, 1414 W. Hamilton Ave., P.O. Box 8, Eau Claire, WI 54702-0008; and Matthew J. Miller, Hydro Licensing Specialist, Xcel Energy, 1414 W. Hamilton Ave., P.O. Box 8, Eau Claire, WI 54702-0008.
                </P>
                <P>
                    i. 
                    <E T="03">FERC Contact:</E>
                     Kim Carter at (202) 502-6486; 
                    <E T="03">Kim.Carter@ferc.gov</E>
                    .
                </P>
                <P>
                    j. Deadline for filing comments, motions to intervene, and protests, is 30 days from the issuance date of this notice. All documents may be filed electronically via the Internet. 
                    <E T="03">See,</E>
                     18 CFR 385.2001(a)(1)(iii) and the instructions on the Commission's Web site at 
                    <E T="03">http://www.ferc.gov/docs-filing/efiling.asp</E>
                    . If unable to be filed electronically, documents may be paper-filed. To paper-file, an original and seven copies should be mailed to: Secretary, Federal Energy Regulatory Commission, 888 First Street, NE., Washington, DC 20426. Commenters can submit brief comments up to 6,000 characters, without prior registration, using the eComment system at 
                    <E T="03">http://www.ferc.gov/docs-filing/ecomment.asp</E>
                    . You must include your name and contact information at the end of your comments.
                </P>
                <P>Please include the project number (P-2056-052) on any comments, motions, or recommendations filed.</P>
                <P>
                    k. 
                    <E T="03">Description of Request:</E>
                     The licensee proposes to amend the license for the St. Anthony Falls Hydroelectric Project to reflect the rehabilitated units. The authorized installed capacity would increase by 1,845.25 kW [from 12,400 kW to 14,245.25 kW] and the maximum hydraulic capacity would increase by 341 cubic feet per second (cfs) [from 4,025 to 4,366 cfs].
                </P>
                <P>
                    l. 
                    <E T="03">Locations of the Application:</E>
                     A copy of the application is available for inspection and reproduction at the Commission's Public Reference Room, located at 888 First Street, NE., Room 2A, Washington, DC 20426, or by calling (202) 502-8371. This filing may also be viewed on the Commission's Web site at 
                    <E T="03">http://www.ferc.gov/docs-filing/elibrary.asp</E>
                    . Enter the docket number excluding the last three digits in the docket number field to access the document. You may also register online at 
                    <E T="03">http://www.ferc.gov/docs-filing/esubscription.asp</E>
                     to be notified via e-mail of new filings and issuances related to this or other pending projects. For assistance, call 1-866-208-3676 or e-mail 
                    <E T="03">FERCOnlineSupport@ferc.gov,</E>
                     for TTY, call (202) 502-8659. A copy is also available for inspection and reproduction at the address in item (h) above.
                </P>
                <P>m. Individuals desiring to be included on the Commission's mailing list should so indicate by writing to the Secretary of the Commission.</P>
                <P>
                    n. 
                    <E T="03">Comments, Protests, or Motions to Intervene:</E>
                     Anyone may submit comments, a protest, or a motion to intervene in accordance with the requirements of Rules of Practice and Procedure, 18 CFR 385.210, .211, .214. In determining the appropriate action to take, the Commission will consider all protests or other comments filed, but only those who file a motion to intervene in accordance with the Commission's Rules may become a party to the proceeding. Any comments, protests, or motions to intervene must be received on or before the specified comment date for the particular application.
                </P>
                <P>
                    o. 
                    <E T="03">Filing and Service of Responsive Documents:</E>
                     Any filing must (1) Bear in all capital letters the title “COMMENTS”, “PROTEST”, or “MOTION TO INTERVENE” as applicable; (2) set forth in the heading the name of the applicant and the project number of the application to which the filing responds; (3) furnish the name, address, and telephone number of the person protesting or intervening; and (4) otherwise comply with the requirements of 18 CFR 385.2001 through 385.2005. All comments, motions to intervene, or protests must set forth their evidentiary basis and otherwise comply with the requirements of 18 CFR 4.34(b). All comments, motions to intervene, or protests should relate to project works 
                    <PRTPAGE P="35213"/>
                    which are the subject of the license surrender. Agencies may obtain copies of the application directly from the applicant. A copy of any protest or motion to intervene must be served upon each representative of the applicant specified in the particular application. If an intervener files comments or documents with the Commission relating to the merits of an issue that may affect the responsibilities of a particular resource agency, they must also serve a copy of the document on that resource agency. A copy of all other filings in reference to this application must be accompanied by proof of service on all persons listed in the service list prepared by the Commission in this proceeding, in accordance with 18 CFR 4.34(b) and 385.2010.
                </P>
                <SIG>
                    <DATED>Dated: June 10, 2011.</DATED>
                    <NAME>Kimberly D. Bose,</NAME>
                    <TITLE>Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-14966 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6717-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF ENERGY</AGENCY>
                <SUBAGY>Federal Energy Regulatory Commission</SUBAGY>
                <DEPDOC>[Project No. 2984-042]</DEPDOC>
                <SUBJECT>S. D. Warren Company; Notice of Supplement to the License Application And Soliciting Comments</SUBJECT>
                <P>Take notice that the following supplement to the license application has been filed with the Commission and is available for public inspection.</P>
                <P>
                    a. 
                    <E T="03">Type of Filing:</E>
                     Supplement to the licensing application for the Eel Weir Project.
                </P>
                <P>
                    b. 
                    <E T="03">Project No.:</E>
                     P-2984-042.
                </P>
                <P>
                    c. 
                    <E T="03">Date Filed:</E>
                     June 6, 2011 (The version of the supplement filed on May 26, 2011, was superseded by the revised version filed on June 6, 2011).
                </P>
                <P>
                    d. 
                    <E T="03">Applicant:</E>
                     S. D. Warren Company.
                </P>
                <P>
                    e. 
                    <E T="03">Location:</E>
                     The existing project is located at the outlet of Sebago Lake on the Presumpscot River, in Cumberland County, Maine. The project does not affect federal lands.
                </P>
                <P>
                    g. 
                    <E T="03">Filed Pursuant to:</E>
                     Federal Power Act 16 U.S.C. 791(a)-825(r).
                </P>
                <P>
                    h. 
                    <E T="03">Applicant Contact:</E>
                     Nancy J. Skancke, GKRSE, 1500 K Street, NW., Suite 330, Washington, DC 20005; (202) 408-5400.
                </P>
                <P>
                    i. 
                    <E T="03">FERC Contact:</E>
                     Tom Dean (202) 502-6041.
                </P>
                <P>
                    j. 
                    <E T="03">Deadline for filing comments on the supplement:</E>
                     30 days from the issuance date of this notice. All reply comments must be filed with the Commission within 45 days from the date of this notice.
                </P>
                <P>
                    All comments and reply comments may be filed electronically via the Internet. See 18 CFR 385.2001(a)(1)(iii) and the instructions on the Commission's Web site 
                    <E T="03">http://www.ferc.gov/docs-filing/efiling.asp</E>
                    . Commenters can submit brief comments up to 6,000 characters, without prior registration, using the eComment system at 
                    <E T="03">http://www.ferc.gov/docs-filing/ecomment.asp</E>
                    . You must include your name and contact information at the end of your comments. For assistance, please contact FERC Online Support at 
                    <E T="03">FERCOnlineSupport@ferc.gov</E>
                     or toll free at 1-866-208-3676, or for TTY, (202) 502-8659. Although the Commission strongly encourages electronic filing, documents may also be paper-filed. To paper-file, mail an original and seven copies to: Kimberly D. Bose, Secretary, Federal Energy Regulatory Commission, 888 First Street, NE., Washington, DC 20426.
                </P>
                <P>The Commission's Rules of Practice require all intervenors filing documents with the Commission to serve a copy of that document on each person on the official service list for the project. Further, if an intervenor files comments or documents with the Commission relating to the merits of an issue that may affect the responsibilities of a particular resource agency, they must also serve a copy of the document on that resource agency.</P>
                <P>
                    k. 
                    <E T="03">Description of the supplement:</E>
                     S. D. Warren (Warren) requests the Commission adopt modifications to the existing Sebago Lake Level Management Plan (LLMP) that would include changing project operation from requiring seasonal target lake water surface elevations to a seasonal flow-based regime. Under the modified LLMP, Warren would first direct flows into the bypassed reach as required by the license, and would then direct flows that are above the required minimum bypassed reach flow into the power canal. Warren also requests confirmation that no further wetland studies at Sebago Lake are necessary, that no shoreline permitting program is needed under a new license, and that no new shallow boat launch near the project facilities is necessary.
                </P>
                <P>
                    l. A copy of the supplement is available for review at the Commission in the Public Reference Room or may be viewed on the Commission's Web site at 
                    <E T="03">http://www.ferc.gov</E>
                     using the “eLibrary” link. Enter the docket number excluding the last three digits in the docket number field to access the document. For assistance, contact FERC Online Support.
                </P>
                <P>
                    m. You may also register online at 
                    <E T="03">http://www.ferc.gov/docs-filing/esubscription.asp</E>
                     to be notified via e-mail of new filings and issuances related to this or other pending projects. For assistance, contact FERC Online Support
                </P>
                <SIG>
                    <DATED>Dated: June 9, 2011.</DATED>
                    <NAME>Kimberly D. Bose,</NAME>
                    <TITLE>Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-14898 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6717-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF ENERGY</AGENCY>
                <SUBAGY>Federal Energy Regulatory Commission</SUBAGY>
                <DEPDOC> [Project No. 14115-000]</DEPDOC>
                <SUBJECT> AJT Mining Properties, Inc.; Notice of Preliminary Permit Application Accepted for Filing and Soliciting Comments, Motions To Intervene, and Competing Applications</SUBJECT>
                <P>On March 21, 2011, AJT Mining Properties, Inc., filed an application for a preliminary permit, pursuant to section 4(f) of the Federal Power Act (FPA), proposing to study the feasibility of the Yeldagalga Creek Hydroelectric Project (project) to be located on the Yeldagalga Creek, near Haines, in the boroughs of Haines and Juneau, Alaska. The project would be located on lands within the Tongass National Forest, which is owned and managed by the U.S.D.A. Forest Service. The sole purpose of a preliminary permit, if issued, is to grant the permit holder priority to file a license application during the permit term. A preliminary permit does not authorize the permit holder to perform any land-disturbing activities or otherwise enter upon lands or waters owned by others without the owners' express permission.</P>
                <P>The proposed project would consist of the following: (1) A 10-foot-high, 50-foot-wide diversion dam; (2) an overflow spillway; (3) a 42-inch-diameter, 2,500-foot-long penstock; (4) a powerhouse containing a generating unit rated at 8 megawatts; (5) a short tailrace; (6) living quarters for personnel; (7) a dock and barge landing facility; (8) a 34.5-kilovolt, 16-mile-long overhead transmission line; and (9) appurtenant facilities. The estimated annual generation of the project would be 31,000 megawatt-hours.</P>
                <P>
                    <E T="03">Applicant Contact:</E>
                     Mr. Scott Willis, AJT Mining Properties, Inc., 5601 Tonsgard Court, Juneau, Alaska 99801; 
                    <E T="03">phone:</E>
                     (907) 463-6396.
                </P>
                <P>
                    <E T="03">FERC Contact:</E>
                     Kelly Wolcott; 
                    <E T="03">phone:</E>
                     (202) 502-6480.
                    <PRTPAGE P="35214"/>
                </P>
                <P>
                    Deadline for filing comments, motions to intervene, competing applications (without notices of intent), or notices of intent to file competing applications: 60 days from the issuance of this notice. Competing applications and notices of intent must meet the requirements of 18 CFR 4.36. Comments, motions to intervene, notices of intent, and competing applications may be filed electronically via the Internet. See 18 CFR 385.2001(a)(1)(iii) and the instructions on the Commission's Web site 
                    <E T="03">http://www.ferc.gov/docs-filing/efiling.asp</E>
                    . Commenters can submit brief comments up to 6,000 characters, without prior registration, using the eComment system at 
                    <E T="03">http://www.ferc.gov/docs-filing/ecomment.asp</E>
                    . You must include your name and contact information at the end of your comments. For assistance, please contact FERC Online Support at 
                    <E T="03">FERCOnlineSupport@ferc.gov</E>
                     or toll free at 1-866-208-3676, or for TTY, (202) 502-8659. Although the Commission strongly encourages electronic filing, documents may also be paper-filed. To paper-file, mail an original and seven copies to: Kimberly D. Bose, Secretary, Federal Energy Regulatory Commission, 888 First Street, NE., Washington, DC 20426.
                </P>
                <P>
                    More information about this project, including a copy of the application, can be viewed or printed on the “eLibrary” link of Commission's Web site at 
                    <E T="03">http://www.ferc.gov/docs-filing/elibrary.asp</E>
                    . Enter the docket number (P-14115-000) in the docket number field to access the document. For assistance, contact FERC Online Support.
                </P>
                <SIG>
                    <DATED>Dated: June 10, 2011.</DATED>
                    <NAME>Kimberly D. Bose,</NAME>
                    <TITLE>Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-14961 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6717-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF ENERGY</AGENCY>
                <SUBAGY>Federal Energy Regulatory Commission</SUBAGY>
                <SUBJECT>Notice of Staff Attendance at Southwest Power Pool Board of Directors Meetings</SUBJECT>
                <P>
                    The Federal Energy Regulatory Commission hereby gives notice that members of its staff may attend the meetings of the 
                    <E T="03">Southwest Power Pool, Inc.</E>
                     (SPP) Board of Directors, as noted below. Their attendance is part of the Commission's ongoing outreach efforts.
                </P>
                <P>All meetings will be held at: The Marriott Las Colinas, 223 West Las Colinas Boulevard, Irving, TX 75039.</P>
                <P>The Board meeting is June 13-14 (1:30 p.m.-5 p.m. and 8 a.m.-5 p.m.).</P>
                <P>The discussions may address matters at issue in the following proceedings:</P>
                <FP SOURCE="FP-2">
                    Docket No. ER06-451, 
                    <E T="03">Southwest Power Pool, Inc.</E>
                </FP>
                <FP SOURCE="FP-2">
                    Docket No. ER08-1419, 
                    <E T="03">Southwest Power Pool, Inc.</E>
                </FP>
                <FP SOURCE="FP-2">
                    Docket No. ER09-659, 
                    <E T="03">Southwest Power Pool, Inc.</E>
                </FP>
                <FP SOURCE="FP-2">
                    Docket No. ER09-1050, 
                    <E T="03">Southwest Power Pool, Inc.</E>
                </FP>
                <FP SOURCE="FP-2">
                    Docket No. ER10-696, 
                    <E T="03">Southwest Power Pool, Inc.</E>
                </FP>
                <FP SOURCE="FP-2">
                    Docket No. ER10-941, 
                    <E T="03">Southwest Power Pool, Inc.</E>
                </FP>
                <FP SOURCE="FP-2">
                    Docket No. ER10-1069, 
                    <E T="03">Southwest Power Pool, Inc.</E>
                </FP>
                <FP SOURCE="FP-2">
                    Docket No. ER09-1254, 
                    <E T="03">Southwest Power Pool, Inc.</E>
                </FP>
                <FP SOURCE="FP-2">
                    Docket No. ER10-1269, 
                    <E T="03">Southwest Power Pool, Inc.</E>
                </FP>
                <FP SOURCE="FP-2">
                    Docket No. ER10-1697, 
                    <E T="03">Southwest Power Pool, Inc.</E>
                </FP>
                <FP SOURCE="FP-2">
                    Docket No. ER10-2244, 
                    <E T="03">Southwest Power Pool, Inc.</E>
                </FP>
                <FP SOURCE="FP-2">
                    Docket No. ER11-13, 
                    <E T="03">Southwest Power Pool, Inc.</E>
                </FP>
                <FP SOURCE="FP-2">
                    Docket No. ER11-2428, 
                    <E T="03">Southwest Power Pool, Inc.</E>
                </FP>
                <FP SOURCE="FP-2">
                    Docket No. ER11-2528, 
                    <E T="03">Southwest Power Pool, Inc.</E>
                </FP>
                <FP SOURCE="FP-2">
                    Docket No. ER11-2677, 
                    <E T="03">Southwest Power Pool, Inc.</E>
                </FP>
                <FP SOURCE="FP-2">
                    Docket No. ER11-2711, 
                    <E T="03">Southwest Power Pool, Inc.</E>
                </FP>
                <FP SOURCE="FP-2">
                    Docket No. ER11-2719, 
                    <E T="03">Southwest Power Pool, Inc.</E>
                </FP>
                <FP SOURCE="FP-2">
                    Docket No. ER11-2758, 
                    <E T="03">Southwest Power Pool, Inc.</E>
                </FP>
                <FP SOURCE="FP-2">
                    Docket No. ER11-2781, 
                    <E T="03">Southwest Power Pool, Inc.</E>
                </FP>
                <FP SOURCE="FP-2">
                    Docket No. ER11-2787, 
                    <E T="03">Southwest Power Pool, Inc.</E>
                </FP>
                <FP SOURCE="FP-2">
                    Docket No. ER11-2861, 
                    <E T="03">Southwest Power Pool, Inc.</E>
                </FP>
                <FP SOURCE="FP-2">
                    Docket No. ER11-3230, 
                    <E T="03">Southwest Power Pool, Inc.</E>
                </FP>
                <FP SOURCE="FP-2">
                    Docket No. ER11-3243, 
                    <E T="03">Southwest Power Pool, Inc.</E>
                </FP>
                <FP SOURCE="FP-2">
                    Docket No. ER11-3452, 
                    <E T="03">Southwest Power Pool, Inc.</E>
                </FP>
                <FP SOURCE="FP-2">
                    Docket No. ER11-3453, 
                    <E T="03">Southwest Power Pool, Inc.</E>
                </FP>
                <FP SOURCE="FP-2">
                    Docket No. ER11-3494, 
                    <E T="03">Southwest Power Pool, Inc.</E>
                </FP>
                <FP SOURCE="FP-2">
                    Docket No. ER11-3501, 
                    <E T="03">Southwest Power Pool, Inc.</E>
                </FP>
                <FP SOURCE="FP-2">
                    Docket No. ER11-3504, 
                    <E T="03">Southwest Power Pool, Inc.</E>
                </FP>
                <FP SOURCE="FP-2">
                    Docket No. ER11-3509, 
                    <E T="03">Southwest Power Pool, Inc.</E>
                </FP>
                <FP SOURCE="FP-2">
                    Docket No. ER11-3511, 
                    <E T="03">Southwest Power Pool, Inc.</E>
                </FP>
                <FP SOURCE="FP-2">
                    Docket No. ER11-3489, 
                    <E T="03">Southwest Power Pool, Inc.</E>
                </FP>
                <FP SOURCE="FP-2">
                    Docket No. ER11-3474, 
                    <E T="03">Southwest Power Pool, Inc.</E>
                </FP>
                <FP SOURCE="FP-2">
                    Docket No. ER11-3478, 
                    <E T="03">Southwest Power Pool, Inc.</E>
                </FP>
                <FP SOURCE="FP-2">
                    Docket No. ER11-3666, 
                    <E T="03">Southwest Power Pool, Inc.</E>
                </FP>
                <FP SOURCE="FP-2">
                    Docket No. ER11-3455, 
                    <E T="03">Southwest Power Pool, Inc.</E>
                </FP>
                <FP SOURCE="FP-2">
                    Docket No. ER11-3622, 
                    <E T="03">Southwest Power Pool, Inc.</E>
                </FP>
                <FP SOURCE="FP-2">
                    Docket No. ER11-3627, 
                    <E T="03">Southwest Power Pool, Inc.</E>
                </FP>
                <FP SOURCE="FP-2">
                    Docket No. ER11-3650, 
                    <E T="03">Southwest Power Pool, Inc.</E>
                </FP>
                <FP SOURCE="FP-2">
                    Docket No. ER11-3299, 
                    <E T="03">Southwest Power Pool, Inc.</E>
                </FP>
                <FP SOURCE="FP-2">
                    Docket No. ER11-3331, 
                    <E T="03">Southwest Power Pool, Inc.</E>
                </FP>
                <FP SOURCE="FP-2">
                    Docket No. ER11-3450, 
                    <E T="03">Southwest Power Pool, Inc.</E>
                </FP>
                <FP SOURCE="FP-2">
                    Docket No. ER11-3451, 
                    <E T="03">Southwest Power Pool, Inc.</E>
                </FP>
                <FP SOURCE="FP-2">
                    Docket No. ER11-3490, 
                    <E T="03">Southwest Power Pool, Inc.</E>
                </FP>
                <FP SOURCE="FP-2">
                    Docket No. ER11-3503, 
                    <E T="03">Southwest Power Pool, Inc.</E>
                </FP>
                <FP SOURCE="FP-2">
                    Docket No. ER11-3599, 
                    <E T="03">Southwest Power Pool, Inc.</E>
                </FP>
                <FP SOURCE="FP-2">
                    Docket No. ER11-3601, 
                    <E T="03">Southwest Power Pool, Inc.</E>
                </FP>
                <FP SOURCE="FP-2">
                    Docket No. EL11-34, 
                    <E T="03">Midwest Independent System Transmission Operator, Inc.</E>
                </FP>
                <P>These meetings are open to the public.</P>
                <P>
                    For more information, contact John Rogers, Office of Energy Market Regulation, Federal Energy Regulatory Commission at (202)-502-8564 or 
                    <E T="03">john.rogers@ferc.gov.</E>
                </P>
                <SIG>
                    <DATED>Dated: June 9, 2011.</DATED>
                    <NAME>Kimberly D. Bose,</NAME>
                    <TITLE>Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-14901 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6717-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">ENVIRONMENTAL PROTECTION AGENCY</AGENCY>
                <DEPDOC>[FRL-9319-9]</DEPDOC>
                <SUBJECT>Notice of Determination of Adequacy of Ohio's Research, Development and Demonstration (RD&amp;D) Permit Provisions for Municipal Solid Waste Landfills</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>
                        On March 22, 2004, the U.S. EPA issued final regulations allowing research, development and demonstration (RD&amp;D) permits to be issued to certain municipal solid waste landfills by approved states. On March 3, 2011, Ohio submitted an application to the U.S. EPA Region 5 seeking Federal approval of its RD&amp;D. Ohio's 
                        <PRTPAGE P="35215"/>
                        RD&amp;D requirements allow the State to issue RD&amp;D permits to owners and operators of MSWLF units in accordance with state law. Subject to public review and comment, this notice approves Ohio's RD&amp;D permit requirements.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>This determination of RD&amp;D program adequacy for Ohio will become effective August 15, 2011 unless adverse comments are received on or before August 15, 2011. If adverse comments are received, the U.S. EPA will review those comments and publish another FR document responding to those comments and either affirming or revising the U.S. EPA's initial decision.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Written comments should be sent to Rebecca Geyer, Land and Chemicals Division (Mail Code LM-8J), U.S. EPA Region 5, 77 West Jackson Boulevard, Chicago, Illinois 60604, 
                        <E T="03">telephone:</E>
                         (312) 353-8314. Comments may also be submitted electronically to 
                        <E T="03">geyer.rebecca@epa.gov</E>
                         or by facsimile at (312) 582-5122. You may examine copies of Ohio's application and relevant portions of Ohio's regulations during normal business hours at U.S. EPA Region 5.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Rebecca Geyer, Land and Chemicals Division (Mail Code LM-8J), U.S. EPA Region 5, 77 West Jackson Boulevard, Chicago, Illinois 60604, 
                        <E T="03">telephone:</E>
                         (312) 353-8314, 
                        <E T="03">geyer.rebecca@epa.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">A. Background</HD>
                <P>On March 22, 2004, EPA issued a final rule amending the municipal solid waste landfill criteria in 40 CFR Part 258 to allow for research, development and demonstration permits (69 FR 13242). This rule allows for variances from specified criteria for a limited period of time, to be implemented through state-issued RD&amp;D permits. RD&amp;D permits are available only in states with approved MSWLF permit programs that have been modified to incorporate RD&amp;D permit authority. While States are not required to adopt this new provision, those States that are interested in providing RD&amp;D permits to owners and operators of MSWLFs must seek approval from EPA before issuing such permits. Approval procedures for new provisions of 40 CFR Part 258 are outlined in 40 CFR Part 239.12.</P>
                <P>Ohio's MSWLF permit program was approved on June 13, 1994 (59 FR 112). On March 3, 2011, Ohio applied for approval of its RD&amp;D permit provisions. Ohio submitted its amended laws under OAC 3745-27-80 to 3745-27-89 for review.</P>
                <HD SOURCE="HD1">B. Decision</HD>
                <P>After a thorough review, U.S. EPA Region 5 determined that Ohio's RD&amp;D permit provisions as defined under OAC 3745-27-80 to 3745-27-89 are adequate to ensure compliance with the Federal criteria as defined at 40 CFR Part 258.4.</P>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P>This action is issued under the authority of section 2002, 4005 and 4010(c) of the Solid Waste Disposal Act, as amended, 42 U.S.C. 6912, 6945 and 6949(a).</P>
                </AUTH>
                <SIG>
                    <DATED>Dated: June 3, 2011.</DATED>
                    <NAME>Susan Hedman,</NAME>
                    <TITLE>Regional Administrator, U.S. EPA Region 5.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-15001 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6560-50-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">ENVIRONMENTAL PROTECTION AGENCY</AGENCY>
                <DEPDOC>[EPA-HQ-OW-2010-0464; FRL-9318-8]</DEPDOC>
                <SUBJECT>Notice of EPA Workshop on Sanitary Sewer Overflows and Peak Wet Weather Discharges</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 Office of Wastewater Management of the U.S. Environmental Protection Agency is holding a workshop to solicit the views of stakeholders concerning a number of issues. These include views on how the National Pollutant Discharge Elimination System (NPDES) regulations should apply to municipal sanitary sewer collection systems, sanitary sewer overflows (SSOs), and peak wet weather discharges at publicly owned treatment works (POTW) treatment plants. EPA will also seek views on the 2005 draft Peak Flows Policy. The workshop will include a facilitated discussion with representatives of organizations that represent POTWs, state NPDES permitting authorities, and non-for-profit environmental groups. EPA invites other interested members of the public to observe the workshop and to offer verbal comments at designated times during the workshop or to submit written comments to the Agency.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        The workshop will be held on July 14, from 8 a.m. to 5:15 p.m. and on July 15, from 8 a.m. to 12:30 p.m. If you plan to participate in the workshop as an observer, EPA requests that you pre-register by July 6, 2011 at 
                        <E T="03">http://www.epa.gov/npdes/sso</E>
                        .
                    </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>The workshop will be held at the Ronald Reagan Building and International Trade Center, Horizon Ballroom, located in Washington, DC at 1300 Pennsylvania Avenue, NW.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        For further information about this notice, contact Greg Schaner, EPA Headquarters, Office of Water, Office of Wastewater Management at tel.: 202-564-0721 or e-mail: 
                        <E T="03">schaner.greg@epa.gov</E>
                        .
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Background</HD>
                <P>Properly designed, operated, and maintained sanitary sewer systems are meant to collect and transport all of the sewage that flows into them to a publicly owned treatment works (POTW). However, occasional discharges of raw sewage from municipal sanitary sewers occur in almost every system. These types of discharges are called sanitary sewer overflows (SSOs). SSOs have a variety of causes, including but not limited to blockages, line breaks, sewer defects that allow storm water and groundwater to overload the system, lapses in sewer system operation and maintenance, power failures, inadequate sewer design and vandalism. EPA estimates that there are at least 23,000-75,000 SSOs per year (not including sewage backups into buildings). The untreated sewage from these overflows can contaminate our waters, causing serious water quality problems. It can also back-up into basements, causing property damage and threatening public health.</P>
                <P>Additionally, aging sewer line infrastructure in many communities allows rain and snow melt to enter sanitary sewer systems and cause excess flow at the treatment plant. During significant wet weather events it is possible for influent flows to exceed the treatment capacity of existing secondary treatment units. Known as “peak flows,” these wet weather flows are sometimes diverted around secondary treatment units and then either recombined with flows from the secondary treatment units or discharged directly into waterways from the treatment plant in order to prevent any damage to the treatment facility. Operators of wastewater treatment plants must manage these high flows to ensure continued operation of the treatment process.</P>
                <P>
                    For additional background on SSOs and peak wet weather discharges, refer to the “background” section of EPA's notice announcing the 2010 Listening Sessions at 75 FR 30395 (June 1, 2010) and to information included on EPA's Web site at 
                    <E T="03">http://cfpub.epa.gov/npdes/home.cfm?program_id=4</E>
                    .
                </P>
                <HD SOURCE="HD1">II. 2010 Listening Sessions</HD>
                <P>
                    In 2010, EPA held several listening sessions to obtain information from the 
                    <PRTPAGE P="35216"/>
                    public regarding the potential modification to the NPDES regulations to address SSOs and other types of peak wet weather discharges. 
                    <E T="03">See</E>
                     75 FR 30395 (June 1, 2010). Participants in the sessions offered both verbal and written comments. The Agency received 235 written comments to the docket. You can view these comments at 
                    <E T="03">http://www.regulations.gov,</E>
                     under Docket ID # EPA-HQ-OW-2010-0464.
                </P>
                <HD SOURCE="HD1">III. Purpose of SSO/Peak Wet Weather Flow Workshop</HD>
                <P>
                    As a follow-up to the 2010 Listening Sessions, EPA will hold a 1
                    <FR>1/2</FR>
                     day workshop on July 14-15, 2011 in Washington, DC. The purpose of this workshop is to provide interested parties and other members of the public an opportunity to elaborate on their recommendations to the Agency with respect to actions that could be taken to strengthen the permitting program's approach to regulating SSOs and peak wet weather discharges. EPA has invited several stakeholder groups representing non-governmental interests, POTWs and collection systems, and state permitting authorities to recommend members of their community to participate in the workshop as experts. In addition to eliciting the views of the representative groups, EPA will also invite comments during the meeting from any member of the public who wishes to observe and participate at the workshop.
                </P>
                <P>
                    The specific issues that EPA is seeking feedback on have significant overlap with those highlighted for the 2010 listening sessions. 
                    <E T="03">See</E>
                     75 FR 30399-30401 (June 1, 2010). For example, EPA will be interested in the views of the representatives and observers on whether and to what extent specific NPDES permit requirements should be developed to address the following:
                </P>
                <P>• How SSOs are reported to EPA or state permitting authorities and documented in POTW records, and how and when the public is notified of overflows;</P>
                <P>• What components of POTW programs for capacity, management, operations, and maintenance (CMOM) should be made part of standard NPDES permit conditions;</P>
                <P>• Whether to require NPDES permits for “municipal satellite collection systems”, and what types of requirements should such permits include; and</P>
                <P>• Are there any circumstances under which an SSO may be authorized under an NPDES permit.</P>
                <P>
                    EPA will also seek input on the disposition of the 2005 draft Peak Flows Policy (
                    <E T="03">see http://cfpub.epa.gov/npdes/wetweather.cfm</E>
                    ) that pertains to wet weather diversions at POTW treatment plants.
                </P>
                <P>It is not EPA's objective during the workshop to establish consensus among the parties or to obtain a collective set of recommendations. Rather, it is EPA's intention to obtain individual input from interested parties so that the Agency can better understand the differences and commonalities among the individual recommendations. In this regard, EPA has determined that this workshop is not subject to the requirements of the Federal Advisory Committee Act. 5 U.S.C. Appendix 2.</P>
                <HD SOURCE="HD1">IV. Participation in the Workshop</HD>
                <P>
                    Members of the public are welcome to participate as observers in the workshop. The agenda will be structured to invite specific verbal comments from observers on key issues. If you plan to participate as an observer at the workshop, in order that EPA may properly anticipate the correct number of people, EPA requests that you pre-register by July 6, 2011 at 
                    <E T="03">http://www.epa.gov/npdes/sso</E>
                    .
                </P>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P>
                        Clean Water Act, 33 U.S.C. 1251 
                        <E T="03">et seq.</E>
                    </P>
                </AUTH>
                <SIG>
                    <DATED>Dated: June 7, 2011.</DATED>
                    <NAME>James A. Hanlon,</NAME>
                    <TITLE>Director, Office of Wastewater Management.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-15003 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6560-50-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">ENVIRONMENTAL PROTECTION AGENCY</AGENCY>
                <DEPDOC>[FRL-9320-1]</DEPDOC>
                <SUBJECT>Science Advisory Board Staff Office Notification of a Public Teleconference of the Chartered Science Advisory Board</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 EPA Science Advisory Board (SAB) Staff Office announces a public teleconference of the chartered SAB on July 5, 2011 to conduct a quality review of a draft SAB report, 
                        <E T="03">Review of EPA's Draft Hydraulic Fracturing Study Plan (Quality Review Draft</E>
                        ).
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The public teleconference will be held on July 5, 2011 from 11 a.m. to 3 p.m. (Eastern Daylight Time).</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>The public teleconference will be conducted by telephone only.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Any member of the public wishing to obtain general information concerning the public teleconference may contact Dr. Angela Nugent, Designated Federal Officer (DFO). Dr. Nugent may be contacted at the EPA Science Advisory Board (1400R), U.S. Environmental Protection Agency, 1200 Pennsylvania Avenue, NW., Washington, DC 20460; or by telephone/voice mail at (202) 564-2188; fax at (202) 565-2098; or e-mail at 
                        <E T="03">nugent.angela@epa.gov.</E>
                         General information concerning the EPA Science Advisory Board can be found on the EPA Web site at 
                        <E T="03">http://www.epa.gov/sab</E>
                        .
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    The SAB was established pursuant to the Environmental Research, Development, and Demonstration Authorization Act (ERDAA), codified at 42 U.S.C. 4365, to provide independent scientific and technical advice to the EPA Administrator on the technical basis for Agency positions and regulations. The SAB is a Federal Advisory Committee chartered under the Federal Advisory Committee Act (FACA), 5 U.S.C., App. 2. Pursuant to FACA and EPA policy, notice is hereby given that the SAB will hold a public teleconference to conduct a quality review of a draft report entitled 
                    <E T="03">Review of EPA's Draft Hydraulic Fracturing Study Plan</E>
                    . The SAB will comply with the provisions of FACA and all appropriate SAB Staff Office procedural policies.
                </P>
                <P>
                    <E T="03">Background:</E>
                     EPA's Office of Research and Development (ORD) is initiating a study of the potential environmental and human health implications of hydraulic fracturing with special emphasis on the relationship between hydraulic fracturing and drinking water resources. ORD has requested that the SAB review its draft Study Plan. The SAB Hydraulic Fracturing Study Plan Review Panel has developed the draft report that will undergo quality review by the chartered SAB.
                </P>
                <P>
                    Background information about the SAB advisory activity, including its meetings and teleconferences, can be found on the SAB Web site at 
                    <E T="03">http://yosemite.epa.gov/sab/sabproduct.nsf/fedrgstr_activites/HFSP?OpenDocument</E>
                    .
                </P>
                <P>
                    <E T="03">Availability of Meeting Materials:</E>
                     The agenda and other materials in support of the teleconference will be placed on the SAB Web site at 
                    <E T="03">http://www.epa.gov/sab</E>
                     in advance of the teleconference.
                </P>
                <P>
                    <E T="03">Procedures for Providing Public Input:</E>
                     Public comment for consideration by EPA's federal advisory committees and panels has a different purpose from public comment provided to EPA program offices. Therefore, the process for submitting comments to a federal advisory committee is different from the process used to submit comments to an EPA program office.
                    <PRTPAGE P="35217"/>
                </P>
                <P>Federal advisory committees and panels, including scientific advisory committees, provide independent advice to EPA. Members of the public can submit comments for a federal advisory committee to consider as it develops advice for EPA. Input from the public to the SAB will have the most impact if it provides specific scientific or technical information or analysis for SAB panels to consider or if it relates to the clarity or accuracy of the technical information. Members of the public wishing to provide comment should contact the Designated Federal Officer directly. </P>
                <P>
                    <E T="03">Oral Statements:</E>
                     In general, individuals or groups requesting an oral presentation at a teleconference will be limited to three minutes. Those interested in being placed on the public speakers list for the July 5, 2011 teleconference should contact Dr. Nugent at the contact information provided above no later than June 30, 2011. 
                </P>
                <P>
                    <E T="03">Written Statements:</E>
                     Written statements should be supplied to the DFO via email at the contact information noted above by June 30, 2011 for the teleconference so that the information may be made available to the Panel members for their consideration. Written statements should be supplied in one of the following electronic formats: Adobe Acrobat PDF, MS Word, MS PowerPoint, or Rich Text files in IBM-PC/Windows 98/2000/XP format. It is the SAB Staff Office general policy to post written comments on the Web page for the advisory meeting or teleconference. Submitters are requested to provide an unsigned version of each document because the SAB Staff Office does not publish documents with signatures on its Web sites. Members of the public should be aware that their personal contact information, if included in any written comments, may be posted to the SAB Web site. Copyrighted material will not be posted without explicit permission of the copyright holder.
                </P>
                <P>
                    <E T="03">Accessibility:</E>
                     For information on access or services for individuals with disabilities, please contact Dr. Nugent (202) 564-2188 or 
                    <E T="03">nugent.angela@epa.gov</E>
                    . To request accommodation of a disability, please contact Dr. Nugent preferably at least ten days prior to the teleconference to give EPA as much time as possible to process your request.
                </P>
                <SIG>
                    <DATED>Dated: June 9, 2011.</DATED>
                    <NAME>Vanessa T. Vu,</NAME>
                    <TITLE>Director, EPA Science Advisory Staff Office.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-15002 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6560-50-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">EXPORT-IMPORT BANK OF THE UNITED STATES</AGENCY>
                <SUBJECT>Notice of Open Special Meeting of the Sub-Saharan Africa Advisory Committee (SAAC) of the Export-Import Bank of the United States (Export-Import Bank)</SUBJECT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Sub-Saharan Africa Advisory Committee was established by Public Law 105-121, November 26, 1997, to advise the Board of Directors on the development and implementation of policies and programs designed to support the expansion of the Bank's financial commitments in Sub-Saharan Africa under the loan, guarantee, and insurance programs of the Bank. Further, the committee shall make recommendations on how the Bank can facilitate greater support by U.S. commercial banks for trade with Sub-Saharan Africa.</P>
                    <P>
                        <E T="03">Time and Place:</E>
                         July 13, 2011 at 9:30 a.m. to 12:30 p.m. The meeting will be held at the Export-Import Bank in Room 1143, 811 Vermont Avenue, NW., Washington, DC 20571.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         Presentation on recent developments in Sub-Saharan Africa markets by Export-Import Bank staff; an update on the Bank's on-going business development initiatives in the region; and Committee discussion of current challenges and opportunities for U.S. exporters.
                    </P>
                    <P>
                        <E T="03">Public Participation:</E>
                         The meeting will be open to public participation, and the last 10 minutes will be set aside for oral questions or comments. Members of the public may also file written statement(s) before or after the meeting. If any person wishes auxiliary aids (such as a sign language interpreter) or other special accommodations, please contact, prior to July 13, 2011, Richard Thelen, 811 Vermont Avenue, NW., Washington, DC 20571, 
                        <E T="03">Voice:</E>
                         (202) 565-3515 or TDD (202) 565-3377.
                    </P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>For further information, contact Richard Thelen, 811 Vermont Avenue, NW., Washington, DC 20571, (202) 565-3515.</P>
                    <SIG>
                        <NAME>Angela Mariana Freyre,</NAME>
                        <TITLE>Senior Vice President and General Counsel.</TITLE>
                    </SIG>
                </FURINF>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-14908 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6690-01-M</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">FEDERAL DEPOSIT INSURANCE CORPORATION</AGENCY>
                <SUBJECT>Sunshine Act Meeting</SUBJECT>
                <P>Pursuant to the provisions of the “Government in the Sunshine Act” (5 U.S.C. 552b), notice is hereby given that at 10:20 a.m. on Tuesday, June 14, 2011, the Board of Directors of the Federal Deposit Insurance Corporation met in closed session to consider matters related to the Corporation's supervision, corporate and resolution activities.</P>
                <P>In calling the meeting, the Board determined, on motion of Director John E. Bowman (Acting Director, Office of Thrift Supervision), seconded by Vice Chairman Martin J. Gruenberg, concurred in by Director Thomas J. Curry (Appointive), Director John G. Walsh (Acting Comptroller of the Currency), and Chairman Sheila C. Bair, that Corporation business required its consideration of the matters which were to be the subject of this meeting on less than seven days' notice to the public; that no earlier notice of the meeting was practicable; that the public interest did not require consideration of the matters in a meeting open to public observation; and that the matters could be considered in a closed meeting by authority of subsections (c)(2), (c)(4), (c)(6), (c)(8), (c)(9)(A)(ii), (c)(9)(B), and (c)(10) of the “Government in the Sunshine Act” (5 U.S.C. 552b(c)(2), (c)(4), (c)(6), (c)(8), (c)(9)(A)(ii), (c)(9)(B), and (c)(10)).</P>
                <P>The meeting was held in the Board Room of the FDIC Building located at 550 17th Street, NW., Washington, DC.</P>
                <SIG>
                    <DATED>Dated: June 14, 2011.</DATED>
                    <FP>Federal Deposit Insurance Corporation.</FP>
                    <NAME>Robert E. Feldman,</NAME>
                    <TITLE>Executive Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-15059 Filed 6-14-11; 4:15 pm]</FRDOC>
            <BILCOD>BILLING CODE P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">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.
                    <PRTPAGE P="35218"/>
                </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.</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 July 11, 2011.</P>
                <P>A. Federal Reserve Bank of Atlanta (Clifford Stanford, Vice President) 1000 Peachtree Street, NE., Atlanta, Georgia 30309:</P>
                <P>
                    1. 
                    <E T="03">Savannah River Financial Corporation,</E>
                     Augusta, Georgia; to become a bank holding company by acquiring 100 percent of the voting shares of Savannah River Banking Company, Aiken, South Carolina, upon its conversion to a state non-member bank.
                </P>
                <SIG>
                    <DATED>Board of Governors of the Federal Reserve System, June 13, 2011.</DATED>
                    <NAME>Robert deV. Frierson,</NAME>
                    <TITLE>Deputy Secretary of the Board.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-14979 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6210-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">FEDERAL RESERVE SYSTEM</AGENCY>
                <SUBJECT>Notice of Proposals To Engage in Permissible Nonbanking Activities or To Acquire Companies That Are Engaged in Permissible Nonbanking Activities</SUBJECT>
                <P>
                    The companies listed in this notice have given notice under section 4 of the Bank Holding Company Act (12 U.S.C. 1843) (BHC Act) and Regulation Y, (12 CFR part 225) to engage 
                    <E T="03">de novo,</E>
                     or to acquire or control voting securities or assets of a company, including the companies listed below, that engages either directly or through a subsidiary or other company, in a nonbanking activity that is listed in § 225.28 of Regulation Y (12 CFR 225.28) or that the Board has determined by Order to be closely related to banking and permissible for bank holding companies. Unless otherwise noted, these activities will be conducted throughout the United States.
                </P>
                <P>Each notice is available for inspection at the Federal Reserve Bank indicated. The notice also will be available for inspection at the offices of the Board of Governors. Interested persons may express their views in writing on the question whether the proposal complies with the standards of section 4 of the BHC Act.</P>
                <P>Unless otherwise noted, comments regarding the applications must be received at the Reserve Bank indicated or the offices of the Board of Governors not later than July 1, 2011.</P>
                <P>A. Federal Reserve Bank of Chicago (Colette A. Fried, Assistant Vice President) 230 South LaSalle Street, Chicago, Illinois 60690-1414:</P>
                <P>
                    <E T="03">1. First American Bank Corporation,</E>
                     Elk Grove Village, Illinois; to engage 
                    <E T="03">de novo</E>
                     in extending credit and servicing loans, pursuant to section 225.28(b)(1) of Regulation Y.
                </P>
                <P>B. Federal Reserve Bank of San Francisco (Kenneth Binning, Vice President, Applications and Enforcement) 101 Market Street, San Francisco, California 94105-1579:</P>
                <P>
                    <E T="03">1.</E>
                      
                    <E T="03">Western Liberty Bancorp,</E>
                     Las Vegas, Nevada; to form a wholly owned subsidiary, OREOSUB, Las Vegas, Nevada, and thereby engage in extending credit and servicing loans, pursuant to sections 225.28(b)(1) and (2) of Regulation Y.
                </P>
                <SIG>
                    <P>Board of Governors of the Federal Reserve System, June 13, 2011.</P>
                    <NAME>Robert deV. Frierson,</NAME>
                    <TITLE>Deputy Secretary of the Board.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-14978 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6210-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF DEFENSE</AGENCY>
                <AGENCY TYPE="O">GENERAL SERVICES ADMINISTRATION</AGENCY>
                <AGENCY TYPE="O">NATIONAL AERONAUTICS AND SPACE ADMINISTRATION</AGENCY>
                <DEPDOC>[OMB Control No. 9000-0013; Docket 2011-0079; Sequence 16]</DEPDOC>
                <SUBJECT>Federal Acquisition Regulation; Information Collection; Cost or Pricing Data Requirements and Information Other Than Cost or Pricing Data</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Department of Defense (DOD), General Services Administration (GSA), and National Aeronautics and Space Administration (NASA).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of request for public comments regarding an extension to an existing OMB clearance.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>Under the provisions of the Paperwork Reduction Act (44 U.S.C. chapter 35), the Regulatory Secretariat (MVCB) will be submitting to the Office of Management and Budget (OMB) a request to review and approve an extension of a previously approved information collection requirement concerning cost or pricing data requirements and information other than cost or pricing data.</P>
                    <P>Public comments are particularly invited on: Whether this collection of information is necessary for the proper performance of functions of the FAR, and whether it will have practical utility; whether our estimate of the public burden of this collection of information is accurate, and based on valid assumptions and methodology; ways to enhance the quality, utility, and clarity of the information to be collected; and ways in which we can minimize the burden of the collection of information on those who are to respond, through the use of appropriate technological collection techniques or other forms of information technology.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Submit comments on or before August 15, 2011.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Submit comments identified by Information Collection 9000-0013, Cost or Pricing Data Requirements and Information Other Than Cost or Pricing Data, by any of the following methods:</P>
                    <P>
                        • 
                        <E T="03">Regulations.gov: http://www.regulations.gov</E>
                        . Submit comments via the Federal eRulemaking portal by inputting “Information Collection 9000-0013, Cost or Pricing Data Requirements and Information Other Than Cost or Pricing Data”, under the heading “Enter Keyword or ID” and selecting “Search”. Select the link “Submit a Comment” that corresponds with “Information Collection 9000-0013, Cost or Pricing Data Requirements and Information Other Than Cost or Pricing Data”. Follow the instructions provided at the “Submit a Comment” screen. Please include your name, company name (if any), and “Information Collection 9000-0013, Cost or Pricing Data Requirements and Information Other Than Cost or Pricing Data”, on your attached document.
                    </P>
                    <P>
                        • 
                        <E T="03">Fax:</E>
                         202-501-4067.
                    </P>
                    <P>
                        • 
                        <E T="03">Mail:</E>
                         General Services Administration, Regulatory Secretariat (MVCB), 1275 First Street, NE., Washington, DC 20417. ATTN: Hada Flowers/IC 9000-0013, Cost or Pricing Data Requirements and Information Other Than Cost or Pricing Data.
                    </P>
                    <P>
                        <E T="03">Instructions:</E>
                         Please submit comments only and cite Information Collection 9000-0013, Cost or Pricing Data Requirements and Information Other Than Cost or Pricing Data, in all 
                        <PRTPAGE P="35219"/>
                        correspondence related to this collection. All comments received will be posted without change to 
                        <E T="03">http://www.regulations.gov,</E>
                         including any personal and/or business confidential information provided.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Mr. Edward Chambers, Procurement Analyst, Acquisition Policy Division, GSA (202) 501-3221 or 
                        <E T="03">Edward.chambers@gsa.gov</E>
                        .
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">A. Purpose</HD>
                <P>The Truth in Negotiations Act requires the Government to obtain certified cost or pricing data under certain circumstances. Contractors may request an exemption from this requirement under certain conditions and provide other information instead.</P>
                <HD SOURCE="HD1">B. Annual Reporting Burden</HD>
                <P>
                    <E T="03">Respondents:</E>
                     33,332.
                </P>
                <P>
                    <E T="03">Responses per Respondent:</E>
                     6.
                </P>
                <P>
                    <E T="03">Total Responses:</E>
                     199,992.
                </P>
                <P>
                    <E T="03">Hours per Response:</E>
                     50.51.
                </P>
                <P>
                    <E T="03">Total Burden Hours:</E>
                     10,101,684.
                </P>
                <P>
                    <E T="03">Obtaining Copies of Proposals:</E>
                     Requesters may obtain a copy of the information collection documents from the General Services Administration, Regulatory Secretariat Division (MVCB), 1275 First Street, NE., Washington, DC 20417, telephone (202) 501-4755. Please cite OMB Control No. 9000-0013, Cost or Pricing Data Requirements and Information Other Than Cost or Pricing Data, in all correspondence.
                </P>
                <SIG>
                    <DATED>Dated: June 7, 2011.</DATED>
                    <NAME>Millisa Gary,</NAME>
                    <TITLE>Acting Director, Office of Governmentwide Acquisition Policy.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-14863 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6820-EP-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF DEFENSE</AGENCY>
                <AGENCY TYPE="O">GENERAL SERVICES ADMINISTRATION</AGENCY>
                <AGENCY TYPE="O">NATIONAL AERONAUTICS AND SPACE ADMINISTRATION</AGENCY>
                <DEPDOC>[OMB Control No. 9000-0144; Docket 2011-0079; Sequence 17]</DEPDOC>
                <SUBJECT>Federal Acquisition Regulation; Information Collection; Payment by Electronic Fund Transfer</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Department of Defense (DOD), General Services Administration (GSA), and National Aeronautics and Space Administration (NASA).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of request for public comments regarding an extension to an existing OMB clearance.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>Under the provisions of the Paperwork Reduction Act (44 U.S.C. chapter 35), the Regulatory Secretariat (MVCB) will be submitting to the Office of Management and Budget (OMB) a request to review and approve an extension of a previously approved information collection requirement concerning payment by electronic fund transfer.</P>
                    <P>Public comments are particularly invited on: Whether this collection of information is necessary for the proper performance of functions of the FAR, and whether it will have practical utility; whether our estimate of the public burden of this collection of information is accurate, and based on valid assumptions and methodology; ways to enhance the quality, utility, and clarity of the information to be collected; and ways in which we can minimize the burden of the collection of information on those who are to respond, through the use of appropriate technological collection techniques or other forms of information technology.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Submit comments on or before August 15, 2011.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Submit comments identified by Information Collection 9000-0144, Payment by Funds Transfer, by any of the following methods:</P>
                    <P>
                        • 
                        <E T="03">Regulations.gov: http://www.regulations.gov</E>
                        . Submit comments via the Federal eRulemaking portal by inputting “Information Collection 9000-0144, Payment by Funds Transfer,” under the heading “Enter Keyword or ID” and selecting “Search.” Select the link “Submit a Comment” that corresponds with “Information Collection 9000-0144, Payment by Funds Transfer”. Follow the instructions provided at the “Submit a Comment” screen. Please include your name, company name (if any), and “Information Collection 9000-0144, Payment by Funds Transfer”, on your attached document.
                    </P>
                    <P>
                        • 
                        <E T="03">Fax:</E>
                         202-501-4067.
                    </P>
                    <P>
                        • 
                        <E T="03">Mail:</E>
                         General Services Administration, Regulatory Secretariat (MVCB), 1275 First Street, NE., Washington, DC 20417. 
                        <E T="03">Attn:</E>
                         Hada Flowers/IC 9000-0144, Payment by Funds Transfer.
                    </P>
                    <P>
                        <E T="03">Instructions:</E>
                         Please submit comments only and cite Information Collection 9000-0144, Payment by Funds Transfer, in all correspondence related to this collection. All comments received will be posted without change to 
                        <E T="03">http://www.regulations.gov,</E>
                         including any personal and/or business confidential information provided.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Mr. Edward Chambers, Procurement Analyst, Acquisition Policy Division, GSA (202) 501-3221, or 
                        <E T="03">Edward.chambers@gsa.gov</E>
                        .
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">A. Purpose</HD>
                <P>The FAR requires certain information to be provided by contractors which would enable the Government to make payments under the contract by electronic fund transfer (EFT). The information necessary to make the EFT transaction is specified in clause 52.232-33, Payment by Electronic Funds Transfer—Central Contractor Registration, which the contractor is required to provide prior to award, and clause 52.232-34, Payment by Electronic Funds Transfer—Other than Central Contractor Registration, which requires EFT information to be provided as specified by the agency to enable payment by EFT.</P>
                <HD SOURCE="HD1">B. Annual Reporting Burden</HD>
                <P>
                    <E T="03">Respondents:</E>
                     14,000.
                </P>
                <P>
                    <E T="03">Responses per Respondent:</E>
                     10.
                </P>
                <P>
                    <E T="03">Annual Responses:</E>
                     140,000.
                </P>
                <P>
                    <E T="03">Hours per Response:</E>
                     .5.
                </P>
                <P>
                    <E T="03">Total Burden Hours:</E>
                     70,000.
                </P>
                <P>
                    <E T="03">Obtaining Copies of Proposals:</E>
                     Requesters may obtain a copy of the information collection documents from the General Services Administration, Regulatory Secretariat (MVCB), 1275 First Street, NE., Washington, DC 20417, telephone (202) 501-4755. Please cite OMB Control No. 9000-0144, Payment by Electronic Funds Transfer, in all correspondence.
                </P>
                <SIG>
                    <DATED>Dated: June 7, 2011.</DATED>
                    <NAME>Millisa Gary,</NAME>
                    <TITLE>Acting Director, Office of Governmentwide Acquisition Policy.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-14862 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6820-EP-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>Administration for Children and Families</SUBAGY>
                <SUBJECT>Submission for OMB Review; Comment Request</SUBJECT>
                <P>
                    <E T="03">Title:</E>
                     Innovative Strategies for Increasing Self-Sufficiency: Baseline Data Collection.
                </P>
                <P>
                    <E T="03">OMB No.:</E>
                     New Collection.
                </P>
                <P>
                    <E T="03">Description:</E>
                     The Administration for Children and Families (ACF), U.S. Department of Health and Human Services (HHS), is proposing a data collection activity as part of the Innovative Strategies for Increasing Self-Sufficiency (ISIS) demonstration and 
                    <PRTPAGE P="35220"/>
                    evaluation. The ISIS project will test a range of promising strategies to promote employment, self-sufficiency, and reduce dependence on cash welfare. The ISIS project will evaluate multiple employment-focused strategies that build on previous approaches and are adapted to the current Federal, State, and local policy environment. The major goals of the project include increasing the empirical knowledge about the effectiveness of a variety of programs for low-income families to sustain employment and advance to positions that enable self-sufficiency, as well as producing useful findings for both policymakers and program administrators.
                </P>
                <P>This proposed information collection activity focuses on collecting baseline data elements. Two data collection instruments will be completed by all participants prior to random assignment, and a third mill be an interview guide to collect information from program staff. The first is a short baseline information form (BIF) that will collect basic identification, demographic, and contact information. The form will include relatively standard items from prior evaluations and national surveys. The second instrument will be a self-administered questionnaire (SAQ), covering information related to the project goals. The third instrument, baseline implementation data collection interviews, will be used to collect information from knowledgeable informants about the service context for each evaluation site using a baseline implementation guide. The purpose of such interviews is to document and assess the service environment in which the evaluation is implemented and the opportunities for control group members to access the same or similar services as the treatment group members.</P>
                <P>
                    <E T="03">Respondents:</E>
                     Individuals enrolled in ISIS demonstration interventions, control group members, ISIS program operators (BIF and SAQ) and State and local informants (interviews).
                </P>
                <GPOTABLE COLS="5" OPTS="L2,i1" CDEF="s50,12,12,8.2,12">
                    <TTITLE>Annual Burden Estimates</TTITLE>
                    <BOXHD>
                        <CHED H="1">Instrument </CHED>
                        <CHED H="1">
                            Annual
                            <LI>number of</LI>
                            <LI>respondents</LI>
                        </CHED>
                        <CHED H="1">
                            Number of
                            <LI>responses</LI>
                            <LI>per </LI>
                            <LI>respondent</LI>
                        </CHED>
                        <CHED H="1">
                            Average
                            <LI>burden hours</LI>
                            <LI>per response</LI>
                        </CHED>
                        <CHED H="1">Total annual burden hours</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Baseline Information Form</ENT>
                        <ENT>4,800</ENT>
                        <ENT>1</ENT>
                        <ENT>0.75</ENT>
                        <ENT>3,600</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Self-Administered Questionnaire</ENT>
                        <ENT>4,800</ENT>
                        <ENT>1</ENT>
                        <ENT>0.75</ENT>
                        <ENT>3,600</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Baseline Implementation Data Collection Interviews</ENT>
                        <ENT>30</ENT>
                        <ENT>1</ENT>
                        <ENT>1</ENT>
                        <ENT>30</ENT>
                    </ROW>
                </GPOTABLE>
                <P>
                    <E T="03">Estimated Total Annual Burden Hours:</E>
                     7,230
                </P>
                <P>
                    <E T="03">Additional Information:</E>
                     Copies of the proposed collection may be obtained by writing to the Administration for Children and Families, Office of Planning, Research and Evaluation, 370 L'Enfant Promenade, SW., Washington, DC 20447, Attn: OPRE Reports Clearance Officer. All requests should be identified by the title of the information collection. E-mail address: 
                    <E T="03">OREinfocollection@acf.hhs.gov.</E>
                </P>
                <P>
                    <E T="03">OMB Comment:</E>
                     OMB is required to make a decision concerning the collection of information between 30 and 60 days after publication of this document in the 
                    <E T="04">Federal Register.</E>
                     Therefore, a comment is best assured of having its full effect if OMB receives it within 30 days of publication. Written comments and recommendations for the proposed information collection should be sent directly to the following: Office of Management and Budget, Paperwork Reduction Project, Fax: 202-395-6974, Attn: Desk Officer for the Administration for Children and Families.
                </P>
                <SIG>
                    <DATED>Dated: June 10, 2011.</DATED>
                    <NAME>Steven M. Hanmer,</NAME>
                    <TITLE>OPRE Reports Clearance Officer.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-14869 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4184-09-M</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>Administration for Children and Families</SUBAGY>
                <SUBJECT>Submission for OMB Review; Comment Request</SUBJECT>
                <P>
                    <E T="03">Title:</E>
                     Implementation, Systems and Outcome Evaluation of the Tribal and Low-Income Health Profession Opportunity Grants (HPOG).
                </P>
                <P>
                    <E T="03">OMB No.:</E>
                     New Collection.
                </P>
                <P>
                    <E T="03">Description:</E>
                     The Administration for Children and Families (ACF) is proposing information collection activities as part of the Implementation, Systems and Outcome Evaluation of the Health Profession Opportunity Grants (HPOG). Through this information collection, ACE seeks to develop comprehensive management and performance reports on the HPOG initiative and design a feasible and reliable evaluation design to produce accurate evidence of the effect of HPOG on individuals and health job training programs systems.
                </P>
                <P>The goals of the HPOG evaluation are to establish a performance management reporting process for HPOG, and design an evaluation of HPOG. Both goals require collecting information from HPOG grantees on a regular basis. The information collection proposed is an Internet-based collection of information from HPOG grantees on (1) program participants: Baseline characteristics, program participation and patterns, and participant outputs and outcomes; and (2) program designs and operating characteristics. The performance management system would collect information from grantees on their programs and participants on a bi-annual basis.</P>
                <P>
                    <E T="03">Respondents:</E>
                     Participant data to be collected by program staff in the 32 grantee organizations (higher education institutions, workforce investment boards, private training institutions, and tribal entities).
                </P>
                <GPOTABLE COLS="5" OPTS="L2,i1" CDEF="s100,12C,12C,12C,12C">
                    <TTITLE>Annual Burden Estimates</TTITLE>
                    <BOXHD>
                        <CHED H="1">Instrument</CHED>
                        <CHED H="1">
                            Annual 
                            <LI>number of </LI>
                            <LI>respondents</LI>
                        </CHED>
                        <CHED H="1">
                            Number of 
                            <LI>responses per respondent</LI>
                        </CHED>
                        <CHED H="1">
                            Average 
                            <LI>burden hours per response</LI>
                        </CHED>
                        <CHED H="1">Total annual burden hours</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Semi-annual HPOG Program Performance Report </ENT>
                        <ENT>32 </ENT>
                        <ENT>2 </ENT>
                        <ENT>31.25 </ENT>
                        <ENT>2,000</ENT>
                    </ROW>
                </GPOTABLE>
                <PRTPAGE P="35221"/>
                <P>
                    <E T="03">Estimated Total Annual Burden Hours:</E>
                     2,000.
                </P>
                <P>
                    <E T="03">Additional Information:</E>
                     Copies of the proposed collection may be obtained by writing to the Administration for Children and Families, Office of Planning, Research and Evaluation, 370 L'Enfant Promenade, SW., Washington, DC 20447, 
                    <E T="03">Attn:</E>
                     OPRE Reports Clearance Officer. All requests should be identified by the title of the information collection. 
                    <E T="03">E-mail address: OPREinfocollection@acf.hhs.gov.</E>
                </P>
                <P>
                    <E T="03">OMB Comment:</E>
                     OMB is required to make a decision concerning the collection of information between 30 and 60 days after publication of this document in the 
                    <E T="04">Federal Register</E>
                    . Therefore, a comment is best assured of having its full effect if OMB receives it within 30 days of publication. Written comments and recommendations for the proposed information collection should be sent directly to the following:
                </P>
                <FP SOURCE="FP-1">
                    Office of Management and Budget, Paperwork Reduction Project, 
                    <E T="03">Fax:</E>
                     202-395-6974, 
                    <E T="03">Attn:</E>
                     Desk Officer for the Administration, for Children and Families.
                </FP>
                <SIG>
                    <DATED>Dated: June 9, 2011.</DATED>
                    <NAME>Steven M. Hanmer,</NAME>
                    <TITLE>OPRE Reports Clearance Officer.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-14811 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4184-09-M</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>Indian Health Service</SUBAGY>
                <SUBJECT>Epidemiology Program for American Indian/Alaska Native Tribes and Urban Indian Communities; Correction</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Indian Health Service, HHS.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice; correction.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The Indian Health Service published a document in the 
                        <E T="04">Federal Register</E>
                         on June 8, 2011, concerning competitive cooperative agreement applications to establish Tribal Epidemiology Centers serving American Indian/Alaska Native Tribes and urban Indian communities. The document contained one incorrect date.
                    </P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Betty Gould, 301-443-1116.</P>
                    <HD SOURCE="HD1">Correction</HD>
                    <P>
                        In the 
                        <E T="04">Federal Register</E>
                         of June 8, 2011, in FR Doc. 2011-14131, on page 33318, in the first column, last complete sentence in the paragraph “Letters of Intent,” correct the sentence to read:
                    </P>
                    <P>“The LoI must be submitted to the Division of Grants Management to the attention of Andrew Diggs by June 17, 2011.”</P>
                    <SIG>
                        <DATED>Dated: June 9, 2011.</DATED>
                        <NAME>Betty Z. Gould,</NAME>
                        <TITLE>Federal Register Liaison Officer, Indian Health Service.</TITLE>
                    </SIG>
                </FURINF>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-14794 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4165-16-M</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>National Institutes of Health</SUBAGY>
                <SUBJECT>Proposed Collection; Comment Request; NINR End-of-Life and Palliative Care Science Needs Assessment: Funding Source Questionnaire (Survey of Authors)</SUBJECT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>In compliance with the requirement of Section 3506(c)(2)(A) of the Paperwork Reduction Act of 1995, for opportunity for public comment on proposed data collection projects, the National Institute of Nursing Research (NINR), the National Institutes of Health (NIH) will publish periodic summaries of proposed projects to be submitted to the Office of Management and Budget (OMB).</P>
                    <P>
                        <E T="03">Proposed Collection: Title:</E>
                         NINR End-of-Life and Palliative Care Science Needs Assessment: Funding Source Questionnaire (Survey of Authors). 
                        <E T="03">Type of Information Collection Request:</E>
                         NEW. 
                        <E T="03">Need and Use of Information Collection:</E>
                         The NINR End-of-Life Science Palliative Care (EOL PC) Needs Assessment: Funding Source Questionnaire will obtain information on funding sources of EOL PC research published studies for which a funding source is not cited or the information is unclear. Target participants are authors of publically-available EOL PC research studies published between 1997-2010 for whom a funding source is unknown or unclear. The questionnaire inquires about the funding source of the published study, type of funding received, year of funding, and duration of funded study. This is a 7-item questionnaire that takes approximately 5 minutes to complete. Data collected is part of a needs assessment to address the breadth and depth of EOL PC scientific issues for use in stimulating research capacity in the field. 
                        <E T="03">Frequency of Response:</E>
                         One time. 
                        <E T="03">Affected Public:</E>
                         Individual authors of publically available EOL PC research publications who do not list a funding source or the source is unclear within their publication. 
                        <E T="03">Type of Respondents:</E>
                         EOL PC researchers. The annual reporting burden is as follows: 
                        <E T="03">Estimated Number of Respondents:</E>
                         1840; 
                        <E T="03">Estimated Number of Responses per Respondent:</E>
                         1; 
                        <E T="03">Average Burden Hours per Response:</E>
                         .08; and 
                        <E T="03">Estimated Total Annual Burden Hours Requested:</E>
                         147. There are no Capital Costs, Operating or Maintenance Costs to report.
                    </P>
                    <P>
                        <E T="03">Request for Comments:</E>
                         Written comments and/or suggestions from the public and affected agencies are invited on one or more of the following points: (1) Whether the proposed collection of information is necessary for the proper performance of the function 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.
                    </P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        To request more information on the proposed project or to obtain a copy of the data collection plans and instruments, contact Dr. Amanda Greene, Science Evaluation Officer, Office of Science Policy and Public Liaison, NINR, Democracy One, 6701 Democracy Blvd., Suite 710, Bethesda, MD 20892, or call non-toll-free number 301-496-9601, or e-mail your request to 
                        <E T="03">amanda.greene@nih.gov.</E>
                    </P>
                    <P>
                        <E T="03">Comments Due Date:</E>
                         Comments regarding this information collection are best assured of having their full effect if received within 60 days of the date of this publication.
                    </P>
                    <SIG>
                        <DATED>Dated: June 6, 2011.</DATED>
                        <NAME>Amanda Greene,</NAME>
                        <TITLE>Science Evaluation Officer, NINR, National Institutes of Health.</TITLE>
                    </SIG>
                </FURINF>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-14878 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4140-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>National Institutes of Health</SUBAGY>
                <SUBJECT>Office of the Director; Notice of Charter Renewal for the Advisory Committee to the Director</SUBJECT>
                <P>
                    In accordance with Title 41 of the U.S. Code of Federal Regulations, Section 102-3.65(a), notice is hereby given that the Charter for the Advisory Committee to the Director, National Institutes of Health was renewed for an 
                    <PRTPAGE P="35222"/>
                    additional two-year period on May 31, 2011.
                </P>
                <P>It is determined that the Advisory Committee to the Director, National Institutes of Health, is in the public interest in connection with the performance of duties imposed on the National Institutes of Health by law, and that these duties can best be performed through the advice and counsel of this group.</P>
                <P>
                    Inquiries may be directed to Jennifer Spaeth, Director, Office of Federal Advisory Committee Policy, Office of the Director, National Institutes of Health, 6701 Democracy Boulevard, Suite 1000, Bethesda, Maryland 20892 (Mail code 4875), Telephone (301) 496-2123, or 
                    <E T="03">spaethj@od.nih.gov.</E>
                </P>
                <SIG>
                    <DATED>Dated: June 10, 2011.</DATED>
                    <NAME>Jennifer S. Spaeth,</NAME>
                    <TITLE>Director, Office of Federal Advisory Committee Policy.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-15006 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4140-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>National Institutes of Health</SUBAGY>
                <SUBJECT>National Institute on Deafness and Other Communication Disorders; Notice of Closed Meetings</SUBJECT>
                <P>Pursuant to section 10(d) of the Federal Advisory Committee Act, as amended (5 U.S.C. App.), notice is hereby given of the following meetings.</P>
                <P>The meetings will be closed to the public in accordance with the provisions set forth in sections 552b(c)(4) and 552b(c)(6), Title 5 U.S.C., as amended. The grant applications and the discussions could disclose confidential trade secrets or commercial property such as patentable material, and personal information concerning individuals associated with the grant applications, the disclosure of which would constitute a clearly unwarranted invasion of personal privacy.</P>
                <EXTRACT>
                    <P>
                        <E T="03">Name of Committee:</E>
                         National Institute on Deafness and Other Communication Disorders Special Emphasis Panel, R24—NIDCD Community-Wide Scientific Resources Limited Competition.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         July 7, 2011.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         11 a.m. to 2 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Place:</E>
                         National Institutes of Health, 6120 Executive Blvd., Rockville, MD 20852, (Telephone Conference Call).
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Susan L. Sullivan, PhD, Scientific Review Officer, National Institute of Deafness and Other Communication Disorders 6120 Executive Blvd Ste., 400C, Rockville, MD 20852, 301-496-8683, 
                        <E T="03">sullivas@mail.nih.gov.</E>
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         National Institute on Deafness and Other Communication Disorders Special Emphasis Panel, P30 Review.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         July 14, 2011.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         12 p.m. to 2 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Place:</E>
                         National Institutes of Health, 6120 Executive Blvd., Rockville, MD 20852, (Telephone Conference Call).
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Susan L. Sullivan, PhD, Scientific Review Officer, National Institute of Deafness and Other Communication Disorders, 6120 Executive Blvd Ste., 400C, Rockville, MD 20852, 301-496-8683, 
                        <E T="03">sullivas@mail.nih.gov.</E>
                    </P>
                    <FP>(Catalogue of Federal Domestic Assistance Program Nos. 93.173, Biological Research Related to Deafness and Communicative Disorders, National Institutes of Health, HHS)</FP>
                </EXTRACT>
                <SIG>
                    <DATED>Dated: June 10, 2011.</DATED>
                    <NAME>Jennifer S. Spaeth,</NAME>
                    <TITLE>Director, Office of Federal Advisory Committee Policy.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-14864 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4140-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>National Institutes of Health</SUBAGY>
                <SUBJECT>National Institute of General Medical Sciences; Notice of Closed Meeting</SUBJECT>
                <P>Pursuant to section 10(d) of the Federal Advisory Committee Act, as amended (5 U.S.C. App.), notice is hereby given of the following meeting.</P>
                <P>The meeting will be closed to the public in accordance with the provisions set forth in sections 552b(c)(4) and 552b(c)(6), Title 5 U.S.C., as amended. The grant applications and the discussions could disclose confidential trade secrets or commercial property such as patentable material, and personal information concerning individuals  associated with the grant applications, the disclosure of which would constitute a clearly unwarranted invasion of personal privacy.</P>
                <EXTRACT>
                    <P>
                        <E T="03">Name of Committee:</E>
                         National Institute of General Medical Sciences Initial Review Group, Minority Programs Review Subcommittee B.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         July 11, 2011.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         8:30 a.m. to 5 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Place:</E>
                         Hyatt Regency—Bethesda, One Bethesda Metro Center, 7400 Wisconsin Avenue, Bethesda, MD 20814.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Rebecca H. Johnson, PhD, Scientific Review Officer, Office of Scientific Review, National Institute of General Medical Sciences, National Institutes of Health, 45 Center Drive, Room 3AN18C Bethesda, MD 20892, 301-594-2771, 
                        <E T="03">johnsonrh@nigms.nih.gov.</E>
                    </P>
                    <FP>(Catalogue of Federal Domestic Assistance Program Nos. 93.375, Minority Biomedical Research Support; 93.821, Cell Biology and Biophysics Research; 93.859, Pharmacology, Physiology, and Biological Chemistry Research; 93.862, Genetics and Developmental Biology Research; 93.88, Minority Access to Research Careers; 93.96, Special Minority Initiatives, National Institutes of Health, HHS)</FP>
                </EXTRACT>
                <SIG>
                    <DATED>Dated: June 10, 2011.</DATED>
                    <NAME>Jennifer Spaeth,</NAME>
                    <TITLE>Director, Office of Federal Advisory Committee Policy.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-14865 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4140-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>National Institutes of Health</SUBAGY>
                <SUBJECT>National Institute on Deafness and Other Communication Disorders; Notice of Closed Meetings</SUBJECT>
                <P>Pursuant to section 10(d) of the Federal Advisory Committee Act, as amended (5 U.S.C. App.), notice is hereby given of the following meetings.</P>
                <P>The meetings will be closed to the public in accordance with the provisions set forth in sections 552b(c)(4) and 552b(c)(6), Title 5 U.S.C., as amended. The grant applications and the discussions could disclose confidential trade secrets or commercial property such as patentable material, and personal information concerning individuals associated with the grant applications, the disclosure of which would constitute a clearly unwarranted invasion of personal privacy.</P>
                <EXTRACT>
                    <P>
                        <E T="03">Name of Committee:</E>
                         National Institute on Deafness and Other Communication Disorders Special Emphasis Panel, CDRC Conflicts.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         June 23, 2011.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         10 a.m. to 1 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Place:</E>
                         National Institutes of Health, 6120 Executive Blvd., Rockville, MD 20852, (Telephone Conference Call).
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Christine A. Livingston, PhD, Scientific Review Officer, Division of Extramural Activities, National Institutes of Health/NIDCD, 6120 Executive Blvd.—MSC 7180, Bethesda, MD 20892, (301) 496-8683, 
                        <E T="03">livingsc@mail.nih.gov</E>
                        .
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         National Institute on Deafness and Other Communication Disorders Special Emphasis Panel, U24.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         June 28, 2011.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         12 p.m. to 2 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Place:</E>
                         National Institutes of Health, 6120 Executive Blvd., Rockville, MD 20852, (Telephone Conference Call).
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Christine A. Livingston, PhD, Scientific Review Officer, Division of 
                        <PRTPAGE P="35223"/>
                        Extramural Activities, National Institutes of Health/NIDCD, 6120 Executive Blvd.—MSC 7180, Bethesda, MD 20892, (301) 496-8683, 
                        <E T="03">livingsc@mail.nih.gov</E>
                        .
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         National Institute on Deafness and Other Communication Disorders Special Emphasis Panel, R01/R21—Translational,
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         June 30, 2011.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         11 a.m. to 2 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Place:</E>
                         National Institutes of Health, 6120 Executive Blvd., Rockville, MD 20852, (Telephone Conference Call).
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Christine A. Livingston, PhD, Scientific Review Officer, Division of Extramural Activities, National Institutes of Health/NIDCD, 6120 Executive Blvd.—MSC 7180, Bethesda, MD 20892 (301) 496-8683, 
                        <E T="03">livingsc@mail.nih.gov</E>
                        .
                    </P>
                    <FP>(Catalogue of Federal Domestic Assistance Program Nos. 93.173, Biological Research Related to Deafness and Communicative Disorders, National Institutes of Health, HHS)</FP>
                </EXTRACT>
                <SIG>
                    <DATED>Dated: June 10, 2011.</DATED>
                    <NAME>Jennifer S. Spaeth,</NAME>
                    <TITLE>Director, Office of Federal Advisory Committee Policy.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-14866 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4140-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>National Institutes of Health</SUBAGY>
                <SUBJECT>Center for Scientific Review; Notice of Closed Meetings</SUBJECT>
                <P>Pursuant to section 10(d) of the Federal Advisory Committee Act, as amended (5 U.S.C. App.), notice is hereby given of the following meetings.</P>
                <P>The meetings will be closed to the public in accordance with the provisions set forth in sections 552b(c)(4) and 552b(c)(6), Title 5 U.S.C., as amended. The grant applications and the discussions could disclose confidential trade secrets or commercial property such as patentable material, and personal information concerning individuals associated with the grant applications, the disclosure of which would constitute a clearly unwarranted invasion of personal privacy.</P>
                <EXTRACT>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel, Small Business Grant Applications: Immunology.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         June 27, 2011.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         8:30 a.m. to 6 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Place:</E>
                         The River Inn, 924 25th Street, NW., Washington, DC 20037.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Stephen M Nigida, PhD, Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Room 4212, MSC 7812, Bethesda, MD 20892, 301-435-1222, 
                        <E T="03">nigidas@csr.nih.gov.</E>
                    </P>
                    <P>This notice is being published less than 15 days prior to the meeting due to the timing limitations imposed by the review and funding cycle.</P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel, Member Conflict: Ventricular Arrhythmias and Sudden Death.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         June 30, 2011.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         2 p.m. to 5 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Place:</E>
                         National Institutes of Health, 6701 Rockledge Drive, Bethesda, MD 20892, (Telephone Conference Call).
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Olga A. Tjurmina, PhD, Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Room 4138, MSC 7814, Bethesda, MD 20892, (301) 451-1375, 
                        <E T="03">ot3d@nih.gov.</E>
                    </P>
                    <P>This notice is being published less than 15 days prior to the meeting due to the timing limitations imposed by the review and funding cycle.</P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         AIDS and Related Research Integrated Review Group, Behavioral and Social Consequences of HIV/AIDS Study Section.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         July 7-8, 2011.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         8 a.m. to 5 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Place:</E>
                         St. Gregory Hotel, 2033 M Street, NW., Washington, DC 20036.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Mark P Rubert, PhD, Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Room 5218, MSC 7852, Bethesda, MD 20892, 301-806-6596, 
                        <E T="03">rubertm@csr.nih.gov.</E>
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         AIDS and Related Research Integrated Review Group, AIDS Discovery and Development of Therapeutics Study Section.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         July 8, 2011.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         8 a.m. to 5 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Place:</E>
                         Ritz Carlton Hotel, 1150 22nd Street, NW., Washington, DC 20037.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Shiv A Prasad, PhD, Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Room 5220, MSC 7852, Bethesda, MD 20892, 301-443-5779, 
                        <E T="03">prasads@csr.nih.gov.</E>
                    </P>
                    <FP>(Catalogue of Federal Domestic Assistance Program Nos. 93.306, Comparative Medicine; 93.333, Clinical Research, 93.306, 93.333, 93.337, 93.393-93.396, 93.837-93.844, 93.846-93.878, 93.892, 93.893, National Institutes of Health, HHS)</FP>
                </EXTRACT>
                <SIG>
                    <DATED>Dated: June 9, 2011.</DATED>
                    <NAME>Jennifer S. Spaeth,</NAME>
                    <TITLE>Director, Office of Federal Advisory Committee Policy.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-14873 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4140-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>National Institutes of Health</SUBAGY>
                <SUBJECT>National Human Genome Research Institute; Notice of Closed Meeting</SUBJECT>
                <P>Pursuant to section 10(d) of the Federal Advisory Committee Act, as amended (5 U.S.C. App.), notice is hereby given of the following meeting.</P>
                <P>The meeting will be closed to the public in accordance with the provisions set forth in sections 552b(c)(4) and 552b(c)(6), Title 5 U.S.C., as amended. The grant applications and the discussions could disclose confidential trade secrets or commercial property such as patentable material, and personal information concerning individuals associated with the grant applications, the disclosure of which would constitute a clearly unwarranted invasion of personal privacy.</P>
                <EXTRACT>
                    <P>
                        <E T="03">Name of Committee:</E>
                         National Human Genome Research Institute Special Emphasis Panel, Sequencing Centers—SEP.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         July 7-8, 2011.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         8 a.m. to 5 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Place:</E>
                         Renaissance Hotel, 2800 Potomac Avenue, Arlington, VA 22202.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Rudy O. Pozzatti, PhD, Scientific Review Officer, Scientific Review Branch, National Human Genome Research Institute, 5635 Fishers Lane, Suite 4076, MSC 9306, Rockville, MD 20852, (301) 402-0838, 
                        <E T="03">pozzattr@mail.nih.gov</E>
                        .
                    </P>
                    <FP>(Catalogue of Federal Domestic Assistance Program Nos. 93.172, Human Genome Research, National Institutes of Health, HHS)</FP>
                </EXTRACT>
                <SIG>
                    <DATED>Dated: June 9, 2011.</DATED>
                    <NAME>Jennifer S. Spaeth,</NAME>
                    <TITLE>Director, Office of Federal Advisory Committee Policy.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-14876 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4140-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>National Institutes of Health</SUBAGY>
                <SUBJECT>National Center for Research Resources; Notice of Closed Meeting</SUBJECT>
                <P>Pursuant to section 10(d) of the Federal Advisory Committee Act, as amended (5 U.S.C. App.), notice is hereby given of the following meeting.</P>
                <P>
                    The meeting will be closed to the public in accordance with the provisions set forth in sections 552b(c)(4) and 552b(c)(6), Title 5 U.S.C., as amended. The grant applications and the discussions could disclose confidential trade secrets or commercial property such as patentable material, 
                    <PRTPAGE P="35224"/>
                    and personal information concerning individuals associated with the grant applications, the disclosure of which would constitute a clearly unwarranted invasion of personal privacy.
                </P>
                <EXTRACT>
                    <P>
                        <E T="03">Name of Committee:</E>
                         National Center for Research Resources Special Emphasis Panel,
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         June 21, 2011.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         1 p.m. to 2 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Place:</E>
                         National Institutes of Health/NCRR/OR, Democracy 1, 6701 Democracy Blvd., 1084, Bethesda, MD 20892.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Mohan Viswanathan, BS, PhD, Scientific Review Officer, Office of Review, NCRR, Natonal Institutes of Health, 1 Democracy Plaza, 6701 Democracy Blvd., MSC 4874, RM. 1084, Bethesda, MD 20892-4874, 301-435-0829, 
                        <E T="03">viswanathanm@ncrr.nih.gov</E>
                        .
                    </P>
                    <P>This notice is being published less than 15 days prior to the meeting due to the timing limitations imposed by the review and funding cycle.</P>
                    <FP>(Catalogue of Federal Domestic Assistance Program Nos. 93.306, Comparative Medicine; 93.333, Clinical Research; 93.371, Biomedical Technology; 93.389, Research Infrastructure, 93.306, 93.333; 93.702, ARRA Related Construction Awards., National Institutes of Health, HHS)</FP>
                </EXTRACT>
                <SIG>
                    <DATED>Dated: June 8, 2011.</DATED>
                    <NAME>Jennifer S. Spaeth,</NAME>
                    <TITLE>Director, Office of Federal Advisory Committee Policy.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-14877 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4140-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>National Institutes of Health</SUBAGY>
                <SUBJECT>National Human Genome Research Institute; Notice of Closed Meeting</SUBJECT>
                <P>Pursuant to section 10(d) of the Federal Advisory Committee Act, as amended (5 U.S.C. App.), notice is hereby given of the following meeting.</P>
                <P>The meeting will be closed to the public in accordance with the provisions set forth in sections 552b(c)(4) and 552b(c)(6), Title 5 U.S.C., as amended. The grant applications and the discussions could disclose confidential trade secrets or commercial property such as patentable material, and personal information concerning individuals associated with the grant applications, the disclosure of which would constitute a clearly unwarranted invasion of personal privacy.</P>
                <EXTRACT>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Inherited Disease Research Access Committee. 
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         July 15, 2011.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         11:30 a.m. to 2 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Place:</E>
                         National Institutes of Health, 5635 Fishers Lane, Bethesda, MD 20892, (Telephone Conference Call).
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Camilla E. Day, PhD, Scientific Review Officer, CIR, National Human Genome Research Institute, National Institutes of Health, 5635 Fishers Lane, Suite 4075, Bethesda, MD 20892 301-402-8837, 
                        <E T="03">camilla.day@nih.gov.</E>
                    </P>
                    <FP>(Catalogue of Federal Domestic Assistance Program Nos. 93.172, Human Genome Research, National Institutes of Health, HHS)</FP>
                </EXTRACT>
                <SIG>
                    <DATED>Dated: June 10, 2011.</DATED>
                    <NAME>Jennifer S. Spaeth,</NAME>
                    <TITLE>Director, Office of Federal Advisory Committee Policy.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-15011 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4140-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>National Institutes of Health</SUBAGY>
                <SUBJECT>National Institute of Allergy and Infectious Diseases; Notice of Closed Meetings</SUBJECT>
                <P>Pursuant to section 10(d) of the Federal Advisory Committee Act, as amended (5 U.S.C. App.), notice is hereby given of the following meetings. </P>
                <P>The meetings will be closed to the public in accordance with the provisions set forth in sections 552b(c)(4) and 552b(c)(6), Title 5 U.S.C., as amended. The grant applications and the discussions could disclose confidential trade secrets or commercial property such as patentable material, and personal information concerning individuals associated with the grant applications, the disclosure of which would constitute a clearly unwarranted invasion of personal privacy.</P>
                <EXTRACT>
                    <P>
                        <E T="03">Name of Committee:</E>
                         National Institute of Allergy and Infectious Diseases Special Emphasis Panel, NIAID Investigator Initiated Program Project.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         July 8, 2011.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         11 a.m. to 5 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Place:</E>
                         National Institutes of Health, 6700B Rockledge Drive, Bethesda, MD 20817, (Telephone Conference Call).
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         James T. Snyder, PhD, Scientific Review Officer, Scientific Review Program, Division of Extramural Activities, DHHS/NIH/NIAID, 6700B Rockledge Drive, MSC 7616, Room #3257, Bethesda, MD 20892, 301-435-1614, 
                        <E T="03">james.snyder@nih.gov.</E>
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         National Institute of Allergy and Infectious Diseases Special Emphasis Panel, Disease Effector Mechanisms in SLE and Rheumatoid Arthritis.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         July 13, 2011.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         11 a.m. to 5 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Place:</E>
                         National Institutes of Health, 6700B Rockledge Drive, Bethesda, MD 20817, (Telephone Conference Call).
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Paul A. Amstad, PhD, Scientific Review Officer, Scientific Review Program, Division of Extramural Activities, NIAID/NIH/DHHS, 6700B Rockledge Drive, MSC 7616, Bethesda, MD 20892-7616, 301-402-7098, 
                        <E T="03">pamstad@niaid.nih.gov.</E>
                    </P>
                    <FP>(Catalogue of Federal Domestic Assistance Program Nos. 93.855, Allergy, Immunology, and Transplantation Research; 93.856, Microbiology and Infectious Diseases Research, National Institutes of Health, HHS)</FP>
                </EXTRACT>
                <SIG>
                    <DATED>Dated: June 10, 2011.</DATED>
                    <NAME>Jennifer S. Spaeth,</NAME>
                    <TITLE>Director, Office of Federal Advisory Committee Policy.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-15010 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4140-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>National Institutes of Health</SUBAGY>
                <SUBJECT>National Institute of Allergy and Infectious Diseases; Notice of Closed Meeting</SUBJECT>
                <P>Pursuant to section 10(d) of the Federal Advisory Committee Act, as amended (5 U.S.C. App.), notice is hereby given of the following meeting.</P>
                <P>The meeting will be closed to the public in accordance with the provisions set forth in sections 552b(c)(4) and 552b(c)(6), Title 5 U.S.C., as amended. The grant applications and the discussions could disclose confidential trade secrets or commercial property such as patentable material, and personal information concerning individuals associated with the grant applications, the disclosure of which would constitute a clearly unwarranted invasion of personal privacy.</P>
                <EXTRACT>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Microbiology, Infectious Diseases and AIDS Initial Review Group, Acquired Immunodeficiency Syndrome Research Review Committee.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         July 12, 2011.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         8:30 a.m. to 5 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Place:</E>
                         Hyatt Regency Bethesda, One Bethesda Metro Center, 7400 Wisconsin Avenue, Bethesda, MD 20814.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Sujata Vijh, PhD, Scientific Review Officer, Scientific Review Program, DEA/NIAID/NIH, 6700B Rockledge Drive, MSC 7616, Bethesda, MD 20892-7616, 301-594-0985, 
                        <E T="03">vijhs@niaid.nih.gov.</E>
                    </P>
                    <FP>(Catalogue of Federal Domestic Assistance Program Nos. 93.855, Allergy, Immunology, and Transplantation Research; 93.856, Microbiology and Infectious Diseases Research, National Institutes of Health, HHS)</FP>
                </EXTRACT>
                <SIG>
                    <PRTPAGE P="35225"/>
                    <DATED>Dated: June 10, 2011.</DATED>
                    <NAME>Jennifer S. Spaeth,</NAME>
                    <TITLE>Director, Office of Federal Advisory Committee Policy.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-15009 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4140-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>National Institutes of Health</SUBAGY>
                <SUBJECT>National Institute of Arthritis and Musculoskeletal and Skin Diseases; Notice of Closed Meeting</SUBJECT>
                <P>Pursuant to section 10(d) of the Federal Advisory Committee Act, as amended (5 U.S.C. App.), notice is hereby given of the following meeting.</P>
                <P>The meeting will be closed to the public in accordance with the provisions set forth in sections 552b(c)(4) and 552b(c)(6), Title 5 U.S.C., as amended. The grant applications and the discussions could disclose confidential trade secrets or commercial property such as patentable material, and personal information concerning individuals associated with the grant applications, the disclosure of which would constitute a clearly unwarranted invasion of personal privacy.</P>
                <EXTRACT>
                    <P>
                        <E T="03">Name of Committee:</E>
                         National Institute of Arthritis and Musculoskeletal and Skin Diseases, Special Emphasis Panel. Clinical Trials Planning Pilot and Research.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         July 12, 2011.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         8:30 a.m. to 5 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Place:</E>
                         Courtyard by Marriott, 5520 Wisconsin Avenue, Chevy Chase, MD 20815.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Charles N. Rafferty, PhD, Chief, Scientific Review Branch, National Institute of Arthritis, Musculoskeletal and Skin Diseases, National Institutes of Health, 6701 Democracy Boulevard, Suite 800, Bethesda, MD 20817, 301-594-5019, 
                        <E T="03">charles.rafferty@nih.gov.</E>
                    </P>
                    <FP>(Catalogue of Federal Domestic Assistance Program Nos. 93.846, Arthritis, Musculoskeletal and Skin Diseases Research, National Institutes of Health, HHS)</FP>
                </EXTRACT>
                <SIG>
                    <DATED>Dated: June 10, 2011.</DATED>
                    <NAME>Jennifer S. Spaeth,</NAME>
                    <TITLE>Director, Office of Federal Advisory Committee Policy.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-15008 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4140-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>National Institutes of Health</SUBAGY>
                <SUBJECT>National Institute of Environmental Health Sciences; Notice of Closed Meetings</SUBJECT>
                <P>Pursuant to section 10(d) of the Federal Advisory Committee Act, as amended (5 U.S.C. App.), notice is hereby given of the following meetings.</P>
                <P>The meetings will be closed to the public in accordance with the provisions set forth in sections 552b(c)(4) and 552b(c)(6), Title 5 U.S.C., as amended. The grant applications and the discussions could disclose confidential trade secrets or commercial property such as patentable material, and personal information concerning individuals associated with the grant applications, the disclosure of which would constitute a clearly unwarranted invasion of personal privacy.</P>
                <EXTRACT>
                    <P>
                        <E T="03">Name of Committee:</E>
                         National Institute of Environmental Health Sciences Special Emphasis Panel, Pathway to Independence/Career Development.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         July 14, 2011.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         11 a.m. to 2:25 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Place:</E>
                         NIEHS/National Institutes of Health, Keystone Building, 530 Davis Drive, Research Triangle Park, NC 27713, (Telephone Conference Call).
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Linda K. Bass, PhD, Scientific Review Administrator, Scientific Review Branch, Division of Extramural Research and Training, Nat. Institute Environmental Health Sciences, P.O. Box 12233, MD EC-30, Research Triangle Park, NC 27709, (919) 541-1307, 
                        <E T="03">bass@niehs.nih.gov.</E>
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         National Institute of Environmental Health Sciences Special Emphasis Panel, Research Careers in Environmental Health.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         July 14, 2011.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         2:30 p.m. to 5:30 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Place:</E>
                         NIEHS/National Institutes of Health, Keystone Building, 530 Davis Drive, Research Triangle Park, NC 27713, (Telephone Conference Call).
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Linda K. Bass, PhD, Scientific Review Administrator, Scientific Review Branch, Division of Extramural Research and Training, Nat. Institute Environmental Health Sciences, P.O. Box 12233, MD EC-30, Research Triangle Park, NC 27709, (919) 541-1307, 
                        <E T="03">bass@niehs.nih.gov.</E>
                    </P>
                    <FP>(Catalogue of Federal Domestic Assistance Program Nos. 93.115, Biometry and Risk Estimation—Health Risks from Environmental Exposures; 93.142, NIEHS Hazardous Waste Worker Health and Safety Training; 93.143, NIEHS Superfund Hazardous Substances—Basic Research and Education; 93.894, Resources and Manpower Development in the Environmental Health Sciences; 93.113, Biological Response to Environmental Health Hazards; 93.114, Applied Toxicological Research and Testing, National Institutes of Health, HHS)</FP>
                </EXTRACT>
                <SIG>
                    <DATED>Dated: June 10, 2011.</DATED>
                    <NAME>Jennifer S. Spaeth,</NAME>
                    <TITLE>Director, Office of Federal Advisory Committee Policy.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-15007 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4140-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>National Institutes of Health</SUBAGY>
                <SUBJECT>Center for Scientific Review; Notice of Closed Meetings</SUBJECT>
                <P>Pursuant to section 10(d) of the Federal Advisory Committee Act, as amended (5 U.S.C. App.), notice is hereby given of the following meetings.</P>
                <P>The meetings will be closed to the public in accordance with the provisions set forth in sections 552b(c)(4) and 552b(c)(6), Title 5 U.S.C., as amended. The grant applications and the discussions could disclose confidential trade secrets or commercial property such as patentable material, and personal information concerning individuals associated with the grant applications, the disclosure of which would constitute a clearly unwarranted invasion of personal privacy.</P>
                <EXTRACT>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel, Drug Discovery and Mechanisms of Antimicrobial Resistance Overflow.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         June 24, 2011.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         1 p.m. to 5 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Place:</E>
                         National Institutes of Health, 6701 Rockledge Drive, Bethesda, MD 20892. (Telephone Conference Call)
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Guangyong Ji, PhD, Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Room 3188, MSC 7808, Bethesda, MD 20892. 301-435-1146. 
                        <E T="03">jig@csr.nih.gov.</E>
                    </P>
                    <P>This notice is being published less than 15 days prior to the meeting due to the timing limitations imposed by the review and funding cycle.</P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         AIDS and Related Research Integrated Review Group, HIV/AIDS Vaccines Study Section.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         July 8, 2011.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         8:30 a.m. to 6 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Place:</E>
                         Ritz Carlton Hotel, 1150 22nd Street, NW., Washington, DC 20037.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Mary Clare Walker, PhD, Scientific Review Officer, Center for Scientific Review, National Institutes of 
                        <PRTPAGE P="35226"/>
                        Health, 6701 Rockledge Drive, Room 5208, MSC 7852, Bethesda, MD 20892. (301) 435-1165. 
                        <E T="03">walkermc@csr.nih.gov.</E>
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel, Fellowship: Oncological Sciences.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         July 18-19, 2011.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         8 a.m. to 6 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Place:</E>
                         Embassy Suites at the Chevy Chase Pavilion, 4300 Military Road, NW., Washington, DC 20015.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Allen Richon, PhD, Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Room 6184, MSC 7892, Bethesda, MD 20892. 301-435-1024. 
                        <E T="03">allen.richon@nih.hhs.gov.</E>
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel, Fellowships: Infectious Diseases and Microbiology.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         July 18-19, 2011.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         8:30 a.m. to 6 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Place:</E>
                         Avenue Hotel Chicago, 160 E. Huron Street, Chicago, IL 60611.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Alexander D Politis, PhD, Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Room 3210, MSC 7808, Bethesda, MD 20892. (301) 435-1150. 
                        <E T="03">politisa@csr.nih.gov.</E>
                    </P>
                    <FP>(Catalogue of Federal Domestic Assistance Program Nos. 93.306, Comparative Medicine; 93.333, Clinical Research, 93.306, 93.333, 93.337, 93.393-93.396, 93.837-93.844, 93.846-93.878, 93.892, 93.893, National Institutes of Health, HHS)</FP>
                </EXTRACT>
                <SIG>
                    <DATED>Dated: June 10, 2011.</DATED>
                    <NAME>Jennifer S. Spaeth,</NAME>
                    <TITLE>Director, Office of Federal Advisory Committee Policy.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-15005 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4140-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>National Institutes of Health</SUBAGY>
                <SUBJECT>Eunice Kennedy Shriver National Institute of Child Health &amp; Human Development; Notice of Meeting</SUBJECT>
                <P>Pursuant to section 10(a) of the Federal Advisory Committee Act, as amended (5 U.S.C. App.), notice is hereby given of a meeting of the National Children's Study Advisory Committee.</P>
                <P>
                    The meeting will be open to the public, with attendance limited to space available. Registration is required since space is limited and will begin at 8 a.m. Please visit the conference Web site for information on meeting logistics and to register for the meeting 
                    <E T="03">http://www.circlesolutions.com/ncs/ncsac/index.cfm</E>
                    . Individuals who plan to attend and need special assistance, such as sign language interpretation or other reasonable accommodations, should notify the Contact Person listed below in advance of the meeting.
                </P>
                <EXTRACT>
                    <P>
                        <E T="03">Name of Committee:</E>
                         National Children's Study Advisory Committee.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         July 20, 2011.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         9 a.m. to 5 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         The major topic to be discussed will be privacy and participant data, a revised sampling strategy, and a high-level discussion of the Main Study protocol.
                    </P>
                    <P>
                        <E T="03">Place:</E>
                         National Institutes of Health, Natcher Conference Center, 45 Center Drive, Room E1/E2, Bethesda, MD 20892.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Kate Winseck, MSW, Executive Secretary,  National Children's Study, Eunice Kennedy Shriver National Institute of  Child Health and Human Development, NIH, 6100 Executive Blvd., Room 5C01, Bethesda, MD 20892, (703) 902-1339,  
                        <E T="03">ncs@circlesolutions.com</E>
                        .
                    </P>
                    <P>
                        Any interested person may file written comments with the committee by forwarding the statement to the Contact Person listed on this notice. The statement should include the name, address, telephone number and when applicable, the business or professional affiliation of the interested person. For additional information about the Federal Advisory Committee meeting, please contact Circle Solutions at 
                        <E T="03">ncs@circlesolutions.com</E>
                        .
                    </P>
                    <FP>(Catalogue of Federal Domestic Assistance Program Nos. 93.864, Population Research; 93.865, Research for Mothers and Children; 93.929, Center for Medical Rehabilitation Research; 93.209, Contraception and Infertility Loan Repayment Program, National Institutes of Health, HHS)</FP>
                </EXTRACT>
                <SIG>
                    <DATED>Dated: June 9, 2011</DATED>
                    <NAME>Jennifer S. Spaeth,</NAME>
                    <TITLE>Director, Office of Federal Advisory Committee Policy.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-14875 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4140-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>National Institutes of Health</SUBAGY>
                <SUBJECT>National Institute on Drug Abuse; Notice of Closed Meetings</SUBJECT>
                <P>Pursuant to section 10(d) of the Federal Advisory Committee Act, as amended (5 U.S.C. App), notice is hereby given of the following meetings.</P>
                <P>The meetings will be closed to the public in accordance with the provisions set forth in sections 552b(c)(4) and 552b(c)(6), Title 5 USC, as amended. The grant applications and the discussions could disclose confidential trade secrets or commercial property such as patentable materials, and personal information concerning individuals associated with the grant applications, the disclosure of which would constitute a clearly unwarranted invasion of personal privacy.</P>
                <EXTRACT>
                    <P>
                        <E T="03">Name of Committee:</E>
                         National Institute on Drug Abuse Special Emphasis Panel, 2011 NIDA Avant-Garde Award Program for HIV/AIDS Research (DP1).
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         June 28, 2011.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         8:30 a.m. to 5 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Place:</E>
                         Westin Alexandria, 400 Courthouse Square, Alexandria, VA 22314.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Nadine Rogers, PhD, Scientific Review Administrator, Office of Extramural Affairs, National Institute on Drug Abuse, NIH, DHHS, Room 4229, MSC 9550, 6001 Executive Blvd., Bethesda, MD 20892-9550, 301-402-2105, 
                        <E T="03">rogersn2@nida.nih.gov</E>
                        .
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         National Institute on Drug Abuse Special Emphasis Panel, R01 and R34 Review.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         June 30, 2011.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         11 a.m. to 2 p.m
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Place:</E>
                         National Institutes of Health, Neuroscience Center, 6001 Executive Boulevard, Rockville, MD 20852, (Telephone Conference Call).
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Nataly Strunnikova, PhD, Scientific Review Officer, Office of Extramural Affairs, National Institute on Drug Abuse, NIH, DHHS, Room 4237, MSC 9550, 6001 Executive Blvd., Bethesda, MD 20892-9550, 301-402-0288, 
                        <E T="03">strunnikovan@nei.nih.gov</E>
                        .
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         National Institute on Drug Abuse Special Emphasis Panel, Medication Initiative for Tobacco Dependence (MITD): A New Product Development Partnership (PDP) (UH2/UH3).
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         July 7, 2011.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         8 a.m. to 5:30 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Place:</E>
                         Hyatt Regency Bethesda, One Bethesda Metro Center, 7400 Wisconsin Avenue, Bethesda, MD 20814.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Gerald L. McLaughlin, PhD, Scientific Review Officer, Office of Extramural Affairs, National Institute on Drug Abuse, NIH, DHHS, Room 4238, MSC 9550, 6001 Executive Blvd., Bethesda, MD 20892-9550, 301-402-6626, 
                        <E T="03">gm145a@nih.gov</E>
                        .
                    </P>
                    <FP>(Catalogue of Federal Domestic Assistance Program Nos.: 93.279, Drug Abuse and Addiction Research Programs, National Institutes of Health, HHS)</FP>
                </EXTRACT>
                <SIG>
                    <DATED>Dated: June 9, 2011.</DATED>
                    <NAME>Jennifer S. Spaeth,</NAME>
                    <TITLE>Director, Office of Federal Advisory Committee Policy.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-14868 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4140-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="35227"/>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>National Institutes of Health</SUBAGY>
                <SUBJECT>National Center for Complementary &amp; Alternative Medicine; Notice of Closed Meeting</SUBJECT>
                <P>Pursuant to section 10(d) of the Federal Advisory Committee Act, as amended (5 U.S.C. App.), notice is hereby given of the following meeting.</P>
                <P>The meeting will be closed to the public in accordance with the provisions set forth in sections 552b(c)(4) and 552b(c)(6), Title 5 U.S.C., as amended. The grant applications and the discussions could disclose confidential trade secrets or commercial property such as patentable material, and personal information concerning individuals associated with the grant applications, the disclosure of which would constitute a clearly unwarranted invasion of personal privacy.</P>
                <EXTRACT>
                    <P>
                        <E T="03">Name of Committee:</E>
                         National Center for Complementary and Alternative Medicine Special Emphasis Panel, NIH-HMO Collaboratory Coordinating Center (U54).
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         July 14, 2011.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         9 a.m. to 2:30 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate cooperative agreement applications.
                    </P>
                    <P>
                        <E T="03">Place:</E>
                         National Institutes of Health, Two Democracy Plaza, 6707 Democracy Boulevard, Bethesda, MD 20892 (Telephone Conference Call).
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Dale L. Birkle, PhD, Scientific Review Administrator, Office of Scientific Review, National Center for Complementary, and Alternative Medicine, NIH, 6707 Democracy Blvd., Suite 401, Bethesda, MD 20892, (301) 451-6570, 
                        <E T="03">birkled@mail.nih.gov.</E>
                    </P>
                    <FP>(Catalogue of Federal Domestic Assistance Program Nos. 93.213, Research and Training in Complementary and Alternative Medicine, National Institutes of Health, HHS)</FP>
                </EXTRACT>
                <SIG>
                    <DATED>Dated: June 13, 2011.</DATED>
                    <NAME>Jennifer S. Spaeth,</NAME>
                    <TITLE>Director, Office of Federal Advisory Committee Policy.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-15013 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4140-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>National Institutes of Health</SUBAGY>
                <SUBJECT>Center for Scientific Review; Notice of Closed Meetings</SUBJECT>
                <P>Pursuant to section 10(d) of the Federal Advisory Committee Act, as amended (5 U.S.C. App.), notice is hereby given of the following meetings.</P>
                <P>The meetings will be closed to the public in accordance with the provisions set forth in sections 552b(c)(4) and 552b(c)(6), Title 5 U.S.C., as amended. The grant applications and the discussions could disclose confidential trade secrets or commercial property such as patentable material, and personal information concerning individuals associated with the grant applications, the disclosure of which would constitute a clearly unwarranted invasion of personal privacy.</P>
                <EXTRACT>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel; Translational Research in Diabetes, Obesity and Endocrinology.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         July 14-15, 2011.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         8 a.m. to 12 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Place:</E>
                         National Institutes of Health, 6701 Rockledge Drive, Bethesda, MD 20892, (Virtual Meeting).
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Nancy Sheard, SCD, Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Room 6046-E, MSC 7892, Bethesda, MD 20892, 301-408-9901, 
                        <E T="03">sheardn@csr.nih.gov.</E>
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel; Small Business: Non-HIV Diagnostics, Food Safety, Sterilization/Disinfection and Bioremediation.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         July 20-21, 2011.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         8:30 a.m. to 5:30 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Place:</E>
                         Avenue Crowne Plaza Hotel, 160 East Huron, Chicago, IL 60611.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Gagan Pandya, PhD, Scientific Review Officer, National Institutes of Health, Center for Scientific Review, 6701 Rockledge Dr., RM 3200, Bethesda, MD 20892, 301-435-1167, 
                        <E T="03">pandyaga@mai.nih.gov.</E>
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel; Small Business: Non-HIV Microbial Vaccine Development.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         July 22, 2011.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         8 a.m. to 4:30 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Place:</E>
                         The Westin St. Francis, 335 Powell Street, San Francisco, CA 94102.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Scott Jakes, PhD, Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Room 4198, MSC 7812, Bethesda, MD 20892, 301-495-1506, 
                        <E T="03">jakesse@mail.nih.gov.</E>
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel; Small Business: Non-HIV Anti-Infective Therapeutics.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         July 22, 2011.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         8 a.m. to 6 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Place:</E>
                         Avenue Crowne Plaza Hotel and Suites, 160 East Huron Street, Chicago, IL 60611.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Kenneth M Izumi, PhD, Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Room 3204, MSC 7808, Bethesda, MD 20892, 301-496-6980, 
                        <E T="03">izumikm@csr.nih.gov.</E>
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel; Member Conflict: Immune Mechanism.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         July 22, 2011.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         4:30 p.m. to 5:30 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Place:</E>
                         The Westin St. Francis, 335 Powell Street, San Francisco, CA 94102.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Scott Jakes, PhD, Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Room 4198, MSC 7812, Bethesda, MD 20892, 301-495-1506, 
                        <E T="03">jakesse@mail.nih.gov.</E>
                    </P>
                    <FP>(Catalogue of Federal Domestic Assistance Program Nos. 93.306, Comparative Medicine; 93.333,Clinical Research, 93.306, 93.333, 93.337, 93.393-93.396, 93.837-93.844, 93.846-93.878, 93.892,93.893, National Institutes of Health, HHS)</FP>
                </EXTRACT>
                <SIG>
                    <DATED>Dated: June 10, 2011.</DATED>
                    <NAME>Jennifer S. Spaeth,</NAME>
                    <TITLE>Director, Office of Federal Advisory Committee Policy.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-15012 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4140-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>National Institutes of Health</SUBAGY>
                <SUBJECT>National Institute on Drug Abuse; Notice of Closed Meeting</SUBJECT>
                <P>Pursuant to section 10(d) of the Federal Advisory Committee Act, as amended (5 U.S.C. App), notice is hereby given of the following meeting.</P>
                <P>The meeting will be closed to the public in accordance with the provisions set forth in sections 552b(c)(4) and 552b(c)(6), Title 5 U.S.C., as amended. The contract proposals and the discussions could disclose confidential trade secrets or commercial property such as patentable materials, and personal information concerning individuals associated with the contract proposals, the disclosure of which would constitute a clearly unwarranted invasion of personal privacy.</P>
                <EXTRACT>
                    <P>
                        <E T="03">Name of Committee:</E>
                         National Institute on Drug Abuse Special Emphasis Panel, SecuRX: Preventing Prescription Drug Diversion (5560).
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         June 27, 2011.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         3 p.m. to 4:30 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate contract proposals.
                    </P>
                    <P>
                        <E T="03">Place:</E>
                         National Institutes of Health, Neuroscience Center, 6001 Executive Boulevard, Rockville, MD 20852 (Telephone Conference Call).
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Jose F. Ruiz, PhD, Scientific Review Officer, Office of Extramural Affairs, National Institute on Drug Abuse, NIH, Room 4228, MSC 9550, 
                        <PRTPAGE P="35228"/>
                        6001 Executive Blvd., Bethesda, MD 20892-9550, (301) 451-3086, 
                        <E T="03">ruizjf@nida.nih.gov.</E>
                    </P>
                    <FP>(Catalogue of Federal Domestic Assistance Program Nos.: 93.279, Drug Abuse and Addiction Research Programs, National Institutes of Health, HHS)</FP>
                </EXTRACT>
                <SIG>
                    <DATED>Dated: June 9, 2011.</DATED>
                    <NAME>Jennifer S. Spaeth,</NAME>
                    <TITLE>Director, Office of Federal Advisory Committee Policy.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-14870 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4140-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>National Institutes of Health</SUBAGY>
                <SUBJECT>Center for Scientific Review; Notice of Closed Meetings</SUBJECT>
                <P>Pursuant to section 10(d) of the Federal Advisory Committee Act, as amended (5 U.S.C. App.), notice is hereby given of the following meetings.</P>
                <P>The meetings will be closed to the public in accordance with the provisions set forth in sections 552b(c)(4) and 552b(c)(6), Title 5 U.S.C., as amended. The grant applications and the discussions could disclose confidential trade secrets or commercial property such as patentable material, and personal information concerning individuals associated with the grant applications, the disclosure of which would constitute a clearly unwarranted invasion of personal privacy.</P>
                <EXTRACT>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel, Program Project: Mechanisms of Drug Disposition During Pregnancy.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         July 13, 2011.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         12 p.m. to 3 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Place:</E>
                         National Institutes of Health, 6701 Rockledge Drive, Bethesda, MD 20892. (Telephone Conference Call).
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                          
                    </P>
                    <P>
                        Patricia Greenwel, PhD, Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Room 2178, MSC 7818, Bethesda, MD 20892, 301-435-1169, 
                        <E T="03">greenwep@csr.nih.gov.</E>
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel, Small Business: Cancer Diagnostics and Treatments (CDT).
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         July 14-15, 2011.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         10 a.m. to 6 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Place:</E>
                         National Institutes of Health, 6701 Rockledge Drive, Bethesda, MD 20892, (Virtual Meeting).
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Zhang-Zhi Hu, MD, Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Room 6186, MSC 7804, Bethesda, MD 20892, (301) 594-2414, 
                        <E T="03">huzhuang@csr.nih.gov.</E>
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel, Fellowships: Physiology and Pathobiology of Musculoskeletal, Oral, and Skin Systems.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         July 15, 2011.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         8 a.m. to 5 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Place:</E>
                         The Ritz-Carlton Washington DC, 1150 22nd Street, NW., Washington, DC 20037. 
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Abdelouahab Aitouche, PhD, Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Room 4222, MSC 7812, Bethesda, MD 20892, 301-435-2365, 
                        <E T="03">aitouchea@csr.nih.gov.</E>
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel, Fellowships: Risk Prevention and Health Behavior.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         July 15, 2011.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         8 a.m. to 5 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Place:</E>
                         Crowne Plaza Tyson's Corner, 1960 Chain Bridge Road, Mclean, VA 22102. 
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Martha M Faraday, PhD, Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Room 3110, MSC 7808, Bethesda, MD 20892, 301-435-3575, 
                        <E T="03">faradaym@csr.nih.gov.</E>
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel, Small Business: Diabetes, Obesity and Reproductive Sciences,
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         July 15, 2011,
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         8 a.m. to 5 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Place:</E>
                         Hyatt Regency Bethesda, One Bethesda Metro Center, 7400 Wisconsin Avenue, Bethesda, MD 20814.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Krish Krishnan, PhD, Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Room 6164, MSC 7892, Bethesda, MD 20892, (301) 435-1041, 
                        <E T="03">krishnak@csr.nih.gov.</E>
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel, Fellowships: Health and Health Related Behavior of Individuals and Populations.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         July 15, 2011.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         8 a.m. to 6 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Place:</E>
                         Hotel Monaco Alexandria, 480 King Street, Alexandria, VA 22314. 
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Karin F Helmers, PhD, Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Room 3166, MSC 7770, Bethesda, MD 20892, 301-254-9975, 
                        <E T="03">helmersk@csr.nih.gov.</E>
                    </P>
                    <FP>(Catalogue of Federal Domestic Assistance Program Nos. 93.306, Comparative Medicine; 93.333, Clinical Research, 93.306, 93.333, 93.337, 93.393-93.396, 93.837-93.844, 93.846-93.878, 93.892, 93.893, National Institutes of Health, HHS)</FP>
                </EXTRACT>
                <SIG>
                    <DATED>Dated:  June 8, 2011.</DATED>
                    <NAME>Jennifer S. Spaeth,</NAME>
                    <TITLE>Director, Office of Federal Advisory Committee Policy.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-14872 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4140-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
                <SUBAGY>Coast Guard</SUBAGY>
                <DEPDOC>[USCG-2011-0494]</DEPDOC>
                <SUBJECT>Information Collection Request to Office of Management and Budget</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Coast Guard, DHS.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Sixty-day notice requesting comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>In compliance with the Paperwork Reduction Act of 1995, the U.S. Coast Guard intends to submit an Information Collection Request (ICR) to the Office of Management and Budget (OMB), Office of Information and Regulatory Affairs (OIRA), requesting approval of revisions to the following collection of information: 1625-0009, Oil Record Book for Ships. Our ICR describes the information we seek to collect from the public. Before submitting this ICR to OIRA, the Coast Guard is inviting comments as described below.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must reach the Coast Guard on or before August 15, 2011.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may submit comments identified by Coast Guard docket number [USCG-2011-0494] to the Docket Management Facility (DMF) at the U.S. Department of Transportation (DOT). To avoid duplicate submissions, please use only one of the following means:</P>
                    <P>
                        (1) 
                        <E T="03">Online: http://www.regulations.gov.</E>
                    </P>
                    <P>
                        (2) 
                        <E T="03">Mail:</E>
                         DMF (M-30), DOT, West Building Ground Floor, Room W12-140, 1200 New Jersey Avenue, SE., Washington, DC 20590-0001.
                    </P>
                    <P>
                        (3) 
                        <E T="03">Hand delivery:</E>
                         Same as mail address above, between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays. The telephone number is 202-366-9329.
                    </P>
                    <P>
                        (4) 
                        <E T="03">Fax:</E>
                         202-493-2251. To ensure your comments are received in a timely manner, mark the fax, to attention Desk Officer for the Coast Guard.
                    </P>
                    <P>
                        The DMF maintains the public docket for this Notice. Comments and material received from the public, as well as documents mentioned in this Notice as being available in the docket, will become part of the docket and will be available for inspection or copying at 
                        <PRTPAGE P="35229"/>
                        room W12-140 on the West Building Ground Floor, 1200 New Jersey Avenue, SE., Washington, DC, between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays. You may also find the docket on the Internet at 
                        <E T="03">http://www.regulations.gov.</E>
                    </P>
                    <P>
                        A copy of the ICR is available through the docket on the Internet at 
                        <E T="03">http://www.regulations.gov.</E>
                         Additionally, copies are available from: Commandant (CG-611), ATTN: Paperwork Reduction Act Manager, US Coast Guard, 2100 2nd Street, SW., Stop 7101, Washington, DC 20593-7101.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Ms. Kenlinishia Tyler, Office of Information Management, telephone 202-475-3652, or fax 202-475-3929, for questions on these documents. Contact Ms. Renee V. Wright, Program Manager, Docket Operations, 202-366-9826, for questions on the docket.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Public Participation and Request for Comments</HD>
                <P>This Notice relies on the authority of the Paperwork Reduction Act of 1995; 44 U.S.C. Chapter 35, as amended. An ICR is an application to OIRA seeking the approval, extension, or renewal of a Coast Guard collection of information (Collection). The ICR contains information describing the Collection's purpose, the Collection's likely burden on the affected public, an explanation of the necessity of the Collection, and other important information describing the Collection. There is one ICR for each Collection.</P>
                <P>The Coast Guard invites comments on whether this ICR should be granted based on the Collection being necessary for the proper performance of Departmental functions. In particular, the Coast Guard would appreciate comments addressing: (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 information subject to the Collection; and (4) ways to minimize the burden of the Collection on respondents, including the use of automated collection techniques or other forms of information technology. In response to your comments, we may revise this ICR or decide not to seek approval of revisions of the Collection. We will consider all comments and material received during the comment period.</P>
                <P>
                    We encourage you to respond to this request by submitting comments and related materials. Comments must contain the OMB Control Number of the ICR and the docket number of this request, [USCG-2011-0494], and must be received by August 15, 2011. We will post all comments received, without change, to 
                    <E T="03">http://www.regulations.gov.</E>
                     They will include any personal information you provide. We have an agreement with DOT to use their DMF. Please see the “Privacy Act” paragraph below.
                </P>
                <HD SOURCE="HD1">Submitting Comments</HD>
                <P>
                    If you submit a comment, please include the docket number [USCG-2011-0494], indicate the specific section of the document to which each comment applies, providing a reason for each comment. If you submit a comment online via 
                    <E T="03">http://www.regulations.gov,</E>
                     it will be considered received by the Coast Guard when you successfully transmit the comment. If you fax, hand deliver, or mail your comment, it will be considered as having been received by the Coast Guard when it is received at the DMF. We recommend you include your name, mailing address, an e-mail address, or other contact information in the body of your document so that we can contact you if we have questions regarding your submission.
                </P>
                <P>
                    You may submit your comments and material by electronic means, mail, fax, or hand delivery to the DMF at the address under 
                    <E T="02">ADDRESSES</E>
                    ; but please submit them by only one means. To submit your comment online, go to 
                    <E T="03">http://www.regulations.gov,</E>
                     and type “USCG-2011-0494” in the “Keyword” box. If you submit your comments by mail or hand delivery, submit them in an unbound format, no larger than 8
                    <FR>1/2</FR>
                     by 11 inches, suitable for copying and electronic filing. If you submit comments by mail and would like to know that they reached the Facility, please enclose a stamped, self-addressed postcard or envelope. We will consider all comments and material received during the comment period and will address them accordingly.
                </P>
                <HD SOURCE="HD1">Viewing Comments and Documents</HD>
                <P>
                    To view comments, as well as documents mentioned in this Notice as being available in the docket, go to 
                    <E T="03">http://www.regulations.gov,</E>
                     click on the “read comments” box, which will then become highlighted in blue. In the “Keyword” box insert “USCG-2011-0494” and click “Search.” Click the “Open Docket Folder” in the “Actions” column. You may also visit the DMF in Room W12-140 on the ground floor of the DOT West Building, 1200 New Jersey Avenue, SE., Washington, DC 20590, between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays.
                </P>
                <HD SOURCE="HD1">Privacy Act</HD>
                <P>
                    Anyone can search the electronic form of comments received in dockets by the name of the individual submitting the comment (or signing the comment, if submitted on behalf of an association, business, labor union, 
                    <E T="03">etc.</E>
                    ). You may review a Privacy Act statement regarding Coast Guard public dockets in the January 17, 2008, issue of the 
                    <E T="04">Federal Register</E>
                     (73 FR 3316).
                </P>
                <HD SOURCE="HD1">Information Collection Request</HD>
                <P>
                    <E T="03">Title:</E>
                     Oil Record Book for Ships.
                </P>
                <P>
                    <E T="03">OMB Control Number:</E>
                     1625-0009.
                </P>
                <P>
                    <E T="03">Summary:</E>
                     The Act to Prevent Pollution from Ships (APPS) and the International Convention for Prevention of Pollution from Ships, 1973, as modified by the 1978 Protocol relating thereto (MARPOL 73/78), requires that information about oil cargo or fuel operations be entered into an Oil Record Book (CG-4602A). The requirement is contained in 33 CFR 151.25.
                </P>
                <P>
                    <E T="03">Need:</E>
                     This information is used to verify sightings of actual violations of the APPS to determine the level of compliance with MARPOL 73/78 and as a means of reinforcing the discharge provisions.
                </P>
                <P>
                    <E T="03">Forms:</E>
                     CG-4602A.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Operators of vessels.
                </P>
                <P>
                    <E T="03">Frequency:</E>
                     On occasion.
                </P>
                <P>
                    <E T="03">Burden Estimate:</E>
                     The estimated burden has increased from 19,425 hours to 20,221 hours a year.
                </P>
                <SIG>
                    <DATED>Dated: June 9, 2011.</DATED>
                    <NAME>C.A. Mathieu,</NAME>
                    <TITLE>Captain, U.S. Coast Guard, Acting Assistant Commandant for Command, Control, Communications, Computers and Information Technology.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-14924 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 9110-04-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
                <SUBAGY>Transportation Security Administration</SUBAGY>
                <SUBJECT>Intent to Request Renewal and Amendment From OMB of One Current Public Collection of Information: Critical Facility Information of the Top 100 Most Critical Pipelines</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Transportation Security Administration, DHS.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>60-day Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The Transportation Security Administration (TSA) invites public comment on one currently approved Information Collection Request (ICR), Office of Management and Budget (OMB) control number 1652-0050, abstracted below that we will submit to 
                        <PRTPAGE P="35230"/>
                        OMB for renewal and amendment in compliance with the Paperwork Reduction Act (PRA). The ICR describes the nature of the information collection and its expected burden. The 9/11 Act required TSA to develop and implement a plan to inspect critical pipeline systems.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Send your comments by August 15, 2011.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Comments may be e-mailed to 
                        <E T="03">TSAPRA@dhs.gov</E>
                         or delivered to the TSA PRA Officer, Office of Information Technology (OIT), TSA-11, Transportation Security Administration, 601 South 12th Street, Arlington, VA 20598-6011.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Joanna Johnson at the above address, or by telephone (571) 227-3651.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <HD SOURCE="HD1">Comments Invited</HD>
                <P>
                    In accordance with the Paperwork Reduction Act of 1995 (44 U.S.C. 3501 
                    <E T="03">et seq.</E>
                    ), an agency may not conduct or sponsor, and a person is not required to respond to, a collection of information unless it displays a valid OMB control number. The ICR documentation is available at 
                    <E T="03">http://www.reginfo.gov.</E>
                     Therefore, in preparation for OMB review and approval of the following information collection, TSA is soliciting comments to—
                </P>
                <P>(1) Evaluate whether the proposed information requirement 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 the agency's estimate of the burden;</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, including using appropriate automated, electronic, mechanical, or other technological collection techniques or other forms of information technology.</P>
                <HD SOURCE="HD1">Information Collection Requirement</HD>
                <P>
                    <E T="03">OMB Control Number 1652-0050; Critical Facility Information of the Top 100 Most Critical Pipelines:</E>
                     Section 1557(b) of the Implementing the Recommendations of the 9/11 Commission Act of 2007, specifically tasked TSA to develop and implement a plan for inspecting critical facilities of the 100 most critical pipeline systems. See Public Law 110-53, 121 Stat. 266, 475 (Aug. 3, 2007). Operators determined their critical facilities based on guidance and criteria set forth in the Department of Transportation's (DOT) September 5, 2002, “Pipeline Security Information Circular” and June 2002 “Pipeline Security Contingency Planning Guidance.” With OMB approval (OMB Control Number 1652-0050), TSA reached out to the operators of the top 125 critical pipeline systems and requested they submit a listing of their critical facilities to TSA. This critical facility information was submitted to TSA between November 2008 and August 2009. In April 2011, TSA updated the “Pipeline Security Guidelines” in consultation with stakeholders and DOT. TSA is now seeking to renew its OMB approval to request critical facility information from the top 125 pipeline operators. TSA anticipates that each operator will report, on average, a total of 5 critical facilities on their system, for a total of approximately 600 critical facilities across the top 125 operators.
                </P>
                <P>Once updated critical facility information is obtained, TSA intends to visit critical pipeline facilities and collect site-specific information from pipeline operators on facility security policies, procedures, and physical security measures. Information obtained on the visits will be collected on a Critical Facility Security Review (CFSR) Form. The CFSR will differ from TSA's Corporate Security Review (CSR) in that a CSR looks at corporate or company-wide security management plans and practices while the CFSR will look at individual pipeline facility security measures and procedures. TSA is seeking OMB approval to utilize the CFSR document during critical facility reviews in order to collect facility security information. Information collected from the reviews would be analyzed and used to determine strengths and weaknesses at the nation's critical pipeline facilities, areas to target for risk reduction strategies, pipeline industry implementation of the voluntary guidelines, and the need for regulations in accordance with Section 1557(d) of the Implementing the Recommendations of the 9/11 Commission Act of 2007. TSA anticipates visiting 120 critical facilities each year.</P>
                <P>TSA is also seeking OMB approval to follow up with pipeline operators on their implementation of security improvements and recommendations made during facility visits. During critical facility visits, TSA documents and provides recommendations to improve the security posture of the facility. TSA intends to follow up with pipeline operators via email on their status toward implementation of the recommendations made during the critical facility visits. The follow up will be conducted between approximately 12 and 24 months after the facility visit.</P>
                <P>TSA will use the information collected to determine to what extent the pipeline industry is implementing the 2011 guidance document and security improvement recommendations made during critical facility visits. The information provided by owners or operators for each information collection is Sensitive Security Information (SSI), and it will be protected in accordance with procedures meeting the transmission, handling and storage requirements of SSI set forth in 49 CFR parts 15 and 1520.</P>
                <P>The burden related to the renewal of the collection for updated critical facility information from the top 125 pipeline system operators will require 4 hours per operator (125 × 4), for a burden of 500 hours in the first year only.</P>
                <P>The annual burden for the approval of the information collection related to the Critical Facility Review Form is estimated to be 480 hours. A maximum of 120 facility reviews will be conducted each year with each review taking approximately 4 hours (120 × 4).</P>
                <P>The annual burden for the approval of the information collection related to the follow up on the recommendations made to facility operators is estimated to be 600 hours. It will take approximately 5 hours for each operator to submit a response to TSA regarding its implementation of security recommendations made during critical facility visits. If a maximum of 120 critical facilities are reviewed each year, and TSA follows up with each facility operator between approximately 12 and 24 months following the visit, the total annual burden is 600 (120 × 5) hours. An additional burden of 1,750 hours is estimated in the first year only for information collection on the follow up of the recommendations made during the 350 facility visits conducted in accordance with the requirement in the 9/11 Act (350 × 5 = 1,750). The estimated number of respondents will be 125 for the renewal of the critical facility data and 600 for the critical facility review form and recommendations. The total estimated burdens are 2,730 hours in the first year and 1,080 hours annually in subsequent years.</P>
                <SIG>
                    <DATED>Issued in Arlington, Virginia, on June 13, 2011.</DATED>
                    <NAME>Joanna Johnson,</NAME>
                    <TITLE>TSA Paperwork Reduction Act Officer, Office of Information Technology.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-14996 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 9110-05-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="35231"/>
                <AGENCY TYPE="N">DEPARTMENT OF HOUSING AND URBAN DEVELOPMENT</AGENCY>
                <DEPDOC>[Docket No. FR-5481-N-09]</DEPDOC>
                <SUBJECT>Notice of Proposed Information Collection for Public Comment; McKinney-Vento Technical Assistance Narrative, Matrices, and Reporting Requirements</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of the Assistant Secretary for Community Planning and Development, U.S. Department of Housing and Urban Development (HUD).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of proposed information collection.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The proposed information collection requirement described below will be submitted to the Office of Management and Budget (OMB) for review, as required by the Paperwork Reduction Act. The Department is soliciting public comments on the subject proposal.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        <E T="03">Comments Due Date:</E>
                         August 15, 2011.
                    </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Interested persons are invited to submit comments regarding this proposal. Comments should refer to the proposal by name/or OMB Control number and should be sent to: Colette Pollard, Departmental Reports Management Officer, QDAM, U.S. Department of Housing and Urban Development, 451 7th Street, SW., Room 4160, Washington, DC 20410-5000; telephone (202) 402-3400, (this is not a toll-free number) or e-mail Ms. Pollard at 
                        <E T="03">Colette_Pollard@hud.gov</E>
                         for a copy of proposed forms, or other available information. Persons with hearing or speech impairments may access this number through TTY by calling the toll-free Federal Information Relay Service at (800) 877-8339.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Ann Marie Oliva, Director, Office of Special Needs Assistance Programs, Office of Community Planning and Development, U.S. Department of Housing and Urban Development, 451 7th Street, SW., Room 7262, Washington, DC 20410; telephone (202) 708-1590 (this is not a toll-free number).</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    The Department will submit the proposed information collection to OMB for review, as required by the Paperwork Reduction Act of 1995 (44 U.S.C. chapter 35, as amended). This Notice is soliciting comments from members of the public and affected agencies concerning the proposed collection of information to: (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; (2) evaluate the accuracy of the agency's estimate of the burden of the proposed collection of information; (3) enhance the quality, utility, and clarity of the information to be collected; and (4) minimize the burden of the collection of information on those who are to respond, including through the use of appropriate automated collection techniques or other forms of information technology, 
                    <E T="03">e.g.,</E>
                     permitting electronic submission of responses. This Notice also lists the following information:
                </P>
                <P>
                    <E T="03">Title of Proposal:</E>
                     McKinney-Vento Technical Assistance Narrative, Matrices, and Reporting Requirements.
                </P>
                <P>
                    <E T="03">Description of the need for the information proposed:</E>
                     McKinney-Vento Technical Assistance (MV-TA) Narrative, Matrices, and Reporting Requirements will allow the Office of Special Needs Assistance Programs (SNAPS) to accurately assess the experience, expertise, and overall capacity of applicants applying for technical assistance funding under the FY2011 McKinney-Vento Technical Assistance Notice of Funding Availability (NOFA). They will also allow SNAPS to monitor and evaluate TA progress over the course of the grant and make necessary interventions. The new format for this type of collection also makes it easier for applicants to apply and report by reducing the time required for filling out an application and reporting forms, while retaining the utility of previous collection methods.
                </P>
                <HD SOURCE="HD1">Agency Form Numbers</HD>
                <P>
                    <E T="03">Members of the affected public:</E>
                     Private for-profit, not-for-profit, and public entities applying for funding as technical assistance providers under the FY2011 MV-TA NOFA.
                </P>
                <P>
                    <E T="03">Estimation of the total number of hours needed to prepare the information collection including number of respondents, frequency of response, and hours of response:</E>
                     10 applicants × 4,080 minutes per response + 5 grant recipients × 3,600 minutes per reporting year = 58,800 total minutes per year or 980 hours per year.
                </P>
                <P>
                    <E T="03">Status of proposed information collection:</E>
                     New Collection
                </P>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P> Section 3506 of the Paperwork Reduction act of 1995, 44 U.S.C. chapter 35, as amended.</P>
                </AUTH>
                <SIG>
                    <DATED>Dated: June 8, 2011. </DATED>
                    <NAME>Clifford D. Taffet,</NAME>
                    <TITLE>General Deputy Assistant Secretary for Community Planning and Development.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-14905 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4210-67-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HOUSING AND URBAN DEVELOPMENT</AGENCY>
                <DEPDOC>[Docket No. FR-5480-N-51]</DEPDOC>
                <SUBJECT>Notice of Submission of Proposed Information Collection to OMB Section 3 Business Self-Certification Application</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of the Chief Information Officer, HUD.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The proposed information collection requirement described below has been submitted to the Office of Management and Budget (OMB) for review, as required by the Paperwork Reduction Act. The Department is soliciting public comments on the subject proposal.</P>
                    <P>The information collected from the Section 3 Business Self-Certification Application will allow HUD and recipients of covered HUD funding to identify Section 3 Businesses within their communities. The overriding purpose of this information collection is to ensure that contracting opportunities are provided to Section 3 businesses in fulfillment of the regulatory requirements set forth at 24 CFR part 135, and to increase the capacity of covered agencies to comply with the requirements of Section 3. HUD will use the information to identify firms that self-certify that they meet the regulatory definition of a Section 3 Business. The information collected from the Section 3 Business Self-Certification Application will be posted in a registry of Section 3 Businesses which will be posted on HUD's webpage. Agencies that receive covered HUD funding in the five pilot locations will be encouraged to notify the Section 3 Businesses contained in HUD's registry about the availability of covered contracting opportunities.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        <E T="03">Comments Due Date:</E>
                         July 18, 2011.
                    </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Interested persons are invited to submit comments regarding this proposal.</P>
                    <P>
                        Comments should refer to the proposal by name and/or OMB approval Number (2529-Pending) and should be sent to: HUD Desk Officer, Office of Management and Budget, New Executive Office Building, Washington, DC 20503; 
                        <E T="03">e-mail: OIRA-Submission@omb.eop.gov,</E>
                         fax: 202-395-5806.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Colette Pollard, Reports Management Officer, QDAM, Department of Housing and Urban Development, 451 Seventh Street, SW., Washington, DC 20410; 
                        <E T="03">e-mail:</E>
                         Colette Pollard at 
                        <PRTPAGE P="35232"/>
                        <E T="03">Colette.Pollard@hud.gov;</E>
                         or 
                        <E T="03">telephone:</E>
                         (202) 402-3400. This is not a toll-free number. Copies of available documents submitted to OMB may be obtained from Ms. Pollard.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    This notice informs the public that the Department of Housing and Urban Development has submitted to OMB a request for approval of the Information collection described below. This notice is soliciting comments from members of the public and affecting agencies concerning the proposed collection of information to: (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; (2) Evaluate the accuracy of the agency's estimate of the burden of the proposed collection of information; (3) Enhance the quality, utility, and clarity of the information to be collected; and (4) Minimize the burden of the collection of information on those who are to respond, including through the use of appropriate automated collection techniques or other forms of information technology, 
                    <E T="03">e.g.,</E>
                     permitting electronic submission of responses.
                </P>
                <P>This notice also lists the following information:</P>
                <P>
                    <E T="03">Title of Proposal:</E>
                     Section 3 Business Self-Certification Application.
                </P>
                <P>
                    <E T="03">OMB Approval Number:</E>
                     2529-Pending.
                </P>
                <P>
                    <E T="03">Form Numbers:</E>
                     None.
                </P>
                <P>
                    <E T="03">Description of the Need for the Information and Its Proposed Use:</E>
                     The information collected from the Section 3 Business Self-Certification Application will allow HUD and recipients of covered HUD funding to identify Section 3 Businesses within their communities. The overriding purpose of this information collection is to ensure that contracting opportunities are provided to Section 3 businesses in fulfillment of the regulatory requirements set forth at 24 CFR part 135, and to increase the capacity of covered agencies to comply with the requirements of Section 3. HUD will use the information to identify firms that self-certify that they meet the regulatory definition of a Section 3 Business. The information collected from the Section 3 Business Self-Certification Application will be posted in a registry of Section 3 Businesses which will be posted on HUD's webpage. Agencies that receive covered HUD funding in the five pilot locations will be encouraged to notify the Section 3 Businesses contained in HUD's registry about the availability of covered contracting opportunities.
                </P>
                <P>
                    <E T="03">Frequency of Submission:</E>
                     On occasion.
                </P>
                <P>
                    <E T="03">Estimation of the Total Numbers of Hours Needed To Prepare the Information Collection Including Number of Respondents, Frequency of Responses, and Hours of Responses:</E>
                     The Department estimates that approximately 20,000 businesses in the five pilot locations may complete the Section 3 Self-Certification Application during the six-month pilot program.
                </P>
                <P>It is estimated that each application will take approximately 30 minutes to complete for a total of 10,000 hours.</P>
                <P>
                    <E T="03">Total Estimated Burden Hours:</E>
                     10,000.
                </P>
                <P>
                    <E T="03">Status:</E>
                     New collection.
                </P>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P>Section 3507 of the Paperwork Reduction Act of 1995, 44 U.S.C. 35, as amended.</P>
                </AUTH>
                <SIG>
                    <DATED>Dated: June 09, 2011.</DATED>
                    <NAME>Colette Pollard,</NAME>
                    <TITLE>Departmental Reports Management Officer, Office of the Chief Information Officer.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-14909 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4210-67-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HOUSING AND URBAN DEVELOPMENT</AGENCY>
                <DEPDOC>[Docket No. FR-5486-N-14]</DEPDOC>
                <SUBJECT>Notice of Proposed Information Collection for Public Comment; Housing Choice Voucher Program Administrative Fee Study Pretest</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of the Policy Development and Research, HUD.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The proposed information collection requirement described below will be submitted to the Office of Management and Budget (OMB) for review, as required by the Paperwork Reduction Act. The Department is soliciting public comments on the subject proposal.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        <E T="03">Comments Due Date:</E>
                         August 15, 2011.
                    </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Interested persons are invited to submit comments regarding this proposal. Comments should refer to the proposal by name and/or OMB Control number and should be sent to: Reports Liaison Officer, Office of Policy Development &amp; Research, Department of Housing and Urban Development, 451 7th Street, SW., Room 8226, Washington, DC 20410-5000.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Marina L. Myhre, (202) 402-5705 for copies of the proposed forms and other available documents. (This is not a toll-free number.)</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    The Department will submit the proposed information collection to OMB for review, as required by the Paperwork Reduction Act of 1995 (44 U.S.C. chapter 35, as amended). This Notice is soliciting comments from members of the public and affected agencies concerning the proposed collection of information to: (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; (2) Evaluate the accuracy of the agency's estimate of the burden of the proposed collection of information; (3) Enhance the quality, utility, and clarity of the information to be collected; and (4) Minimize the burden of the collection of information on those who are to respond, including through the use of appropriate automated collection techniques or other forms of information technology (
                    <E T="03">e.g.,</E>
                     permitting electronic submission of responses).
                </P>
                <P>This Notice also lists the following information:</P>
                <P>
                    <E T="03">Title of Proposal:</E>
                     Housing Choice Voucher Program Administrative Fee Study Pretest.
                </P>
                <P>
                    <E T="03">Description of the Need for the Information and Proposed Use:</E>
                     This request is for the clearance of on-site data collection from public housing agencies (PHAs) to test the methodology for the Housing Choice Voucher (HCV) Program Administrative Fee study. The purpose of the study is to collect accurate information on the costs of administering the HCV program across a representative sample of high performing and efficient PHAs and to use this information to develop a new administrative fee allocation formula for the HCV program. The study is proceding in multiple phases. This request is for data collection to test the methodology for estimating program costs in the study. We propose to use two main methods for collecting cost data: (1) Measuring the time that front line staff spend working on the program and translating that time into costs using the salaries and benefits of the staff doing the work and adjusting for market factors; and (2) collecting information via interviews and document review on the overhead costs and other costs related to HCV program administration that cannot be captured by measuring staff time spent on the program. We will test these data collection approaches at between 5 and 10 PHAs across the country. The results of the pretest will be used to refine the methodology used for the full study of 
                    <PRTPAGE P="35233"/>
                    administrative fees with a larger sample of PHAs.
                </P>
                <P>
                    <E T="03">OMB Approval Number:</E>
                     Pending.
                </P>
                <P>
                    <E T="03">Agency Form Numbers:</E>
                     None.
                </P>
                <P>
                    <E T="03">Members of Affected Public:</E>
                     Up to 250 PHA staff persons across up to 10 PHAs.
                </P>
                <P>
                    <E T="03">Estimation of the Total Number of Hours Needed To Prepare the Information Collection Including Number of Respondents, Frequency of Response, and Hours of Response:</E>
                     We plan to conduct the pretest at 5 to 10 PHAs across the country. The pretest will involve a combination of on-site and telephone data collection from PHA staff through interviews, observation, and self-reporting of time spent working on the HCV program via timesheets and other methods. There are five data collection activities that involve PHA staff. First, at each pretest site, PHA staff will spend up to 32 hours assembling data for the study and being interviewed by the study team (32 hours  ×  10 sites = 320 hours). Second, at each site up to 15 staff will be observed in their work for up to four weeks (28 working days). These staff will engage with the researchers for approximately 15 minutes per day, for a total of 7 hours per staff over four weeks (7 hours  ×  15 staff  ×  10 sites = 1,050 hours). Third, at each site up to 15 staff will complete timesheets or respond to messages via a SmartPhone for a period of approximately two months (45 working days). These activities will take approximately 15 minutes per day, for a total of 11.25 hours per staff over the two-month period (11.25 hours  ×  15 staff  ×  10 sites = 1,688 hours). Fourth, all staff involved in time measurement activities will participate in up to 2 hours of training or preparation activities (2 hours  ×  30 staff  ×  10 sites = 600 hours). Fifth, an average of 10 PHA staff per site will spend approximately 60 minutes debriefing with the research team about their experiences with the pretest (1 hour  ×  10 staff  ×  10 sites = 100 hours). The total estimated burden across all proposed data collection activities is 3,758 hours.
                </P>
                <P>
                    <E T="03">Status of the Proposed Information Collection:</E>
                     Pending OMB approval.
                </P>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P>U.S. Code 12, 1701z-1, Research and demonstrations.</P>
                </AUTH>
                <SIG>
                    <DATED>Dated: June 9, 2011.</DATED>
                    <NAME>Raphael W. Bostic,</NAME>
                    <TITLE>Assistant Secretary for Policy Development and Research.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-14906 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4210-67-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HOUSING AND URBAN DEVELOPMENT</AGENCY>
                <DEPDOC>[Docket No. FR-5500-N-13]</DEPDOC>
                <SUBJECT>Notice of Funding Availability (NOFA) for HUD's Fiscal Year 2011; Housing Opportunities for Persons With AIDA (HOPWA)</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of the Chief of the Human Capital Officer, HUD.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>HUD announces the availability on its Web site of the applicant information, submission deadlines, funding criteria, and other requirements for HUD's FY2011 Housing for Persons with AIDS (HOPWA) Program NOFA. Specifically, this NOFA announces the availability of approximately $9.1 million made available under the Department of Defense and Full-Year Continuing Appropriations Act, 2011, Public Law 112-10, approved April 15, 2011 for the Housing for Persons with AIDS (HOPWA) Program.</P>
                    <P>
                        The purpose of the HOPWA program is to advance HUD's implementation of the National HIV/AIDS Strategy (NHAS). HOPWA NOFA also addresses the Department's Fiscal Year 2010-2015 Strategic Plan and the 
                        <E T="03">Opening Doors Federal Strategic Plan To Prevent and End Homelessness.</E>
                         These actions address goals to: Prevent and end homelessness; increase the supply of affordable housing; and increase the coordination of mainstream housing resources and other health and human services.
                    </P>
                    <P>The HOPWA NOFA announces funds available for projects that address both: (1) Direct housing assistance and service delivery to low income persons and families living with HIV/AIDS, including homeless individuals and families; and (2) comprehensive planning and coordination of local resources in meeting housing and service needs of the population. As a result of project efforts, communities will be assisted in the development and use of an Integrated HIV/AIDS Housing Plan (IHHP) to be issued at the end of the third year of operation. The IHHP is an administrative function and should demonstrate local system changes in the delivery of housing and services. Grantees are expected to provide housing assistance to eligible persons in their communities while concurrently examining and comprehensively integrating local services for coordinating and streamlining where possible the delivery of those services in your community.</P>
                    <P>
                        The notice providing information regarding the application process, funding criteria and eligibility requirements, application and instructions can be found using the Department of Housing and Urban Development agency link on the Grants.gov/Find Web site at 
                        <E T="03">http://www.grants.gov/search/agency.do.</E>
                         A link to the funding opportunity is also available on the HUD Web site at 
                        <E T="03">http://portal.hud.gov/hudportal/HUD?src=/program_offices/administration/grants/fundsavail.</E>
                    </P>
                    <P>
                        The link from the funds available page will take you to the agency link on Grants.gov. The Catalogue of Federal Domestic Assistance (CFDA) number for this program is 14.241. Applications must be submitted electronically through 
                        <E T="03">Grants.gov.</E>
                    </P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Questions regarding specific program requirements should be directed to the agency contact identified in the program NOFA. Program staff will not be available to provide guidance on how to prepare the application. Questions regarding the 2011 General Section should be directed to the Office of Grants Management and Oversight at (202) 708-0667 or the NOFA Information Center at 800-HUD-8929 (toll free).</P>
                    <P>Persons with hearing or speech impairments may access these numbers via TTY by calling the Federal Information Relay Service at 800-877-8339.</P>
                    <SIG>
                        <DATED>Dated: June 9, 2011.</DATED>
                        <NAME>Barbara S. Dorf,</NAME>
                        <TITLE>Director, Office of Departmental Grants Management and Oversight, Office of the Chief of the Human Capital Officer.</TITLE>
                    </SIG>
                </FURINF>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-14910 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4210-67-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HOUSING AND URBAN DEVELOPMENT</AGENCY>
                <DEPDOC>[Docket No. FR-5500-N-23]</DEPDOC>
                <SUBJECT>Notice of Web Availability; Notice of Funding Availability (NOFA) for HUD's Fiscal Year (FY) 2011 Doctoral Dissertation Research Grant Program</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of the Chief of the Human Capital Officer, HUD.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        HUD announces the availability on its Web site and 
                        <E T="03">Grants.gov</E>
                         of the applicant information, submission deadlines, funding criteria, and other requirements for HUD's FY2011 Doctoral Dissertation Research Grant Program NOFA. Specifically, this 
                        <PRTPAGE P="35234"/>
                        NOFA announces the availability of approximately $400,000 made available under the Department of Defense and Full-Year Continuing Appropriations Act, 2011, Public Law 112-10, enacted April 15, 2011.
                    </P>
                    <P>The purpose of the Doctoral Dissertation Research Grant Program is to enable doctoral candidates enrolled at institutions of higher education accredited by a national or regional accrediting agency recognized by the U.S. Department of Education to complete and improve the quality of their dissertations on policy-relevant housing and urban development issues.</P>
                    <P>
                        The notice providing information regarding the application process, funding criteria and eligibility requirements, application and instructions can be found using the Department of Housing and Urban Development agency link on the 
                        <E T="03">Grants.gov</E>
                        /Find Web site at 
                        <E T="03">http://www.grants.gov/search/agency.do</E>
                        . A link to the funding opportunity is also available on the HUD Web site at 
                        <E T="03">http://portal.hud.gov/hudportal/HUD?src=/program_offices/administration/grants/fundsavail</E>
                        .  The link from the funds available page will take you to the agency link on 
                        <E T="03">Grants.gov</E>
                        . The Catalogue of Federal Domestic Assistance (CFDA) number for this program is 14.516. Applications must be submitted electronically through 
                        <E T="03">Grants.gov.</E>
                    </P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Questions regarding specific program requirements should be directed to the agency contact identified in the program NOFA. Program staff will not be available to provide guidance on how to prepare the application. Questions regarding the 2011 General Section should be directed to the Office of Grants Management and Oversight at (202) 708-0667 or the NOFA Information Center at 800-HUD-8929 (toll free). Persons with hearing or speech impairments may access these numbers via TTY by calling the Federal Information Relay Service at 800-877-8339.</P>
                    <SIG>
                        <DATED>Dated: June 9, 2011.</DATED>
                        <NAME>Barbara S. Dorf,</NAME>
                        <TITLE>Director, Office of Departmental Grants Management and Oversight, Office of the Chief of the Human Capital Officer.</TITLE>
                    </SIG>
                </FURINF>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-14912 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4210-67-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HOUSING AND URBAN DEVELOPMENT</AGENCY>
                <DEPDOC>[Docket No. FR-5500-N-17]</DEPDOC>
                <SUBJECT>Notice of Web Availability: Notice of Funding Availability (NOFA) for HUD's Fiscal Year (FY) 2011 Choice Neighborhoods Initiative—Planning Grants</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of the Chief of the Human Capital Officer, HUD.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>HUD announces the availability on its Web site and Grants.gov applicant information, submission deadlines, funding criteria, and other requirements for HUD's FY2011 Choice Neighborhoods Initiative Program—Planning Grants NOFA. Specifically, this NOFA announces the availability of approximately $3.6 million made available under the Department of Defense and Full-Year Continuing Appropriations Act, 2011, Public Law 112-10, enacted April 15, 2011.</P>
                    <P>The purpose of the Choice Neighborhoods Initiative-Planning Grant Program is to support the development of comprehensive neighborhood revitalization plans which, when implemented, may be expected to achieve the following three core goals:</P>
                    <P>
                        1. 
                        <E T="03">Housing:</E>
                         Transform distressed public and assisted housing into energy efficient, mixed-income housing that is physically and financially viable over the long-term;
                    </P>
                    <P>
                        2. 
                        <E T="03">People:</E>
                         Support positive outcomes for families who live in the target development(s) and the surrounding neighborhood, particularly outcomes related to residents' health, safety, employment, mobility, and education; and
                    </P>
                    <P>
                        3. 
                        <E T="03">Neighborhood:</E>
                         Transform distressed, high-poverty neighborhoods into viable, mixed-income neighborhoods with access to well-functioning services, high quality public schools and education programs, high quality early learning programs and services, public assets, public transportation, and improved access to jobs.
                    </P>
                    <P>To achieve these core goals, communities must develop and implement a comprehensive neighborhood revitalization strategy, or Transformation Plan. This Transformation Plan will become the guiding document for the revitalization of the public and/or assisted housing units, while simultaneously directing the transformation of the surrounding neighborhood and positive outcomes for families.</P>
                    <P>
                        The notice providing information regarding the application process, funding criteria and eligibility requirements, application and instructions can be found using the Department of Housing and Urban Development agency link on the Grants.gov/Find Web site at 
                        <E T="03">http://www.grants.gov/search/agency.do</E>
                        . A link to the funding opportunity is also available on the HUD Web site at 
                        <E T="03">http://portal.hud.gov/hudportal/HUD?src=/program_offices/administration/grants/fundsavail.</E>
                    </P>
                    <P>The link from the funds available page will take you to the agency link on Grants.gov.</P>
                    <P>The Catalogue of Federal Domestic Assistance (CFDA) number for this program is 14.889. Applications must be submitted electronically through Grants.gov.</P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Questions regarding specific program requirements should be directed to the agency contact identified in the program NOFA. Program staff will not be available to provide guidance on how to prepare the application. Questions regarding the 2011 General Section should be directed to the Office of Grants Management and Oversight at (202) 708-0667 or the NOFA Information Center at 800-HUD-8929 (toll free).</P>
                    <P>Persons with hearing or speech impairments may access these numbers via TTY by calling the Federal Information Relay Service at 800-877-8339.</P>
                    <SIG>
                        <DATED>Dated: June 9, 2011.</DATED>
                        <NAME>Barbara S. Dorf,</NAME>
                        <TITLE>Director, Office of Departmental Grants Management and Oversight, Office of the Chief of the Human Capital Officer.</TITLE>
                    </SIG>
                </FURINF>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-14911 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4210-67-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HOUSING AND URBAN DEVELOPMENT</AGENCY>
                <DEPDOC>[Docket No.FR-5415-FA-22]</DEPDOC>
                <SUBJECT>Announcement of Funding Awards for Fiscal Year 2010; Transformation Initiative: Natural Experiments Grant Program</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of the Assistant Secretary for Policy Development and Research, HUD.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Announcement of funding awards.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        In accordance with Section 102(a)(4)(C) of the Department of 
                        <PRTPAGE P="35235"/>
                        Housing and Urban Development (HUD) Reform Act of 1989, this document notifies the public of funding awards for the Fiscal Year (FY) 2010 Transformation Initiative: Natural Experiments Grant Program Notice of Funding Availability (NOFA), which was posted to Grants.gov on January 20, 2011. This announcement contains the names and addresses of the award winners and the amount of the awards to be issued.
                    </P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Michael Morse, Office Policy Development and Research, Division of Program Monitoring and Research, U.S. Department of Housing and Urban Development, Room 8130, 451 7th Street, SW., Washington DC 20410, telephone number 202-402-5738. Persons with hearing or speech impairments may access this number by call the toll free Federal Relay Services at 1-800-877-8339.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The purpose of the FY 2010 Transformation Initiative: Natural Experiments Grant Program NOFA is to provide funding to support scientific research that makes use of natural experiments to evaluate the impacts of local, state, and federal policies. The FY 2010 NOFA made available approximately $600,000 under the Department of Housing and Urban Development Appropriations Act, 2010 (Pub. L. 111-117, approved December 16, 2009). The maximum grant performance period under the NOFA is 24 months; applicants could request $100,000 to $250,000 per award, depending of the scope of the proposed research. Awards under this NOFA will be made in the form of a Cooperative Agreement. A Cooperative Agreement means that HUD will have substantial involvement during the performance of the research project.</P>
                <P>The Catalog of Federal Domestic Assistance number for this program is 14.524.</P>
                <P>On January 20, 2011, HUD posted the FY 2010 Transformation Initiative: Natural Experiments Grant Program NOFA to Grants.gov. The Department reviewed, evaluated and scored the applications received based on the criteria in the NOFA. In accordance with Section 102(a)(4)(C) of the Department of Housing and Urban Development Reform Act of 1989 (103) Stat. 1987, U.S.C. 3545), the Department is publishing the names, addresses, and amounts of the awards made under this competition in Appendix A to this notice.</P>
                <SIG>
                    <DATED>Dated: June 9, 2011.</DATED>
                    <NAME>Raphael W. Bostic,</NAME>
                    <TITLE>Assistant Secretary for Policy Development and Research.</TITLE>
                </SIG>
                <HD SOURCE="HD1">Appendix A</HD>
                <EXTRACT>
                    <HD SOURCE="HD1">List of Awardees for Grant Assistance Under the Fiscal Year (FY) 2010 Transformation Initiative Research Program Funding Competition: Natural Experiment, by Institution, Address, Grant Amount and Name of Contact</HD>
                    <P>1. Case Western Reserve University, Mr. Derek M. Humphrey, Assistant Director, 10900 Euclid Avenue, Cleveland, Ohio 44106-7015. Grant: $250,000.00.</P>
                    <P>2. City of New York Department of Housing Preservation and Development, Ms. Elyzabeth Gaumer, Director, Housing Policy Research and Program Evaluation, 100 Gold Street, New York, New York 10038-1605. Grant: $250,000.00.</P>
                    <P>3. New York City Department of Homeless Services, Ms. Joanna Weissman, Executive Director of Planning and Research, 33 Beaver Street, 20th floor, New York, New York, 10004-2737. Grant: $100,000.00.</P>
                </EXTRACT>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-14913 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4210-67-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF THE INTERIOR</AGENCY>
                <SUBAGY>Fish and Wildlife Service</SUBAGY>
                <DEPDOC>[FWS-R2-ES-2011-N115; 20124-1113-0000-F5]</DEPDOC>
                <SUBJECT>Endangered and Threatened Species Permit Applications</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Fish and Wildlife Service, Interior.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of receipt of applications; request for public comment.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The following applicants have applied for scientific research permits to conduct certain activities with endangered species under the Endangered Species Act of 1973, as amended (Act). The Act requires that we invite public comment on these permit applications.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>To ensure consideration, written comments must be received on or before July 18, 2011.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Written comments should be submitted to the Chief, Endangered Species Division, Ecological Services, P.O. Box 1306, Room 6034, Albuquerque, NM 87103. Documents and other information submitted with these applications are available for review, subject to the requirements of the Privacy Act and Freedom of Information Act. Documents will be available for public inspection, by appointment only, during normal business hours at the U.S. Fish and Wildlife Service, 500 Gold Ave., SW., Room 6034, Albuquerque, NM. Please refer to the respective permit number for each application when submitting comments.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Susan Jacobsen, Chief, Endangered Species Division, P.O. Box 1306, Albuquerque, NM 87103; (505) 248-6920.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <HD SOURCE="HD1">Public Availability of Comments</HD>
                <P>Before including your address, phone number, e-mail address, or other personal identifying information in your comment, you should be aware 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>
                <HD SOURCE="HD1">Permit TE-046517</HD>
                <FP SOURCE="FP-1">
                    <E T="03">Applicant:</E>
                     United States Geological Survey, New Mexico Cooperative Unit, Las Cruces, New Mexico.
                </FP>
                <P>
                    Applicant requests a new permit to hold and rear captive Rio Grande silvery minnows (
                    <E T="03">Hybognathus amarus</E>
                    ) and bonytail chub (
                    <E T="03">Gila elegans</E>
                    ) at the rearing facility at New Mexico State Universtiy.
                </P>
                <HD SOURCE="HD1">Permit TE-42737A</HD>
                <FP SOURCE="FP-1">
                    <E T="03">Applicant:</E>
                     Sevenecoten, LLC, Dripping Springs, Texas.
                </FP>
                <P>
                    Applicant requests a new permit for research and recovery purposes to conduct presence/absence surveys for golden-cheeked warbler (
                    <E T="03">Dendroica chrysoparia</E>
                    ) and black-capped vireo (
                    <E T="03">Vireo atricapilla</E>
                    ) within Texas.
                </P>
                <HD SOURCE="HD1">Permit TE-150490</HD>
                <FP SOURCE="FP-1">
                    <E T="03">Applicant:</E>
                     Sea Life Arizona, Tempe, Arizona.
                </FP>
                <P>
                    Applicant requests a new permit for research and recovery purposes to hold and display for educational purposes the following native fish: woundfin (
                    <E T="03">Plagopterus argentissimus</E>
                    ), bonytail (
                    <E T="03">Gila elegans</E>
                    ), Colorado pikeminnow (
                    <E T="03">Ptychocheilus lucius</E>
                    ), desert pupfish (
                    <E T="03">Cyprinodon macularius</E>
                    ), Gila chub (
                    <E T="03">Gila intermedia</E>
                    ), Gila topminnow (
                    <E T="03">Poeciliopsis occidentalis occidentalis</E>
                    ), humpback chub (
                    <E T="03">Gila cypha</E>
                    ), razorback sucker (
                    <E T="03">Xyrauchen texanus</E>
                    ), Yaqui chub (
                    <E T="03">Gila purpea</E>
                    ), Yaqui sucker (
                    <E T="03">Catostomus bernardini</E>
                    ), and Yaqui topminnow (
                    <E T="03">Poeciliopsis occidentalis sonoriensis</E>
                    ) within the Aquarium.
                    <PRTPAGE P="35236"/>
                </P>
                <HD SOURCE="HD1">Permit TE-42823A</HD>
                <P>
                    <E T="03">Applicant:</E>
                     Wiebke Boeing, Las Cruces, New Mexico.
                </P>
                <P>
                    Applicant requests a new permit for research and recovery purposes to conduct presence/absence surveys for Pecos gambusia (
                    <E T="03">Gambusia nobilis</E>
                    ), Roswell springsnail (
                    <E T="03">Pyrgulopsis roswellensis</E>
                    ), Koster's springsnail (
                    <E T="03">Juturnia kosteri</E>
                    ), and Noel's amphipod (
                    <E T="03">Gammarus desperatus</E>
                    ) in sinkholes of the Bitter Lake National Wildlife Refuge, Roswell, New Mexico.
                </P>
                <HD SOURCE="HD1">Permit TE-051819</HD>
                <FP SOURCE="FP-1">
                    <E T="03">Applicant:</E>
                     Fort Worth Zoo, Fort Worth, Texas.
                </FP>
                <P>
                    Applicant requests a renewal to a current permit for research and recovery purposes to hold, conduct husbandry activities, and captively breed the following species: Barton Springs salamander (
                    <E T="03">Eurycea sosorum</E>
                    ), Houston toad (
                    <E T="03">Bufo houstonensis</E>
                    ), and black-footed ferret (
                    <E T="03">Mustela nigripes</E>
                    ) within the Fort Worth Zoo.
                </P>
                <HD SOURCE="HD1">Permit TE-43719A</HD>
                <FP SOURCE="FP-1">
                    <E T="03">Applicant:</E>
                     Desert Botanical Garden, Phoenix, Arizona.
                </FP>
                <P>
                    Applicant requests a new permit for research and recovery purposes to conduct presence/absence surveys, collect samples, and conduct genetic analysis of Huachuca water umbel (
                    <E T="03">Lilaeopsis schaffneriana</E>
                     var. 
                    <E T="03">recurva)</E>
                     and Arizona hedgehog cactu (
                    <E T="03">Echinocereus triglochidiatus</E>
                     var.
                    <E T="03"> arizonicus</E>
                    ) within Arizona and at the botanical garden.
                </P>
                <HD SOURCE="HD1">Permit TE-43746A</HD>
                <FP SOURCE="FP-1">
                    <E T="03">Applicant:</E>
                     Northern Arizona University, Flagstaff, Arizona.
                </FP>
                <P>
                    Applicant requests a new permit for research and recovery purposes to conduct presence/absence surveys for southwestern willow flycatcher (
                    <E T="03">Empidonax traillii extimus</E>
                    ) within Arizona.
                </P>
                <HD SOURCE="HD1">Permit TE-800923</HD>
                <FP SOURCE="FP-1">
                    <E T="03">Applicant:</E>
                     University of Arizona, Tucson, Arizona.
                </FP>
                <P>
                    Applicant requests a new permit for research and recovery purposes to conduct presence/absence surveys, collect genetic samples, and captively hold the following species: Colorado pikeminnow (
                    <E T="03">Ptychocheilus lucius</E>
                    ), desert pupfish (
                    <E T="03">Cyprinodon macularius</E>
                    ), Gila topminnow (
                    <E T="03">Poecciliopsis occidentalis</E>
                    ), and Gila chub (
                    <E T="03">Gila intermedia</E>
                    ) within Arizona.
                </P>
                <HD SOURCE="HD1">Permit TE-43777A</HD>
                <FP SOURCE="FP-1">
                    <E T="03">Applicant:</E>
                     Sea Life US, LLC, Grapevine, Texas.
                </FP>
                <P>
                    Applicant requests a new permit for husbandry and holding of green sea turtles (
                    <E T="03">Chelonia mydas</E>
                    ) and Kemps ridley sea turtles (
                    <E T="03">Lepidochelys kempii</E>
                    ) at the Sea Life Aquarium in Texas.
                </P>
                <HD SOURCE="HD1">Permit TE-172278</HD>
                <P>
                    <E T="03">Applicant:</E>
                     John C. Abbott, Austin, Texas.
                </P>
                <P>
                    Applicant requests a new permit for research and recovery purposes to conduct presence/absence surveys for American burying beetle (
                    <E T="03">Nicrophorus americanus</E>
                    ) within the Camp Maxey National Guard facility in Texas.
                </P>
                <HD SOURCE="HD1">Permit TE-44306A</HD>
                <FP SOURCE="FP-1">
                    <E T="03">Applicant:</E>
                     United States Geological Survey, Bozeman, Montana.
                </FP>
                <P>
                    Applicant requests a new permit for research and recovery purposes to conduct a study on the effects of electricity on growth and reproduction of razorback suckers (
                    <E T="03">Xyrauchen texanus</E>
                    ) at the Uvalde National Fish Hatchery in Texas.
                </P>
                <HD SOURCE="HD1">Permit TE-026711</HD>
                <FP SOURCE="FP-1">
                    <E T="03">Applicant:</E>
                     Coconino National Forest, Flagstaff, Arizona.
                </FP>
                <P>
                    Applicant requests a new permit for research and recovery purposes to conduct presence/absence surveys for the following species: southwestern willow flycatcher (
                    <E T="03">Empidonax traillii extimus</E>
                    ), Yuma clapper rail (
                    <E T="03">Rallus longirostris yumanensis</E>
                    ), Gila topminnow (
                    <E T="03">Poeciliopsis occidentalis occidentalis</E>
                    ), razorback sucker (
                    <E T="03">Xyrauchen texanus</E>
                    ), black-footed ferret (
                    <E T="03">Mustela nigripes</E>
                    ), Arizona cliffrose (
                    <E T="03">Purshia subintegra</E>
                    ), and Gila chub (
                    <E T="03">Gila intermedia</E>
                    ) within Arizona.
                </P>
                <HD SOURCE="HD1">Permit TE-118414</HD>
                <FP SOURCE="FP-1">
                    <E T="03">Applicant:</E>
                     Cherokee Nation, Tahlequah, Oklahoma.
                </FP>
                <P>
                    Applicant requests a new permit for research and recovery purposes to conduct presence/absence surveys for American burying beetle (
                    <E T="03">Nicrophorus americanus</E>
                    ) within Oklahoma.
                </P>
                <HD SOURCE="HD1">Permit TE-829995</HD>
                <FP SOURCE="FP-1">
                    <E T="03">Applicant:</E>
                     Dallas Zoo and Aquarium, Dallas, Texas.
                </FP>
                <P>
                    Applicant requests an amendment to hold, conduct husbandry activities, and captively breed Houston toads (
                    <E T="03">Bufo houstonensis</E>
                    ) within the zoo.
                </P>
                <HD SOURCE="HD1">Permit TE-207369</HD>
                <FP SOURCE="FP-1">
                    <E T="03">Applicant:</E>
                     U.S. Army Garrison—Fort Huachuca, Fort Huachuca, Arizona.
                </FP>
                <P>
                    Applicant requests an amendment to a current permit for research and recovery purposes to conduct presence/absence surveys, collect samples, and conduct genetic analysis of Huachuca water umbel (
                    <E T="03">Lilaeopsis schaffneriana</E>
                     var. 
                    <E T="03">recurva)</E>
                     and to conduct presence/absence surveys of southwestern willow flycatcher (
                    <E T="03">Empidonax traillii extimus</E>
                    ) within Arizona.
                </P>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P>
                         16 U.S.C. 1531 
                        <E T="03">et seq.</E>
                    </P>
                </AUTH>
                <SIG>
                    <DATED>Dated: June 8, 2011.</DATED>
                    <NAME>Joy E. Nicholopoulos,</NAME>
                    <TITLE> (Acting) Regional Director, Southwest Region, Fish and Wildlife Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-14927 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4310-55-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF THE INTERIOR</AGENCY>
                <SUBAGY>Bureau of Land Management</SUBAGY>
                <DEPDOC>[LLWO220000.L10200000.PH0000.00000000]</DEPDOC>
                <SUBJECT>Renewal of Approved Information Collection</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Bureau of Land Management, Interior.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>30-day Notice and Request for Comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Bureau of Land Management (BLM) has submitted an information collection request to the Office of Management and Budget (OMB) for a 3-year renewal of OMB Control Number 1004-0041 under the Paperwork Reduction Act. This control number covers paperwork requirements approval to continue the collection of information from applicants for grazing permits and leases, and from holders of grazing permits and leases.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The OMB is required to respond to this information collection request within 60 days but may respond after 30 days. Therefore, written comments should be received on or before July 18, 2011.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Please submit comments directly to the Desk Officer for the Department of the Interior (OMB #1004-0041), Office of Management and Budget, Office of Information and Regulatory Affairs, fax 202-395-5806, or by electronic mail at 
                        <E T="03">oira_docket@omb.eop.gov</E>
                        . Please provide a copy of your comments to the BLM. You may do so via mail, fax, or electronic mail.
                    </P>
                    <P>
                        <E T="03">Mail:</E>
                         U.S. Department of the Interior, Bureau of Land Management, 1849 C Street, NW., Room 2134LM, Attention: Jean Sonneman, Washington, DC 20240.
                    </P>
                    <P>
                        <E T="03">Fax:</E>
                         Jean Sonneman at fax number 202-912-7181.
                    </P>
                    <P>
                        <E T="03">Electronic mail: jean_sonneman@blm.gov</E>
                        .
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Kimberly Hackett, Division of 
                        <PRTPAGE P="35237"/>
                        Rangeland Resources, at 202-912-7216. Persons who use a telecommunication device for the deaf may call the Federal Information Relay Service at 1-800-877-8339, to leave a message for Ms. Hackett. You may also review the information collection request online at 
                        <E T="03">http://www.reginfo.gov/public/do/PRAMain</E>
                        .
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    The Paperwork Reduction Act (44 U.S.C. 3501-3521) and OMB regulations at 5 CFR part 1320 provide 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, you are not obligated to respond. 44 U.S.C. 3506 and 3507. In order to obtain and renew an OMB control number, Federal agencies are required to seek public comment on information collection and recordkeeping activities (
                    <E T="03">see</E>
                     5 CFR 1320.8(d) and 1320.12(a)). For this control number, the BLM requests comments on the following subjects:
                </P>
                <P>1. Whether the collection of information is necessary for the proper functioning of the BLM, including whether the information will have practical utility;</P>
                <P>2. The accuracy of the BLM's estimate of the burden of collecting the information, including the validity of the methodology and assumptions used;</P>
                <P>3. The quality, utility and clarity of the information to be collected; and</P>
                <P>4. How to minimize the information collection burden on those who are to respond, including the use of appropriate automated, electronic, mechanical, or other forms of information technology.</P>
                <P>
                    Please send comments as directed under 
                    <E T="02">ADDRESSES</E>
                     and 
                    <E T="02">DATES</E>
                    . Please refer to OMB control number 1004-0041 in your correspondence. Before including your address, phone number, e-mail address, or other personal identifying information in your comment, you should be aware 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>The following information is provided for the information collection:</P>
                <P>
                    <E T="03">Title:</E>
                     Authorizing Grazing Use (43 CFR subparts 4110 and 4130).
                </P>
                <P>
                    <E T="03">Forms:</E>
                </P>
                <P>• Form 4130-1, Grazing Schedule, Grazing Application;</P>
                <P>• Form 4130-1a, Grazing Preference Transfer Application and Preference Application (Base Property Preference Attachment and Assignment);</P>
                <P>• Form 4130-1b, Grazing Application Supplemental Information;</P>
                <P>• Form 4130-3a, Automated Grazing Application;</P>
                <P>• Form 4130-4, Application for Exchange-of-Use Grazing Agreement; and</P>
                <P>• Form 4130-5, Actual Grazing Use Report.</P>
                <P>
                    <E T="03">OMB Control Number:</E>
                     1004-0041.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     The Taylor Grazing Act (43 U.S.C. 315-315n) and Subchapters III and IV of the Federal Land Policy and Management Act (43 U.S.C. 1731-1753) authorize the BLM to manage domestic livestock grazing on public lands consistent with land use plans, the principles of multiple use and sustained yield, environmental values, economic considerations, and other relevant factors. In order to meet those goals, it is necessary to collection information on matters such as permittee and lessee qualifications for a grazing permit or lease, base property used in conjunction with public lands, and the actual use made by livestock authorized to graze on the public lands.
                </P>
                <P>
                    <E T="03">Frequency of Collection:</E>
                     The BLM collects the information on Forms 4130-1, 4130-1a, 4130-1b, and 4130-4 on occasion. The BLM collects the information on Forms 4130-3a and 4130-5 annually. Responses are required in order to obtain or retain a benefit.
                </P>
                <P>
                    <E T="03">Estimated Number and Description of Respondents:</E>
                     Any U.S. citizen or validly licensed business may apply for a BLM grazing permit or lease. The BLM administers nearly 18,000 permits and leases for grazing domestic livestock, mostly cattle and sheep, at least part of the year on public lands. Permits and leases generally cover a 10-year period and are renewable if the BLM determines that the terms and conditions of the expiring permit or lease are being met.
                </P>
                <P>
                    <E T="03">Estimated Reporting and Recordkeeping “Hour” Burden:</E>
                     33,810 responses and 7,811 hours annually. The following table details the individual components and respective hour burdens of this information collection request:
                </P>
                <GPOTABLE COLS="04" OPTS="L2(,0,),tp0,i1" CDEF="s50,12,12,12">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Type of response</CHED>
                        <CHED H="1">
                            Number of 
                            <LI>responses</LI>
                        </CHED>
                        <CHED H="1">
                            Time per 
                            <LI>response </LI>
                            <LI>(minutes)</LI>
                        </CHED>
                        <CHED H="1">Total hours</CHED>
                    </BOXHD>
                    <ROW RUL="s">
                        <ENT I="25">A </ENT>
                        <ENT>B </ENT>
                        <ENT>C </ENT>
                        <ENT>(B × C)</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Grazing Schedule—Grazing Application</ENT>
                        <ENT>3,000</ENT>
                        <ENT>15</ENT>
                        <ENT>750</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">(43 CFR 4130.1-1)</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Form 4130-1</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Grazing Preference Application and Preference Transfer Application (Base Property Preference Attachment and Assignment)</ENT>
                        <ENT>900</ENT>
                        <ENT>35 </ENT>
                        <ENT>525</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="031" O="xl">(43 CFR 4110.1(c), 4110.2-1(c), and 4110.2-3)</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Form 4130-1a and related nonform information</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Grazing Application Supplemental Information</ENT>
                        <ENT>900</ENT>
                        <ENT>30 </ENT>
                        <ENT>450</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">(43 CFR 4110.1 and 4130.7)</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Form 4130-1b</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Automated Grazing Application</ENT>
                        <ENT>14,000</ENT>
                        <ENT>10 </ENT>
                        <ENT>2,333</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">(43 CFR 4130.4)</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Form 4130-3a</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Application for Exchange-of-Use Grazing Agreement</ENT>
                        <ENT>10</ENT>
                        <ENT>18 </ENT>
                        <ENT>3</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">(43 CFR 4130.6-1)</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Form 4130-4</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Actual Grazing Use Report</ENT>
                        <ENT>15,000</ENT>
                        <ENT>15 </ENT>
                        <ENT>3,750</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">(43 CFR 4130.3-2(d))</ENT>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="03" O="xl">Form 4130-5</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="05">Totals </ENT>
                        <ENT>33,810 </ENT>
                        <ENT>  </ENT>
                        <ENT>7,811</ENT>
                    </ROW>
                </GPOTABLE>
                <PRTPAGE P="35238"/>
                <P>
                    <E T="03">Estimated Annual Reporting and Recordkeeping “Non-Hour Cost” Burden:</E>
                     $30,000.
                </P>
                <P>
                    <E T="03">60-Day Notice:</E>
                     As required in 5 CFR 1320.8(d), the BLM published a 60-day notice in the 
                    <E T="04">Federal Register</E>
                     on January 25, 2011 (76 FR 4369), soliciting comments from the public and other interested parties. The comment period closed on March 28, 2010. The BLM received one comment. The comment was a general invective about the Federal government, the Department of the Interior, and the BLM. It did not address, and was not germane to, this information collection. Therefore, we have not changed the information collection in response to the comment.
                </P>
                <SIG>
                    <NAME>Jean Sonneman,</NAME>
                    <TITLE>Bureau of Land Management, Information Collection Clearance Officer.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-14984 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4310-84-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">INTERNATIONAL TRADE COMMISSION</AGENCY>
                <SUBJECT>Notice of Receipt of Complaint; Solicitation of Comments Relating to the Public Interest</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>U.S. International Trade Commission.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        Notice is hereby given that the U.S. International Trade Commission has received a complaint entitled 
                        <E T="03">In Re Static Random Access Memories and Products Containing Same,</E>
                         DN 2816; the Commission is soliciting comments on any public interest issues raised by the complaint.
                    </P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        James R. Holbein, Secretary to the Commission, U.S. International Trade Commission, 500 E Street, SW., Washington, DC 20436, telephone (202) 205-2000. The public version of the complaint can be accessed on the Commission's electronic docket (EDIS) at 
                        <E T="03">http://edis.usitc.gov,</E>
                         and will be available for inspection during official business hours (8:45 a.m. to 5:15 p.m.) in the Office of the Secretary, U.S. International Trade Commission, 500 E Street, SW., Washington, DC 20436, telephone (202) 205-2000.
                    </P>
                    <P>
                        General information concerning the Commission may also be obtained by accessing its Internet server (
                        <E T="03">http://www.usitc.gov</E>
                        ). The public record for this investigation may be viewed on the Commission's electronic docket (EDIS) at 
                        <E T="03">http://edis.usitc.gov.</E>
                         Hearing-impaired persons are advised that information on this matter can be obtained by contacting the Commission's TDD terminal on (202) 205-1810.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The Commission has received a complaint filed on behalf of Cypress Semiconductor Corporation on June 10, 2011. The complaint alleges violations of section 337 of the Tariff Act of 1930 (19 U.S.C. 1337) in the importation into the United States, the sale for importation, and the sale within the United States after importation of certain static random access memories and products containing same. The complaint names as respondents GSI Technology of Sunnyvale, CA; Alcatel-Lucent of Paris, France; Telefonaktiebolaget LM Ericsson of Stockholm, Sweden; Motorola Solutions of Schaumburg, IL; Arrow Electronics, Inc. of Melville, NY; and Nu Horizons Electronics Corp. of Melville, NY.</P>
                <P>The complainant, proposed respondents, other interested parties, and members of the public are invited to file comments, not to exceed five pages in length, on any public interest issues raised by the complaint. Comments should address whether issuance of an exclusion order and/or a cease and desist order in this investigation would negatively affect the public health and welfare in the United States, competitive conditions in the United States economy, the production of like or directly competitive articles in the United States, or United States consumers.</P>
                <P>In particular, the Commission is interested in comments that:</P>
                <P>(i) Explain how the articles potentially subject to the orders are used in the United States;</P>
                <P>(ii) Identify any public health, safety, or welfare concerns in the United States relating to the potential orders;</P>
                <P>(iii) Indicate the extent to which like or directly competitive articles are produced in the United States or are otherwise available in the United States, with respect to the articles potentially subject to the orders; and</P>
                <P>(iv) Indicate whether Complainant, Complainant's licensees, and/or third party suppliers have the capacity to replace the volume of articles potentially subject to an exclusion order and a cease and desist order within a commercially reasonable time.</P>
                <P>
                    Written submissions must be filed no later than by close of business, five business days after the date of publication of this notice in the 
                    <E T="04">Federal Register</E>
                    . There will be further opportunities for comment on the public interest after the issuance of any final initial determination in this investigation.
                </P>
                <P>
                    Persons filing written submissions must file the original document and 12 true copies thereof on or before the deadlines stated above with the Office of the Secretary. Submissions should refer to the docket number (“Docket No. 2816”) in a prominent place on the cover page and/or the first page. The Commission's rules authorize filing submissions with the Secretary by facsimile or electronic means only to the extent permitted by section 201.8 of the rules (see Handbook for Electronic Filing Procedures, 
                    <E T="03">http://www.usitc.gov/secretary/fed_reg_notices/rules/documents/handbook_on_electronic_filing.pdf</E>
                    ). Persons with questions regarding electronic filing should contact the Secretary (202-205-2000).
                </P>
                <P>
                    Any person desiring to submit a document to the Commission in confidence must request confidential treatment. All such requests should be directed to the Secretary to the Commission and must include a full statement of the reasons why the Commission should grant such treatment. 
                    <E T="03">See</E>
                     19 CFR 201.6. Documents for which confidential treatment by the Commission is properly sought will be treated accordingly. All nonconfidential written submissions will be available for public inspection at the Office of the Secretary.
                </P>
                <P>This action is taken under the authority of section 337 of the Tariff Act of 1930, as amended (19 U.S.C. 1337), and of sections 201.10 and 210.50(a)(4) of the Commission's Rules of Practice and Procedure (19 CFR 201.10, 210.50(a)(4)).</P>
                <SIG>
                    <P>By order of the Commission.</P>
                    <DATED>Issued: June 13, 2011.</DATED>
                    <NAME>James R. Holbein,</NAME>
                    <TITLE>Secretary to the Commission.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-14934 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 7020-02-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF JUSTICE</AGENCY>
                <SUBJECT>Notice of Lodging of Consent Decree Under the Clean Air Act</SUBJECT>
                <P>
                    Notice is hereby given that on June 7, 2011, a proposed Consent Decree in 
                    <E T="03">United States</E>
                     v. 
                    <E T="03">Polar Industries, Inc.,</E>
                     Civil Action No. 3:11-cv-00915, was filed with the United States District Court for Connecticut.
                </P>
                <P>
                    In this action, the United States sought penalties and injunctive relief for the Defendant's violations of the Clean Air Act, 42 U.S.C. 7401
                    <E T="03"> et seq.,</E>
                     at its foam block manufacturing facility in Prospect, Connecticut. To resolve the United States' claims, the Defendants 
                    <PRTPAGE P="35239"/>
                    will pay a penalty of $102,000, and will install air emission controls at its plant to reduce its emissions of Volatile Organic Compounds into the air.
                </P>
                <P>
                    The Department of Justice will receive for a period of thirty (30) days from the date of this publication comments relating to the Consent Decree. Comments should be addressed to the Assistant Attorney General, Environment and Natural Resources Division, and either emailed to 
                    <E T="03">pubcomment-ees.enrd@usdoj.gov</E>
                     or mailed to P.O. Box 7611, U.S. Department of Justice, Washington, DC 20044-7611, and should refer to either: 
                    <E T="03">United States</E>
                     v. 
                    <E T="03">Industries Inc.,</E>
                     Civil Action No. 3:11-cv-00915, or D.J. Ref. 90-5-2-1-09881. The Consent Decree may be examined at the Office of the United States Attorney, District of Connecticut, Connecticut Financial Center, 157 Church St., 23d Floor, New Haven, Connecticut, and at the United States Environmental Protection Agency, 5 Post Office Square, Suite 100, Boston, Massachusetts 02109. During the public comment period, the Consent Decree may also be examined on the following Department of Justice Web site, 
                    <E T="03">http://www.usdoj.gov/enrd/Consent_Decrees.html.</E>
                     A copy of the Consent Decree may also be obtained by mail from the Consent Decree Library, P.O. Box 7611, U.S. Department of Justice, Washington, DC 20044-7611 or by faxing or e-mailing a request to Tonia Fleetwood (
                    <E T="03">tonia.fleetwood@usdoj.gov</E>
                    ), fax no. (202) 514-0097, phone confirmation number (202) 514-1547. In requesting a copy from the Consent Decree Library, please enclose a check, payable to the U.S. Treasury, in the amount of $9.50 (25 cents per page reproduction cost), or, if by email or fax, forward a check in the applicable amount to the Consent Decree Library at the stated address.
                </P>
                <SIG>
                    <NAME>Maureen Katz,</NAME>
                    <TITLE>Assistant Chief, Environmental Enforcement Section, Environment and Natural Resources Division.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-14914 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4410-15-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF JUSTICE</AGENCY>
                <SUBAGY>Drug Enforcement Administration</SUBAGY>
                <SUBJECT>Importer of Controlled Substances; Notice of Application</SUBJECT>
                <P>Pursuant to 21 U.S.C. 958(i), the Attorney General shall, prior to issuing a registration under this section to a bulk manufacturer of a controlled substance in schedule I or II, and prior to issuing a regulation under 21 U.S.C. 952(a)(2) authorizing the importation of such a substance, provide manufacturers holding registrations for the bulk manufacture of the substance an opportunity for a hearing.</P>
                <P>Therefore, in accordance with 21 CFR 1301.34(a), this is notice that on May 3, 2011, Boehringer Ingelheim Chemicals, Inc., 2820 N. Normandy Drive, Petersburg, Virginia 23805, made application by renewal to the Drug Enforcement Administration (DEA) to be registered as an importer of Phenylacetone (8501), a basic class of controlled substance listed in schedule II.</P>
                <P>The company plans to import the listed controlled substance to bulk manufacture amphetamine.</P>
                <P>Any bulk manufacturer who is presently, or is applying to be, registered with DEA to manufacture such basic class of controlled substance may file comments or objections to the issuance of the proposed registration, and may, at the same time, file a written request for a hearing on such application pursuant to 21 CFR 1301.43 and in such form as prescribed by 21 CFR 1316.47.</P>
                <P>Any such comments or objections should be addressed, in quintuplicate, to the Drug Enforcement Administration, Office of Diversion Control, Federal Register Representative (ODL), 8701 Morrissette Drive, Springfield, Virginia 22152; and must be filed no later than July 18, 2011.</P>
                <P>
                    This procedure is to be conducted simultaneously with, and independent of, the procedures described in 21 CFR 1301.34(b), (c), (d), (e), and (f). As noted in a previous notice published in the 
                    <E T="04">Federal Register</E>
                     on September 23, 1975, 40 FR 43745-46, all applicants for registration to import a basic class of any controlled substance in schedule I or II are, and will continue to be, required to demonstrate to the Deputy Assistant Administrator, Office of Diversion Control, Drug Enforcement Administration, that the requirements for such registration pursuant to 21 U.S.C. 958(a); 21 U.S.C. 823(a); and 21 CFR 1301.34(b), (c), (d), (e), and (f) are satisfied.
                </P>
                <SIG>
                    <DATED>Dated: June 7, 2011.</DATED>
                    <NAME>Joseph T. Rannazzisi</NAME>
                    <TITLE>Deputy Assistant Administrator, Office of Diversion Control, Drug Enforcement Administration.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-14976 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4410-09-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF JUSTICE</AGENCY>
                <SUBAGY>Drug Enforcement Administration</SUBAGY>
                <SUBJECT>Importer of Controlled Substances; Notice of Application</SUBJECT>
                <P>This is notice that on March 1, 2011, Penick Corporation, 33 Industrial Park Road, Pennsville, New Jersey 08070, made application by renewal to the Drug Enforcement Administration (DEA) for registration as an importer of the following basic classes of controlled substances:</P>
                <GPOTABLE COLS="02" OPTS="L2,tp0,i1" CDEF="s50,xs36">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Drug </CHED>
                        <CHED H="1">Schedule</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Coca Leaves (9040) </ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Raw Opium (9600) </ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Poppy Straw (9650) </ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Concentrate of Poppy Straw (9670) </ENT>
                        <ENT>II</ENT>
                    </ROW>
                </GPOTABLE>
                <P>The company plans to import the listed controlled substances to manufacture bulk controlled substance intermediates for sale to its customers.</P>
                <P>As explained in the Correction to Notice of Application pertaining to Rhodes Technologies, 72 FR 3417 (2007), comments and requests for hearings on applications to import narcotic raw material are not appropriate.</P>
                <P>
                    As noted in a previous notice published in the 
                    <E T="04">Federal Register</E>
                     on September 23, 1975, 40 FR 43745, all applicants for registration to import a basic class of any controlled substance in schedule I or II are, and will continue to be, required to demonstrate to the Deputy Assistant Administrator, Office of Diversion Control, Drug Enforcement Administration, that the requirements for such registration pursuant to 21 U.S.C. § 958(a); 21 U.S.C. 823(a); and 21 CFR 1301.34(b), (c), (d), (e), and (f) are satisfied.
                </P>
                <SIG>
                    <DATED> Dated: June 7, 2011.</DATED>
                    <NAME>Joseph T. Rannazzisi,</NAME>
                    <TITLE>Deputy Assistant Administrator, Office of Diversion Control, Drug Enforcement Administration.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-14975 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4410-09-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF JUSTICE</AGENCY>
                <SUBAGY>Drug Enforcement Administration</SUBAGY>
                <SUBJECT>Importer of Controlled Substances; Notice of Application</SUBJECT>
                <P>
                    Pursuant to 21 U.S.C. 958(i), the Attorney General shall, prior to issuing a registration under this Section to a bulk manufacturer of a controlled substance in schedule I or II, and prior to issuing a regulation under 21 U.S.C. 
                    <PRTPAGE P="35240"/>
                    952(a) authorizing the importation of such a substance, provide manufacturers holding registrations for the bulk manufacture of the substance an opportunity for a hearing.
                </P>
                <P>Therefore, in accordance with 21 CFR 1301.34(a), this is notice that on March 14, 2011, Noramco Inc., 1440 Olympic Drive, Athens, Georgia 30601, made application by letter to the Drug Enforcement Administration (DEA) to be registered as an importer of Phenylacetone (8501), a basic class of controlled substance listed in schedule II.</P>
                <P>The company plans to import the listed controlled substance in bulk for the manufacture of a controlled substance.</P>
                <P>Any bulk manufacturer who is presently, or is applying to be, registered with DEA to manufacture such basic class of controlled substance may file comments or objections to the issuance of the proposed registration, and may, at the same time, file a written request for a hearing on such application pursuant to 21 CFR 1301.43, and in such form as prescribed by 21 CFR 1316.47.</P>
                <P>
                    Any such comments or objections should be addressed, in quintuplicate, to the Drug Enforcement Administration, Office of Diversion Control, 
                    <E T="04">Federal Register</E>
                     Representative (ODL), 8701 Morrissette Drive, Springfield, Virginia 22152; and must be filed no later than July 18, 2011.
                </P>
                <P>
                    This procedure is to be conducted simultaneously with, and independent of, the procedures described in 21 CFR 1301.34(b), (c), (d), (e), and (f). As noted in a previous notice published in the 
                    <E T="04">Federal Register</E>
                     on September 23, 1975, 40 FR 43745-46, all applicants for registration to import a basic class of any controlled substance listed in schedule I or II are, and will continue to be, required to demonstrate to the Deputy Assistant Administrator, Office of Diversion Control, Drug Enforcement Administration, that the requirements for such registration pursuant to 21 U.S.C. 958(a); 21 U.S.C. 823(a); and 21 CFR 1301.34(b), (c), (d), (e), and (f) are satisfied.
                </P>
                <SIG>
                    <DATED>Dated: June 7, 2011.</DATED>
                    <NAME>Joseph T. Rannazzisi,</NAME>
                    <TITLE>Deputy Assistant Administrator, Office of Diversion Control, Drug Enforcement Administration.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-14972 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4410-09-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF JUSTICE</AGENCY>
                <SUBAGY>Drug Enforcement Administration</SUBAGY>
                <SUBJECT>Importer of Controlled Substances; Notice of Application</SUBJECT>
                <P>Pursuant to 21 U.S.C. 958(i), the Attorney General shall, prior to issuing a registration under this Section to a bulk manufacturer of a controlled substance in schedule I or II, and prior to issuing a regulation under 21 U.S.C. 952(a)(2) authorizing the importation of such a substance, provide manufacturers holding registrations for the bulk manufacture of the substance an opportunity for a hearing.</P>
                <P>Therefore, in accordance with 21 CFR 1301.34(a), this is notice that on March 1, 2011, Lipomed, Inc., One Broadway, Cambridge, Massachusetts 02142, made application by renewal to the Drug Enforcement Administration (DEA) to be registered as an importer of the following basic classes of controlled substances:</P>
                <GPOTABLE COLS="02" OPTS="L2,tp0,i1" CDEF="s50,xs36">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Drug </CHED>
                        <CHED H="1">Schedule</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Cathinone (1235) </ENT>
                        <ENT>I</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Methcathinone (1237) </ENT>
                        <ENT>I</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">N-Ethylamphetamine (1475) </ENT>
                        <ENT>I</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Fenethylline (1503) </ENT>
                        <ENT>I</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Methaqualone (2565) </ENT>
                        <ENT>I</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Gamma Hydroxybutyric Acid (2010) </ENT>
                        <ENT>I</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Lysergic acid diethylamide (7315) </ENT>
                        <ENT>I</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">2,5-Dimethoxy-4-(n)-propylthiophenethylamine  (7348) </ENT>
                        <ENT>I</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Marihuana (7360) </ENT>
                        <ENT>I</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Tetrahydrocannabinols (7370) </ENT>
                        <ENT>I</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Mescaline (7381) </ENT>
                        <ENT>I</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">3,4,5-Trimethoxyamphetamine (7390) </ENT>
                        <ENT>I</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">4-Bromo-2,5-dimethoxyamphetamine (7391) </ENT>
                        <ENT>I</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">4-Bromo-2,5-dimethoxyphenethylamine (7392) </ENT>
                        <ENT>I</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">4-Methyl-2,5-dimethoxyamphetamine (7395) </ENT>
                        <ENT>I</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">2,5-Dimethoxyamphetamine (7396) </ENT>
                        <ENT>I</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">2,5-Dimethoxy-4-ethylamphetamine (7399) </ENT>
                        <ENT>I</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">3,4-Methylenedioxyamphetamine (7400) </ENT>
                        <ENT>I</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">3,4-Methylenedioxy-N-ethylamphetamine (7404) </ENT>
                        <ENT>I</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">3,4-Methylenedioxymethamphetamine (7405) </ENT>
                        <ENT>I</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">4-Methoxyamphetamine (7411) </ENT>
                        <ENT>I</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Dimethyltryptamine (7435) </ENT>
                        <ENT>I</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Psilocybin (7437) </ENT>
                        <ENT>I</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Psilocyn (7438) </ENT>
                        <ENT>I</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">N-Benzylpiperazine (7493) </ENT>
                        <ENT>I</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Acetyldihydrocodeine (9051) </ENT>
                        <ENT>I</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Dihydromorphine (9145) </ENT>
                        <ENT>I</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Heroin (9200) </ENT>
                        <ENT>I</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Normorphine (9313) </ENT>
                        <ENT>I</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Pholcodine (9314) </ENT>
                        <ENT>I</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Tilidine (9750) </ENT>
                        <ENT>I</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">3-Methylfentanyl (9813) </ENT>
                        <ENT>I</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Amphetamine (1100) </ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Methamphetamine (1105) </ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Methylphenidate (1724) </ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Amobarbital (2125) </ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Pentobarbital (2270) </ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Secobarbital (2315) </ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Phencyclidine (7471) </ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Phenylacetone (8501) </ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Cocaine (9041) </ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Codeine (9050) </ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Dihydrocodeine (9120) </ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Oxycodone (9143) </ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Hydromorphone (9150) </ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Benzoylecgonine (9180) </ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Ethylmorphine (9190) </ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Hydrocodone (9193) </ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Levorphanol (9220) </ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Meperidine (9230) </ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Methadone (9250) </ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Dextropropoxyphene, bulk (non-dosage forms) (9273) </ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Morphine (9300) </ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Thebaine (9333) </ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Oxymorphone (9652) </ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Alfentanil (9737) </ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Sufentanil (9740) </ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Fentanyl (9801) </ENT>
                        <ENT>II</ENT>
                    </ROW>
                </GPOTABLE>
                <P>The company plans to import analytical reference standards for distribution to its customers for research and analytical purposes.</P>
                <P>Any bulk manufacturer who is presently, or is applying to be, registered with DEA to manufacture such basic classes of controlled substances may file comments or objections to the issuance of the proposed registration, and may, at the same time, file a written request for a hearing on such application pursuant to 21 CFR 1301.43, and in such form as prescribed by 21 CFR 1316.47.</P>
                <P>Any such comments or objections should be addressed, in quintuplicate, to the Drug Enforcement Administration, Office of Diversion Control, Federal Register Representative (ODL), 8701 Morrissette Drive, Springfield, Virginia 22152; and must be filed no later than July 18, 2011.</P>
                <P>
                    This procedure is to be conducted simultaneously with, and independent of, the procedures described in 21 CFR § 1301.34(b), (c), (d), (e), and (f). As noted in a previous notice published in the 
                    <E T="04">Federal Register</E>
                     on September 23, 1975, 40 FR 43745-46, all applicants for registration to import a basic class of any controlled substance in schedule I or II are, and will continue to be, required to demonstrate to the Deputy Assistant Administrator, Office of Diversion Control, Drug Enforcement Administration, that the requirements for such registration pursuant to 21 U.S.C. 958(a), 21 U.S.C. 823(a), and 21 
                    <PRTPAGE P="35241"/>
                    CFR 1301.34(b), (c), (d), (e), and (f) are satisfied.
                </P>
                <SIG>
                    <DATED>Dated: June 7, 2011.</DATED>
                    <NAME>Joseph T. Rannazzisi,</NAME>
                    <TITLE>Deputy Assistant Administrator, Office of Diversion Control, Drug Enforcement Administration.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-14956 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4410-09-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF JUSTICE</AGENCY>
                <SUBAGY>Drug Enforcement Administration</SUBAGY>
                <SUBJECT>Importer of Controlled Substances; Notice of Application</SUBJECT>
                <P>Pursuant to 21 U.S.C. 958(i), the Attorney General shall, prior to issuing a registration under this Section to a bulk manufacturer of a controlled substance in schedule I or II, and prior to issuing a regulation under 21 U.S.C. 952(a)(2) authorizing the importation of such a substance, provide manufacturers holding registrations for the bulk manufacture of the substance an opportunity for a hearing.</P>
                <P>Therefore, in accordance with 21 CFR 1301.34(a), this is notice that on April 11, 2011, Wildlife Laboratories, 1401 Duff Drive, Suite 400, Fort Collins, Colorado 80524, made application by renewal to the Drug Enforcement Administration (DEA) to be registered as an importer of Etorphine Hydrochloride (9059), a basic class of controlled substance listed in schedule II.</P>
                <P>The company plans to import the listed controlled substance for sale to its customers.</P>
                <P>Any bulk manufacturer who is presently, or is applying to be, registered with DEA to manufacture such basic class of controlled substance may file comments or objections to the issuance of the proposed registration, and may, at the same time, file a written request for a hearing on such application pursuant to 21 CFR 1301.43 and in such form as prescribed by 21 CFR 1316.47.</P>
                <P>Any such comments or objections should be addressed, in quintuplicate, to the Drug Enforcement Administration, Office of Diversion Control, Federal Register Representative (ODL), 8701 Morrissette Drive, Springfield, Virginia 22152; and must be filed no later than July 18, 2011.</P>
                <P>
                    This procedure is to be conducted simultaneously with, and independent of, the procedures described in 21 CFR 1301.34(b), (c), (d), (e), and (f). As noted in a previous notice published in the 
                    <E T="04">Federal Register</E>
                     on September 23, 1975, 40 FR 43745, all applicants for registration to import a basic class of any controlled substance listed in schedule I or II are, and will continue to be, required to demonstrate to the Deputy Assistant Administrator, Office of Diversion Control, Drug Enforcement Administration, that the requirements for such registration pursuant to 21 U.S.C. 958(a), 21 U.S.C. 823(a), and 21 CFR 1301.34(b), (c), (d), (e), and (f) are satisfied.
                </P>
                <SIG>
                    <DATED>Dated: June 7, 2011.</DATED>
                    <NAME>Joseph T. Rannazzisi,</NAME>
                    <TITLE>Deputy Assistant Administrator, Office of Diversion Control, Drug Enforcement Administration.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-14957 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4410-09-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF JUSTICE</AGENCY>
                <SUBAGY>Drug Enforcement Administration</SUBAGY>
                <SUBJECT>Importer of Controlled Substances; Notice of Application</SUBJECT>
                <P>Pursuant to Title 21 Code of Federal Regulations 1301.34 (a), this is notice that on May 12, 2011, Chattem Chemicals Inc., 3801 St. Elmo Avenue, Chattanooga, Tennessee 37409, made application by renewal to the Drug Enforcement Administration (DEA) for registration as an importer of the following basic classes of controlled substances:</P>
                <GPOTABLE COLS="2" OPTS="L2,tp0,i1" CDEF="s50,xs36">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Drug</CHED>
                        <CHED H="1">Schedule</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Methamphetamine (1105)</ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">4-Anilino-N-Phenethyl-4-Piperidine (8333)</ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Phenylacetone (8501) </ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Raw Opium (9600)</ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Concentrate of Poppy Straw (9670)</ENT>
                        <ENT>II</ENT>
                    </ROW>
                </GPOTABLE>
                <P>The company plans to import the listed controlled substances to manufacture bulk controlled substances for sale to its customers.</P>
                <P>No comments, objections, or requests for any hearings will be accepted on any application for registration or re-registration to import crude opium, poppy straw, concentrate of poppy straw, and coca leaves. As explained in the Correction to Notice of Application pertaining to Rhodes Technologies, 72 FR 3417 (2007), comments and requests for hearings on applications to import narcotic raw material are not appropriate.</P>
                <P>Any bulk manufacturer who is presently, or is applying to be, registered with DEA to manufacture such basic classes of controlled substances listed in schedule I or II, which fall under the authority of section 1002(a)(2)(B) of the Act [21 U.S.C. 952(a)(2)(B)] may, in the circumstances set forth in 21 U.S.C. 958(i), file comments or objections to the issuance of the proposed registration and may, at the same time, file a written request for a hearing on such application pursuant to 21 CFR 1301.43 and in such form as prescribed by 21 CFR 1316.47.</P>
                <P>Any such comments or objections should be addressed, in quintuplicate, to the Drug Enforcement Administration, Office of Diversion Control, Federal Register Representative (ODL), 8701 Morrissette Drive, Springfield, Virginia 22152; and must be filed no later than July 18, 2011.</P>
                <P>
                    This procedure is to be conducted simultaneously with, and independent of, the procedures described in 21 CFR § 1301.34(b), (c), (d), (e), and (f). As noted in a previous notice published in the 
                    <E T="04">Federal Register</E>
                     on September 23, 1975, 40 FR 43745-46, all applicants for registration to import a basic class of any controlled substance in schedule I or II are, and will continue to be, required to demonstrate to the Deputy Assistant Administrator, Office of Diversion Control, Drug Enforcement Administration, that the requirements for such registration pursuant to 21 U.S.C. 958(a); 21 U.S.C. 823(a); and 21 CFR 1301.34(b), (c), (d), (e), and (f) are satisfied.
                </P>
                <SIG>
                    <DATED>Dated: June 7, 2011.</DATED>
                    <NAME>Joseph T. Rannazzisi,</NAME>
                    <TITLE>Deputy Assistant Administrator, Office of Diversion Control, Drug Enforcement Administration.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-14954 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4410-09-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF JUSTICE</AGENCY>
                <SUBAGY>Drug Enforcement Administration</SUBAGY>
                <SUBJECT>Importer of Controlled Substances; Notice of Application</SUBJECT>
                <P>Pursuant to 21 U.S.C. 958(i), the Attorney General shall, prior to issuing a registration under this Section to a bulk manufacturer of a controlled substance in schedule I or II, and prior to issuing a regulation under 21 U.S.C. 952(a) authorizing the importation of such a substance, provide manufacturers holding registrations for the bulk manufacture of the substance an opportunity for a hearing.</P>
                <P>
                    Therefore, in accordance with 21 CFR 1301.34(a), this is notice that on March 14, 2011, Noramco Inc., 500 Swedes Landing Road, Wilmington, Delaware 19801-4417, made application by letter to the Drug Enforcement Administration (DEA) to be registered as an importer of Phenylacetone (8501), a basic class of 
                    <PRTPAGE P="35242"/>
                    controlled substance listed in schedule II.
                </P>
                <P>The company plans to import the listed controlled substance in bulk for distribution to its customers.</P>
                <P>Any bulk manufacturer who is presently, or is applying to be, registered with DEA to manufacture such basic class of controlled substance may file comments or objections to the issuance of the proposed registration, and may, at the same time, file a written request for a hearing on such application pursuant to 21 CFR 1301.43, and in such form as prescribed by 21 CFR 1316.47.</P>
                <P>Any such comments or objections should be addressed, in quintuplicate, to the Drug Enforcement Administration, Office of Diversion Control, Federal Register Representative (ODL), 8701 Morrissette Drive, Springfield, Virginia 22152; and must be filed no later than July 18, 2011.</P>
                <P>
                    This procedure is to be conducted simultaneously with, and independent of, the procedures described in 21 CFR 1301.34(b), (c), (d), (e), and (f). As noted in a previous notice published in the 
                    <E T="04">Federal Register</E>
                     on September 23, 1975, 40 FR 43745-46, all applicants for registration to import a basic class of any controlled substance listed in schedule I or II are, and will continue to be, required to demonstrate to the Deputy Assistant Administrator, Office of Diversion Control, Drug Enforcement Administration, that the requirements for such registration pursuant to 21 U.S.C. 958(a); 21 U.S.C. 823(a); and 21 CFR 1301.34(b), (c), (d), (e), and (f) are satisfied.
                </P>
                <SIG>
                    <DATED> Dated: June 7, 2011.</DATED>
                    <NAME>Joseph T. Rannazzisi,</NAME>
                    <TITLE>Deputy Assistant Administrator, Office of Diversion Control, Drug Enforcement Administration.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-14973 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4410-09-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF JUSTICE</AGENCY>
                <SUBAGY>Drug Enforcement Administration</SUBAGY>
                <SUBJECT>Importer of Controlled Substances; Notice of Registration</SUBJECT>
                <P>
                    By Notice dated April 11, 2011 and published in the 
                    <E T="04">Federal Register</E>
                     on April 19, 2011, 76 FR 21915, Stepan Company, Natural Products Department, 100 W. Hunter Avenue, Maywood, New Jersey 07607, made application by renewal to the Drug Enforcement Administration (DEA) to be registered as an importer of Coca Leaves (9040), a basic class of controlled substance listed in schedule II.
                </P>
                <P>The company plans to import the listed controlled substance for the manufacture of a bulk controlled substance for distribution to its customer.</P>
                <P>No comments or objections have been received. DEA has considered the factors in 21 U.S.C. 823(a) and 952(a) and determined that the registration of Stepan Company to import the basic class of controlled substance is consistent with the public interest and with United States obligations under international treaties, conventions, or protocols in effect on May 1, 1971. DEA has investigated Stepan Company to ensure that the company's registration is consistent with the public interest. The investigation has included inspection and testing of the company's physical security systems, verification of the company's compliance with state and local laws, and a review of the company's background and history. Therefore, pursuant to 21 U.S.C. 952(a) and 958(a), and in accordance with 21 CFR 1301.34, the above named company is granted registration as an importer of the basic class of controlled substance listed.</P>
                <SIG>
                    <DATED>Dated: June 8, 2011.</DATED>
                    <NAME>Joseph T. Rannazzisi, </NAME>
                    <TITLE>Deputy Assistant Administrator, Office of Diversion Control, Drug Enforcement Administration.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-14959 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4410-09-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF JUSTICE</AGENCY>
                <SUBAGY>Drug Enforcement Administration</SUBAGY>
                <SUBJECT>Manufacturer of Controlled Substances; Notice of Application</SUBJECT>
                <P>Pursuant to § 1301.33(a), Title 21 of the Code of Federal Regulations (CFR), this is notice that on May 12, 2011, Chattem Chemicals Inc., 3801 St. Elmo Avenue, Building 18, Chattanooga, Tennessee 37409, made application by renewal to the Drug Enforcement Administration (DEA) to be registered as a bulk manufacturer of the following basic classes of controlled substances:</P>
                <GPOTABLE COLS="2" OPTS="L2,tp0,i1" CDEF="s50,xs36">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Drug </CHED>
                        <CHED H="1">Schedule</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">4-Methoxyamphetamine (7411) </ENT>
                        <ENT>I</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Dihydromorphine (9145) </ENT>
                        <ENT>I</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Amphetamine (1100) </ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Methamphetamine (1105) </ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Lisdexamfetamine (1205) </ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Methylphenidate (1724) </ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Pentobarbital (2270) </ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Codeine (9050) </ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Dihydrocodeine (9120) </ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Oxycodone (9143) </ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Hydromorphone (9150) </ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Hydrocodone (9193) </ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Meperidine (9230) </ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Methadone (9250) </ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Methadone intermediate (9254) </ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Morphine (9300) </ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Oripavine (9330) </ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Thebaine (9333) </ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Oxymorphone (9652) </ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Noroxymorphone (9668) </ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Alfentanil (9737) </ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Remifentanil (9739) </ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Sufentanil (9740) </ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Fentanyl (9801) </ENT>
                        <ENT>II</ENT>
                    </ROW>
                </GPOTABLE>
                <P>The company plans to manufacture the listed controlled substances in bulk for distribution to its customers.</P>
                <P>Any other such applicant, and any person who is presently registered with DEA to manufacture such substances, may file comments or objections to the issuance of the proposed registration pursuant to 21 CFR 1301.33(a).</P>
                <P>Any such comments or objections should be addressed, in quintuplicate, to the Drug Enforcement Administration, Office of Diversion Control, Federal Register Representative (ODL), 8701 Morrissette Drive, Springfield, Virginia 22152; and must be filed no later than August 15, 2011.</P>
                <SIG>
                    <DATED>Dated: June 7, 2011.</DATED>
                    <NAME>Joseph T. Rannazzisi,</NAME>
                    <TITLE>Deputy Assistant Administrator, Office of Diversion Control, Drug Enforcement Administration.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-14953 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4410-09-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF JUSTICE</AGENCY>
                <SUBAGY>Drug Enforcement Administration</SUBAGY>
                <SUBJECT>Manufacturer of Controlled Substances; Notice of Application</SUBJECT>
                <P>Pursuant to § 1301.33(a), Title 21 of the Code of Federal Regulations (CFR), this is notice that on March 1, 2011, Penick Corporation, 33 Industrial Park Road, Pennsville, New Jersey 08070, made application by renewal to the Drug Enforcement Administration (DEA) to be registered as a bulk manufacturer of the following basic classes of controlled substances:</P>
                <GPOTABLE COLS="2" OPTS="L2,tp0,i1" CDEF="s50,xs36">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Drug</CHED>
                        <CHED H="1">Schedule</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Cocaine (9041)</ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Codeine (9050)</ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Dihydrocodeine (9120)</ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Oxycodone (9143)</ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Hydromorphone (9150)</ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Diphenoxylate (9170) </ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Ecgonine (9180)</ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Hydrocodone (9193)</ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01"> Morphine (9300)</ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Oripavine (9330)</ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Thebaine (9333)</ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="35243"/>
                        <ENT I="01">Oxymorphone (9652)</ENT>
                        <ENT>II</ENT>
                    </ROW>
                </GPOTABLE>
                <P>The company plans to manufacture the listed controlled substances as bulk controlled substance intermediates for distribution to its customers.</P>
                <P>Any other such applicant, and any person who is presently registered with DEA to manufacture such substances, may file comments or objections to the issuance of the proposed registration pursuant to 21 CFR 1301.33(a).</P>
                <P>Any such comments or objections should be addressed, in quintuplicate, to the Drug Enforcement Administration, Office of Diversion Control, Federal Register Representative (ODL), 8701 Morrissette Drive, Springfield, Virginia 22152; and must be filed no later than August 15, 2011.</P>
                <SIG>
                    <DATED>Dated: June 7, 2011.</DATED>
                    <NAME>Joseph T. Rannazzisi,</NAME>
                    <TITLE>Deputy Assistant Administrator, Office of Diversion Control, Drug Enforcement Administration.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-14977 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4410-09-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF JUSTICE</AGENCY>
                <SUBAGY>Drug Enforcement Administration</SUBAGY>
                <SUBJECT>Manufacturer of Controlled Substances; Notice of Application</SUBJECT>
                <P>Pursuant to § 1301.33(a), Title 21 of the Code of Federal Regulations (CFR), this is notice that on April 13, 2011, American Radiolabeled Chemicals, Inc., 101 Arc Drive, St. Louis, Missouri 63146, made application by renewal to the Drug Enforcement Administration (DEA) as a bulk manufacturer of the following basic classes of controlled substances:</P>
                <GPOTABLE COLS="2" OPTS="L2,tp0,i1" CDEF="s50,xs36">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Drug </CHED>
                        <CHED H="1">Schedule</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Gamma Hydroxybutyric Acid (2010)</ENT>
                        <ENT>I</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Ibogaine (7260)</ENT>
                        <ENT>I</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Lysergic acid diethylamide (7315)</ENT>
                        <ENT>I</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Tetrahydrocannabinols (7370)</ENT>
                        <ENT>I</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Dimethyltryptamine (7435)</ENT>
                        <ENT>I</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">1-[1-(2-Thienyl)cyclohexyl]piperidine (7470)</ENT>
                        <ENT>I</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Dihydromorphine (9145)</ENT>
                        <ENT>I</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Normorphine (9313)</ENT>
                        <ENT>I</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Amphetamine (1100) </ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Methamphetamine (1105)</ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Amobarbital (2125) </ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Phencyclidine (7471) </ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Phenylacetone (8501)</ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Cocaine (9041) </ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Codeine (9050)</ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Diprenorphine (9058)</ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Dihydrocodeine (9120) </ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Oxycodone (9143)</ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Hydromorphone (9150)</ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Ecgonine (9180)</ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Hydrocodone (9193)</ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Heroin (9200)</ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Meperidine (9230) </ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Metazocine (9240) </ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Dextropropoxyphene, bulk (non-dosage forms) (9273)</ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Morphine (9300) </ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Oripavine (9330)</ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Thebaine (9333)</ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Oxymorphone (9652) </ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Phenazocine (9715) </ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Fentanyl (9801) </ENT>
                        <ENT>II</ENT>
                    </ROW>
                </GPOTABLE>
                <P>The company plans to manufacture small quantities of the listed controlled substances as radiolabeled compounds for biochemical research.</P>
                <P>Any other such applicant, and any person who is presently registered with DEA to manufacture such substances, may file comments or objections to the issuance of the proposed registration pursuant to 21 CFR 1301.33(a).</P>
                <P>Any such written comments or objections should be addressed, in quintuplicate, to the Drug Enforcement Administration, Office of Diversion Control, Federal Register Representative (ODL), 8701 Morrissette Drive, Springfield, Virginia 22152; and must be filed no later than August 15, 2011.</P>
                <SIG>
                    <DATED>Dated: June 7, 2011.</DATED>
                    <NAME>Joseph T. Rannazzisi,</NAME>
                    <TITLE>Deputy Assistant Administrator, Office of Diversion Control, Drug Enforcement Administration.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-14974 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4410-09-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF JUSTICE</AGENCY>
                <SUBAGY>Drug Enforcement Administration</SUBAGY>
                <SUBJECT>Manufacturer of Controlled Substances; Notice of Application</SUBJECT>
                <P>Pursuant to § 1301.33(a), Title 21 of the Code of Federal Regulations (CFR), this is notice that on April 1, 2011, Archimica, Inc., 2460 W. Bennett Street, Springfield, Missouri 65807-1229, made application by renewal to the Drug Enforcement Administration (DEA) to be registered as a bulk manufacturer of the following basic classes of controlled substances:</P>
                <GPOTABLE COLS="2" OPTS="L2,tp0,i1" CDEF="s50,xs36">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Drug</CHED>
                        <CHED H="1">Schedule</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Gamma Hydroxybutyric Acid (2010)</ENT>
                        <ENT>I</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Amphetamine (1100)</ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Lisdexamfetamine (1205)</ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Methylphenidate (1724)</ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Phenylacetone (8501)</ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Hydrocodone (9193)</ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Methadone Intermediate (9254)</ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Tapentadol (9780)</ENT>
                        <ENT>II</ENT>
                    </ROW>
                </GPOTABLE>
                <P>The company plans to manufacture the listed controlled substances in bulk for distribution and sale to its customers for Amphetamine (1100).</P>
                <P>The company plans to acquire the listed controlled substance in bulk from a domestic source in order to manufacture other controlled substances in bulk for distribution to its customers.</P>
                <P>Any other such applicant, and any person who is presently registered with DEA to manufacture such substances, may file comments or objections to the issuance of the proposed registration pursuant to 21 CFR 1301.33(a).</P>
                <P>Any such comments or objections should be addressed, in quintuplicate, to the Drug Enforcement Administration, Office of Diversion Control, Federal Register Representative (ODL), 8701 Morrissette Drive, Springfield, Virginia 22152; and must be filed no later than August 15, 2011.</P>
                <SIG>
                    <DATED>Dated: June 7, 2011.</DATED>
                    <NAME>Joseph T. Rannazzisi,</NAME>
                    <TITLE>Deputy Assistant Administrator, Office of Diversion Control, Drug Enforcement Administration.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-14968 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4410-09-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF JUSTICE</AGENCY>
                <SUBAGY>Drug Enforcement Administration</SUBAGY>
                <SUBJECT>Manufacturer of Controlled Substances; Notice of Registration</SUBJECT>
                <P>
                    By Notice dated January 18, 2011, and published in the 
                    <E T="04">Federal Register</E>
                     on February 2, 2011, 76 FR 5829, Sigma Aldrich Research Biochemicals, Inc., 1-3 Strathmore Road, Natick, Massachusetts 01760-2447, made application by renewal to the Drug Enforcement Administration (DEA) to be registered as a bulk manufacturer of the following basic classes of controlled substances:
                </P>
                <GPOTABLE COLS="2" OPTS="L2,tp0,i1" CDEF="s25,xs36">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Drug </CHED>
                        <CHED H="1">Schedule</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Cathinone (1235) </ENT>
                        <ENT>I</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Methcathinone (1237) </ENT>
                        <ENT>I</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Aminorex (1585) </ENT>
                        <ENT>I</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Alpha-ethyltryptamine (7249) </ENT>
                        <ENT>I</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Lysergic acid diethylamide (7315) </ENT>
                        <ENT>I</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Tetrahydrocannabinols (7370) </ENT>
                        <ENT>I</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">4-Bromo-2,5-dimethoxyamphetamine (7391) </ENT>
                        <ENT>I</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">4-Bromo-2,5-dimethoxyphenethylamine (7392) </ENT>
                        <ENT>I</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="35244"/>
                        <ENT I="01">2,5-Dimethoxyamphetamine (7396) </ENT>
                        <ENT>I</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">3,4-Methylenedioxyamphetamine (7400) </ENT>
                        <ENT>I</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">N-Hydroxy-3,4-methylenedioxyamphetamine (7402) </ENT>
                        <ENT>I</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">3,4-Methylenedioxy-N-ethylamphetamine (7404) </ENT>
                        <ENT>I</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">3,4-Methylenedioxymethamphetamine (MDMA) (7405) </ENT>
                        <ENT>I</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Psilocybin (7437) </ENT>
                        <ENT>I</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">5-Methoxy-N,N-diisopropyltryptamine (7439) </ENT>
                        <ENT>I</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">1-[1-(2-Thienyl)cyclohexyl]piperidine (TCP) (7470) </ENT>
                        <ENT>I</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">N-Benzylpiperazine (BZP) (7493) </ENT>
                        <ENT>I</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Heroin (9200) </ENT>
                        <ENT>I</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Normorphine (9313) </ENT>
                        <ENT>I</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Amphetamine (1100) </ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Methamphetamine (1105) </ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Nabilone (7379) </ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">1-Phenylcyclohexylamine (7460) </ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Phencyclidine (7471) </ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Cocaine (9041) </ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Codeine (9050) </ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Diprenorphine (9058) </ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Ecgonine (9180) </ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Levomethorphan (9210) </ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Levorphanol (9220) </ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Meperidine (9230) </ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Metazocine (9240) </ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Methadone (9250) </ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Morphine (9300) </ENT>
                        <ENT>II </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Thebaine (9333) </ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Levo-alphacetylmethadol (9648) </ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Remifentanil (9739) </ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Carfentanil (9743) </ENT>
                        <ENT>II</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Fentanyl (9801) </ENT>
                        <ENT>II</ENT>
                    </ROW>
                </GPOTABLE>
                <P>The company plans to manufacture reference standards.</P>
                <P>No comments or objections have been received. DEA has considered the factors in 21 U.S.C. 823(a) and determined that the registration of Sigma Aldrich Research Biochemicals, Inc. to manufacture the listed basic classes of controlled substances is consistent with the public interest at this time. DEA has investigated Sigma Aldrich Research Biochemicals, Inc. to ensure that the company's registration is consistent with the public interest. The investigation has included inspection and testing of the company's physical security systems, verification of the company's compliance with state and local laws, and a review of the company's background and history. Therefore, pursuant to 21 U.S.C. 823(a), and in accordance with 21 CFR 1301.33, the above named company is granted registration as a bulk manufacturer of the basic classes of controlled substances listed.</P>
                <SIG>
                    <DATED>Dated: June 7, 2011.</DATED>
                    <NAME>Joseph T. Rannazzisi,</NAME>
                    <TITLE>Deputy Assistant Administrator, Office of Diversion Control, Drug Enforcement Administration.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-14960 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4410-09-M</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF LABOR</AGENCY>
                <SUBAGY>Office of the Secretary</SUBAGY>
                <SUBJECT>Bureau of International Labor Affairs; Office of Trade and Labor Affairs; Bahrain—United States Free Trade Agreement; Notice of Determination Regarding Review of Submission #2011-01</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Bureau of International Labor Affairs, U.S. Department of Labor.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Office of Trade and Labor Affairs (OTLA) gives notice that on June 10, 2011, Submission #2011-01 was accepted for review pursuant to Article 15.4.2 of Chapter Fifteen (the Labor Chapter) of the Bahrain—United States Free Trade Agreement.</P>
                    <P>The submission was filed with OTLA on April 21, 2011, by the American Federation of Labor and Congress of Industrial Organizations, with a statement from the General Federation of Bahrain Trade Unions. The submission alleges the Government of Bahrain has violated Article 15.1.1 of the Labor Chapter of the Bahrain—United States Free Trade Agreement by failing to fulfill its obligations and commitments under the International Labour Organization Declaration on Fundamental Principles and Rights at Work and its Follow-up with regard to the rights of association and non-discrimination against trade unionists. These allegations were supported by specific factual descriptions which, if substantiated, could demonstrate that the Government of Bahrain's actions were inconsistent with its commitments under the Labor Chapter.</P>
                    <P>The objectives of the review of the submission will be to gather information so that OTLA can better understand and publicly report on the U.S. Government's views regarding whether the Government of Bahrain's actions were consistent with the obligations set forth in the Labor Chapter of the Bahrain—United States Free Trade Agreement.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Effective date: June 10, 2011.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Gregory Schoepfle, Director, OTLA, U.S. Department of Labor, 200 Constitution Avenue, NW., Room S-5303, Washington, DC 20210. 
                        <E T="03">Telephone:</E>
                         (202) 693-4900 (this is not a toll-free number).
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    Article 15.4.2 of the Labor Chapter of the Bahrain—United States Free Trade Agreement establishes that each Party's contact point shall provide for the submission, receipt, and consideration of communications from persons of a Party on matters related to provisions of the Labor Chapter and shall review such communications in accordance with domestic procedures. On December 14, 2006, the Department of Labor's OTLA was designated as the office to serve as the contact point for administering the labor provisions in free trade agreements, including the Bahrain—United States Free Trade Agreement. 71 FR 76691 (2006). The same 
                    <E T="04">Federal Register</E>
                     notice informed the public of the Procedural Guidelines that OTLA would follow for the receipt and review of public submissions. These Procedural Guidelines are available at 
                    <E T="03">http://www.dol.gov/ilab/programs/otla/proceduralguidelines.htm.</E>
                     According to the definitions contained in the Procedural Guidelines (Section B) a “submission,” as used in the guidelines, means “a communication from the public containing specific allegations, accompanied by relevant supporting information, that another Party has failed to meet its commitments or obligations arising under a labor chapter * * *.”
                </P>
                <P>The Procedural Guidelines specify that OTLA shall consider six factors, to the extent that they are relevant, in determining whether to accept a submission for review:</P>
                <P>1. Whether the submission raises issues relevant to any matter arising under a labor chapter;</P>
                <P>2. Whether a review would further the objectives of a labor chapter;</P>
                <P>3. Whether the submission clearly identifies the person filing the submission, is signed and dated, and is sufficiently specific to determine the nature of the request and permit an appropriate review;</P>
                <P>4. Whether the statements contained in the submission, if substantiated, would constitute a failure of the other Party to comply with its obligations or commitments under a labor chapter;</P>
                <P>5. Whether the statements contained in the submission or available information demonstrate that appropriate relief has been sought under the domestic laws of the other Party, or that the matter or a related matter is pending before an international body; and,</P>
                <P>
                    6. Whether the submission is substantially similar to a recent 
                    <PRTPAGE P="35245"/>
                    submission and significant, new information has been furnished that would substantially differentiate the submission from the one previously filed.
                </P>
                <P>The submission raises pertinent issues that would further the objectives of the Labor Chapter and that would, if substantiated, constitute a failure of the GOB to comply with its FTA commitments. The submission provides new information and was filed in a correct and complete manner with an allegation that is specific enough to be investigated. The affected trade unionists have attempted to engage in dialogue with the Government of Bahrain regarding the allegations contained in the submission. The OTLA has taken these factors into account and accepted the submission for review.</P>
                <P>OTLA's decision to accept the submission for review is not intended to indicate any determination as to the validity or accuracy of the allegations contained in the submission. The objectives of the review of the submission will be to gather information so that OTLA can better understand and publicly report on the U.S. Government's views regarding whether the Government of Bahrain's actions were consistent with the obligations set forth in the Labor Chapter of the Bahrain—United States Free Trade Agreement. The review will be completed and a public report issued within 180 days, unless circumstances, as determined by OTLA, require an extension of time, as set out in the Procedural Guidelines. The public report will include a summary of the review process, as well as findings and recommendations.</P>
                <SIG>
                    <DATED>Signed at Washington, DC, on June 10, 2011.</DATED>
                    <NAME>Sandra Polaski,</NAME>
                    <TITLE>Deputy Undersecretary, International Affairs.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-14893 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4510-28-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">SECURITIES AND EXCHANGE COMMISSION</AGENCY>
                <SUBJECT>Submission for OMB Review; Comment Request</SUBJECT>
                <FP SOURCE="FP-1">
                    <E T="03">Upon Written Request,</E>
                      
                    <E T="03">Copies Available From:</E>
                     Securities and Exchange Commission, Office of Investor Education and Advocacy, Washington, DC 20549-0213.
                </FP>
                <EXTRACT>
                    <FP SOURCE="FP-2">“Investor Form;” SEC File No. 270-485; OMB Control No. 3235-0547.</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”) has submitted to the Office of Management and Budget a request to approve the collection of information discussed below.
                </P>
                <P>
                    Investors who submit complaints, ask questions, or provide tips do so voluntarily. To make it easier for the public to contact the agency electronically, the Commission created a series of investor complaint and question electronic forms. Investors can access forms through the 
                    <E T="03">SEC Center for Complaints and Enforcement Tips</E>
                     portal. The Commission consolidated four paper complaint forms into one electronic form (
                    <E T="03">the Investor Form</E>
                    ) that provides drop down options to choose from in order to categorize the investor's complaint or question, and may also provide the investor with automated information about their issue. The investor may describe their complaint and submit it without their name or contact information.
                </P>
                <P>The Investor Form asks investors to provide information concerning, among other things, their names, how they can be reached, the names of the individuals or entities involved, the nature of their complaint or tip, what documents they can provide, and what, if any, actions they have taken. Use of the Investor Form is strictly voluntary. Moreover, the Commission does not require investors to submit complaints, questions, tips, or other feedback. Absent the forms, the  public still has several ways to contact the agency, including telephone, facsimile, letters, and  e-mail.</P>
                <P>Approximately 20,000 investors each year voluntarily choose to use the complaint and question form. Investors who choose not to use the electronic Investor Form receive the same level of service as those who do. The dual purpose of the form is to make it easier for the public to contact the agency with complaints, questions, tips, or other feedback and to further streamline the workflow of Commission staff that record, process, and respond to investor contacts.</P>
                <P>The SEC has used—and will continue to use—the information that investors supply on the complaint and question forms, and the electronic Investor Form to review and process the contact (which may, in turn, involve responding to questions, processing complaints, or, as appropriate, initiating enforcement investigations), to maintain a record of contacts, to track the volume of investor complaints, and to analyze trends.</P>
                <P>The Commission estimates that the total reporting burden for using the Investor Form is 5,000 hours. The calculation of this estimate depends on the number of investors who use the forms each year and the estimated time it takes to complete the forms: 20,000 respondents × 15 minutes = 5,000 burden hours.</P>
                <P>
                    Members of the public should be aware that an agency may not conduct or sponsor, and a person is not required to respond to, a collection of information unless a currently valid Office of Management and Budget control number is displayed. Background documentation for this information collection may be viewed at the following link, 
                    <E T="03">http://www.reginfo.gov.</E>
                     General comments regarding the above information should be directed to the following persons: (i) Desk Officer for the Securities and Exchange Commission, Office of Information and Regulatory Affairs, Office of Management and Budget, Room 10102, New Executive Office Building, Washington, DC 20503 or send an e-mail to: 
                    <E T="03">Shagufta_Ahmed@omb.eop.gov;</E>
                     and (ii) Thomas Bayer, Director/Chief Information Officer, Securities and Exchange Commission, c/o Remi Pavlik-Simon, 6432 General Green Way, Alexandria, VA 22312; or send an e-mail to: 
                    <E T="03">PRA_Mailbox@sec.gov.</E>
                     Comments must be submitted to OMB within 30 days of this notice.
                </P>
                <SIG>
                    <DATED> June 11, 2011.</DATED>
                    <NAME>Cathy H. Ahn,</NAME>
                    <TITLE>Deputy Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-14988 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 8011-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">SECURITIES AND EXCHANGE COMMISSION</AGENCY>
                <DEPDOC>[Release No. IC-29691; File No. 812-13865]</DEPDOC>
                <SUBJECT>Country Investors Life Assurance Company, et al.</SUBJECT>
                <DATE>June 9, 2011.</DATE>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Securities and Exchange Commission (the “Commission”).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of application for an order pursuant to Section 26(c) of the Investment Company Act of 1940, as amended (the “1940 Act” or “Act”), approving certain substitutions of securities.</P>
                </ACT>
                <PREAMHD>
                    <HD SOURCE="HED">Applicants:</HD>
                    <P>COUNTRY Investors Life Assurance Company (the “Company”), COUNTRY Investors Variable Life Account (the “Life Account”) and COUNTRY Investors Variable Annuity Account (the “Annuity Account”) (together, the “Applicants”).</P>
                </PREAMHD>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        Applicants seek an order pursuant to Section 26(c) of the 1940 Act approving the substitution of: (1) Shares of the Fidelity VIP Index 500 
                        <PRTPAGE P="35246"/>
                        Portfolio (“Replacement Portfolio A”) of the Fidelity Variable Insurance Products Funds II (the “Fidelity Fund II”) for shares of the COUNTRY VP Growth Fund (“Replaced Portfolio A”) of the COUNTRY Mutual Funds Trust (the “COUNTRY Fund”); and (2) shares of the Fidelity VIP Investment Grade Bond Portfolio (“Replacement Portfolio B”) of the Fidelity Variable Insurance Products Fund V (the “Fidelity Fund V”) for shares of the COUNTRY VP Bond Fund (“Replaced Portfolio B”) of the COUNTRY Fund. Shares of Replacement Portfolio A, Replacement Portfolio B, Replaced Portfolio A, and Replaced Portfolio B currently are held by the Life Account and the Annuity Account (each an “Account,” together, the “Accounts”) to support variable life insurance or variable annuity contracts, respectively, issued by the Company (each a “Contract,” collectively, the “Contracts”).
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                          
                        <E T="7462">Filing Date:</E>
                         The Application was filed on February 1, 2011 and amended and restated on May 13, 2011.
                    </P>
                </DATES>
                <FP>
                    <E T="7462">Hearing or Notification of Hearing:</E>
                     An order granting the application will be issued unless the Commission orders a hearing. Interested persons may request a hearing by writing to the Secretary of the Commission and serving Applicants with a copy of the request, personally or by mail. Hearing requests must be received by the Commission by 5:30 p.m. on July 5, 2011, and should be accompanied by proof of service on Applicants in the form of an affidavit or, for lawyers, a certificate of service. Hearing requests should state the nature of the requester's interest, the reason for the request, and the issues contested. Persons who wish to be notified of a hearing may request notification by writing to the Secretary of the Commission.
                </FP>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Secretary, Securities and Exchange Commission, 100 F Street, NE., Washington, DC 20549-1090. Applicants, c/o Virginia L. Eves, Assistant General Counsel, Country Investors Life Assurance Company, 1701 N. Towanda Avenue, Bloomington, IL 61702-2901. Copies to Thomas E. Bisset, Esq., Sutherland Asbill &amp; Brennan LLP, 1275 Pennsylvania Avenue, NW., Washington, DC 20004-2415.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Alison T. White, Senior Counsel, or Joyce M. Pickholz, Branch Chief, Office of Insurance Products, Division of Investment Management, at (202) 551-6795.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    The following is a summary of the application. The complete application may be obtained via the Commission's Web site by searching for the file number, or for an applicant using the Company name box, at 
                    <E T="03">http://www.sec.gov/search/search.htm,</E>
                     or by calling (202) 551-8090.
                </P>
                <HD SOURCE="HD1">Applicants' Representations</HD>
                <P>1. The Company is a stock life insurance company organized under Illinois law in 1981. The Company is principally engaged in the offering of life insurance policies and annuity contracts, and is admitted to do business in 43 states. For purposes of the Act, the Company is the depositor and sponsor of each of the Accounts, as those terms have been interpreted by the Commission with respect to variable life insurance and variable annuity separate accounts.</P>
                <P>2. Under the insurance law of Illinois, the assets of each Account attributable to the Contracts issued through that Account are owned by the Company, but are held separately from the other assets of the Company for the benefit of the owners of, and the persons entitled to payment under, those Contracts. Each Account is a “separate account” as defined by Rule 0-1(e) under the Act. Each Account is registered with the Commission as a unit investment trust (File No. 811-21394 (the Life Account); File No. 811-21330 (the Annuity Account)). Each Account is comprised of a number of subaccounts and each subaccount invests exclusively in one of the insurance dedicated mutual fund portfolios made available as investment options underlying the Contracts.</P>
                <P>3. The Life Account is currently divided into 57 subaccounts. The assets of the Life Account support variable life insurance contracts, and interests in the Account offered through such contracts have been registered under the Securities Act of 1933, as amended (the “1933 Act”) on Form N-6 (File No. 333-106757).</P>
                <P>4. The Annuity Account is currently divided into 57 subaccounts. The assets of the Annuity Account support variable annuity contracts, and interests in the Account offered through such contracts have been registered under the 1933 Act on Form N-4 (File No. 333-104424).</P>
                <P>5. The Contracts are flexible premium variable life insurance and variable annuity contracts. The variable life insurance Contracts provide for the accumulation of values on a variable basis, a fixed basis, or a combination of both, throughout the insured's life, and for a death benefit upon the death of the insured. The variable annuity Contracts provide for the accumulation of values on a variable basis, a fixed basis, or a combination of both, during the accumulation period, and provide settlement or annuity payment options on a variable basis, a fixed basis, or a combination of both, during the income period. Under each of the Contracts, the Company reserves the right to substitute shares of one underlying fund for shares of another, or of another investment portfolio, including a portfolio of a different management investment company. The prospectuses for the Contracts and the Accounts contain the appropriate disclosure of this right.</P>
                <P>6. For as long as a variable life insurance Contract remains in force or a variable annuity Contract remains in force and has not yet been annuitized, a Contract owner may transfer all or any part of the Contract value from one subaccount to any other subaccount without limit, although certain restrictions apply to transfers to and from the fixed account interest investment option under the Contract funded by the Company's general account (the “Declared Interest Option”). The Company reserves the right to revoke or modify the transfer privilege to discourage excessive trading by Contract owners or to prevent transfers that may have a detrimental effect upon Contract owners, subaccount unit values, the insurance dedicated mutual fund portfolios underlying the subaccounts or the Declared Interest Option. The Contracts reserve to the Company the right to assess a charge of $25 for transfers in excess of twelve per Contract year.</P>
                <P>7. The Company began offering the variable life insurance Contracts in January, 2004 (the “Original VLI Contracts”) and discontinued offering the Original VLI Contracts on or about December 1, 2008 once the Company received state approval to offer an enhanced version of the Original VLI Contracts (the “New VLI Contracts”). Likewise, the Company began offering the variable annuity Contracts in January, 2004 (the “Original VA Contracts”) and discontinued offering the Original VA Contracts on or about December 1, 2008 once the Company received state approval to offer an enhanced version of the Original VA Contracts (the “New VA Contracts”). The Company discontinued offering the New VLI Contracts and New VA Contracts on or about November 30, 2010.</P>
                <P>
                    8. Currently, there are 34 underlying mutual fund investment options available under the Original VLI Contracts and the Original VA Contracts. Following the substitution transactions there will be 32 underlying mutual fund investment options 
                    <PRTPAGE P="35247"/>
                    available under the Original VLI Contracts and the Original VA Contracts.
                </P>
                <P>9. Under the New VLI Contracts and the New VA Contracts, there are 36 underlying mutual fund investment options available under the Contracts. Following the substitution transactions there will be 34 underlying mutual fund investment options available under the New VLI Contracts and the New VA Contracts.</P>
                <P>10. The COUNTRY Fund is organized as a Delaware business trust and registered as an open-end management investment company under the Act (File No. 811-10475). The COUNTRY Fund currently offers 4 separate investment portfolios, two of which would be involved in the proposed substitutions, the Replaced Portfolios. The COUNTRY Fund issues a separate series of shares of beneficial interest in connection with each Replaced Portfolio and has registered such shares under the 1933 Act on Form N-1A (File No. 333-68270). COUNTRY Fund Management (“COUNTRY Advisor”), a separately identifiable department of COUNTRY Trust Bank, serves as the investment adviser to each Replaced Portfolio.</P>
                <P>11. The Fidelity Fund II is registered as an open-end management investment company under the Act (File No. 811-05511) and currently offers three (3) investment portfolios, each with multiple share classes. The Fidelity Fund II issues a series of shares of beneficial interest in connection with each portfolio and has registered such shares under the 1933 Act on Form N-1A (File No. 033-20773). Each portfolio of the Fidelity Fund II has entered into a management agreement with Fidelity Management &amp; Research Company (“FMR”) under which FMR acts as investment adviser for the portfolio. Under the management agreement and pursuant to an exemptive order issued by the Commission, FMR also acts as a manager of managers for Replacement Portfolio A, meaning that FMR has the responsibility to oversee sub-advisers for Replacement Portfolio A and recommend the hiring, termination and replacement of such sub-advisers. Subject to the approval of the Fidelity Fund II board of trustees but without a shareholder approval, FMR may replace or hire unaffiliated sub-advisers or amend the terms of their existing sub-advisory agreements.</P>
                <P>12. The Fidelity Fund V is registered as an open-end management investment company under the Act (File No. 811-05361) and currently offers thirty-one (31) investment portfolios, each with multiple share classes. The Fidelity Fund V issues a series of shares of beneficial interest in connection with each portfolio and has registered such shares under the 1933 Act on Form N-1A (File No. 033-17704).</P>
                <P>13. The investment objectives of each Replaced Portfolio and Replacement Portfolio are as follows:</P>
                <P>a. Replaced Portfolio A and Replacement Portfolio A: The COUNTRY VP Growth Fund seeks growth of capital and dividend income, if any, will be incidental to this objective. The Fidelity VIP Index 500 Portfolio seeks investment results that correspond to the total return of common stocks publicly traded in the United States, as represented by the S&amp;P 500 Index.</P>
                <P>b. Replaced Portfolio B and Replacement Portfolio B: The COUNTRY VP Bond Fund seeks maximum total return consistent with preservation of capital. The Fidelity VIP Investment Grade Bond Portfolio seeks as high a level of current income as is consistent with the preservation of capital.</P>
                <P>14. The advisory fees, other expenses and total operating expenses (before and after any contractual waivers and reimbursements) for the year ended December 31, 2010, expressed as an annual percentage of average daily net assets, of the Replaced Portfolios and the Replacement Portfolios are as follows:</P>
                <GPOTABLE COLS="3" OPTS="L2,tp0,i1" CDEF="s100,xls80,xls92">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1"> </CHED>
                        <CHED H="1">
                            Replaced Portfolio A 
                            <LI>COUNTRY VP </LI>
                            <LI>Growth Fund </LI>
                            <LI>(percent)</LI>
                        </CHED>
                        <CHED H="1">
                            Replacement Portfolio A
                            <LI>Fidelity VIP Index 500</LI>
                            <LI>Portfolio </LI>
                            <LI>(percent)</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Advisory Fees </ENT>
                        <ENT>.75 </ENT>
                        <ENT>.10</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Distribution and/or 12b-1 Fees </ENT>
                        <ENT>N/A </ENT>
                        <ENT>.25</ENT>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="01">Other Expenses </ENT>
                        <ENT>.65 </ENT>
                        <ENT>0.00</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Total Operating Expenses </ENT>
                        <ENT>1.40 </ENT>
                        <ENT>.35</ENT>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="01">Less Contractual Fee Waivers and Expense Reimbursements </ENT>
                        <ENT>(.50) </ENT>
                        <ENT>0.00</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="05">Net Operating Expenses </ENT>
                        <ENT>.90 </ENT>
                        <ENT>.35</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="22">  </ENT>
                        <ENT O="oi0">
                            Replaced Portfolio B 
                            <LI O="oi0">COUNTRY Bond Fund </LI>
                            <LI O="oi0">(percent)</LI>
                        </ENT>
                        <ENT O="oi0">
                            Replacement Portfolio B
                            <LI O="oi0">Fidelity VIP Investment</LI>
                            <LI O="oi0">Grade Bond Portfolio</LI>
                            <LI O="oi0">(percent)</LI>
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Advisory Fees </ENT>
                        <ENT>.50 </ENT>
                        <ENT>.32</ENT>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="01">Other Expenses </ENT>
                        <ENT>.67 </ENT>
                        <ENT>.11</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Total Operating Expenses </ENT>
                        <ENT>1.17 </ENT>
                        <ENT>.43</ENT>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="01">Less Contractual Fee Waivers and Expense Reimbursements </ENT>
                        <ENT>(.46) </ENT>
                        <ENT>(.01)</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="05">Net Operating Expenses </ENT>
                        <ENT>.71 </ENT>
                        <ENT>.42</ENT>
                    </ROW>
                </GPOTABLE>
                <P>
                    15. The investment performance of each Replacement Portfolio compares favorably to the investment performance of the corresponding Replaced Portfolio. For the last fiscal year, the investment performance of Replacement Portfolio B significantly exceeded the investment performance of Replaced Portfolio B while the investment performance of Replacement Portfolio A slightly trailed the investment performance of Replaced Portfolio A. For the last five fiscal year period and ten fiscal year/since inception period, the investment performance of Replacement Portfolio A trailed the investment performance of Replaced Portfolio A, however, much of that underperformance can be traced directly to the extraordinary market conditions that existed in fiscal year 2008. In that regard, Replacement 
                    <PRTPAGE P="35248"/>
                    Portfolio A significantly outperformed Replaced Portfolio A in fiscal year 2009. For the last five fiscal year period and for the ten fiscal year/since inception period, the investment performance of Replacement Portfolio B exceeded the investment performance of Replaced Portfolio B. In addition, each Replacement Portfolio has a longer history of investment performance than that of the corresponding Replaced Portfolio.
                </P>
                <P>16. For those Contracts that are in force on the date of the proposed substitutions, the Company will take the following action during the twenty-four months following the date of the proposed substitutions. On the last day of each fiscal period (not to exceed a fiscal quarter), the Company will reimburse Contract owners to the extent that the sum of the operating expenses of the Replacement Portfolio (taking into account any fee waivers and expense reimbursements) and subaccount expenses for such period exceed, on an annualized basis, the sum of the operating expenses of the corresponding Replaced Portfolio (taking into account any fee waivers and expense reimbursements) and subaccount expenses for the fiscal year preceding the date of the proposed substitution. In addition, for twenty-four months following the proposed substitutions, the Company will not increase asset-based fees or charges for Contracts outstanding on the date of the proposed substitutions.</P>
                <P>17. The Board of Trustees of the COUNTRY Fund voted to close the Replaced Portfolios to new investment as of April 29, 2011, and to liquidate the Replaced Portfolios on or before June 30, 2012, the Liquidation Date. In turn, the COUNTRY VP Growth Fund Subaccount and the COUNTRY VP Bond Fund Subaccount (together the “Discontinued Subaccounts”) that invest in Replaced Portfolio A and Replaced Portfolio B, respectively, also are no longer available for new investments (allocation of premium payments and transfers) as of April 29, 2011 (the “Closing Date”) and will be discontinued altogether under the Contracts on a date no later than the Liquidation Date.</P>
                <P>18. If the Commission grants this request for substitution relief, Contract owners' investment in the COUNTRY VP Growth Fund Subaccount and the COUNTRY VP Bond Fund Subaccount will automatically be transferred to the applicable Fidelity VIP Index 500 Portfolio Subaccount and the Fidelity VIP Investment Grade Bond Portfolio Subaccount (the “Replacement Subaccounts”), respectively, as of a date determined by the Company following receipt of a Commission order granting substitution relief (the “Substitution”). Contract owners will receive advance notice of the date of the Substitution (the “Substitution Date”).</P>
                <P>19. By supplements to the prospectuses for the registration statements of the Accounts filed with the Commission on February 2, 2011 (collectively, the “2011 Supplements”), the Company notified owners of the Contracts of its intention to take the necessary actions, including seeking the order requested by this amended and restated application, to carry out the proposed substitutions as described herein.</P>
                <P>20. The 2011 Supplements advised Contract owners that accumulated Contract value may continue to remain in the Discontinued Subaccounts after the Closing Date until the Substitution Date. After the Closing Date, however, Contract owners will not be able to allocate premium payments or transfer accumulated Contract value to the Discontinued Subaccounts from the Declared Interest Option or from the other subaccounts available under the Contract. Prospectuses for the Contracts dated May 1, 2011 also provided Contract owners the same information included in the 2011 Supplements as well as more detailed information regarding each Replaced Portfolio and each Replacement Portfolio.</P>
                <P>21. In addition, the Company has forwarded to each Contract owner invested in a Replaced Portfolio the most recent prospectus for the Replaced Portfolio and the corresponding Replacement Portfolio.</P>
                <P>22. From the date of the 2011 Supplements, Contract owners may transfer accumulated Contract value from the Discontinued Subaccounts to the Declared Interest Option and the other subaccounts available under the Contract free of charge and without such transfers counting against the number of free transfers allowed each Contract year. For 30 days following the Substitution Date, Contract owners whose accumulated Contract value was transferred to the Replacement Subaccounts as a result of the Substitution may transfer accumulated Contract value from the Replacement Subaccounts to the Declared Interest Option and the other subaccounts available under the Contract free of charge and without such transfers counting against the number of free transfers. Although the Company has no present intention to increase the charge for transfers under the Contracts, the Company will agree not to exercise any rights reserved by it under the Contracts to impose additional charges for transfers until at least 30 days after the Substitution Date.</P>
                <P>23. Within five days after the Substitution Date, Contract owners who are affected by the substitutions will be sent a written notice informing them that the substitutions were carried out. The notice also will reiterate the facts that: (1) For at least 30 days after the Substitution Date, the Company will not exercise any rights reserved by it under the Contract to impose additional charges for transfers; and (2) for 30 days following the Substitution Date, Contract owners may transfer accumulated Contract value that was transferred into the Replacement Subaccounts as a result of the substitution out of the Replacement Subaccounts and into the Declared Interest Option and the other subaccounts available under the Contracts free of charge and without such transfers counting against the number of free transfers allowed each Contract year.</P>
                <P>24. The Company will carry out the proposed substitutions by redeeming shares of each Replaced Portfolio held by the Accounts for cash and applying the proceeds to the purchase of shares of the corresponding Replacement Portfolio. Redemption requests and purchase orders will be placed simultaneously so that Contract values will remain fully invested at all times. All redemptions of shares of the Replaced Portfolios and purchases of shares of the Replacement Portfolios will be effected in accordance with Rule 22c-1 of the Act.</P>
                <P>
                    25. The proposed substitutions will take place at relative net asset value and will not result in a change in the amount of any Contract owner's accumulated Contract value or death benefit, or in the dollar value of his or her investment in any of the Accounts. Contract owners will not incur any fees or charges as a result of the proposed substitutions, nor will their rights or the Company's obligations under the Contracts be altered in any way. All applicable expenses incurred in connection with the proposed substitutions, including brokerage commissions and legal, accounting, and other fees and expenses, will be paid by the Company. In addition, the proposed substitutions will not result in adverse tax consequences for, and will not alter, the tax benefits to Contract owners. The proposed substitutions will not cause the Contract fees and charges currently being paid by existing Contract owners to be greater after the proposed substitutions than before the proposed substitutions.
                    <PRTPAGE P="35249"/>
                </P>
                <P>26. Applicants believe that Contract owners will be better off with the Replacement Portfolios than with the Replaced Portfolios, and that the proposed substitutions also are unlike the type of substitution that Section 26(c) was designed to prevent.</P>
                <HD SOURCE="HD1">Conclusion</HD>
                <P>For the reasons and upon the facts set forth above, Applicants submit that the requested order meets the standards set forth in Section 26(c). Applicants request an order of the Commission, pursuant to Section 26(c) of the Act, approving the Substitutions.</P>
                <SIG>
                    <P>For the Commission, by the Division of Investment Management, pursuant to delegated authority.</P>
                    <NAME>Cathy H. Ahn,</NAME>
                    <TITLE>Deputy Secretary.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-14859 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 8011-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">SECURITIES AND EXCHANGE COMMISSION</AGENCY>
                <DEPDOC>[[Release No. IC-29693; File No. 812-13821]</DEPDOC>
                <SUBJECT>Allianz Life Insurance Company of North America, et al; Notice of Application</SUBJECT>
                <DATE>June 10, 2011.</DATE>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Securities and Exchange Commission (“SEC” or “Commission”).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of application for an order approving the substitution of certain securities pursuant to Section 26(c) of the Investment Company Act of 1940, as amended (the “1940 Act” or “Act”) and an order of exemption pursuant to Section 17(b) of the Act from Section 17(a) of the Act.</P>
                </ACT>
                <FP>
                    <E T="7462">Applicants:</E>
                     Allianz Life Insurance Company of North America (“Allianz Life”) and Allianz Life Insurance Company of New York (“Allianz NY”) (together the “Insurance Company Applicants”); their respective separate accounts Allianz Life Variable Account A (“Allianz Account A”), Allianz Life Variable Account B (“Allianz Account B”), and Allianz Life of NY Variable Account C (“Allianz Account C”) (collectively with the Insurance Company Applicants, the “Applicants”); and PIMCO Equity Series VIT (the “PIMCO EqS VIT” and collectively with the Applicants, the “Section 17 Applicants”).
                </FP>
                <FP>
                    <E T="7462">Summary of Application:</E>
                     The Applicants seek an order pursuant to Section 26(c) of the 1940 Act, approving the substitution of the securities of the PIMCO EqS Pathfinder Portfolio for the securities of the Mutual Global Discovery Securities Fund (the “Substitution) held by Allianz Account A, Allianz Account B, or Allianz Account C (collectively, the “Separate Accounts” or “Separate Account Applicants”) to support certain individual variable annuity contracts and variable life insurance contracts (the “Contracts”) issued by Allianz Life and Allianz NY. The Section 17 Applicants seek an order pursuant to Section 17(b) of the 1940 Act exempting them from Section 17(a) of the Act to the extent necessary to permit them to engage in certain in-kind transactions in connection with the Substitution.
                </FP>
                <FP>
                    <E T="7462">Filing Date:</E>
                     The application was filed on September 14, 2010, and amended on October 6, 2010, October 12, 2010 and May 26, 2011.
                </FP>
                <FP>
                    <E T="7462">Hearing or Notification of Hearing:</E>
                     An order granting the application will be issued unless the Commission orders a hearing. Interested persons may request a hearing by writing to the Secretary of the Commission and serving Applicants and PIMCO EqS VIT with a copy of the request, personally or by mail. Hearing requests should be received by the Commission by 5:30 p.m. on July 5, 2011, and should be accompanied by proof of service on Applicants and PIMCO EqS VIT in the form of an affidavit or, for lawyers, a certificate of service. Hearing requests should state the nature of the requester's interest, the reason for the request, and the issues contested. Persons who wish to be notified of a hearing may request notification by writing to the Secretary of the Commission.
                </FP>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Secretary, SEC, 100 F Street, NE., Washington, DC 20549-1090. Applicants: Allianz Life Insurance Company of North America, Allianz Life Variable Account A, and Allianz Life Variable Account B, 5701 Golden Hills Dr., Minneapolis, MN 55416-1297; Allianz Life Insurance Company of New York, and Allianz Life of NY Variable Account C, One Chase Manhattan Plaza, 37th Floor, New York, NY 10005-1423; and PIMCO Equity Series VIT, 840 Newport Center Drive, Newport Beach, CA 92660.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Sally Samuel, Senior Counsel, or Joyce M. Pickholz, Branch Chief, Office of Insurance Products, Division of Investment Management, at (202) 551-6795.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    The following is a summary of the application. The complete application may be obtained via the Commission's Web site by searching for the file number, or for an applicant using the Company name box, at 
                    <E T="03">http://www.sec.gov/search/search.htm,</E>
                     or by calling (202) 551-8090.
                </P>
                <P>
                    <E T="03">Applicants' and PIMCO EqS VIT's Representations:</E>
                </P>
                <P>1. The Applicants propose to substitute certain classes of shares of the PIMCO EqS Pathfinder Portfolio (the “Replacement Fund”) for the corresponding class of shares of the Mutual Global Discovery Securities Fund (the “Replaced Fund”) currently held by the Separate Accounts, as shown in the table below:</P>
                <GPOTABLE COLS="4" OPTS="L2,i1" CDEF="s100,r50,r100,xs52">
                    <TTITLE>The Replacement Fund and the Replaced Fund </TTITLE>
                    <TDESC>[Each a “Fund” and collectively the “Funds”]</TDESC>
                    <BOXHD>
                        <CHED H="1">
                            Replacement Fund 
                            <LI>(investment adviser)</LI>
                        </CHED>
                        <CHED H="1">Share classes</CHED>
                        <CHED H="1">
                            Replaced Fund 
                            <LI>(investment adviser)</LI>
                        </CHED>
                        <CHED H="1">Share classes</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">
                            PIMCO EqS Pathfinder Portfolio 
                            <SU>TM</SU>
                              
                            <LI>(Pacific Investment Management Company LLC or “PIMCO”)</LI>
                        </ENT>
                        <ENT>
                            Institutional Class
                            <LI>Advisor Class *</LI>
                        </ENT>
                        <ENT>Mutual Global Discovery Securities Fund (Franklin Mutual Advisers, LLC)</ENT>
                        <ENT>
                            Class 1 
                            <LI>Class 2*</LI>
                        </ENT>
                    </ROW>
                    <TNOTE>* A distribution (12b-1) fee is assessed against assets attributable to this class of shares at the annual rate of 0.25% of the average daily net assets attributable to the class.</TNOTE>
                </GPOTABLE>
                <P>2. The Replacement Fund is a series of the PIMCO EqS VIT, a Delaware statutory trust. The PIMCO EqS VIT is registered as an open-end management investment company under the 1940 Act (File No. 811-22376) and its shares are registered as securities under the Securities Act of 1933, as amended (the “1933 Act”) (File No. 333-164078).</P>
                <P>
                    3. Shares of the Replacement Fund are sold to separate accounts of Allianz Life and Allianz NY for the purpose of 
                    <PRTPAGE P="35250"/>
                    funding variable annuity contracts and variable life insurance policies. The Replacement Fund is managed by PIMCO, an affiliate of the Insurance Company Applicants.
                </P>
                <P>4. The Replaced Fund is a series of Franklin Templeton Variable Insurance Products Trust (“FTVIPT”), a Delaware statutory trust. FTVIPT is registered as an open-end management investment company under the 1940 Act (File No. 811-05583), and its shares are registered as securities under the 1933 Act (File No. 033-23493). The Replaced Fund is managed by Franklin Mutual Advisers, LLC, which is not an affiliate of the Insurance Company Applicants.</P>
                <P>5. The following table shows the inception date and net assets at December 31, 2010, for each class of shares of the Replaced Fund:</P>
                <GPOTABLE COLS="3" OPTS="L2,tp0,i1" CDEF="s75,r50,xs60">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Replaced Fund</CHED>
                        <CHED H="1">Inception date</CHED>
                        <CHED H="1">
                            Net assets at 
                            <LI>December 31, </LI>
                            <LI>2010</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="22">Mutual Global Discovery Securities Fund:</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Class 1</ENT>
                        <ENT>Nov. 8, 1996</ENT>
                        <ENT>$84.2 million*</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Class 2</ENT>
                        <ENT>Jan. 6, 1999</ENT>
                        <ENT>1.35 billion**</ENT>
                    </ROW>
                    <TNOTE>* As of December 31, 2010, approximately 99.9% of the assets in Class 1 of the Replaced Fund would have been transferred to Institutional Class of the Replacement Fund.</TNOTE>
                    <TNOTE>** As of December 31, 2010, approximately 36.4% of the assets in Class 2 of the Replaced Fund would have been transferred to Advisor Class of the Replacement Fund.</TNOTE>
                </GPOTABLE>
                <P>6. The following table shows the inception date and net assets at December 31, 2010, for each class of shares of the Replacement Fund:</P>
                <GPOTABLE COLS="3" OPTS="L2,tp0,i1" CDEF="s75,r50,xs52">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Replacement Fund</CHED>
                        <CHED H="1">Inception date</CHED>
                        <CHED H="1">
                            Net assets at 
                            <LI>December 31, </LI>
                            <LI>2010</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="22">
                            PIMCO EqS Pathfinder Portfolio
                            <SU>TM</SU>
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Institutional Class</ENT>
                        <ENT>April 14, 2010</ENT>
                        <ENT>$3.3 million.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Advisor Class</ENT>
                        <ENT>April 14, 2010</ENT>
                        <ENT>2.5 million.</ENT>
                    </ROW>
                </GPOTABLE>
                <P>7. Subaccounts investing in Class 1 shares of the Replaced Fund and Institutional Class shares of the Replacement Fund are available only to owners of certain Contracts that are no longer offered for sale by the Insurance Company Applicants. Pursuant to the proposed Substitution, the Insurance Company Applicants will replace shares of subaccounts investing in Class 1 shares of the Replaced Fund on the date of the Substitution with Institutional Class shares of the Replacement Fund.</P>
                <P>8. Subaccounts investing in Class 2 shares of the Replaced Fund and Advisor Class shares of the Replacement Fund are available to owners of various Contracts, including Contracts that are no longer offered for sale and Contracts currently offered for sale by the Insurance Company Applicants. Pursuant to the proposed Substitution, the Insurance Company Applicants will replace shares of subaccounts investing in Class 2 shares of the Replaced Fund on the date of the Substitution with Advisor Class shares of the Replacement Fund.</P>
                <P>9. It is currently anticipated that the Substitution will occur on or about July 22, 2011, or as soon thereafter as may be practicable following receipt of the requested Order of the Commission (the “Substitution Date”). Following the Substitution, the Replaced Fund will no longer be offered under any Contract issued by Allianz Life or Allianz NY.</P>
                <P>10. Allianz Life is a stock life insurance company organized under the laws of the state of Minnesota in 1896. Allianz Life offers fixed and variable annuities and individual life insurance. Allianz Life is licensed to do direct business in 49 states and the District of Columbia. Allianz Life is a subsidiary of Allianz SE, a “Societas Europaea” or European stock corporation.</P>
                <P>11. Allianz NY is a stock life insurance company organized under the laws of the state of New York on September 21, 1982. Allianz NY offers fixed and variable annuities. Allianz NY is licensed to do direct business in six states, including New York and the District of Columbia.</P>
                <P>12. Allianz Account A is a segregated asset account of Allianz Life. Allianz Account A was established by Allianz Life on May 31, 1985, under Minnesota insurance laws. Allianz Account A is used to fund certain variable life insurance policies issued by Allianz Life. Allianz Account A is divided into a number of subaccounts, each of which invests in and reflects the investment performance of a specific underlying registered investment company or portfolio thereof (each an “Investment Option”). Allianz Account A is registered as a unit investment trust under the 1940 Act (File No. 811-04965).</P>
                <P>13. Allianz Account B is a segregated asset account of Allianz Life. Allianz Account B was established by Allianz Life on May 31, 1985, under Minnesota insurance laws. Allianz Account B is used to fund certain variable annuity contracts issued by Allianz Life. Allianz Account B is divided into a number of subaccounts, each of which invests in and reflects the investment performance of a specific Investment Option. Allianz Account B is registered as a unit investment trust under the 1940 Act (File No. 811-05618).</P>
                <P>14. Allianz Account C is a segregated asset account of Allianz NY. Allianz Account C was established by Allianz NY on February 26, 1988, under New York insurance laws. Allianz Account C is used to fund certain variable annuity contracts issued by Allianz NY. Allianz Account C is divided into a number of subaccounts, each of which invests in and reflects the investment performance of a specific Investment Option. Allianz Account C is registered as a unit investment trust under the 1940 Act (File No. 811-05716).</P>
                <P>
                    15. The table below shows current and effective registration statements with the Commission for Contracts funded by Allianz Account B that offer the Replaced Fund as an Investment Option:
                    <PRTPAGE P="35251"/>
                </P>
                <GPOTABLE COLS="5" OPTS="L2,tp0,i1" CDEF="s50,12,r50,r50,10">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Separate account</CHED>
                        <CHED H="1">Registration No.</CHED>
                        <CHED H="1">Contract name</CHED>
                        <CHED H="1">Type of contract</CHED>
                        <CHED H="1">Number of Investment Options (total/unaffiliated)</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Allianz Account B</ENT>
                        <ENT>333-82329</ENT>
                        <ENT>
                            Allianz Alterity 
                            <SU>(2)</SU>
                        </ENT>
                        <ENT>Variable Deferred Annuity</ENT>
                        <ENT>67/25</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Allianz Account B</ENT>
                        <ENT>333-145866</ENT>
                        <ENT>
                            Allianz Connections 
                            <SU>(2)</SU>
                        </ENT>
                        <ENT>Variable Deferred Annuity</ENT>
                        <ENT>52/11</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Allianz Account B</ENT>
                        <ENT>333-90260</ENT>
                        <ENT>
                            Allianz High Five 
                            <SU>(2)</SU>
                        </ENT>
                        <ENT>Variable Deferred Annuity</ENT>
                        <ENT>61/24</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Allianz Account B</ENT>
                        <ENT>333-120181</ENT>
                        <ENT>
                            Allianz High Five L.
                            <SU>(2)</SU>
                        </ENT>
                        <ENT>Variable Deferred Annuity</ENT>
                        <ENT>57/20</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Allianz Account B</ENT>
                        <ENT>333-95729</ENT>
                        <ENT>
                            Allianz Rewards 
                            <SU>(2)</SU>
                        </ENT>
                        <ENT>Variable Deferred Annuity</ENT>
                        <ENT>66/25</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Allianz Account B</ENT>
                        <ENT>333-139701</ENT>
                        <ENT>
                            Allianz Vision 
                            <SU>(2)</SU>
                        </ENT>
                        <ENT>Variable Deferred Annuity</ENT>
                        <ENT>52/11</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Allianz Account B</ENT>
                        <ENT>33-23035</ENT>
                        <ENT>
                            Valuemark II 
                            <SU>(1)</SU>
                        </ENT>
                        <ENT>Variable Deferred Annuity</ENT>
                        <ENT>62/25</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Allianz Account B</ENT>
                        <ENT>333-06709</ENT>
                        <ENT>
                            Valuemark IV 
                            <SU>(1)</SU>
                        </ENT>
                        <ENT>Variable Deferred Annuity</ENT>
                        <ENT>62/25</ENT>
                    </ROW>
                    <TNOTE>
                        <SU>(1)</SU>
                         Only Class 1 shares are available through this contract.
                    </TNOTE>
                    <TNOTE>
                        <SU>(2)</SU>
                         Only Class 2 shares are available through this contract.
                    </TNOTE>
                </GPOTABLE>
                <P>16. In addition, Allianz Life has the following registration statements that are no longer updated for eleven Contracts funded by Allianz Account A and Allianz Account B (the “A and B Great Wested Contracts”). Although the A and B Great Wested Contracts are no longer offered for sale, they do offer the Replaced Fund as an Investment Option:</P>
                <GPOTABLE COLS="5" OPTS="L2,tp0,i1" CDEF="s50,12,r50,r50,10">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Separate account</CHED>
                        <CHED H="1">Registration No.</CHED>
                        <CHED H="1">Contract name</CHED>
                        <CHED H="1">Type of contract</CHED>
                        <CHED H="1">Number of Investment Options (Total/unaffiliated)</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Allianz Account B</ENT>
                        <ENT>333-126217</ENT>
                        <ENT>
                            Allianz Custom Income 
                            <SU>(2)</SU>
                        </ENT>
                        <ENT>Variable Deferred Annuity</ENT>
                        <ENT>28/8</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Allianz Account B</ENT>
                        <ENT>333-134267</ENT>
                        <ENT>
                            Allianz Elite 
                            <SU>(2)</SU>
                        </ENT>
                        <ENT>Variable Deferred Annuity</ENT>
                        <ENT>49/13</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Allianz Account A</ENT>
                        <ENT>33-11158</ENT>
                        <ENT>
                            Allianz ValueLife 
                            <SU>(1)</SU>
                        </ENT>
                        <ENT>Flexible Premium Variable Universal Life</ENT>
                        <ENT>32/17</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Allianz Account B</ENT>
                        <ENT>333-111049</ENT>
                        <ENT>
                            Allianz High Five Bonus 
                            <SU>(2)</SU>
                        </ENT>
                        <ENT>Variable Deferred Annuity</ENT>
                        <ENT>57/20</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Allianz Account B</ENT>
                        <ENT>333-63719</ENT>
                        <ENT>
                            USAllianz Charter 
                            <SU>(2)</SU>
                        </ENT>
                        <ENT>Variable Deferred Annuity</ENT>
                        <ENT>42/23</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Allianz Account B</ENT>
                        <ENT>333-101812</ENT>
                        <ENT>
                            USAllianz Charter II 
                            <SU>(2)</SU>
                        </ENT>
                        <ENT>Variable Deferred Annuity</ENT>
                        <ENT>46/22</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Allianz Account B</ENT>
                        <ENT>333-47886</ENT>
                        <ENT>
                            USAllianz Dimensions 
                            <SU>(2)</SU>
                        </ENT>
                        <ENT>Variable Deferred Annuity</ENT>
                        <ENT>38/22</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Allianz Account A</ENT>
                        <ENT>333-60206</ENT>
                        <ENT>
                            USAllianz LifeFund 
                            <SU>(2)</SU>
                        </ENT>
                        <ENT>Flexible Premium Variable Universal Life</ENT>
                        <ENT>44/22</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Allianz Account B</ENT>
                        <ENT>33-72046</ENT>
                        <ENT>
                            Valuemark III 
                            <SU>(1)</SU>
                        </ENT>
                        <ENT>Variable Deferred Annuity</ENT>
                        <ENT>62/25</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Allianz Account B</ENT>
                        <ENT>33-76190</ENT>
                        <ENT>
                            Valuemark Income Plus 
                            <SU>(1)</SU>
                        </ENT>
                        <ENT>Variable Immediate Annuity</ENT>
                        <ENT>54/23</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Allianz Account A</ENT>
                        <ENT>33-15464</ENT>
                        <ENT>
                            Valuemark Life 
                            <SU>(1)</SU>
                        </ENT>
                        <ENT>Single Premium Variable Life</ENT>
                        <ENT>32/17</ENT>
                    </ROW>
                    <TNOTE>
                        <SU>(1)</SU>
                         Only Class 1 shares are available through this contract.
                    </TNOTE>
                    <TNOTE>
                        <SU>(2)</SU>
                         Only Class 2 shares are available through this contract.
                    </TNOTE>
                </GPOTABLE>
                <P>17. Currently Allianz NY has the following current and effective registration statement with the Commission for one Contract funded by Allianz Account C that offers the Replaced Fund as an Investment Option:</P>
                <GPOTABLE COLS="5" OPTS="L2,tp0,i1" CDEF="s50,12,r50,r50,10">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Separate account</CHED>
                        <CHED H="1">Registration No.</CHED>
                        <CHED H="1">Contract name</CHED>
                        <CHED H="1">Type of contract</CHED>
                        <CHED H="1">Number of Investment Options (Total/Unaffiliated)</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Allianz Account C</ENT>
                        <ENT>333-143195</ENT>
                        <ENT>Allianz Vision NY-(Only Class 2 shares available)</ENT>
                        <ENT>Variable Deferred Annuity</ENT>
                        <ENT>52/11</ENT>
                    </ROW>
                </GPOTABLE>
                <P>18. In addition, Allianz NY has the following registration statements that are no longer updated for six Contracts funded by Allianz Account C (the “C Great Wested Contracts”). Although the C Great Wested Contracts are no longer offered for sale, they do offer the Replaced Fund as an Investment Option:</P>
                <GPOTABLE COLS="5" OPTS="L2,tp0,i1" CDEF="s50,12,r50,r50,10">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Separate account</CHED>
                        <CHED H="1">Registration No.</CHED>
                        <CHED H="1">Contract name</CHED>
                        <CHED H="1">Type of contract</CHED>
                        <CHED H="1">Number of Investment Options (Total/Unaffiliated)</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Allianz Account C</ENT>
                        <ENT>333-19699</ENT>
                        <ENT>
                            Allianz Advantage NY 
                            <SU>(2)</SU>
                        </ENT>
                        <ENT>Variable Deferred Annuity</ENT>
                        <ENT>65/25</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Allianz Account C</ENT>
                        <ENT>333-105274</ENT>
                        <ENT>
                            Allianz Charter II NY 
                            <SU>(2)</SU>
                        </ENT>
                        <ENT>Variable Deferred Annuity</ENT>
                        <ENT>61/21</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Allianz Account C</ENT>
                        <ENT>333-124767</ENT>
                        <ENT>
                            Allianz High Five NY 
                            <SU>(2)</SU>
                        </ENT>
                        <ENT>Variable Deferred Annuity</ENT>
                        <ENT>57/20</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Allianz Account C</ENT>
                        <ENT>333-75718</ENT>
                        <ENT>
                            Allianz Opportunity NY 
                            <SU>(2)</SU>
                        </ENT>
                        <ENT>Variable Deferred Annuity</ENT>
                        <ENT>65/25</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="35252"/>
                        <ENT I="01">Allianz Account C</ENT>
                        <ENT>33-26646</ENT>
                        <ENT>
                            Valuemark II NY 
                            <SU>(1)</SU>
                        </ENT>
                        <ENT>Variable Deferred Annuity</ENT>
                        <ENT>32/17</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Allianz Account C</ENT>
                        <ENT>333-19699</ENT>
                        <ENT>
                            Valuemark IV NY 
                            <SU>(1)</SU>
                        </ENT>
                        <ENT>Variable Deferred Annuity</ENT>
                        <ENT>47/23</ENT>
                    </ROW>
                    <TNOTE>
                        <SU>(1)</SU>
                         Only Class 1 shares are available through this contract.
                    </TNOTE>
                    <TNOTE>
                        <SU>(2)</SU>
                         Only Class 2 shares are available through this contract.
                    </TNOTE>
                </GPOTABLE>
                <P>19. Of the Contracts that offer the Replaced Fund as an Investment Option, only Allianz Vision and Allianz Vision New York currently are offered for sale.</P>
                <P>20. Under the Contracts, the Insurance Company Applicants reserve the right, subject to regulatory approval, to substitute one of the Investment Options with another Investment Option after appropriate notice. Moreover, the Contracts permit the Insurance Company Applicants to limit allocation of purchase payments to one or more subaccounts that invest in an Investment Option. The prospectuses for the Contracts also contain disclosure of these rights.</P>
                <P>21. The proposed Substitution is due primarily to the fact that the Replacement Fund, which has the same investment objective and substantially similar investment strategies as the Replaced Fund, is managed by the same portfolio managers who previously managed the Replaced Fund. The Replacement Fund's portfolio is jointly managed by Anne Gudefin and Charles Lahr. Ms. Gudefin and Mr. Lahr were hired by PIMCO at the end of 2009, to manage the Replacement Fund on its inception in April, 2010; they previously served as the co-lead portfolio managers of the Replaced Fund since 2007. As a result, the Replacement Fund now is managed by the same portfolio managers, and with substantially the same mandate and value-oriented style, as the Replaced Fund prior to the transition. The Replaced Fund, on the other hand, now is managed by a new portfolio management team.</P>
                <P>22. The proposed Substitution also is part of an overall business plan of the Insurance Company Applicants to make their respective products more efficient to monitor and administer and more competitive (both in terms of new sales and the retention of existing business). The Insurance Company Applicants believe that more concentrated and streamlined operations for Investment Options will result in increased operational and administrative efficiencies and economies of scale for the Insurance Company Applicants. Having added the Replacement Fund as an Investment Option to retain the ability for Contract holders to invest in a value-oriented fund managed by Ms. Gudefin and Mr. Lahr, the Insurance Company Applicants believe that it would enhance operational and administrative efficiency to replace the Replaced Fund, which, with the same mandate and value-oriented style as the Replacement Fund, is a largely redundant Investment Option.</P>
                <P>23. For these reasons and the reasons discussed below, the Applicants believe that substituting the Replacement Fund for the Replaced Fund is appropriate and in the best interests of the contract owners.</P>
                <P>24. The Insurance Company Applicants believe that the Replacement Fund is an appropriate replacement for the Replaced Fund because its investment objective is the same (both funds seek capital appreciation) and its principal investment strategies are substantially the same as those of the Replaced Fund. In addition, because the principal investment risks of the Replaced Fund and the Replacement Fund are substantially the same, the risk expectations of those contract owners with interests in the Replaced Fund will continue to be met after the Substitution. Comparisons of the investment objectives, principal investment policies and principal investment risks of the Funds are set forth in the application.</P>
                <P>25. The following chart compares the management fees and the total annual fund operating expenses (before and after any waivers and reimbursements) for the year ended December 31, 2010, expressed as an annual percentage of average daily net assets, of the Replaced Fund and the Replacement Fund.</P>
                <GPOTABLE COLS="5" OPTS="L2,tp0,i1" CDEF="s100,12,12,13,13">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1"> </CHED>
                        <CHED H="1">
                            Mutual Global Discovery 
                            <LI>Securities Fund </LI>
                            <LI>(Replaced Fund)</LI>
                            <LI>(percent)</LI>
                        </CHED>
                        <CHED H="2">Class 1</CHED>
                        <CHED H="2">Class 2</CHED>
                        <CHED H="1">
                            PIMCO EqS Pathfinder 
                            <LI>
                                Portfolio
                                <SU>TM</SU>
                                 (Replacement Fund)
                            </LI>
                            <LI>(percent)</LI>
                        </CHED>
                        <CHED H="2">Institutional class</CHED>
                        <CHED H="2">Advisor class</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Management Fee</ENT>
                        <ENT>0.80</ENT>
                        <ENT>0.80</ENT>
                        <ENT>
                            <SU>(1)</SU>
                             0.75
                        </ENT>
                        <ENT>
                            <SU>(1)</SU>
                             0.75
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Distribution (12b-1) Fees</ENT>
                        <ENT/>
                        <ENT>0.25</ENT>
                        <ENT/>
                        <ENT>0.25</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Other Expenses</ENT>
                        <ENT>0.20</ENT>
                        <ENT>0.20</ENT>
                        <ENT>0.04</ENT>
                        <ENT>0.02</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Acquired Fund Fees and Expenses</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT>0.02</ENT>
                        <ENT>0.02</ENT>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="01">Supervision and Administration Fee</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT>
                            <SU>(2)</SU>
                             0.35
                        </ENT>
                        <ENT>
                            <SU>(2)</SU>
                             0.35
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Total Annual Fund Operating Expenses</ENT>
                        <ENT>1.00</ENT>
                        <ENT>1.25</ENT>
                        <ENT>1.16</ENT>
                        <ENT>1.39</ENT>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="01">Fee Waiver/Expense Reimbursement</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT>
                            <SU>(3)</SU>
                             (0.13)
                        </ENT>
                        <ENT>
                            <SU>(3)</SU>
                             (0.13)
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Total Annual Fund Operating Expenses After Fee Waiver/Expense Reimbursement</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT>1.03</ENT>
                        <ENT>1.26</ENT>
                    </ROW>
                    <TNOTE>
                        <SU>(1)</SU>
                         Pursuant to an Investment Advisory Contract, dated March 30, 2010, PIMCO acts as investment adviser to the Replacement Fund and receives, as compensation from the fund, an investment advisory fee of 0.75%.
                        <PRTPAGE P="35253"/>
                    </TNOTE>
                    <TNOTE>
                        <SU>(2)</SU>
                         Pursuant to a Supervision and Administration Agreement, dated March 30, 2010, PIMCO also acts as the administrator to the Replacement Fund and is responsible both for providing various supervisory and administrative services and for paying the expenses of various other services (such as audits, transfer agent, registrar, custodial services, shareholder meetings, ordinary legal fees, and fidelity bond/insurance premiums). As compensation for these services, PIMCO receives a supervisory and administrative fee of 0.35%. In its prospectus, the Replacement Fund discloses this fee together with the investment advisory fee as a combined management fee of 1.10%. The expenses incurred by the Replaced Fund for similar administrative services are included under Other Expenses.
                    </TNOTE>
                    <TNOTE>
                        <SU>(3)</SU>
                         PIMCO has contractually agreed, through May 1, 2012, to reduce its advisory fee by 0.13% of the average daily net assets of the Portfolio. This Fee Limitation Agreement renews annually unless terminated by PIMCO upon at least 30 days' prior notice to the end of the contract term. Under certain conditions, PIMCO may recoup amounts reduced in future periods, not exceeding three years.
                    </TNOTE>
                </GPOTABLE>
                <P>26. The assets and performance of the Funds for the years ending December 31, 2009 and December 31, 2010 are set forth in the application.</P>
                <P>27. Applicants hereby request the Commission's approval to effect the substitution of shares of the Replacement Fund for shares of the Replaced Fund as follows: Institutional Class shares of the PIMCO EqS Pathfinder Portfolio for Class 1 shares of the Mutual Global Discovery Securities Fund; and Advisor Class shares of the PIMCO EqS Pathfinder Portfolio for Class 2 shares of the Mutual Global Discovery Securities Fund.</P>
                <P>28. At the close of business on the Substitution Date, Allianz Life and Allianz NY will each redeem shares of the Replaced Fund held by their Separate Accounts in-kind or in cash, or a combination thereof, and apply the proceeds of such redemptions to the purchase of shares of the Replacement Fund. Thus, after the Substitution, each subaccount of the Separate Accounts previously holding shares of the Replaced Fund will hold shares of the Replacement Fund.</P>
                <P>29. Redemption requests and purchase orders will be placed simultaneously so that redemption of Replaced Fund shares and purchase of Replacement Fund shares will both occur at the price for such shares computed as of the close of business on the Substitution Date in a manner consistent with Rule 22c-1 under the 1940 Act. As a result, the full net asset value of the Replaced Fund shares held by the Separate Account Applicants will be reflected in the contract owners' contract values following the Substitution, without reduction for brokerage or other such fees or charges. All expenses incurred in connection with the Substitution, including legal, accounting, transactional, and other fees and expenses, including brokerage commissions, will be paid by Allianz Life, Allianz NY or PIMCO. Accordingly, contract value attributable to contract owners then invested in the Replaced Fund will remain fully invested at all times, and the Substitution will take place at relative net asset value with no change in the amount of any contract owner's contract value, death benefit, or in the dollar value of his or her investment in the applicable Separate Account.</P>
                <P>
                    30. Affected contract owners will not incur any fees or charges in connection with the Substitution so that the net asset value of redeemed shares of the Replaced Fund held by the Separate Account Applicants will be reflected in the contract owners' contract values following the Substitution. Moreover, neither the obligations of the respective Insurance Company Applicants under the Contracts nor the rights of contract owners will be altered in any way by the Substitution. The Substitution will not impose any tax liability or have any adverse tax consequences on contract owners. The Substitution will not cause Contract fees and charges currently being paid by existing owners of Contracts to be greater after the Substitution than they were before the Substitution. For a period of at least 30 days following the Substitution, neither Allianz Life nor Allianz NY will exercise any right they may have under the Contracts to impose additional restrictions on transfers.
                    <SU>1</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         One exception to this would be restrictions that Allianz Life or Allianz NY may impose to deter or prevent “market timing” activities by owners of Contracts or their agents.
                    </P>
                </FTNT>
                <P>31. The Insurance Company Applicants represent that PIMCO and the Replacement Fund will enter into a written contract agreeing that during the 24 months following the Substitution Date, the total annual fund operating expenses, net of any acquired fund fees and expenses, of the Replacement Fund (taking into account applicable fee waivers and expense reimbursements) will not exceed the total annual fund operating expenses, net of any acquired fund fees and expenses, of the Replaced Fund for the fiscal year ended December 31, 2010; this contractual expense limitation will be set at 1.00% for Institutional Class shares and 1.25% for Advisor Class shares. In addition, for the 24 months following the Substitution Date, the Insurance Company Applicants will not increase separate account fees and charges for the Contracts outstanding on the Substitution Date. Thereafter, total annual fund operating expenses for the Replacement Fund will vary from year to year and may exceed those of the Replaced Fund.</P>
                <P>32. Contract owners have been notified of the application by means of a Notice of Substitution sent on May 25, 2011, stating that the Applicants filed the initial application and seek approval for the Substitution. The Notice of Substitution set forth the anticipated Substitution Date and advised affected contract owners that on the Substitution Date contract values allocated to subaccounts investing in shares of the Replaced Fund will be transferred to subaccounts investing in shares of the Replacement Fund, without charge (including sales charges or surrender charges) and without being counted toward the number of transfers that may be permitted without charge.</P>
                <P>33. The Notice of Substitution also stated that, from the date of the Notice (May 25, 2011) through the date 30 days after the Substitution (the “Free Transfer Period”), the respective Insurance Company Applicants will allow the affected contract owners to make one transfer of contract value held in each subaccount investing in the Replaced Fund (before the Substitution) or Replacement Fund (after the Substitution) to one or more Investment Options available pursuant to the Contracts, subject to any Investment Option allocation restrictions under their Contract, without charge and without assessing transfer fees. Such a transfer will not be counted as a transfer request under any contractual provisions of the Contracts that limit the number of transfers that may be made without charge. Further, prior to the Substitution, all affected contract owners will receive a copy of the most recent prospectus for the Replacement Fund.</P>
                <P>
                    34. Within five days following the Substitution, the Insurance Company Applicants will send a Post-Substitution notice to affected contract owners stating that the Substitution was carried out and reiterating the information set forth in the Notice, including a reminder that the Free Transfer Period will continue through the date 30 days after the Substitution.
                    <PRTPAGE P="35254"/>
                </P>
                <HD SOURCE="HD1">Applicants' Legal Analysis and Conditions</HD>
                <HD SOURCE="HD2">Section 26(c) Relief</HD>
                <P>1. Applicants submit that the Substitution does not present the type of costly forced redemption or other harms that Section 26(c) of the Act was intended to guard against and is consistent with the protection of investors and the purposes fairly intended by the 1940 Act. The Substitution is consistent with contract owners' objectives and risk expectations because the investment objective, principal investment strategies and risks of the Replacement Fund are substantially similar to those of the Replaced Fund. In addition, the total annual fund operating expenses of the Replacement Fund will be no higher than those of the Replaced Fund, after applicable fee waivers and expense reimbursements that will be in place for the Replacement Fund, for a period of at least 24 months following the Substitution.</P>
                <P>2. Applicants represent that for a period of 24 months from the date of the Substitution, the PIMCO EqS Pathfinder Portfolio will be subject to an expense cap (1.00% for Institutional Class shares; 1.25% for Advisor Class shares) limiting its total annual fund operating expenses, net of any acquired fund fees and expenses, to an amount not to exceed the total annual fund operating expenses of the Mutual Global Discovery Securities Fund, net of any acquired fund fees and expenses, for the fiscal year ended December 31, 2010. In addition, for the 24 months following the Substitution Date, the Insurance Company Applicants will not increase separate account fees and charges for the Contracts outstanding on the Substitution Date</P>
                <P>3. Owners of Contracts who are beneficial shareholders of the Replaced Fund have been provided with appropriate Notice of the Substitution and Free Transfer Period. No 12b-1 fees are assessed to Class 1 shares of the Replaced Fund or the Institutional Class shares of the Replacement Fund. Identical 12b-1 fees of 0.25% of average daily net assets are assessed to Class 2 shares of the Replaced Fund and the Advisor Class shares of the Replacement Fund.</P>
                <P>4. Applicants submit that the investment objectives are the same and the investment strategies are substantially the same for both Funds; both primarily invest in equity securities (and securities convertible into, or that the adviser expects to be exchanged for, common or preferred stock) of issuers that the manager believes are undervalued. The risks are similar for both Funds and are consistent with the risks generally applicable to the types of securities (such as value-oriented equity securities, arbitrage securities and distressed companies and foreign securities) in which both funds invest.</P>
                <P>5. In addition to identical investment objectives and substantially similar principal investment strategies and risks, as well as total annual fund operating expenses that are expected to be no higher (after waivers), the advisory services that are provided to the Replacement Fund by its investment adviser are comparable to the types of advisory services provided to the Replaced Fund by its investment adviser. The investment advisory fee paid to PIMCO by the Replacement Fund (0.75%) is slightly lower than the investment advisory fee paid to Franklin Mutual Advisers by the Replaced Fund (0.80%).</P>
                <P>6. The Contracts contain features that provide adequate protection to contract owners in the event of a substitution. Moreover, the Substitution will be subject to the following: (1) A contract owner may request that his or her contract value be reallocated to another Investment Option, subject to any Investment Option allocation restrictions under their Contract, at any time during the Free Transfer Period without charge. The Free Transfer Period provides sufficient time for contract owners to reconsider their Investment Options; (2) the Substitution will be at the net asset value of the respective shares, without the imposition of any transfer, brokerage or similar charge; (3) neither the contract owners, the Replaced Fund, nor the Replacement Fund will bear any costs of the Substitution, and all legal, accounting, and transactional costs and any brokerage or other costs incurred in the Substitution will be paid by the Insurance Company Applicants or PIMCO, and accordingly, the Substitution will have no impact on the contract owners' contract values; (4) the Substitution will in no way alter the contractual obligations of the Insurance Company Applicants or the rights and privileges of contract owners under the Contracts; and (5) the Substitution will in no way alter the tax benefits to contract owners.</P>
                <P>7. The Applicants, on the basis of the facts and circumstances described above and in the application, have determined that it is in the best interests of contract owners to substitute shares of the Replaced Fund with shares of the Replacement Fund.</P>
                <P>8. Applicants submit that the Substitution is consistent with the protection of investors and the purposes fairly intended by the policy and provisions of the 1940 Act.</P>
                <HD SOURCE="HD2">Section 17(b) Relief</HD>
                <P>1. The Section 17 Applicants request that the Commission issue an order pursuant to Section 17(b) of the 1940 Act exempting them from Section 17(a) of the 1940 Act to the extent necessary to permit Allianz Life and Allianz NY to carry out the Substitution by redeeming shares of the Replaced Fund in kind and using such proceeds to purchase shares of the Replacement Fund.</P>
                <P>2. Section 17(a)(1) of the 1940 Act prohibits any affiliated person of a registered investment company, or an affiliated person of an affiliated person, acting as principal, from selling any security or other property to such registered investment company. Section 17(a)(2) of the 1940 Act prohibits any of the persons described above, acting as principal, from purchasing any security or other property from such registered investment company.</P>
                <P>
                    3. Applicants may be considered affiliates of the Replacement Fund based upon the definition of “affiliated person” in Section 2(a)(3) of the 1940 Act. Shares of the Replacement Fund are held by the Separate Accounts. Because shares held by a separate account of an insurance company are legally owned by the insurance company, Allianz Life and Allianz NY and their affiliates collectively own of record shares of the Replacement Fund. Further, PIMCO, which is an affiliated person of the Replacement Fund by virtue of Section 2(a)(3)(E) of the 1940 Act, is, like Allianz Life and Allianz NY, a wholly owned subsidiary of Allianz SE. For these reasons, the Replacement Fund is arguably under the control of Allianz Life and Allianz NY notwithstanding the fact that contract owners may be considered the beneficial owners of those shares held in the Separate Accounts. If the Replacement Fund is under the control of Allianz Life and Allianz NY, then each of Allianz Life and Allianz NY, or any person controlling Allianz Life and Allianz NY, or any person under common control with Allianz Life and Allianz NY, is an affiliated person of the Replacement Fund. Similarly, if the Replacement Fund is under the control of Allianz Life and Allianz NY, then the Replacement Fund is an affiliated person of Allianz Life and Allianz NY, and of any persons that control Allianz Life and Allianz NY or are under 
                    <PRTPAGE P="35255"/>
                    common control with Allianz Life and Allianz NY.
                </P>
                <P>
                    4. At the close of business on the Substitution Date, the Insurance Company Applicants will redeem shares of the Replaced Fund either in-kind or in cash, or a combination thereof, and use the proceeds of such redemptions to purchase shares of the Replacement Fund, with each subaccount of the applicable Separate Account investing the proceeds of its redemption from the Replaced Fund in the Replacement Fund. Thus, the proposed transactions may involve a transfer of portfolio securities by the Replaced Fund to Allianz Life and Allianz NY. Immediately thereafter, Allianz Life and Allianz NY would purchase shares of the Replacement Fund with the portfolio securities and/or cash received from the Replaced Fund. This aspect of the Substitution may be deemed to involve one or more sales by Allianz Life or Allianz NY of securities or other property to the Replacement Fund, and could therefore be viewed as being prohibited by Section 17(a) of the l940 Act. Accordingly, the Section 17 Applicants seek relief from Section 17(a) of the 1940 Act for the in-kind purchases and sales of the Replacement Fund shares.
                    <SU>2</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         Any in-kind redemptions from the Replaced Fund will be effected in accordance with the conditions set forth in the Commission's no-action letter issued to the Signature Financial Group (publicly available December 28, 1999).
                    </P>
                </FTNT>
                <P>5. Any in-kind redemptions and purchases for purposes of the Substitution will be effected in a manner consistent with the investment objectives and strategies of the Replaced Fund and the Replacement Fund. PIMCO will review the securities holdings of the Replaced Fund and determine which of the Replaced Fund's portfolio holdings would be suitable investments for the Replacement Fund in the overall context of the Replacement Fund's investment objective and strategies and consistent with PIMCO's management of the Replacement Fund. PIMCO will accept only those securities as consideration for shares that it would have acquired for the Replacement Fund in a cash transaction. The Section 17 Applicants submit that these portfolio securities will be of the type and quality that the Replacement Fund would have acquired with the proceeds from share sales had the shares been sold for cash.</P>
                <P>6. The Section 17 Applicants state that any securities to be paid out as redemption proceeds and subsequently contributed to the Replacement Fund to effect the contemplated in-kind purchases of shares will be valued based on valuation procedures adopted by the board of the PIMCO EqS VIT. The redeeming and purchasing values will be the same. Consistent with Rule 17a-7(d) under the 1940 Act, no brokerage commissions, fees, or other remuneration will be paid by the Replaced Fund or the Replacement Fund in connection with the in-kind transactions. If PIMCO declines to accept particular portfolio securities of the Replaced Fund for purchase in-kind of shares of the Replacement Fund, those positions will be liquidated by the Replaced Fund and shares of the Replacement Fund will be purchased with cash.</P>
                <P>7. Section 17(b) of the 1940 Act provides that the Commission may, upon application, grant an order exempting any transaction from the prohibitions of Section 17(a) of the l940 Act if the evidence establishes that: (1) The terms of the proposed transaction, including the consideration to be paid or received, are reasonable and fair and do not involve overreaching on the part of any person concerned; (2) the proposed transaction is consistent with the policy of each registered investment company concerned, as recited in its registration statement and records found under the 1940 Act; and (3) the proposed transaction is consistent with the general purposes of the 1940 Act.</P>
                <P>8. The Section 17 Applicants submit that the terms of the Substitution, including the consideration to be paid and received, are reasonable and fair and do not involve overreaching on the part of any person concerned principally because the transactions will conform with all but one of the conditions enumerated in Rule 17a-7 under the 1940 Act. The use of in-kind transactions will not cause contract owner interests to be diluted. The proposed transactions will take place at relative net asset value in conformity with the requirements of Section 22(c) of the 1940 Act and Rule 22c-1 thereunder with no change in the amount of any contract owner's contract value or death benefit or in the dollar value of his or her investment in any of the Separate Accounts. The proposed transactions cannot be effected at a price that is disadvantageous to either the Replaced Fund or the Replacement Fund. Contract owners will not suffer any adverse tax consequences as a result of the Substitution. Fees and charges under the Contracts will not increase because of the Substitution. Even though they may not rely on Rule 17a-7 under the 1940 Act, the Section 17 Applicants submit that the Rule's conditions outline the type of safeguards that result in transactions that are fair and reasonable to registered investment company participants and preclude overreaching in connection with an investment company by its affiliated persons.</P>
                <P>9. The board of the PIMCO EqS VIT has adopted procedures, as required by paragraph (e)(1) of Rule 17a-7 under the 1940 Act, pursuant to which the Replacement Fund may purchase and sell securities to and from its affiliates. The Section 17 Applicants will carry out the proposed in-kind purchases in conformity with all of the conditions of Rule 17a-7 under the Act and the Replacement Fund's policies and procedures relating to Rule 17a-7 under the Act, except that the consideration paid for the securities being purchased or sold may not be entirely cash. Nevertheless, the circumstances surrounding the proposed Substitution will be such as to offer to the Replacement Fund the same degree of protection from overreaching that Rule 17a-7 under the Act provides to the Replacement Fund generally in connection with its purchase and sale of securities under that Rule in the ordinary course of its business. In particular, Allianz Life and Allianz NY (or any of their affiliates) cannot effect the proposed transactions at a price that is disadvantageous to the Replacement Fund. Although the transactions may not be entirely for cash, each will be effected based upon (1) The independent market price of the portfolio securities valued as specified in paragraph (b) of Rule 17a-7 under the Act, and (2) the net asset value per share of each Fund involved valued in accordance with the procedures disclosed in its respective registration statement and as required by Rule 22c-1 under the 1940 Act. No brokerage commission, fee, or other remuneration will be paid to any party in connection with the proposed transactions. The board of the PIMCO EqS VIT will conduct its review of the transactions in the same manner that it normally would follow in accordance with Rule 17a-7 under the l940 Act.</P>
                <P>
                    10. The proposed transactions also are reasonable and fair in that they will be effected in a manner consistent with the public interest and the protection of investors. Contract owners will be fully informed of the terms of the Substitution and they will be provided a prospectus for the Replacement Fund. In addition, contract owners will have the opportunity to make a free transfer from the Replacement Fund to any other available Investment Option offered under their Contract, subject to any Investment Option allocation 
                    <PRTPAGE P="35256"/>
                    restrictions under their Contract, during the Free Transfer Period.
                </P>
                <P>11. The Section 17 Applicants also submit that the Substitution is consistent with the policies of the Replaced Fund and the Replacement Fund as recited in the current registration statement and reports filed under the 1940 Act.</P>
                <P>12. In addition, the Section 17 Applicants submit that the proposed Substitution is consistent with the general purposes of the 1940 Act as stated in the Findings and Declaration of Policy in Section 1 of the 1940 Act. The proposed transactions do not present any of the conditions or abuses that the 1940 Act was designed to prevent. Securities to be paid out as redemption proceeds from the Replaced Fund and subsequently contributed to the Replacement Fund to effect the contemplated in-kind purchases of shares will be valued in accordance with the requirements of Rule 17a-7 under the l940 Act. Therefore, there will be no change in value to any contract owner as a result of the Substitution.</P>
                <HD SOURCE="HD1">Conclusion</HD>
                <P>For the reasons and upon the facts set forth above and in the application, the Applicants and the Section 17 Applicants believe that the requested order meets the standards set forth in Section 26(c) of the Act and Section 17(b) of the Act, respectively, and should therefore, be granted.</P>
                <SIG>
                    <P>For the Commission, by the Division of Investment Management, under delegated authority.</P>
                    <NAME>Cathy H. Ahn,</NAME>
                    <TITLE>Deputy Secretary.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-14895 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 8011-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">SECURITIES AND EXCHANGE COMMISSION</AGENCY>
                <DEPDOC>[Release No. 34-64645; File No. SR-Phlx-2011-81]</DEPDOC>
                <SUBJECT>Self-Regulatory Organizations; Notice of Filing and Immediate Effectiveness of Proposed Rule Change by NASDAQ OMX PHLX LLC Relating to Routing Fees</SUBJECT>
                <DATE>June 10, 2011.</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 June 7, 2011, NASDAQ OMX PHLX LLC (“Phlx” or “Exchange”) filed with the Securities and Exchange Commission (“SEC” or “Commission”) the proposed rule change as described in Items I, II, and III, below, which Items have been prepared by the Exchange. 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>
                <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 its Customer Routing Fee governing pricing for Exchange members using the Phlx XL II system,
                    <SU>3</SU>
                    <FTREF/>
                     for routing standardized equity and index option Customer orders to the C2 Options Exchange, Inc. (“C2”) for execution.
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         For a complete description of Phlx XL II, 
                        <E T="03">see</E>
                         Securities Exchange Act Release No. 59995 (May 28, 2009), 74 FR 26750 (June 3, 2009) (SR-Phlx-2009-32). The instant proposed fees will apply only to option orders entered into, and routed by, the Phlx XL II system.
                    </P>
                </FTNT>
                <P>While fee changes pursuant to this proposal are effective upon filing, the Exchange has designated these changes to be operative on July 1, 2011.</P>
                <P>
                    The text of the proposed rule change is available on the Exchange's Web site at 
                    <E T="03">http://nasdaqtrader.com/micro.aspx?id=PHLXfilings,</E>
                     at the principal office of the Exchange, at the Commission's Public Reference Room, and on the Commission's Web site at 
                    <E T="03">http://www.sec.gov.</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 purpose of the proposed rule change is to recoup costs that the Exchange incurs for routing and executing Customer orders in equity and index options to C2.</P>
                <P>The Exchange's Fee Schedule includes Routing Fees for routing and executing Customer and Professional orders to away markets. The Exchange currently assesses a Customer Routing Fee of $0.21 per contract for option orders that are routed to C2.</P>
                <P>
                    C2 recently amended its Fees Schedule to increase its public customer taker fee from $.15 to $.25.
                    <SU>4</SU>
                    <FTREF/>
                     The Exchange is proposing to amend its Customer Routing Fee to C2 to account for this increase. The Exchange proposes to amend its Fee Schedule to assess a Customer Routing Fee of $0.31 per contract for option orders that are routed to C2.
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 64390 (May 4, 2011), 76 FR 27117 (May 10, 2011) (SR-C2-2011-011).
                    </P>
                </FTNT>
                <P>
                    In May 2009, the Exchange adopted Rule 1080(m)(iii)(A) to establish Nasdaq Options Services LLC (“NOS”), a member of the Exchange, as the Exchange's exclusive order router.
                    <SU>5</SU>
                    <FTREF/>
                     NOS is utilized by the Phlx XL II system solely to route orders in options listed and open for trading on the Phlx XL II system to destination markets. Each time NOS routes to away markets NOS is charged a $0.06 clearing fee and, in the case of certain exchanges, a transaction fee is also charged in certain symbols, which fees are passed through to the Exchange. The Exchange is proposing this amendment in order to recoup clearing and transaction charges incurred by the Exchange when Customer orders are routed to C2.
                    <SU>6</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 59995 (May 28, 2009), 74 FR 26750 (June 3, 2009) (SR-Phlx-2009-32).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         The Exchange is proposing to recoup the $.25 per contract public customer transaction fee for orders routed to C2 along with the $0.06 clearing fee which is incurred by the Exchange, as explained above. 
                        <E T="03">See</E>
                         C2 Fees Schedule.
                    </P>
                </FTNT>
                <P>As with all fees, the Exchange may adjust these Routing Fees in response to competitive conditions by filing a new proposed rule change. While fee changes pursuant to this proposal are effective upon filing, the Exchange has designated these changes to be operative on July 1, 2011.</P>
                <HD SOURCE="HD3">2. Statutory Basis</HD>
                <P>
                    The Exchange believes that its proposal to amend its Fee Schedule is consistent with Section 6(b) of the Act 
                    <SU>7</SU>
                    <FTREF/>
                     in general, and furthers the objectives of Section 6(b)(4) of the Act 
                    <SU>8</SU>
                    <FTREF/>
                     in particular, in that it is an equitable allocation of reasonable fees and other charges among Exchange members.
                </P>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         15 U.S.C. 78f(b).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         15 U.S.C. 78f(b)(4).
                    </P>
                </FTNT>
                <P>
                    The Exchange believes that this fee is reasonable because it seeks to recoup costs that are incurred by the Exchange when routing Customer orders to C2 on behalf of its members. Each destination market's transaction charge varies and there is a standard clearing charge for each transaction incurred by the 
                    <PRTPAGE P="35257"/>
                    Exchange. The Exchange believes that the proposed Routing Fee would enable the Exchange to recover the public customer transaction fee assessed by C2, plus clearing fees for the execution of Customer orders. The Exchange also believes that the proposed Routing Fee is equitable because it would be uniformly applied to all Customers.
                </P>
                <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 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>9</SU>
                    <FTREF/>
                     At any time within 60 days of the filing of the proposed rule change, the Commission summarily may temporarily suspend 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. If the Commission takes such action, the Commission shall institute proceedings to determine whether the proposed rule should be approved or disapproved.
                </P>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         15 U.S.C. 78s(b)(3)(A)(ii).
                    </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-Phlx-2011-81 on the subject line.
                </P>
                <HD SOURCE="HD2">Paper Comments</HD>
                <P>• Send paper comments in triplicate to Elizabeth M. Murphy, Secretary, Securities and Exchange Commission, 100 F Street, NE., Washington, DC 20549-1090.</P>
                <FP>
                    All submissions should refer to File Number SR-Phlx-2011-81. 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 Web site viewing and printing in the Commission's Public Reference Room, 100 F Street, NE., Washington, DC 20549, on official business days between the hours of 10 a.m. and 3 p.m. Copies of such 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-Phlx-2011-81 and should be submitted on or before July 7, 2011.
                    <FTREF/>
                </FP>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         17 CFR 200.30-3(a)(12).
                    </P>
                </FTNT>
                <SIG>
                    <P>
                        For the Commission, by the Division of Trading and Markets, pursuant to delegated authority.
                        <SU>10</SU>
                    </P>
                    <NAME>Cathy H. Ahn,</NAME>
                    <TITLE>Deputy Secretary. </TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-14903 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 8011-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">SECURITIES AND EXCHANGE COMMISSION</AGENCY>
                <DEPDOC>[Release No. 34-64644; File No. SR-CHX-2011-11]</DEPDOC>
                <SUBJECT> Self-Regulatory Organizations; Chicago Stock Exchange, Inc.; Notice of Filing and Immediate Effectiveness of Proposed Rule Change To Add a Rule Concerning the CHX Book Feed</SUBJECT>
                <DATE>June 10, 2011.</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 June 2, 2011, 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 and II below, which Items have been prepared by the Exchange. CHX has filed this proposal pursuant to Exchange Act Rule 19b-4(f)(6) 
                    <SU>3</SU>
                    <FTREF/>
                     which is 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>
                         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>
                    CHX proposes to add Article 4, Rule 1 (Book Feed) to include an explicit description of the Exchange's Book Feed information service. The text of this proposed rule change is available on the Exchange's Web site at (
                    <E T="03">http://www.chx.com</E>
                    ) and in 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 CHX 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 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 makes information about display-eligible orders sent to and trades executed on the Exchange available to Participants and other interested persons via its Book Feed Service. The purpose of making this information available is to increase the transparency of orders and trading activity on the Exchange. The Book Feed service became effective pursuant to a rule filing made with the Commission in 2007, but the service was not described in the Exchange's rules.
                    <SU>4</SU>
                    <FTREF/>
                     In order to remove any potential ambiguity about the nature of the Exchange's technology and communications offerings, we are now 
                    <PRTPAGE P="35258"/>
                    proposing to add language to our rules describing the Book Feed. The Book Feed service has not changed in any material respect.
                    <SU>5</SU>
                    <FTREF/>
                     Use of the Book Feed service by any Exchange Participant is entirely optional and is not required to direct orders to our Matching System for execution or display.
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         Securities Exchange Act Release No. 56611 (Oct. 4, 2007), 72 FR 57980 (Oct. 11, 2007).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         
                        <E T="03">See</E>
                         e-mail, dated June 2, 2011, from David C. Whitcomb, Jr., General Counsel and Chief Regulatory Officer, CHX, to Christopher W. Chow, Special Counsel, Commission.
                    </P>
                </FTNT>
                <P>New Article 4, Rule 1 governs the provision by the Exchange of its Book Feed data service. The CHX Book Feed distributes data regarding orders received and trades executed by the Matching System, our trading facility. The Book Feed service supplements the market data provided by the Exchange through the industry-mandated Securities Information Processors or SIPs (currently Nasdaq and SIAC). The SIPs collect market data from each trading center, consolidate it into a unified transmission, and disseminate it to market participants, including market data vendors.</P>
                <P>
                    The CHX Book Feed is intended to augment the market data provided by the SIPs by providing additional detail about orders resident in the Exchange's Matching System. Unlike SIP data, quotations distributed via the Book Feed are not aggregated at a particular price point. Instead, each individual order is separately represented in the Book Feed, even if there are multiple orders at the same price and on the same side of the market. Moreover, the Book Feed provides information for all displayed orders resident in the Matching System, including odd lots and orders inferior to our top of book.
                    <SU>6</SU>
                    <FTREF/>
                     The Book Feed data includes basic information about each order, including the size and price of the order; whether it was an order to buy or sell; its time of receipt; and the identity of the participant firm that submitted the order.
                    <SU>7</SU>
                    <FTREF/>
                     The Book Feed also provides for the transmission of last sale data through the Book Feed in a manner which is substantially similar to that provided through the SIPs.
                    <SU>8</SU>
                    <FTREF/>
                     Proposed Rule 1 of Article 4 authorizes the Exchange to provide Book Feed data to a recipient which has entered into a Book Feed Subscriber agreement with the Exchange and in a form acceptable to the Exchange.
                    <SU>9</SU>
                    <FTREF/>
                     No market participant is required to subscribe to the Book Feed service. The Exchange believes that some market participants will be interested in receiving our Book Feed transmission since it provides additional information about the orders residing in the Matching System beyond what is available from the SIPs.
                    <SU>10</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         Undisplayed orders and the undisplayed portions of reserve size orders are not to be disseminated through the Book Feed; however, any odd lot orders (which are not expressly identified as “undisplayed”) are disseminated through the Book Feed.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         A participant firm can choose, either on a firm-wide or order-by-order basis, to have its identity kept confidential in the order information that is distributed in the Book Feed.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         The Book Feed includes transaction data for all trades executed in the Matching System, including odd lot transactions, while the SIP last sale transmissions may not include data on odd lot executions.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         The Exchange makes the Book Feed available to any person or entity which signs our subscriber agreement. It is not necessary to be an Exchange Participant to be eligible to receive the Book Feed.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         Within the Exchange's systems, the data that is disseminated as part of the Book Feed leaves the Matching System immediately following the best bids, offers and last sales that are being sent to the SIPs. The Exchange would not use any technology that is designed to make the Book Feed data available from the Matching System earlier than the best bids, offers and last sales are available to the SIPs.
                    </P>
                </FTNT>
                <P>
                    Any charges for the Exchange's Book Feed service would be specified in our Schedule of Fees and Assessments. Currently, the Fee Schedule provides that the Book Feed shall be available free of charge to subscribers.
                    <SU>11</SU>
                    <FTREF/>
                     Rule 603(a)(2) for Regulation NMS requires trading centers to distribute market data “on terms that are not unreasonably discriminatory.” 
                    <SU>12</SU>
                    <FTREF/>
                     The policy of the Exchange is to require that all Book Feed recipients execute a subscriber agreement. This requirement applies equally to all recipients and therefore the Exchange believes that its proposal satisfies Rule 603(a)(2) for Regulation NMS.
                </P>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         The Exchange does not currently plan to charge a fee for the distribution of this data, but may choose to do so in the future. Any decision to charge a fee for the Book Feed data would be reflected in a filing submitted to the Commission as required by Rule 19b-4 of the Act.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         17 CFR 603(a)(2).
                    </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>13</SU>
                    <FTREF/>
                     in general, and furthers the objectives of Section 6(b)(1) of the Act 
                    <SU>14</SU>
                    <FTREF/>
                     in particular, in that it allows the Exchange to be organized and have the capacity to be able to carry out the purposes of the Act and to comply, and (subject to any rule or order of the Commission pursuant to section 17(d) or 19(g)(2) of the Act) to enforce compliance by its members and persons associated with such members, with the provisions of the Act, the rules and regulations thereunder, and the rules of the exchange. As noted above, the Book Feed service was previously described in a filing with the Commission in 2007.
                    <SU>15</SU>
                    <FTREF/>
                     By adding a description of the nature of the Book Feed service to the Exchange's rules, this proposal advances the purposes of the Exchange Act by providing added clarity about the nature and extent of certain services offered by the Exchange to its Participants, and thereby contributing to the ability of our members in complying with the requirements related to those services.
                </P>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         15 U.S.C. 78f.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>14</SU>
                         15 U.S.C. 78f(b)(1).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>15</SU>
                         
                        <E T="03">See</E>
                         note 4, 
                        <E T="03">supra,</E>
                         and accompanying text.
                    </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. As noted above, the Exchange believes that its Book Feed service will compete with the existing market data products issued by other exchanges and will assist the Exchange in attracting and retaining order flow. The Exchange further believes that the added transparency offered by the Book Feed service will benefit market participants looking to interact with orders residing in the Matching System or trying to determine the level of buying or selling interest in a security. The fact that the Exchange currently distributes market data for no charge also acts as a competitive force among market data products. As noted above, the Book Feed service is entirely optional and Participants are not required to subscribe to it in order to gain access to our marketplace.</P>
                <HD SOURCE="HD2">C. Self-Regulatory Organization's Statement on Comments Regarding 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) of the Act 
                    <SU>16</SU>
                    <FTREF/>
                     and Rule 19b-4(f)(6) 
                    <SU>17</SU>
                    <FTREF/>
                     thereunder in that it effects a change that: (i) Does not significantly affect the protection of investors or the public interest; (ii) does not impose any significant burden on competition; and (iii) by its terms, does not 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.
                </P>
                <FTNT>
                    <P>
                        <SU>16</SU>
                         15 U.S.C. 78s(b)(3)(A).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>17</SU>
                         17 CFR 240.19b-4(f)(6).
                    </P>
                </FTNT>
                <PRTPAGE P="35259"/>
                <P>At any time within 60 days of the filing of the proposed rule change, the Commission summarily may temporarily suspend 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>
                <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-CHX-2011-11 on the subject line.
                </P>
                <HD SOURCE="HD2">Paper Comments</HD>
                <P>• Send paper comments in triplicate to Elizabeth M. Murphy, Secretary, Securities and Exchange Commission, 100 F Street, NE., Washington, DC 20549-1090.</P>
                <FP>
                    All submissions should refer to File Number SR-CHX-2011-11. 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 Web site viewing and printing in the Commission's Public Reference Room, 100 F Street, NE., Washington, DC 20549, on official business days between the hours of 10 a.m. and 3 p.m. 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-CHX-2011-11 and should be submitted on or before July 7, 2011.
                </FP>
                <SIG>
                    <P>
                        For the Commission, by the Division of Trading and Markets, pursuant to delegated authority.
                        <SU>18</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>18</SU>
                             17 CFR 200.30-3(a)(12).
                        </P>
                    </FTNT>
                    <NAME>Cathy H. Ahn,</NAME>
                    <TITLE>Deputy Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-14894 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 8011-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">SECURITIES AND EXCHANGE COMMISSION</AGENCY>
                <DEPDOC>[File No. 500-1]</DEPDOC>
                <SUBJECT>Samaritan Pharmaceuticals, Inc., Seaena, Inc., Seirios International, Inc. (f/k/a Exactly Sportswear, Inc.), et al.; Order of Suspension of Trading</SUBJECT>
                <DATE>June 14, 2011.</DATE>
                <EXTRACT>
                    <P>Samaritan Pharmaceuticals, Inc., Seaena, Inc., Seirios International, Inc. (f/k/a Exactly Sportswear, Inc.), Sento Corp., Shoe Pavilion, Inc., Silver Eagle Resources Ltd. (n/k/a Mercator Minerals Ltd.), Simex Technologies, Inc. (n/k/a CT Holdings, Inc.), and Sola Resource Corp. (n/k/a Cancana Resources Corp.)</P>
                </EXTRACT>
                <P>It appears to the Securities and Exchange Commission that there is a lack of current and accurate information concerning the securities of Samaritan Pharmaceuticals, Inc. because it has not filed any periodic reports since the period ended December 31, 2008.</P>
                <P>It appears to the Securities and Exchange Commission that there is a lack of current and accurate information concerning the securities of Seaena, Inc. because it has not filed any periodic reports since the period ended June 30, 2008.</P>
                <P>It appears to the Securities and Exchange Commission that there is a lack of current and accurate information concerning the securities of Seirios International, Inc. (f/k/a Exactly Sportswear, Inc.) because it has not filed any periodic reports since September 30, 1995.</P>
                <P>It appears to the Securities and Exchange Commission that there is a lack of current and accurate information concerning the securities of Sento Corp. because it has not filed any periodic reports since the period ended December 31, 2006.</P>
                <P>It appears to the Securities and Exchange Commission that there is a lack of current and accurate information concerning the securities of Shoe Pavilion, Inc. because it has not filed any periodic reports since the period ended March 29, 2008.</P>
                <P>It appears to the Securities and Exchange Commission that there is a lack of current and accurate information concerning the securities of Silver Eagle Resources Ltd. (n/k/a Mercator Minerals Ltd.) because it has not filed any periodic reports since January 16, 1998.</P>
                <P>It appears to the Securities and Exchange Commission that there is a lack of current and accurate information concerning the securities of Simex Technologies, Inc. (n/k/a CT Holdings, Inc.) because it has not filed any periodic reports since the period ended September 30, 2008.</P>
                <P>It appears to the Securities and Exchange Commission that there is a lack of current and accurate information concerning the securities of Sola Resource Corp. (n/k/a Cancana Resources Corp.) because it has not filed any periodic reports since the period ended January 31, 2003.</P>
                <P>The Commission is of the opinion that the public interest and the protection of investors require a suspension of trading in the securities of the above-listed companies.</P>
                <P>Therefore, it is ordered, pursuant to Section 12(k) of the Securities Exchange Act of 1934, that trading in the securities of the above-listed companies is suspended for the period from 9:30 a.m. EDT on June 14, 2011, through 11:59 p.m. EDT on June 27, 2011.</P>
                <SIG>
                    <P>By the Commission.</P>
                    <NAME>Jill M. Peterson,</NAME>
                    <TITLE>Assistant Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-15056 Filed 6-14-11; 4:15 pm]</FRDOC>
            <BILCOD>BILLING CODE 8011-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">SECURITIES AND EXCHANGE COMMISSION</AGENCY>
                <DEPDOC> [File No. 500-1]</DEPDOC>
                <SUBJECT> In the Matter of Dawn Technologies, Inc., Distinctive Devices, Inc., Haber, Inc., and Independence Brewing Co.; Order of Suspension of Trading</SUBJECT>
                <DATE>June 14, 2011.</DATE>
                <P>It appears to the Securities and Exchange Commission that there is a lack of current and accurate information concerning the securities of Dawn Technologies, Inc. because it has not filed any periodic reports since the period ended September 30, 1999.</P>
                <P>It appears to the Securities and Exchange Commission that there is a lack of current and accurate information concerning the securities of Distinctive Devices, Inc. because it has not filed any periodic reports since the period ended September 30, 2004.</P>
                <P>
                    It appears to the Securities and Exchange Commission that there is a 
                    <PRTPAGE P="35260"/>
                    lack of current and accurate information concerning the securities of Haber, Inc. because it has not filed any periodic reports since the period ended May 31, 2007.
                </P>
                <P>It appears to the Securities and Exchange Commission that there is a lack of current and accurate information concerning the securities of Independence Brewing Co. because it has not filed any periodic reports since the period ended March 31, 1999.</P>
                <P>The Commission is of the opinion that the public interest and the protection of investors require a suspension of trading in the securities of the above-listed companies. Therefore, it is ordered, pursuant to Section 12(k) of the Securities Exchange Act of 1934, that trading in the securities of the above-listed companies is suspended for the period from 9:30 a.m. EDT on June 14, 2011, through 11:59 p.m. EDT on June 27, 2011.</P>
                <SIG>
                    <P>By the Commission.</P>
                    <NAME>Jill M. Peterson,</NAME>
                    <TITLE>Assistant Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-15055 Filed 6-14-11; 4:15 pm]</FRDOC>
            <BILCOD>BILLING CODE 8011-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">SMALL BUSINESS ADMINISTRATION</AGENCY>
                <DEPDOC>[Disaster Declaration #12572 and #12573]</DEPDOC>
                <SUBJECT>Tennessee Disaster Number TN-00053</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>U.S. Small Business Administration. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Amendment 3.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This is an amendment of the Presidential declaration of a major disaster for the State of Tennessee (FEMA-1979-DR), dated 05/09/2011.</P>
                    <P>
                        <E T="03">Incident:</E>
                         Severe Storms, Tornadoes, Straight-line, Winds, and Flooding.
                    </P>
                    <P>
                        <E T="03">Incident Period:</E>
                         04/19/2011 and continuing through 06/07/2011.
                    </P>
                    <P>
                        <E T="03">Effective Date:</E>
                         06/07/2011.
                    </P>
                    <P>
                        <E T="03">Physical Loan Application Deadline Date:</E>
                         07/08/2011.
                    </P>
                    <P>
                        <E T="03">EIDL Loan Application Deadline Date:</E>
                         02/09/2012.
                    </P>
                </SUM>
                <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>The notice of the President's major disaster declaration for the State of Tennessee, dated 05/09/2011 is hereby amended to establish the incident period for this disaster as beginning 04/19/2011 and continuing through 06/07/2011.</P>
                <P>All other information in the original declaration remains unchanged.</P>
                <EXTRACT>
                    <FP>(Catalog of Federal Domestic Assistance Numbers 59002 and 59008)</FP>
                </EXTRACT>
                <SIG>
                    <NAME>Jane M.D. Pease,</NAME>
                    <TITLE>Acting Associate Administrator for Disaster Assistance.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-14917 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 8025-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">SMALL BUSINESS ADMINISTRATION</AGENCY>
                <DEPDOC>[Disaster Declaration # 12574 and # 12575]</DEPDOC>
                <SUBJECT>Tennessee Disaster Number TN-00055</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>U.S. Small Business Administration.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Amendment 2.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This is an amendment of the Presidential declaration of a major disaster for Public Assistance Only for the State of Tennessee (FEMA-1979-DR), dated 05/09/2011.</P>
                    <P>
                        <E T="03">Incident:</E>
                         Severe Storms, Tornadoes, Straight-line, Winds, and Flooding.
                    </P>
                    <P>
                        <E T="03">Incident Period:</E>
                         04/19/2011 through 06/07/2011.
                    </P>
                    <P>
                        <E T="03">Effective Date:</E>
                         06/07/2011.
                    </P>
                    <P>
                        <E T="03">Physical Loan Application Deadline Date:</E>
                         07/08/2011.
                    </P>
                    <P>
                        <E T="03">Economic Injury (EIDL) Loan Application Deadline Date:</E>
                         02/09/2012.
                    </P>
                </SUM>
                <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>Alan 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>The notice of the President's major disaster declaration for Private Non-Profit organizations in the State of Tennessee, dated 05/09/2011, is hereby amended to establish the incident period for this disaster as beginning 04/19/2011 and continuing through 06/07/2011.</P>
                <P>All other information in the original declaration remains unchanged.</P>
                <EXTRACT>
                    <FP>(Catalog of Federal Domestic Assistance Numbers 59002 and 59008).</FP>
                </EXTRACT>
                <SIG>
                    <NAME>Jane M.D. Pease</NAME>
                    <TITLE>Acting Associate Administrator for Disaster Assistance.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-14918 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 8025-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">SMALL BUSINESS ADMINISTRATION</AGENCY>
                <DEPDOC>[Disaster Declaration # 12538 and # 12539]</DEPDOC>
                <SUBJECT>Texas Disaster # TX-00375</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>U.S. Small Business Administration.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Amendment 1.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This is an amendment of the Administrative declaration of a disaster for the State of TEXAS dated 04/26/2011.</P>
                    <P>
                        <E T="03">Incident:</E>
                         Rock House Wildfire.
                    </P>
                    <P>
                        <E T="03">Incident Period:</E>
                         04/09/2011 through 05/10/2011.
                    </P>
                    <P>
                        <E T="03">Effective Date:</E>
                         06/09/2011.
                    </P>
                    <P>
                        <E T="03">Physical Loan Application Deadline Date:</E>
                         06/27/2011.
                    </P>
                    <P>
                        <E T="03">Economic Injury (EIDL) Loan Application Deadline Date:</E>
                         01/26/2012.
                    </P>
                </SUM>
                <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>The notice of the Administrator's disaster declaration for the State of Texas, dated 04/26/2011 is hereby amended to establish the incident period for this disaster as beginning on 04/09/2011 and continuing through 05/10/2011.</P>
                <P>All other information in the original declaration remains unchanged.</P>
                <EXTRACT>
                    <FP>(Catalog of Federal Domestic Assistance Numbers 59002 and 59008)</FP>
                </EXTRACT>
                <SIG>
                    <DATED>Dated: June 9, 2011.</DATED>
                    <NAME>Karen G. Mills,</NAME>
                    <TITLE>Administrator.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-14955 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 8025-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">SMALL BUSINESS ADMINISTRATION</AGENCY>
                <DEPDOC>[Disaster Declaration #12617 and #12618]</DEPDOC>
                <SUBJECT>Illinois Disaster # IL-00030</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>U.S. 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 the Presidential declaration of a major disaster for the State of Illinois (FEMA-1991-DR), dated 06/07/2011.</P>
                    <P>
                        <E T="03">Incident:</E>
                         Severe Storms and Flooding.
                    </P>
                    <P>
                        <E T="03">Incident Period:</E>
                         04/19/2011 and continuing.
                    </P>
                    <P>
                        <E T="03">Effective Date:</E>
                         06/07/2011.
                    </P>
                    <P>
                        <E T="03">Physical Loan Application Deadline Date:</E>
                         08/08/2011.
                        <PRTPAGE P="35261"/>
                    </P>
                    <P>
                        <E T="03">Economic Injury (EIDL) Loan Application Deadline Date:</E>
                         03/07/2012.
                    </P>
                </SUM>
                <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 President's major disaster declaration on 06/07/2011, applications for 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-2">
                    <E T="03">Primary Counties (Physical Damage and Economic Injury Loans):</E>
                     Alexander, Franklin, Gallatin, Hardin, Jackson, Lawrence, Massac, Perry, Pope, Pulaski, Randolph, Saline, White, Williamson.
                </FP>
                <FP SOURCE="FP-2">
                    <E T="03">Contiguous Counties (Economic Injury Loans Only):</E>
                </FP>
                <FP SOURCE="FP1-2">Illinois: Crawford, Edwards, Hamilton, Jefferson, Johnson, Monroe,  Richland, Saint Clair, Union, Wabash, Washington, Wayne.</FP>
                <FP SOURCE="FP1-2">Indiana: Gibson, Knox, Posey. </FP>
                <FP SOURCE="FP1-2">Kentucky: Ballard, Crittenden, Livingston, Mccracken, Union.</FP>
                <FP SOURCE="FP1-2">Missouri: Cape Girardeau, Mississippi, Perry, Sainte Genevieve, Scott.</FP>
                <P>The Interest Rates are:</P>
                <GPOTABLE COLS="2" OPTS="L2,tp0,i1" CDEF="s100,8">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1"> </CHED>
                        <CHED H="1">Percent</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="22">For Physical Damage:</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Homeowners With Credit Available Elsewhere </ENT>
                        <ENT>5.375.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Homeowners Without Credit Available Elsewhere </ENT>
                        <ENT>2.688.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Businesses With Credit Available Elsewhere </ENT>
                        <ENT>6.000.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Businesses Without Credit Available Elsewhere </ENT>
                        <ENT>4.000.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Non-Profit Organizations With Credit Available Elsewhere </ENT>
                        <ENT>3.250.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Non-Profit Organizations Without Credit Available Elsewhere </ENT>
                        <ENT>3.000.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">For Economic Injury:</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Businesses &amp; Small Agricultural Cooperatives Without Credit Available Elsewhere </ENT>
                        <ENT>4.000.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Non-Profit Organizations Without Credit Available Elsewhere </ENT>
                        <ENT>3.000.</ENT>
                    </ROW>
                </GPOTABLE>
                <P>The number assigned to this disaster for physical damage is 126176 and for economic injury is 126180.</P>
                <EXTRACT>
                    <FP>(Catalog of Federal Domestic Assistance Numbers 59002 and 59008)</FP>
                </EXTRACT>
                <SIG>
                    <DATED>Jane M. D. Pease,</DATED>
                    <TITLE>Acting Associate Administrator for Disaster Assistance.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-14951 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 8025-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">SMALL BUSINESS ADMINISTRATION</AGENCY>
                <DEPDOC>[Disaster Declaration #12620 and #12621]</DEPDOC>
                <SUBJECT>Minnesota Disaster #MN-00032</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>U.S. 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 the Presidential declaration of a major disaster for Public Assistance Only for the State of  Minnesota (FEMA-1990-DR), dated 06/07/2011.</P>
                    <P>
                        <E T="03">Incident:</E>
                         Severe Storms and Tornadoes.
                    </P>
                    <P>
                        <E T="03">Incident Period:</E>
                         05/21/2011 through 05/22/2011.
                    </P>
                    <P>
                        <E T="03">Effective Date:</E>
                         06/07/2011.
                    </P>
                    <P>
                        <E T="03">Physical Loan Application Deadline Date:</E>
                         08/08/2011.
                    </P>
                    <P>
                        <E T="03">Economic Injury (EIDL) Loan Application Deadline Date:</E>
                         03/07/2012.
                    </P>
                </SUM>
                <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 President's major disaster declaration on  06/07/2011, Private Non-Profit organizations that provide essential services of governmental nature may file disaster loan applications 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>
                <P>
                    <E T="03">Primary Counties:</E>
                     Anoka, Hennepin.
                </P>
                <P>The Interest Rates are:</P>
                <GPOTABLE COLS="2" OPTS="L2,tp0,i1" CDEF="s50,8">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1"> </CHED>
                        <CHED H="1">Percent</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="22">For Physical Damage:</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Non-Profit Organizations with Credit Available Elsewhere </ENT>
                        <ENT>3.250</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Non-Profit Organizations without Credit Available Elsewhere </ENT>
                        <ENT>3.000</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">For Economic Injury:</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Non-Profit Organizations without Credit Available Elsewhere </ENT>
                        <ENT>3.000</ENT>
                    </ROW>
                </GPOTABLE>
                <P>The number assigned to this disaster for physical damage is 12620B and for economic injury is 12621B.</P>
                <EXTRACT>
                    <FP>(Catalog of Federal Domestic Assistance Numbers 59002 and 59008).</FP>
                </EXTRACT>
                <SIG>
                    <NAME>Jane M.D. Pease,</NAME>
                    <TITLE>Acting Associate Administrator  for Disaster Assistance.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-14950 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 8025-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">SMALL BUSINESS ADMINISTRATION</AGENCY>
                <DEPDOC>[Disaster Declaration #12558 and #12559]</DEPDOC>
                <SUBJECT>Tennessee Disaster Number TN-00052</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>U.S. Small Business Administration.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Amendment 3.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This is an amendment of the Presidential declaration of a major disaster for Public Assistance Only for the State of Tennessee (FEMA-1974-DR), dated 05/01/2011.</P>
                    <P>
                        <E T="03">Incident:</E>
                         Severe Storms, Tornadoes, Straight-line Winds, and Associated Flooding.
                    </P>
                    <P>
                        <E T="03">Incident Period:</E>
                         04/25/2011 through 04/28/2011.
                    </P>
                    <P>
                        <E T="03">Effective Date:</E>
                         06/07/2011.
                    </P>
                    <P>
                        <E T="03">Physical Loan Application Deadline Date:</E>
                         06/30/2011.
                    </P>
                    <P>
                        <E T="03">Economic Injury (EIDL) Loan Application Deadline Date:</E>
                         02/01/2012.
                    </P>
                </SUM>
                <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>The notice of the President's major disaster declaration for Private Non-Profit organizations in the State of Tennessee, dated 05/01/2011, is hereby amended to include the following areas as adversely affected by the disaster.</P>
                <FP SOURCE="FP-2">
                    <E T="03">Primary Counties:</E>
                     Jefferson, Marion.
                </FP>
                <P>All other information in the original declaration remains unchanged.</P>
                <EXTRACT>
                    <FP>(Catalog of Federal Domestic Assistance Numbers 59002 and 59008)</FP>
                </EXTRACT>
                <SIG>
                    <NAME>Jane M.D. Pease,</NAME>
                    <TITLE>Acting Associate Administrator for Disaster Assistance.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-14949 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 8025-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="35262"/>
                <AGENCY TYPE="S">SMALL BUSINESS ADMINISTRATION</AGENCY>
                <DEPDOC>[Disaster Declaration #12562 and #12563]</DEPDOC>
                <SUBJECT>Arkansas Disaster Number AR-00049</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>U.S. Small Business Administration.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Amendment 4.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This is an amendment of the Presidential declaration of a major disaster for Public Assistance Only for the State of Arkansas (FEMA-1975-DR), dated 05/02/2011.</P>
                    <P>
                        <E T="03">Incident:</E>
                         Severe Storms, Tornadoes, and Associated Flooding.
                    </P>
                    <P>
                        <E T="03">Incident Period:</E>
                         04/23/2011 through 06/03/2011.
                    </P>
                    <P>
                        <E T="03">Effective Date:</E>
                         06/03/2011.
                    </P>
                    <P>
                        <E T="03">Physical Loan Application Deadline Date:</E>
                         07/01/2011.
                    </P>
                    <P>
                        <E T="03">Economic Injury (EIDL) Loan Application Deadline Date:</E>
                         02/02/2012.
                    </P>
                </SUM>
                <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>The notice of the President's major disaster declaration for Private Non-Profit organizations in the State of Arkansas, dated 05/02/2011, is hereby amended to establish the incident period for this disaster as beginning 04/23/2011 and continuing through 06/03/2011.</P>
                <P>All other information in the original declaration remains unchanged.</P>
                <EXTRACT>
                    <FP>(Catalog of Federal Domestic Assistance Numbers 59002 and 59008)</FP>
                </EXTRACT>
                <SIG>
                    <NAME>Jane M.D. Pease,</NAME>
                    <TITLE>Acting Associate Administrator for Disaster Assistance.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-14948 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 8025-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">SMALL BUSINESS ADMINISTRATION</AGENCY>
                <DEPDOC>[Disaster Declaration #12578 and #12579]</DEPDOC>
                <SUBJECT>Missouri Disaster Number MO-00049</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>U.S. Small Business Administration.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Amendment 3.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This is an amendment of the Presidential declaration of a major disaster for Public Assistance Only for the State of Missouri (FEMA-1980-DR), dated 05/09/2011.</P>
                    <P>
                        <E T="03">Incident:</E>
                         Severe Storms, Tornadoes, and Flooding
                    </P>
                    <P>
                        <E T="03">Incident Period:</E>
                         04/19/2011 through 06/06/2011.
                    </P>
                    <P>
                        <E T="03">Effective Date:</E>
                         06/06/2011.
                    </P>
                    <P>
                        <E T="03">Physical Loan Application Deadline Date:</E>
                         07/08/2011.
                    </P>
                    <P>
                        <E T="03">Economic Injury (EIDL) Loan Application Deadline Date:</E>
                         02/09/2012.
                    </P>
                </SUM>
                <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>The notice of the President's major disaster declaration for Private Non-Profit organizations in the State of Missouri, dated 05/09/2011, is hereby amended to establish the incident period for this disaster as beginning 04/19/2011 and continuing through 06/06/2011.</P>
                <P>All other information in the original declaration remains unchanged.</P>
                <EXTRACT>
                    <FP>(Catalog of Federal Domestic Assistance Numbers 59002 and 59008)</FP>
                </EXTRACT>
                <SIG>
                    <NAME>Jane M.D. Pease,</NAME>
                    <TITLE>Acting Associate Administrator for Disaster Assistance.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-14947 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 8025-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">SMALL BUSINESS ADMINISTRATION</AGENCY>
                <DEPDOC>[Disaster Declaration #12560 and #12561]</DEPDOC>
                <SUBJECT>Arkansas Disaster Number AR-00048</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>U.S. Small Business Administration.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Amendment 5.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This is an amendment of the Presidential declaration of a major disaster for the State of Arkansas (FEMA-1975-DR), dated 05/02/2011 .</P>
                    <P>
                        <E T="03">Incident:</E>
                         Severe Storms, Tornadoes, and Associated Flooding.
                    </P>
                    <P>
                        <E T="03">Incident Period:</E>
                         04/23/2011 and continuing through 06/03/2011.
                    </P>
                    <P>
                        <E T="03">Effective Date:</E>
                         06/03/2011.
                    </P>
                    <P>
                        <E T="03">Physical Loan Application Deadline Date:</E>
                         07/01/2011.
                    </P>
                    <P>
                        <E T="03">EIDL Loan Application Deadline Date:</E>
                         02/02/2012.
                    </P>
                </SUM>
                <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>The notice of the President's major disaster declaration for the State of Arkansas, dated 05/02/2011 is hereby amended to establish the incident period for this disaster as beginning 04/23/2011 and continuing through 06/03/2011. </P>
                <P>All other information in the original declaration remains unchanged.</P>
                <EXTRACT>
                    <FP>(Catalog of Federal Domestic Assistance Numbers 59002 and 59008)</FP>
                </EXTRACT>
                <SIG>
                    <NAME>Jane M.D. Pease,</NAME>
                    <TITLE>Acting Associate Administrator for Disaster Assistance.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-14946 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 8025-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">SMALL BUSINESS ADMINISTRATION</AGENCY>
                <DEPDOC>[Disaster Declaration # 12586 and # 12587]</DEPDOC>
                <SUBJECT>North Dakota Disaster Number ND-00025</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>U.S. Small Business Administration.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P> Amendment 2.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This is an amendment of the Presidential declaration of a major disaster for Public Assistance Only for the State of North Dakota (FEMA-1981-DR), dated 05/10/2011.</P>
                    <P>
                        <E T="03">Incident:</E>
                         Flooding.
                    </P>
                    <P>
                        <E T="03">Incident Period:</E>
                         02/14/2011 and continuing.
                    </P>
                    <P>
                        <E T="03">Effective Date:</E>
                         06/07/2011.
                    </P>
                    <P>
                        <E T="03">Physical Loan Application Deadline Date:</E>
                         07/11/2011.
                    </P>
                    <P>
                        <E T="03">Economic Injury (EIDL) Loan Application Deadline Date:</E>
                         02/10/2012.
                    </P>
                </SUM>
                <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>The notice of the President's major disaster declaration for Private Non-Profit organizations in the State of North Dakota, dated 05/10/2011, is hereby amended to include the following areas as adversely affected by the disaster.</P>
                <FP SOURCE="FP-2">
                    <E T="03">Primary Counties:</E>
                     Billings, Divide.
                </FP>
                <P>All other information in the original declaration remains unchanged.</P>
                <EXTRACT>
                    <PRTPAGE P="35263"/>
                    <FP>(Catalog of Federal Domestic Assistance Numbers 59002 and 59008)</FP>
                </EXTRACT>
                <SIG>
                    <NAME>Jane M.D. Pease,</NAME>
                    <TITLE>Acting Associate Administrator for Disaster Assistance.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-14945 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 8025-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">SMALL BUSINESS ADMINISTRATION</AGENCY>
                <DEPDOC>[Disaster Declaration #12576 and #12577]</DEPDOC>
                <SUBJECT>Missouri Disaster Number MO-00048</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>U.S. Small Business Administration.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Amendment 4.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This is an amendment of the Presidential declaration of a major disaster for the State of Missouri (FEMA-1980-DR), dated 05/09/2011.</P>
                    <P>
                        <E T="03">Incident:</E>
                         Severe Storms, Tornadoes, and Flooding.
                    </P>
                    <P>
                        <E T="03">Incident Period:</E>
                         04/19/2011 and continuing through 06/06/2011.
                    </P>
                    <P>
                        <E T="03">Effective Date:</E>
                         06/06/2011.
                    </P>
                    <P>
                        <E T="03">Physical Loan Application Deadline Date:</E>
                         07/08/2011.
                    </P>
                    <P>
                        <E T="03">EIDL Loan Application Deadline Date:</E>
                         02/09/2012.
                    </P>
                </SUM>
                <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>The notice of the President's major disaster declaration for the State of Missouri, dated 05/09/2011 is hereby amended to establish the incident period for this disaster as beginning 04/19/2011 and continuing through 06/06/2011.</P>
                <P>All other information in the original declaration remains unchanged.</P>
                <EXTRACT>
                    <FP>(Catalog of Federal Domestic Assistance Numbers 59002 and 59008).</FP>
                </EXTRACT>
                <SIG>
                    <NAME>Jane M.D. Pease,</NAME>
                    <TITLE>Acting Associate Administrator for Disaster Assistance.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-14944 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 8025-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">SMALL BUSINESS ADMINISTRATION</AGENCY>
                <DEPDOC>[License No. 02/72-0625]</DEPDOC>
                <SUBJECT>Founders Equity SBIC I, L.P.; Notice Seeking Exemption Under Section 312 of the Small Business Investment Act, Conflicts of Interest</SUBJECT>
                <P>Notice is hereby given that Founders Equity SBIC I, L.P., 711 Fifth Avenue, 5th Floor, New York, NY 10022, a Federal Licensee under the Small Business Investment Act of 1958, as amended (“the Act”), in connection with the financing of a small concern, has sought an exemption under Section 312 of the Act and Section 107.730, Financings Which Constitute Conflicts of Interest of the Small Business Administration (“SBA”) Rules and Regulations (13 CFR 107.730). Founders Equity SBIC I, L.P. proposes to provide equity security financing to Richardson Foods, Inc., 101 Erie Blvd., Canajoharie, NY 13317. The financing will provide the company with additional capital to meet working capital requirements and for debt repayment.</P>
                <P>The financing is brought within the purview of § 107.730(a) of the Regulations because Founders Equity NY, L.P., an Associate of Founders Equity SBIC I, L.P., owns more than ten percent of Richardson Foods, Inc. and therefore Richardson Foods, Inc. is considered an Associate of Founders Equity SBIC I, L.P. as defined in § 107.50 of the Regulations.</P>
                <P>Notice is hereby given that any interested person may submit written comments on the transaction to the Associate Administrator for Investment, U.S. Small Business Administration, 409 Third Street, SW., Washington, DC 20416.</P>
                <SIG>
                    <DATED>Dated: June 6, 2011.</DATED>
                    <NAME>Sean J. Greene,</NAME>
                    <TITLE>Associate Administrator for Investment.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-14958 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">SMALL BUSINESS ADMINISTRATION</AGENCY>
                <SUBJECT>Small Business Size Standards: Waiver of the Nonmanufacturer Rule; Correction</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>U.S. Small Business Administration.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice: correction.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The U.S. Small Business Administration (SBA) published a notice in the 
                        <E T="04">Federal Register</E>
                         on May 11, 2011, granting a class waiver of the Nonmanufacturer Rule for GEN II and GEN III Image Intensifier Tubes, Product Service Code (PSC) 5855, Night Vision Equipment under North American Industry Classification System (NAICS) code 333314 (Optical Instrument and Lens Manufacturing). In the Supplementary Information section of the notice, additional related items to be considered for waiver are referenced. The PVS-17 item was incorrectly identified and should be corrected to read PVS-7. The correction has no impact on the May 26, 2011, effective date of the waiver, as stated in the May 11, 2011, notice.
                    </P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Ms. Amy Garcia, Procurement Analyst, by e-mail at 
                        <E T="03">amy.garcia@sba.gov,</E>
                         or by telephone at (202) 205-6842.
                    </P>
                    <HD SOURCE="HD1">Correction</HD>
                    <P>
                        In the 
                        <E T="04">Federal Register</E>
                         of May 11, 2011, Vol 76, No. 91, on page 27373, in the second column, correct any item listed as PVS-17 to read: PVS-7.
                    </P>
                    <SIG>
                        <NAME>John W. Klein,</NAME>
                        <TITLE>Director, Office of Government Contracting.</TITLE>
                    </SIG>
                </FURINF>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-14952 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 8025-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Highway Administration</SUBAGY>
                <DEPDOC>[Docket No. FHWA-2011-0059]</DEPDOC>
                <SUBJECT>Agency Information Collection Activities: Notice of Request for Approval of a New Information Collection</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Highway Administration (FHWA), DOT.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of Request for Approval of a New Information Collection.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The FHWA invites public comments about our intention to request the Office of Management and Budget's (OMB) approval of a new information collection that is summarized below under 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                        . We are required to publish this notice in the 
                        <E T="04">Federal Register</E>
                         by the Paperwork Reduction Act of 1995.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Please submit comments by August 15, 2011.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may submit comments identified by DOT Docket ID Number 2011-0059 by any of the following methods:</P>
                    <P>
                        <E T="03">Web Site:</E>
                         For access to the docket to read background documents or comments received, go to the Federal eRulemaking Portal: 
                        <E T="03">http://www.regulations.gov</E>
                        . Follow the online instructions for submitting comments.
                    </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, 
                        <PRTPAGE P="35264"/>
                        West Building Ground Floor, Room W12-140, 1200 New Jersey Avenue, SE., Washington, DC 20590.
                    </P>
                    <P>
                        <E T="03">Hand Delivery or Courier:</E>
                         U.S. Department of Transportation, West Building Ground Floor, Room W12-140, 1200 New Jersey Avenue, SE., Washington, DC 20590, between 9 a.m. and 5 p.m. ET, Monday through Friday, except Federal holidays.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>David Kuehn, 202-493-3414, Office of Corporate Research, Technology, and Innovation Management, Federal Highway Administration, Department of Transportation, 1200 New Jersey Avenue, SE., Washington, DC 20590, Monday through Friday, except Federal holidays.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P SOURCE="NPAR">
                    <E T="03">Title:</E>
                     Exploratory Advanced Research (EAR) Program sponsored project titled “Effects of Automated Transit and Pedestrian/Bicycling Facilities on Urban Travel Patterns.”
                </P>
                <P>
                    <E T="03">Type of request:</E>
                     New information collection requirement.
                </P>
                <P>
                    <E T="03">Background:</E>
                     The Exploratory Advanced Research (EAR) Program was established to conduct longer term, higher risk research that will result in a potentially dramatic breakthrough for improving the durability, efficiency, environmental impact, productivity, and safety of highway and intermodal transportation systems. FHWA awarded a research project titled “Effects of Automated Transit and Pedestrian/Bicycling Facilities on Urban Travel Patterns” that was submitted in response to a solicitation in 2009 and supports the EAR Program focus area of new technology and advanced policies for energy and resource conservation. The project conducted by the University of Michigan with support from the University of Illinois at Chicago has the potential to lead to applications for evidence-based policies and approaches that could substantially reduce the percentage and total number of short trip using private vehicles and increase the percentage and number of trips using current and future transit technology and non-motorized trips, which would reduce use and dependence on fossil fuels and associated pollution impacts.
                </P>
                <P>The research project is attempting to gauge potential travel-behavior response to far-reaching improvements in the pedestrian, cycling, and transit environments of neighborhoods. The transit improvements are inspired by the frequency and quality of service that might be made possibility of future technologies. The project is studying the capacity of these improvements to generate the following kinds of shifts: (1) Modal shift of neighborhood trips from auto to other modes; (2) Increased use of regional public transit based on improved station access; and (3) Shift of more remote non-work destinations to destinations within the neighborhood.</P>
                <P>To explore these issues, the research team is building a model that integrates activity-based and agent-based components. The models in turn will be based on a survey of residents in four neighborhoods of metropolitan Chicago. As part of the survey, respondents will be presented with images representing potential improvements to the pedestrian, cycling, and transit environments of their neighborhoods and will respond to scenarios regarding their travel under these altered conditions.</P>
                <P>We will mail 7,700 invitations with an expectation of 1,400 residents responding. From that pool, 800 will be selected for the study, which includes a survey packet, travel diary and phone interview.</P>
                <P>
                    <E T="03">Respondents:</E>
                     We estimate that 1,400 residents will respond to the initial invitation and 800 residents will participate in the study.
                </P>
                <P>
                    <E T="03">Frequency:</E>
                     This is a one-time collection.
                </P>
                <P>
                    <E T="03">Estimated Average Burden per Response:</E>
                </P>
                <P>The invitation portion takes approximately 15 minutes to complete.</P>
                <P>1400 residents  ×  15 minutes = 350 hours.</P>
                <P>The research study takes approximately 1 hour and 30 minutes (30 minutes for the survey packet and travel diary and 1 hour for the phone interview) 800 residents  ×  90 minutes = 1,200 hours.</P>
                <P>
                    <E T="03">Estimated Total Annual Burden Hours:</E>
                     The total burden for this one-time information collection would be approximately 1,550 hours.
                </P>
                <P>
                    <E T="03">Public Comments Invited:</E>
                     You are asked to comment on any aspect of this information collection, including: (1) Whether the proposed collection of information is necessary for the U.S. DOT's performance, including whether the information will have practical utility; (2) the accuracy of the U.S. DOT's estimate of the burden of the proposed information collection; (3) ways to enhance the quality, usefulness, and clarity of the collected information; and (4) ways that the burden could be minimized, including the use of electronic technology, without reducing the quality of the collected information. The agency will summarize and/or include your comments in the request for OMB's clearance of this information collection.
                </P>
                <AUTH>
                    <HD SOURCE="HED">Authority: </HD>
                    <P>The Paperwork Reduction Act of 1995; 44 U.S.C. Chapter 35, as amended; and 49 CFR 1.48.</P>
                </AUTH>
                <SIG>
                    <DATED> Issued On: June 10, 2011.</DATED>
                    <NAME>Michael Howell,</NAME>
                    <TITLE>Acting Chief, Management Programs and Analysis Division.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-14916 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-22-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Highway Administration</SUBAGY>
                <DEPDOC>[U.S. DOT Docket No. FHWA-2011-0058]</DEPDOC>
                <SUBJECT>Agency Information Collection Activities: Request for Comments for a New Information Collection, Titled: Reports, Forms and Recordkeeping Requirements</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Highway Administration, DOT.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Request for comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The FHWA invites public comments about our intention to request the Office of Management and Budget's (OMB) approval for a new information collection, which is summarized below under 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                        . We published a 
                        <E T="04">Federal Register</E>
                         Notice with a 60-day public comment period on this information collection on February 26, 2009. We are required to publish this notice in the 
                        <E T="04">Federal Register</E>
                         by the Paperwork Reduction Act of 1995.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Please submit comments by July 18, 2011.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may submit comments identified by Docket ID Number FHWA-2009-0054 by any of the following methods:</P>
                    <P>
                        <E T="03">Web Site:</E>
                         For access to the docket to read background documents or comments received go to the Federal eRulemaking Portal: Go to 
                        <E T="03">http://www.regulations.gov.</E>
                         Follow the online instructions for submitting comments.
                    </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, West Building Ground Floor, Room W12-140, 1200 New Jersey Avenue, SE., Washington, DC 20590-0001.
                    </P>
                    <P>
                        <E T="03">Hand Delivery or Courier:</E>
                         U.S. Department of Transportation, West Building Ground Floor, Room W12-140, 1200 New Jersey Avenue, SE., Washington, DC 20590, between 9 a.m. and 5 p.m. ET, Monday through Friday, except Federal holidays.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Ray Krammes, Ph.D, PE, Acting Director, Office of Safety Research and Development, HRDS-07, Turner-
                        <PRTPAGE P="35265"/>
                        Fairbank Highway Research Center, Federal Highway Administration, 6300 Georgetown Pike, McLean, VA 22101, tel. 202-493-3365 between 8 a.m. and 5:30 p.m., Monday through Friday, except Federal holidays, or Paul J. Tremont, Ph.D. (same address) at 202-493-3338.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P SOURCE="NPAR">
                    <E T="03">Title:</E>
                     Reports, Forms and Recordkeeping Requirements.
                </P>
                <P>
                    The FHWA invites public comments on our intention to request the Office of Management and Budget (OMB) to approve a total of 30 field and laboratory research studies that will include collections of information from the general public. These studies will be conducted over a period not to exceed 3 years with an 
                    <E T="03">annual</E>
                     burden of approximately 2000 hours and a grand total burden of approximately 6000 hours. These collections are integral to the performance of various analytical, field, and laboratory human factors research projects that FHWA intends to conduct in support of its mission of improving safety and increasing mobility on our Nation's highways through National Leadership, Innovation, and Program Delivery. The laboratory and field research FHWA conducts usually involves observations of driver behavior in controlled experimental settings. In the field and laboratory, these studies are non-intrusive, as most data are driver performance data and are automatically acquired.
                </P>
                <HD SOURCE="HD1">Research Areas and Associated Collections</HD>
                <P>The FHWA Office of Safety Research and Development intends to conduct analytical, field, and laboratory research projects focused on highway safety that will require acquisition of human performance data from small samples of the driving public. This research is directed at human factors issues within the following broad program areas: (A) Infrastructure design including innovative intersection configurations and signage and roadway markings; (B) highway operations; (C) older and younger driver issues; and (D) pedestrian and bicyclist concerns. Given that the focus of the research in the above areas is on human factors issues, it will require that data be collected on a few key demographic variables such as age, gender, and driving experience, however such data will not be linked to personal identifying information. Before any study is conducted under this approval request, a thorough review will be undertaken to ensure such data is not currently available, and that the proposed study does not duplicate other work.</P>
                <HD SOURCE="HD1">Situations That Require Collections of Information—Examples From Each Category</HD>
                <P>
                    <E T="03">Category A (Infrastructure Design).</E>
                     An example from Category A would be a study designed to test an innovative intersection design such as a Double Crossover Diamond Interchange (DCD). This is a highly efficient intersection design, but if not properly implemented, it could potentially cause confusion. In a DCD, drivers cross over to the left side of the highway, with the result that opposing traffic is placed on their right side. When testing DCD implementations, FHWA needs to know whether drivers perceive any ambiguity in the signage, and if they have any orientation problems seeing opposing traffic on their right side. Other innovative intersection designs would also benefit from similar information acquired from drivers. Roadway departure is another problem area that could benefit from individual driver data. For example, it would be helpful to observe drivers' interactions with roadway geometry and signage so that such information can be applied to design decisions that can lead to reductions in roadway departures.
                </P>
                <P>
                    <E T="03">Category B (Highway Operations).</E>
                     One of the many challenges confronting highway engineers is designing a signal system that maximizes throughput and minimizes delay. Excess delay can have the unintended consequence of encouraging drivers to run red lights. This problem can be examined by observing drivers' behavior under differing signaling conditions. However, direct verbal reports of drivers are often needed to determine why drivers are making their decisions. For example FHWA may learn from questioning drivers that they would be less likely to speed up when approaching a signal if they knew the signal system would recognize this behavior and respond accordingly. One way this might happen is by advising the motorist earlier of the impending signal change. Driver interviews performed under this study area can provide information on many key issues including behavioral adaptation, decision making, and reaction times to signal phases and changes. This kind of information could lead to improvements to signal controllers that increase mobility and improve safety. Speed management is another area that could benefit from interview data. For example, lower speed limits in construction zones are difficult to enforce, and interview data with drivers can provide information on better methods of restraining driver speeds in these hazardous situations.
                </P>
                <P>
                    <E T="03">Category C (Older and Younger Drivers).</E>
                     The driving behaviors of these two high risk groups are of interest for almost all FHWA safety related studies. For example, older driver's performance as they negotiate new designs informs the engineer of those aspects of the design that present potential safety problems, and may be in need of modification. In contrast, young drivers present a separate set of challenges for highway engineers. Their ability to negotiate a new design may be less of a concern, however; it is necessary to understand how these drivers perform as they drive through these new designs. This is important as some younger drivers may be willing to take extra risks in situations where ambiguity exists. Such information from younger drivers will help engineers determine areas of potential ambiguity in design and modify these areas as necessary to ensure they are not introducing safety hazards.
                </P>
                <P>
                    <E T="03">Category D (Pedestrians and Bicyclists).</E>
                     Research related to pedestrians and bicyclists arises from the need to determine the most effective ways to accommodate these infrastructure users. While overt pedestrian and bicyclist behavior needs to be directly observed to enable engineers to determine potential safety hazards to these user groups. For example, when a new intersection design is being introduced (
                    <E T="03">e.g.,</E>
                     a triple lane roundabout) it is especially advantageous to acquire data that shows how pedestrians and bicyclists negotiate such a new design. The needs of disabled pedestrians are also considered when researching new intersection treatments, and in these efforts FHWA works closely with the U.S. Access Board to ensure that novel intersection treatments accommodate their needs. Another example of research in this area is determining bicyclists' reactions to such treatments as separately marked bicycle lanes, signage, and overall roadway configuration.
                </P>
                <HD SOURCE="HD1">Description of How Field and Laboratory Study Participants Will Be Acquired</HD>
                <P>
                    Participants for research studies will be acquired by advertisement in local papers, by the distribution of flyers, or by postings to the internet. Typically, interested parties contact FHWA and they are asked a few questions to determine whether they qualify for the study. These questions involve such issues as age, driver familiarity with the location or scenario being used, number of miles driven per year, and gender.
                    <PRTPAGE P="35266"/>
                </P>
                <HD SOURCE="HD1">Estimate of the Total Annual Reporting and Recordkeeping Burden Resulting From These Information Collections and Requests for Comments</HD>
                <P>
                    <E T="03">Experimental Participants:</E>
                     Approximately 6,000 roadway users drawn form the general driving population.
                </P>
                <P>
                    <E T="03">Frequency:</E>
                     This approval request is for 30 studies over a 3 year period.
                </P>
                <P>
                    <E T="03">Estimated Average Burden per Respondent:</E>
                     FHWA estimates data acquisition from persons participating in research will require on average about 1 hour per person.
                </P>
                <P>
                    <E T="03">Estimated Total and Annual Burden Hours:</E>
                     Assuming 20 studies will be Laboratory based (Simulator), and 10 will be Field based (Field Research Vehicle), the burden is calculated as follows:
                </P>
                <P>
                    <E T="03">Laboratory Experiments:</E>
                     20 Simulator * 210 participants * 1 hour = 4200
                </P>
                <P>
                    <E T="03">Field Experiments:</E>
                     10 studies * 180 participants * 1 hour = 1800 hours
                </P>
                <P>
                    <E T="03">Estimated Total Burden Hours:</E>
                     = 6000 hours
                </P>
                <P>
                    <E T="03">Estimated Annual Burden Hours (over 3 years) = 2000 hours.</E>
                </P>
                <P>
                    <E T="03">Public Comments Invited:</E>
                     You are asked to comment on any aspect of these information collections, including: (1) Whether the proposed collections are necessary for FHWA's performance; (2) the accuracy of the estimated burden; (3) ways for FHWA to enhance the quality, usefulness, and clarity of the collected information; and (4) ways that the burden could be minimized, including the use of electronic technology, without reducing the quality of the collected information. FHWA will respond to your comments and summarize or include them when requesting clearance from OMB for these information data collections.
                </P>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P> The Paperwork Reduction Act of 1995; 44 U.S.C. Chapter 35, as amended; and 49 CFR 1.48.</P>
                </AUTH>
                <SIG>
                    <DATED>Issued on June 10, 2011.</DATED>
                    <NAME>Michael Howell,</NAME>
                    <TITLE>Acting Chief, Management Programs and Analysis Division.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-14892 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>National Highway Traffic Safety Administration</SUBAGY>
                <SUBJECT>Reports, Forms and Record Keeping Requirements; Agency Information Collection Activity Under OMB Review</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Highway Traffic Safety Administration, U.S. Department of Transportation.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        In compliance with the Paperwork Reduction Act of 1995 (44 U.S.C. 3501 
                        <E T="03">et seq.</E>
                        ), this notice announces that the Information Collection Request (ICR) abstracted below has been forwarded to the Office of Management and Budget (OMB) for review and comment. The ICR describes the nature of the information collections and their expected burden. The 
                        <E T="04">Federal Register</E>
                         Notice with a 60-day comment period was published on March 3, 2011 (76 FR 11848). No comments were received.
                    </P>
                    <P>This document describes the collection of information for which NHTSA intends to seek OMB approval. The collection of information described is the “Consolidated Child Restraint System Registration, Labeling and Defect Notification.” (OMB Control Number: 2127-0576)</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be submitted on or before July 18, 2011.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Mrs. Cristina Echemendia at  U.S. Department of Transportation, NHTSA, 1200 New Jersey Avenue, SE., West Building Room W43-447, NVS-113, Washington, DC 20590. Mrs. Cristina Echemendia's telephone number is (202) 366-6345 and fax number is (202) 366-7002.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>National Highway Traffic Safety Administration.</P>
                <P>
                    <E T="03">Title:</E>
                     Consolidated Child Restraint System Registration, Labeling and Defect Notifications”.
                </P>
                <P>
                    <E T="03">OMB Control Number:</E>
                     2127-0576.
                </P>
                <P>
                    <E T="03">Type of Request:</E>
                     Extension of a currently approved collection.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     Child restraint manufacturers are required to provide an owner's registration card for purchasers of child safety seats in accordance with title 49 of the Code of Federal Regulations (CFR), Part 571.213, “Child restraint systems.” The registration card is perforated into two-parts (see Figures 1 and 2). The top part contains a message and suitable instructions to be retained by the purchaser. The bottom part is to be returned to the manufacturer by the purchaser. The bottom part includes prepaid return postage, the pre-printed name/address of the manufacturer, the pre-printed model and date of manufacture, and spaces for the purchaser to fill in his/her name and address. Optionally, child restraint manufacturers are permitted to add to the registration form: (a) Specified statements informing CRS owners that they may register online; (b) the Internet address for registering with the company; (c) revisions to statements reflecting use of the Internet to register; and (d) a space for the consumer's e-mail address. For those CRS owners with access to the Internet, online registration may be a preferred method of registering a CRS.
                </P>
                <P>
                    In addition to the registration card supplied by the manufacturer, NHTSA has implemented a CRS registration system to assist those individuals who have either lost the registration card that came with the CRS or purchased a previously owned CRS. Upon the owner's request, NHTSA provides a substitute registration form that can be obtained either by mail or from the Internet 
                    <SU>1</SU>
                    <FTREF/>
                     (see Figure 3). When the completed registration is returned to the agency, it is then submitted to the CRS manufacturers. In the absence of a substitute registration system, many owners of child passenger safety seats, especially any second-hand owners, might not be notified of safety defects and noncompliances, and would not have the defects and noncompliances remedied.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         
                        <E T="03">http://www-odi.nhtsa.dot.gov/cars/problems/recalls/register/childseat/csregfrm.pdf.</E>
                    </P>
                </FTNT>
                <P>Child seat owner registration information is retained in the event that owners need to be contacted for defect recalls or replacement campaigns. Chapter 301 of title 49 of the United States Code specifies that if either NHTSA or a manufacturer determines that motor vehicles or items of motor vehicle equipment contain a defect that relates to motor vehicle safety or fail to comply with an applicable Federal motor vehicle safety standard, the manufacturer must notify owners and purchasers of the defect or noncompliance and must provide a remedy without charge. In title 49 of the CFR, part 577, defect and noncompliance notification for equipment items, including child restraint systems, must be sent by first class mail to the most recent purchaser known to the manufacturer.</P>
                <P>Child restraint manufacturers are also required to provide a printed instructions brochure with step-by-step information on how the restraint is to be used. Without proper use, the effectiveness of these systems is greatly diminished. Each child restraint system must also have a permanent label. A permanently attached label gives “quicklook” information on whether the restraint meets the safety requirements, recommended installation and use, and warnings against misuse.</P>
                <P>
                    <E T="03">Affected Public:</E>
                     Businesses.
                </P>
                <P>
                    <E T="03">Estimated Total Annual Burden:</E>
                     39,247 hours.
                    <PRTPAGE P="35267"/>
                </P>
                <FP>
                    <E T="02">ADDRESSES:</E>
                     Send comments, within 30 days, to the Office of Information and Regulatory Affairs, Office of Management and Budget, 725 17th Street, NW., Washington, DC 20503, Attention NHTSA Desk Officer.
                </FP>
                <P>
                    <E T="03">Comments are invited on:</E>
                     Whether the proposed collection of information is necessary for the proper performance of the functions of the Department, including whether the information will have practical utility; the accuracy of the Departments estimate of the burden of the proposed information collection; ways to enhance the quality, utility and clarity of the information to be collected; and ways to minimize the burden of the collection of information on respondents, including the use of automated collection techniques or other forms of information technology. A Comment to OMB is most effective if OMB receives it within 30 days of publication.
                </P>
                <SIG>
                    <DATED>Issued on: June 10, 2011.</DATED>
                    <NAME>Christopher J. Bonanti,</NAME>
                    <TITLE>Associate Administrator for Rulemaking.</TITLE>
                </SIG>
                <BILCOD>BILLING CODE 4910-59-P</BILCOD>
                <GPH SPAN="3" DEEP="469">
                    <GID>EN16JN11.000</GID>
                </GPH>
                <GPH SPAN="3" DEEP="417">
                    <PRTPAGE P="35268"/>
                    <GID>EN16JN11.001</GID>
                </GPH>
                <GPH SPAN="3" DEEP="548">
                    <PRTPAGE P="35269"/>
                    <GID>EN16JN11.002</GID>
                </GPH>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-14995 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-59-C</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="35270"/>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>National Highway Traffic Safety Administration</SUBAGY>
                <DEPDOC>[U.S. DOT Docket Number NHTSA-2011-0025]</DEPDOC>
                <SUBJECT>Reports, Forms, and Recordkeeping Requirements</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Highway Traffic Safety Administration (NHTSA), Department of Transportation.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Request for public comment on a reinstatement of a previously approved collection of information.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>Before a Federal agency can collect certain information from the public, it must receive approval from the Office of Management and Budget (OMB). Under procedures established by the Paperwork Reduction Act of 1995, before seeking OMB approval, Federal agencies must solicit public comment on proposed collections of information, including extensions and reinstatement of previously approved collections.</P>
                    <P>This document describes one collection of information for parts 541, 565, and 567 for which NHTSA intends to seek OMB approval.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be received on or before August 15, 2011.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may submit comments [identified by DOT Docket No. NHTSA-2011-0025] by any of the following methods:</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">Mail:</E>
                         Docket Management Facility: U.S. Department of Transportation, 1200 New Jersey Avenue, SE., West Building, Ground Floor, Room W12-140, Washington, DC 20590-0001.
                    </P>
                    <P>
                        • 
                        <E T="03">Hand Delivery or Courier:</E>
                         West Building Ground Floor, Room W12-140, 1200 New Jersey Avenue, SE., Washington, DC, between 9 a.m. and 5 p.m. ET, Monday through Friday, except Federal holidays.
                    </P>
                    <P>
                        • 
                        <E T="03">Fax:</E>
                         1-202-493-2251.
                    </P>
                    <P>• You may call the Docket at (202) 366-9324.</P>
                    <P>Regardless of how you submit your comments, you should mention the docket number of this document. Please identify the proposed collection of information for which a comment is provided, by referencing its OMB clearance number. It is requested, but not required, that two copies of the comment be provided.</P>
                    <P>
                        <E T="03">Instructions:</E>
                         For detailed instructions on submitting comments and additional information on the rulemaking process, see the Public Participation heading of the Supplementary Information section of this document. Note that all comments received will be posted without change to 
                        <E T="03">http://www.regulations.gov,</E>
                         including any personal information provided. 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, 
                        <E T="03">etc.</E>
                        ). You may review DOT's complete Privacy Act Statement in the 
                        <E T="04">Federal Register</E>
                         published on April 11, 2000 (65 FR 19477-78).
                    </P>
                    <P>
                        <E T="03">Docket:</E>
                         For access to the docket to read background documents or comments received, go to the street address listed above. The Internet access to the docket will be at 
                        <E T="03">http://www.regulations.gov</E>
                        . Follow the online instructions for accessing the dockets.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Complete copies of each request for collection of information may be obtained at no charge from Ms. Deborah Mazyck, NHTSA, 1200 New Jersey Avenue, SE., West Building, Room W43-443, Washington, DC 20590. Ms. Mazyck's telephone number is (202) 366-4139 and e-mail address is 
                        <E T="03">Deborah.Mazyck@dot.gov.</E>
                         Please identify the relevant collection of information by referring to its OMB Control Number.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    Under the Paperwork Reduction Act of 1995, before an agency submits a proposed collection of information to OMB for approval, it must first publish a document in the 
                    <E T="04">Federal Register</E>
                     providing a 60-day comment period and otherwise consult with members of the public and affected agencies concerning each proposed collection of information. The OMB has promulgated regulations describing what must be included in such a document. Under OMB's regulation (at 5 CFR 1320.8(d), an agency must ask for public comment on the following:
                </P>
                <P>(i) Whether the proposed collection of information is necessary for the proper performance of the functions of the agency, including whether the information will have practical utility;</P>
                <P>(ii) The accuracy of the agency's estimate of the burden of the proposed collection of information, including the validity of the methodology and assumptions used;</P>
                <P>(iii) How to enhance the quality, utility, and clarity of the information to be collected;</P>
                <P>
                    (iv) How to minimize the burden of the collection of information on those who are to respond, including the use of appropriate automated, electronic, mechanical, or other technological collection techniques or other forms of information technology, 
                    <E T="03">e.g.</E>
                     permitting electronic submission of responses.
                </P>
                <P>In compliance with these requirements, NHTSA asks for public comments on the following request for reinstatement of a previously approved collection of information:</P>
                <P>
                    <E T="03">Title:</E>
                     Consolidated Labeling Requirements for 49 CFR 541, 565 and 567.
                </P>
                <P>
                    <E T="03">OMB Control Number:</E>
                     2127-0510.
                </P>
                <P>
                    <E T="03">Form Number:</E>
                     None.
                </P>
                <P>
                    <E T="03">Affected Public:</E>
                     Vehicle manufacturers.
                </P>
                <P>
                    <E T="03">Requested Expiration Date of Approval:</E>
                     Three years from the approval date.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     For parts 541, 565 and 567.
                </P>
                <HD SOURCE="HD1">Part 541</HD>
                <P>The Motor Vehicle Information and Cost Savings Act was amended by the Anti-Car Theft Act of 1992 (Pub. L. 102-519). The enacted Theft Act requires specified parts of high-theft vehicle to be marked with vehicle identification numbers. In a final rule published on April 6, 2004, the Federal Motor Vehicle Theft Prevention Standard was extended to include all passenger cars and multipurpose passenger vehicles with a gross vehicle weight rating of 6,000 pounds or less, and to light duty trucks with major parts that are interchangeable with a majority of the covered major parts of multipurpose passenger vehicles. Each major component part must be either labeled or affixed with the VIN and its replacement component part must be marked with the DOT symbol, the letter (R) and the manufacturers' logo. The final rule became effective September 1, 2006. Due to expansion of the Federal Motor Vehicle Theft Prevention Standard (part 541), all passenger cars, and multipurpose passenger vehicles with a gross vehicle weight rating of 6,000 pounds or less, and light duty trucks with major parts that are interchangeable with a majority of the covered major parts of multipurpose passenger vehicles, are required to be parts marked.</P>
                <P>NHTSA estimates the vehicle manufacturers will incur a total cost burden of $122,138,000 million.</P>
                <HD SOURCE="HD1">Parts 565 and 567</HD>
                <P>
                    NHTSA's statute at 15 U.S.C. 1392, 1397, 1401, 1407, and 1412 of the National Traffic and Motor Vehicle Safety Act of 1966 authorizes the issuance of Federal Motor Vehicle Safety Standard (FMVSS) and the 
                    <PRTPAGE P="35271"/>
                    collection of data which support their implementation. The agency, in prescribing an FMVSS, is to consider available relevant motor vehicle safety data and to consult with other agencies as it deems appropriate. Further, the Act mandates, that in issuing any FMVSS, the agency should consider whether the standard is reasonable, practicable and appropriate for the particular type of motor vehicle or item of motor vehicle equipment for which it is prescribed, and whether such standards will contribute to carrying out the purpose of the Act. The Secretary is authorized to revoke such rules and regulations as deemed necessary to carry out this subchapter. Using this authority, the agency issued the initial FMVSS No. 115, Vehicle Identification Number, specifying requirements for vehicle identification numbers to aid the agency in achieving many of its safety goals.
                </P>
                <P>The standard was amended in August 1978 by extending its applicability to additional classes of motor vehicles and by specifying the use of a 30-year, 17-character Vehicle Identification Number (VIN) for worldwide use. The standard was amended in May 1983 by deleting portions of FMVSS No. 115 and reissuing those portions as a general agency regulation, part 565. Subsequently, the standard was amended again in June 1996 transferring the text of the FMVSS No. 115 to part 565, without making any substantive changes to the VIN requirements as a result of the proposed consolidation. The provision of the part 565 (amended) regulation requires vehicle manufacturers to assign a unique VIN to each new vehicle and to inform NHTSA of the code used in forming the VIN. These regulations apply to all vehicles: Passenger cars, multipurpose passenger vehicles, trucks, buses, trailers, incomplete vehicles, and motorcycles.</P>
                <P>NHTSA has amended to part 565 to revise certain sections in order to extend the existing VIN system for another thirty years, and to ensure a sufficient supply of unique available VINs and manufacturer identifiers for that time period (72 FR 56027, October 2, 2007). The agency required information to be provided in a slightly different way (e.g., vehicle make being transferred from the first to the second section of the VIN), the scope of the overall reporting requirement of part 565 will not change.</P>
                <P>Part 567 specifies the content and location of, and other requirements for, the certification label or tag to be affixed to motor vehicles and motor vehicle equipment. Specifically, the VIN is required to appear on the certification label. Additionally, this certificate will provide the consumer with information to assist him or her in determining which of the Federal Motor Vehicle Safety Standards are applicable to the vehicle or equipment, and its date of manufacturer.</P>
                <P>NHTSA estimates a cost burden of $13,348,000 for this requirement.</P>
                <P>
                    <E T="03">Estimated Annual Burden:</E>
                     The overall total estimated annual hour burden for this collection is 798,047. The overall total estimated cost burden for this collection is $122,138,000 million.
                </P>
                <P>
                    <E T="03">Number of Respondents:</E>
                     The total number of respondents for this collection (part 541, 565 and part 567) is 1,104.
                </P>
                <P>Comments are invited on: Whether the proposed collection of information is necessary for the proper performance of the functions of the Department, including whether the information will have practical utility; the accuracy of the Department's estimate of the burden of the proposed information collection; ways to enhance the quality, utility and clarity of the information to be collected; and ways to minimize the burden of the collection of information on respondents, including the use of automated collection techniques or other forms of information technology.</P>
                <SIG>
                    <DATED>Issued on: June 10, 2011.</DATED>
                    <NAME>Christopher J. Bonanti,</NAME>
                    <TITLE>Associate Administrator for Rulemaking.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-14993 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-59-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>National Highway Traffic Safety Administration</SUBAGY>
                <DEPDOC>[Docket No. NHTSA-2011-0058; Notice 1]</DEPDOC>
                <SUBJECT>Toyota Motor Corporation, Inc., on Behalf of Toyota Corporation, and Toyota Manufacturing, Indiana, Inc., Receipt of  Petition for Decision of Inconsequential Noncompliance</SUBJECT>
                <P>
                    Toyota Motor North America, Inc., on behalf of Toyota Motor Corporation,
                    <SU>1</SU>
                    <FTREF/>
                     and Toyota Manufacturing, Indiana, Inc.
                    <SU>2</SU>
                    <FTREF/>
                     (collectively referred to as as “Toyota”) has determined that certain model year 2011 Toyota Sienna passenger cars manufactured between January 3, 2011 and February 11, 2011, do not fully comply with paragraph S9.5(a)(3) of Federal Motor Vehicle Safety Standard (FMVSS) No. 225, 
                    <E T="03">Child restraint anchorage systems.</E>
                     Toyota has filed an appropriate report pursuant to 49 CFR part 573, 
                    <E T="03">Defect and Noncompliance Responsibility and Reports</E>
                     (dated March 17, 2011).
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         Toyota Motor Corporation is a Japanese corporation that manufactures and imports motor vehicles.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         Toyota Manufacturing, Indiana, Inc., is an Indiana corporation that manufactures motor vehicles.
                    </P>
                </FTNT>
                <P>Pursuant to 49 U.S.C. 30118(d) and 30120(h) (see implementing rule at 49 CFR part 556), Toyota has petitioned for an exemption from the notification and remedy requirements of 49 U.S.C. Chapter 301 on the basis that this noncompliance is inconsequential to motor vehicle safety.</P>
                <P>This notice of receipt of Toyota's petition is published under 49 U.S.C. 30118 and 30120 and does not represent any agency decision or other exercise of judgment concerning the merits of the petition.</P>
                <P>Affected are approximately 9,122 model year 2011 Toyota Sienna passenger cars that were manufactured between January 3, 2011 and February 11, 2011.</P>
                <P>
                    NHTSA notes that the statutory provisions (49 U.S.C. 30118(d) and 30120(h)) that permit manufacturers to file petitions for a determination of inconsequentiality allow NHTSA to exempt manufacturers only from the duties found in  sections 30118 and 30120, respectively, to notify owners, purchasers, and dealers of a defect or noncompliance and to remedy the defect or noncompliance. Therefore, these provisions only apply to the 9,122 
                    <SU>3</SU>
                    <FTREF/>
                     model year 2011 Toyota Sienna passenger cars that Toyota no longer controlled at the time it determined that the noncompliance existed.
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         Toyota's petition, which was filed under 49 CFR Part 556, requests an agency decision to exempt Toyota as a vehicle manufacturer from the notification and recall responsibilities of 49 CFR Part 573 for 9,122 of the affected vehicles. However, the agency cannot relieve vehicle distributors and dealers of the prohibitions on the sale, offer for sale, introduction or delivery for introduction into interstate commerce of the noncompliant vehicles under their control after Toyota notified them that the subject noncompliance existed. Those vehicles must be brought into conformance, exported, or destroyed.
                    </P>
                </FTNT>
                <P>Paragraph S9.5 of FMVSS No. 225 requires in pertinent part:</P>
                <EXTRACT>
                    <P>S9.5 Marking and conspicuity of the lower anchorages. Each vehicle shall comply with S9.5(a) or (b). (a) Above each bar installed pursuant to S4, the vehicle shall be permanently marked with a circle * * *</P>
                    <P>(1) That is not less than 13 mm in diameter;</P>
                    <P>(2) That is either solid or open, with or without words, symbols or pictograms, provided that if words, symbols or pictograms are used, their meaning is explained to the consumer in writing, such as in the vehicle's owners manual; and</P>
                    <P>
                        (3) That is located such that its center is on each seat back between 50 and 100 mm 
                        <PRTPAGE P="35272"/>
                        above or on the seat cushion 100 ±25 mm forward of the intersection of the vertical transverse and horizontal longitudinal planes intersecting at the horizontal centerline of each lower anchorage, as illustrated in Figure 22. The center of the circle must be in the vertical longitudinal plane that passes through the center of the bar (±25 mm);
                    </P>
                    <P>(4) The circle may be on a tag * * *</P>
                </EXTRACT>
                <P>Toyota explains that the noncompliance is that the label identifying the location of the lower child restraint anchorages in some of the second row seats of the affected vehicles are located slightly outside the limits as stated within the requirements of S9.5(a)(3) of FMVSS No. 225.</P>
                <P>
                    Specifically, Toyota also explains that “the potential deviation of the label location outside the requirement is very small. In a detailed survey of a randomly selected subset involving 18 of these vehicles in which a deviation was observed, the mean deviation was approximately +1.4 mm (
                    <E T="03">i.e.,</E>
                     26.4 mm from the centerline); the maximum deviation observed was +2.5 mm (
                    <E T="03">i.e.,</E>
                     27.5 mm from the centerline); and the standard deviation was only 0.5 mm. While a survey carried out by the seat supplier also supports Toyota's assertions that the potential deviation of the label location from the specified requirements is very small. In the supplier's survey of 240 labels on 120 seats, 3 labels were outside of the specifications of FMVSS No. 225. All 3 of those labels were measured at +1 mm beyond the specification, or 26 mm from the centerline.”
                </P>
                <P>Toyota stated its belief that although the lower child anchorage labels are outside the specified limits of this requirement that the noncompliance is inconsequential to motor vehicle safety for the following reasons:</P>
                <P>(1) The measured deviations are very minor, and such a slight deviation is not noticeable to consumers and would not impair a consumer's ability to locate the lower anchorages.</P>
                <P>(2) Paragraph S9.1 of FMVSS No. 225 requires that the length of the straight portion of the lower anchorage bar be a minimum of 25 mm. In the affected vehicles the length is 30 mm; the total length including the curved portions is 54 mm. As a result, even with greater deviations than noted above in label location, some part of the label would be over some part of the bar, making the bar easy to locate.</P>
                <P>(3) The regulatory history of the provision allowing a ±25 mm lateral tolerance for the location of the center of the circular label further supports the argument that this noncompliance has no adverse safety consequences. As originally adopted, FMVSS No. 225 would have limited the lateral tolerance to ±12 mm. In response to a petition for reconsideration from vehicle manufacturers concerned that such a low tolerance would be difficult to meet due to process limitations and seat design features, NHTSA amended the standard to allow the current ±25 mm tolerance. 69 Fed Reg. 48818 (August 11, 2004). In doing so, The agency stated:</P>
                <P>“* * * Moreover, the agency believes that increasing the tolerance to 25 mm will not significantly affect the consumers' ability to find the LATCH anchorages. While anchor bars are permitted to be as short as 25 mm in the straight portion of the bar, most are considerably longer. Even if a 25 mm bar were used, with a 25 mm tolerance from the center of the bar, the circle will be, at farthest, tangent to a longitudinal vertical plane tangent to the side of the anchorage bar. If a person were to probe the seat bight in the area directly under the marking circle, his or her finger would easily contact the bar. For bars that are greater than 25 mm in length, with a 25 mm tolerance a portion of the marking circle will always be over some part of the bar. In either situation, marking the circle with a 25 mm tolerance will adequately provide a visual reminder to consumers that the LATCH system is present and will help users locate and use the bars. Adopting the 25 mm tolerance will also harmonize FMVSS No. 225 with the comparable Transport Canada requirement.”</P>
                <P>(4) The seat design is such that only one label at a seating position can be noncompliant. As the seat cover, is constructed, the labels are secured to the fabric a specified distance apart that reflects the location of each pair of anchorages, and the labels are designed to be within the lateral tolerance of the standard.</P>
                <P>(5) Information provided in the vehicle owner's manual further reduces any possibility of confusion when installing a child restraint. The instructions clear advise the installer to recline the second row seat and widen the gap between the seat cushion and the seatback to expose the lower anchorages.</P>
                <P>
                    (6) The label locations are correct for the LATCH anchorage system located at the third row center seating position.
                    <SU>4</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         Toyota indicated that this LATCH anchorage is not required by the standard, but was voluntarily installed by Toyota.
                    </P>
                </FTNT>
                <P>(7) There have been no customer complaints, injuries, or accidents related to the deviation of the child restraint label location being slightly outside the limits of the requirement.</P>
                <P>(8) The model year 2011 Sienna is sold by Toyota in both the United States and Canada and the subject noncompliance was reported to both NHTSA and Transport Canada at the same time. (In Canada, the applicable standard is CMVSS 210.2; it contains the same requirements as FMVSS No. 225). Transport Canada responded on March 23, indicating it concurs that “there is no real or implied degradation to motor vehicle safety,” and that no further action in Canada will be required.</P>
                <P>In summation, Toyota believes that the described noncompliance of its vehicles to meet the requirements of FMVSS  No. 225 is inconsequential to motor vehicle safety, and that its petition, to exempt from providing recall notification of noncompliance as required by 49 U.S.C. 30118 and remedying the recall noncompliance as required by 49 U.S.C. 30120 should be granted.</P>
                <P>Interested persons are invited to submit written data, views, and arguments on this petition. Comments must refer to the docket and notice number cited at the beginning of this notice and be submitted by any of the following methods:</P>
                <P>a. By mail addressed to: U.S. Department of Transportation, Docket Operations, M-30, West Building Ground Floor, Room W12-140, 1200 New Jersey Avenue, SE., Washington, DC 20590.</P>
                <P>b. By hand delivery to U.S. Department of Transportation, Docket Operations, M-30, West Building Ground Floor, Room W12-140, 1200 New Jersey Avenue, SE., Washington, DC 20590. The Docket Section is open on weekdays from 10 a.m. to 5 p.m. except Federal holidays.</P>
                <P>
                    c. Electronically: by logging onto the Federal Docket Management System (FDMS) Web site at 
                    <E T="03">http://www.regulations.gov/.</E>
                     Follow the online instructions for submitting comments. Comments may also be faxed to 1-202-493-2251.
                </P>
                <P>
                    Comments must be written in the English language, and be no greater than 15 pages in length, although there is no limit to the length of necessary attachments to the comments. If comments are submitted in hard copy form, please ensure that two copies are provided. If you wish to receive confirmation that your comments were received, please enclose a stamped, self-addressed postcard with the comments. Note that all comments received will be posted without change to 
                    <E T="03">
                        http://
                        <PRTPAGE P="35273"/>
                        www.regulations.gov,
                    </E>
                     including any personal information provided.
                </P>
                <P>
                    Documents submitted to a docket may be viewed by anyone at the address and times given above. The documents may also be viewed on the Internet at 
                    <E T="03">http://www.regulations.gov</E>
                     by following the online instructions for accessing the dockets. DOT's complete Privacy Act Statement is available for review in the 
                    <E T="04">Federal Register</E>
                     published on April 11, 2000, (65 FR 19477-78).
                </P>
                <P>The petition, supporting materials, and all comments received before the close of business on the closing date indicated below will be filed and will be considered. All comments and supporting materials received after the closing date will also be filed and will be considered to the extent possible. When the petition is granted or denied, notice of the decision will be published in the Federal Register pursuant to the authority indicated below.</P>
                <P>
                    <E T="03">Comment closing date:</E>
                     July 18, 2011.
                </P>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P> 49 U.S.C. 30118, 30120: delegations of authority at CFR 1.50 and 501.8.</P>
                </AUTH>
                <SIG>
                    <DATED>Issued on: June 10, 2011.</DATED>
                    <NAME>Claude H. Harris, </NAME>
                    <TITLE>Director, Office of Vehicle Safety Compliance.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-14902 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-59-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Surface Transportation Board</SUBAGY>
                <DEPDOC>[Docket No. FD 35528]</DEPDOC>
                <SUBJECT>CSX Transportation, Inc.; Trackage Rights Exemption; The Indiana Rail Road Company</SUBJECT>
                <P>
                    Pursuant to a supplemental trackage rights agreement (Supplemental Agreement No. 1),
                    <SU>1</SU>
                    <FTREF/>
                     The Indiana Rail Road Company (INRD) has agreed to grant overhead trackage rights to CSX Transportation, Inc. (CSXT) 
                    <SU>2</SU>
                    <FTREF/>
                     over approximately 3.5 miles of rail line in Terre Haute, Vigo County, Ind., as follows: Between Belt Junction (milepost 181.7) and the south end of INRD's Martin Siding (milepost 185.2), including a right of entry and exit at the connections of INRD with CSXT at Belt Junction and Spring Hill (milepost 182.7).
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         A draft of the agreement was included with the notice of exemption. The parties state that, upon execution of the agreement, an executed copy will be filed with the Board.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         CSXT controls INRD. 
                        <E T="03">CSX Corp.—Control—Ind. Rail Rd.,</E>
                         FD 32892 (STB served Nov. 7, 1996).
                    </P>
                </FTNT>
                <P>
                    The new trackage rights agreement extends the trackage rights that INRD had previously granted to CSXT 
                    <SU>3</SU>
                    <FTREF/>
                     to operate over INRD's Chicago Subdivision, between the connection of CSXT and INRD trackage at ConMil at approximately INRD milepost 175.5 and the connection of CSXT and INRD trackage at approximately INRD milepost 181.7, a distance of 6.2 miles. The new trackage rights will allow CSXT's crews to deliver trains to and receive trains from INRD on INRD's newly constructed Martin Siding south of Belt Junction.
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         
                        <E T="03">See CSX Transp., Inc.—Trackage Rights Exemption—Ind. Rail Rd.,</E>
                         FD 35058 (STB served July 13, 2007).
                    </P>
                </FTNT>
                <P>The transaction may be consummated on June 30, 2011, the effective date of the exemption (30 days after the exemption was filed).</P>
                <P>
                    As a condition to this exemption, any employees affected by the trackage rights will be protected by the conditions imposed in 
                    <E T="03">Norfolk &amp; Western Railway—Trackage Rights—Burlington Northern, Inc.,</E>
                     354 I.C.C. 605 (1978), as modified in 
                    <E T="03">Mendocino Coast Railway—Lease &amp; Operate—California Western Railroad,</E>
                     360 I.C.C. 653 (1980).
                </P>
                <P>
                    This notice is filed under 49 CFR 1180.2(d)(7). If the notice contains false or misleading information, the exemption is void 
                    <E T="03">ab initio.</E>
                     Petitions to revoke the exemption under 49 U.S.C. 10502(d) may be filed at any time. The filing of a petition to revoke will not automatically stay the effectiveness of the exemption. Stay petitions must be filed by June 23, 2011 (at least 7 days before the exemption becomes effective).
                </P>
                <P>An original and 10 copies of all pleadings, referring to Docket No. FD 35528, must be filed with the Surface Transportation Board, 395 E Street, SW., Washington, DC 20423-0001. In addition, a copy of each pleading must be served on Louis E. Gitomer, 600 Baltimore Ave., Suite 301, Towson, MD 21204.</P>
                <P>
                    Board decisions and notices are available on our Web site at “
                    <E T="03">http://www.stb.dot.gov.”</E>
                </P>
                <SIG>
                    <DATED>Decided: June 8, 2011.</DATED>
                    <P>By the Board.</P>
                    <NAME>Rachel D. Campbell,</NAME>
                    <TITLE>Director, Office of Proceedings.</TITLE>
                    <NAME>Jeffrey Herzig,</NAME>
                    <TITLE>Clearance Clerk.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-14640 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4915-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF THE TREASURY</AGENCY>
                <SUBJECT>Open Meeting of the President's Advisory Council on Financial Capability</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Department of the Treasury.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of meeting.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The President's Advisory Council on Financial Capability (“Council”) will convene its third meeting on July 12, 2011 via audio webcast beginning at 2:30 p.m. Eastern Time. The webcast will be open to the public. Details about how to access the audio webcast will be posted on the Treasury's Office of Financial Education and Financial Access' Web site at 
                        <E T="03">http://www.treasury.gov</E>
                         (click on Resource Center, then on Office of Financial Education and Financial Access and finally on President's Advisory Council on Financial Capability). The Council will receive a report from the Council's subcommittees (Financial Access, Research and Evaluation, Partnerships, and Youth) on their progress and discuss any possible recommendations.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The meeting will be held on July 12, 2011, at 2:30 p.m. Eastern Time.</P>
                    <P>
                        <E T="03">Submission of Written Statements:</E>
                         The public is invited to submit written statements to the Council. Written statements should be sent by any one of the following methods:
                    </P>
                </DATES>
                <HD SOURCE="HD1">Electronic Statements</HD>
                <P>
                    E-mail 
                    <E T="03">ofe@treasury.gov;</E>
                     or
                </P>
                <HD SOURCE="HD1">Paper Statements</HD>
                <P>Send paper statements to the Department of the Treasury, Office of Financial Education and Financial Access, Main Treasury Building, 1500 Pennsylvania Avenue, NW., Washington, DC 20220.</P>
                <P>In general, the Department will make all statements available in their original format, including any business or personal information provided such as names, addresses, e-mail addresses, or telephone numbers, for public inspection and photocopying in the Department's library, Room 1428, Main Department Building, 1500 Pennsylvania Avenue, NW., Washington, DC 20220, on official business days between the hours of 10 a.m. and 5 p.m. You can make an appointment to inspect statements by calling (202) 622-0990. All statements received, including attachments and other supporting materials, are part of the public record and subject to public disclosure. You should only submit information that you wish to make publicly available.</P>
                <FURINF>
                    <PRTPAGE P="35274"/>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Dubis Correal, Director, Office of Financial Education, Department of the Treasury, 1500 Pennsylvania Avenue, NW., Washington, DC 20220, at (202) 622-5770 or 
                        <E T="03">ofe@treasury.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    On January 29, 2010, the President signed Executive Order 13530, creating the Council to assist the American people in understanding financial matters and making informed financial decisions, thereby contributing to financial stability. The Council is composed of two 
                    <E T="03">ex officio</E>
                     Federal officials and 11 non-governmental members appointed by the President with relevant backgrounds, such as financial services, consumer protection, financial access, and education. The role of the Council is to advise the President and the Secretary of the Treasury on means to promote and enhance individuals' and families' financial capability. The Council held its first meeting on November 30, 2010 and its second on April 21, 2011. During the April 2011 meeting, each Council subcommittee presented a progress report and the recommendations it thought the Council as a whole should make to the President and the Secretary. The Council agreed to make two recommendations: (1) That Treasury support the Workplace Leaders in Financial Educations Award, administered by the American Institute of Certified Public Accountants and the Society for Human Resources Management; and (2) that the Treasury issue a challenge to the private sector to create applications for mobile devices that promote financial capability and financial access. The Department of the Treasury is looking into how to implement those recommendations. Additionally, the Council discussed the composition of its subcommittees and their priorities, and decided that it would be more effective to embed the work of the “Strategy” subcommittee into the work of the other subcommittees.
                </P>
                <P>
                    In accordance with section 10(a) of the Federal Advisory Committee Act, 5 U.S.C. App. 2 and the regulations thereunder, Dubis Correal, Designated Federal Officer of the Council, has ordered publication of this notice that the Council will convene its third meeting on July 12, 2011, via audio webcast, beginning at 2:30 p.m. Eastern Time. The meeting will be open to the public. Details on how to access the audio webcast will be posted closer to the date of the meeting at 
                    <E T="03">http://www.treasury.gov</E>
                     (click on Resource Center, then Office of Financial Education and Financial Access, and then on the President's Advisory Council on Financial Capability) or call (202) 622-5770. The purpose of the meeting is to receive an update from the Council's subcommittees on their ideas, progress, and discuss any possible recommendations.
                </P>
                <SIG>
                    <DATED>Dated: June 9, 2011.</DATED>
                    <NAME>Alastair Fitzpayne,</NAME>
                    <TITLE>Executive Secretary, U.S. Department of the Treasury.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-14998 Filed 6-15-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4810-25-P</BILCOD>
        </NOTICE>
    </NOTICES>
    <VOL>76</VOL>
    <NO>116</NO>
    <DATE>Thursday, June 16, 2011</DATE>
    <UNITNAME>Rules and Regulations</UNITNAME>
    <NEWPART>
        <PTITLE>
            <PRTPAGE P="35275"/>
            <PARTNO>Part II</PARTNO>
            <AGENCY TYPE="P">Department of Commerce</AGENCY>
            <SUBAGY>Bureau of Industry and Security</SUBAGY>
            <HRULE/>
            <CFR>15 CFR Parts 732, 738, 740, et al.</CFR>
            <TITLE>Export Control Reform Initiative: Strategic Trade Authorization License Exception; Final Rule</TITLE>
        </PTITLE>
        <RULES>
            <RULE>
                <PREAMB>
                    <PRTPAGE P="35276"/>
                    <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
                    <SUBAGY>Bureau of Industry and Security</SUBAGY>
                    <CFR>15 CFR Parts 732, 738, 740, 743, and 774</CFR>
                    <DEPDOC>[Docket No. 100923470-1230-03]</DEPDOC>
                    <RIN>RIN 0694-AF03</RIN>
                    <SUBJECT>Export Control Reform Initiative: Strategic Trade Authorization License Exception</SUBJECT>
                    <AGY>
                        <HD SOURCE="HED">AGENCY:</HD>
                        <P>Bureau of Industry and Security, Commerce.</P>
                    </AGY>
                    <ACT>
                        <HD SOURCE="HED">ACTION:</HD>
                        <P>Final Rule.</P>
                    </ACT>
                    <SUM>
                        <HD SOURCE="HED">SUMMARY:</HD>
                        <P>This rule adds a new license exception to the Export Administration Regulations (EAR) that authorizes the export, reexport, and transfer (in-country) of specified items to destinations that pose relatively low risk that those items will be used for a purpose that license requirements are designed to prevent. Use of the exception is conditioned upon the creation and exchange by the parties to the transaction of notifications and statements designed to provide assurance against diversion of such items to other destinations. The exception is only relevant to exports, reexports, and transfers for which a license is required under the EAR. Thus, if the EAR do not impose an obligation to apply for and receive a license before exporting, reexporting, or transferring an item subject to the EAR, STA is not relevant to the transaction. The exception does not alter any of the General Prohibitions in the EAR against unlicensed exports, reexports, or transfers to proscribed end users, end uses, or destinations. This rule, has been cleared by several departments, including Defense, State, Homeland Security, and Justice. This rule is part of the Administration's Export Control Reform Initiative, undertaken as a result of the fundamental review of the U.S. export control system that the President announced in August 2009.</P>
                    </SUM>
                    <EFFDATE>
                        <HD SOURCE="HED">DATES:</HD>
                        <P>Effective date June 16, 2011.</P>
                    </EFFDATE>
                    <FURINF>
                        <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                        <P>
                            William Arvin, Regulatory Policy Division, Bureau of Industry and Security, 
                            <E T="03">william.arvin@bis.doc.gov</E>
                             or 202-482-2440.
                        </P>
                    </FURINF>
                </PREAMB>
                <SUPLINF>
                    <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                    <HD SOURCE="HD1">Background</HD>
                    <HD SOURCE="HD2">The Administration's Export Control Reform Initiative</HD>
                    <P>
                        In August 2009, the President directed a broad-based interagency review of the U.S. export control system with the goal of strengthening national security and the competitiveness of key U.S. manufacturing and technology sectors by focusing on current threats and adapting to the changing economic and technological landscape. The review determined that the current export control system is overly complicated, contains too many redundancies, and, in trying to protect too much, diminishes our ability to focus our efforts on the most critical national security priorities. 
                        <E T="03">See, e.g.,</E>
                         August 30, 2010 press release by the White House, Office of the Press Secretary at 
                        <E T="03">http://www.whitehouse.gov/the-press-office/2010/08/30/president-obama-laysfoundation-a-new-export-controlsystem-strengthen-n.</E>
                         As a result, the Administration has begun the Export Control Reform Initiative, which will fundamentally reform the U.S. export control system. The Export Control Reform Initiative is designed to enhance U.S. national security and strengthen the United States' ability to counter threats such as the proliferation of weapons of mass destruction. The Administration determined that fundamental reform is needed with transformation to a single control list, a single licensing agency, a single information technology system, and a single primary enforcement coordination agency. The Administration is implementing the reform in three phases. The first two phases involve short-and medium-term adjustments to the current export control system, with a focus on establishing harmonized control lists and processes among the Departments of Commerce, State, and the Treasury to the extent practicable in order to build toward the third phase of the single control list, licensing agency, information technology system, and enforcement coordination agency. Under this approach, new criteria for determining what items need to be controlled and a common set of policies for determining when an export license is required will be implemented. The control list criteria will be based on transparent rules, which will reduce the uncertainty faced by our allies, U.S. industry, and its foreign partners, and will allow the government to erect higher enforcement walls around the most sensitive items in order to enhance national security.
                    </P>
                    <HD SOURCE="HD2">A New License Exception as an Initial Step in Reform</HD>
                    <P>License Exception Strategic Trade Authorization (STA) authorizes, with conditions, the export, reexport and transfer (in-country) of specified items to destinations that pose relatively low risk of unauthorized uses. To safeguard against reexports to destinations that are not authorized under License Exception STA, License Exception STA imposes certain notification and consignee statement requirements. The exception does not alter any of the General Prohibitions in the EAR against exports, reexports, or transfers to proscribed end users, end uses, or destinations. Under the direction of the Office of Management and Budget, this rule was reviewed and cleared by the Departments of Defense, State, Energy, the Treasury, Homeland Security, and Justice.</P>
                    <P>The exception is only relevant to exports, reexports, and transfers for which a license is required under the EAR. Thus, if the EAR do not impose an obligation to apply for and receive a license before exporting, reexporting, or transferring an item subject to the EAR, STA is not relevant to the transaction. For exports, reexports, and transfers where STA is relevant, its use is optional. Parties may use other license exceptions that authorize a planned transaction or apply for a license if they prefer to do so.</P>
                    <P>
                        On December 9, 2010, BIS issued a proposed rule (75 FR 76653) describing the proposed new License Exception STA that would be an initial step in the Export Control Reform Initiative. BIS received 41 submissions commenting on the proposed rule. They are available for review at: 
                        <E T="03">http://www.regulations.gov</E>
                         (ID # BIS-2010-0038) and on 
                        <E T="03">http://efoia.bis.doc.gov/pubcomm/records-of-comments/record_of_comments_sta.pdf.</E>
                         This final rule implements License Exception STA. It reflects review and analysis of the public comments. A summary of the comments and responses are provided below under “Review of Public Comments.”
                    </P>
                    <HD SOURCE="HD2">Summary of Changes in the Final Rule as Compared to the Proposed Rule</HD>
                    <P>
                        <E T="03">Releases of software source code and technology:</E>
                         Section 740.20 makes specific reference to releases within a single country of software source code and technology to foreign nationals and provides a different notification procedure than that required for exports, reexports and other in country transfers. These changes are in response to public comments. They are described below under the topic heading “review of public comments.”
                    </P>
                    <P>
                        <E T="03">Clarification of terminology in § 740.20:</E>
                         The term “transactions” in § 740.20 has been replaced with the more explicit “exports, reexports and in country transfers” to avoid confusion that might otherwise arise when a single shipment or single sale includes some 
                        <PRTPAGE P="35277"/>
                        items that are subject to License Exception STA and some that are not. Items in such shipment or sale that are not being exported, reexported or transferred pursuant to License Exception STA need not meet the requirements of License Exception STA.
                    </P>
                    <P>
                        <E T="03">Notification to consignee, consignee statement and destination control statement:</E>
                         The revised provisions of § 740.20(d) are based on consideration of the public's comments regarding the proposed notification requirements. The final rule retains the requirement to furnish to the consignee the ECCN of each item to be shipped to the consignee, but does not require that the ECCN be furnished for every successive shipment of the item at issue to the same consignee so long as the ECCN remains accurate. In addition, one consignee statement may be used for multiple shipments. The final rule, however, requires the exporter, reexporter, or transferor to keep a log or other written record that identifies each shipment made under License Exception STA and identifies the specific consignee statement that is associated with each shipment. In addition, the destination control statement described in the proposed rule is replaced with a more general notice requirement. The changes are described below under the topic heading “Final Rule Revisions to License Exception STA Safeguards.” As revised, § 740.20(d) provides the proper assurances that items shipped under License Exception STA will remain within the group of low risk destinations without posing excessive and complex burdens on parties trading in items subject to the EAR.
                    </P>
                    <P>
                        <E T="03">STA paragraphs:</E>
                         Based on a suggestion in the public comments, the STA license exception paragraphs in 49 ECCNs have been revised to state more clearly that they apply only to the destinations listed in paragraph (c)(2) of § 740.20 and not to STA as a whole. This change is described below under the topic heading “review of public comments.”
                    </P>
                    <P>
                        <E T="03">Removal of EI eligibility:</E>
                         Items controlled for encryption (EI) reasons are ineligible for License Exception STA, because of a determination that License Exception STA is not the appropriate approach to addressing the government interests in encryption export controls. Accordingly, BIS will address encryption-related aspects of the Export Control Reform Initiative separately.
                    </P>
                    <P>
                        <E T="03">Removal of pathogen and toxin eligibility:</E>
                         Items described in ECCNs 1C351.a, .b, .c, d.5, .d.6 or .e; 1C352; 1C353; 1C354; 1C360; 1E001 (for 1C351.a, .b, .c, .d.5, .d.6 or .e, 1C352, 1C353, 1C354 or 1C360) or in ECCN 1E351 may not be exported, reexported, or transferred under the authority of License Exception STA. The potential of these items to make a direct contribution to the creation of weapons of mass destruction and United States Government policy to deter the spread of chemical and biological weapons warrants excluding them from STA eligibility.
                    </P>
                    <P>Items in ECCN 1C351.d.1, .2, .3, .4, .7, .8, .9, or .10 may be exported, reexported, or transferred under the authority of License Exception STA in quantities up to 100 milligrams of any one toxin per shipment and no more than six shipments may be sent to any one end user in any one calendar year. Unlike the items described in the previous paragraph, the items described in the ECCNs identified in this paragraph have more widespread commercial and medical applications and are not of a type that can be used to generate or grow large quantities of the toxin. The quantity and frequency cap in this aspect of STA is designed to allow for shipments under the exception to destinations of relatively low risk for appropriate end uses, but not allow for even the potential of unapproved stockpiling of such items in amounts that would create proliferation threats.</P>
                    <P>
                        <E T="03">Modifications to License Exception GOV:</E>
                         Supplement No. 1 to § 740.11 is revised to remove the prohibition on use of License Exception GOV to export items controlled for chemical and biological weapons reasons (CB) to agencies of cooperating governments (as defined in § 740.11(b)(3)(ii) of the EAR) and to their embassies and consulates (as defined in § 740.11(b)(2)(iv) of the EAR) located in Country Group B (Supp. No. 1 to part 740 of the EAR). This change is needed to facilitate the export of pathogens and toxins to governments of cooperating countries to facilitate collaborative responses to outbreaks of disease, whether man-made or naturally occurring, in the absence of eligibility under License Exception STA as noted above.
                    </P>
                    <P>
                        <E T="03">Removal of certain gas turbine engine related software and technology eligibility:</E>
                         Section 740.20 is revised to make the following software and technology ineligible for license exception STA.
                    </P>
                    <P>(A) License Exception STA may not be used for 9D001 or 9D002 “software” that is specially designed or modified for the “development” or “production” of:</P>
                    <P>• Components of engines controlled by ECCN 9A001 if such components incorporate any of the “technologies” controlled by 9E003.a.1, 9E003.a.2, 9E003.a.3, 9E003.a.4, 9E003.a.5, 9E003.c, 9E003.i (other than technology for fan or power turbines), 9E003.h; or</P>
                    <P>• Equipment controlled by 9B001.</P>
                    <P>(B) License Exception STA may not be used for 9D001 “software” that is specially designed or modified for the “development” of “technology” controlled by 9E003.a.1, 9E003.a.2, 9E003.a.3, 9E003.a.4, 9E003.a.5, 9E003.c, 9E003.i (other than technology for fan or power turbines) or 9E003.h.</P>
                    <P>(C) License Exception STA may not be used for 9D004.f or 9D004.g “software”.</P>
                    <P>(D) License Exception STA may not be used for 9E001 “technology” according to the General Technology Note for the “development” of 9A001.b engines or components of engines controlled by 9A001.b if such components incorporate:</P>
                    <P>• Any of the “technologies” controlled by 9E003.a.1, 9E003.a.2, 9E003.a.3, 9E003.a.4, 9E003.a.5, 9E003.c, 9E003.i (other than technology for fan or power turbines) or 9E003.h; or</P>
                    <P>• Any of the 9D001 or 9D002 software in paragraphs (A) or (B) above.</P>
                    <P>(E) License Exception STA may not be used for 9E002 “technology” according to the General Technology Note for the “production” of components of engines controlled by 9A001.b if such components incorporate any of the “technologies” controlled by 9E003.a.1, 9E003.a.2, 9E003.a.3, 9E003.a.4, 9E003.a.5, 9E003.c, 9E003.i (other than technology for fan or power turbines), 9E003.h.</P>
                    <P>(F) License Exception STA may not be used for “technology” in 9E003.a.1, 9E003.a.2, 9E003.a.3, 9E003.a.4, 9E003.a.5, 9E003.c, 9E003.i (other than technology for fan or power turbines) or 9E003.h.</P>
                    <P>
                        A review of gas turbine engine technology has been unable to establish a satisfactory method of distinguishing the foregoing gas turbine engine technology and software that is within the scope of Tier 1 from such technology that is within the scope of Tier 2 (
                        <E T="03">See</E>
                         75 FR 76665, December 9, 2010 for an explanation of the Tier 1 and Tier 2 criteria). Accordingly, such technology and software may not be exported under the authority of License Exception STA.
                    </P>
                    <HD SOURCE="HD3">Removal of Unneeded License Exception STA Paragraph From ECCN 7D002</HD>
                    <P>
                        License Exception STA paragraphs appeared in 50 ECCNs in the proposed rule. Those paragraphs identified items that may not be shipped under License Exception STA authorizing paragraph (c)(2) (§ 740.20(c)(2) of the EAR). In both 
                        <PRTPAGE P="35278"/>
                        the proposed rule and this final rule the License Exception STA paragraphs in the ECCNs have no effect on authorizing paragraph (c)(1) of STA. Because software covered by ECCN 7D002 is controlled for missile technology reasons (MT), such software is ineligible for either authorizing paragraph (c)(1) or authorizing paragraph (c)(2) of License Exception STA. This final rule accordingly does not include a License Exception STA paragraph in ECCN 7D002.
                    </P>
                    <HD SOURCE="HD3">Clarification of Applicability of Missile Technology Controls to ECCN 7E001 and 7E002</HD>
                    <P>
                        ECCNs 7E001 and 7E002 apply 
                        <E T="03">inter alia</E>
                         to technology for the development and production of equipment controlled by ECCNs 7A001, 7A002 and 7A003.d. ECCNs 7E001 and 7E002 impose a national security reason for control on all of the technology that they cover and apply a missile technology reason for control to technology for the development or production of equipment controlled for missile technology reasons. ECCNs 7A001, 7A002 and 7A003.d impose a national security reason for control on all of the equipment that they cover and impose a missile technology reason for control on such equipment if the equipment meets the parameters of ECCN 7A101, 7A102, or 7A103. That pattern is the reverse of the pattern that prevails in the Commerce Control List, where an item that is subject to an ECCN with a lower number as the third character generally would not also be subject to an ECCN with a higher number as the third character. To guard against the possibility that readers will, as a result of this unusual pattern, erroneously conclude that certain 7E001 and 7E002 technology is not subject to the missile technology reason for control, this rule adds a sentence to the license requirements sections of ECCN 7E001 and 7E002 reminding readers that technology for 7A001, 7A002 and 7A003.d equipment is subject to the missile technology reason for control if that equipment meets the parameters of 7A101, 7A102 or 7A103.
                    </P>
                    <HD SOURCE="HD3">Revisions to Eligible Destinations and Removal of Civil End-Use Requirement</HD>
                    <P>In this final rule, 36 countries are included in § 740.20(c)(1), which authorizes exports, reexports and in country transfers that are subject to multiple reasons for control. Eight destinations are included in § 740.20(c)(2), which authorizes export, reexports and in country transfers that are subject to national security reasons for control. The paragraph (c)(1) destinations are: Argentina, Australia, Austria, Belgium, Bulgaria, Canada, Croatia, Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Japan, Latvia, Lithuania, Luxembourg, Netherlands, New Zealand, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, South Korea, Spain, Sweden, Switzerland, Turkey, and the United Kingdom. The paragraph (c)(2) destinations are: Albania, Hong Kong, India, Israel, Malta, Singapore, South Africa, and Taiwan. This final rule also removes the civil end use requirement that the proposed rule applied to destinations listed in paragraph (c)(2).</P>
                    <P>
                        <E T="03">Preclusion of License Exception APR paragraph (b) in addition to paragraph (a):</E>
                         As published in the proposed rule, this final rule precludes use of License Exception APR paragraph (a) (§ 740.16(a) of the EAR) for items that have been shipped pursuant to License Exception STA. Also as published in the proposed rule, this final rule requires consignees in subsequent exports, reexports and in country transfers authorized by License Exception STA to acknowledge that preclusion. However, paragraph (b) of License Exception APR authorizes reexports to most of the destinations authorized by License Exception STA and does not require such notice. Thus, under the proposed rule, a party could receive via APR an item that previously had been shipped under STA and would be unaware of the preclusion. To remedy this inconsistent result, this final rule revises § 740.20 to preclude the use of License Exception APR paragraph (b) if an item previously has been shipped under License Exception STA and to add acknowledgement of that preclusion to the consignee statement required under License Exception STA.
                    </P>
                    <P>Resolution of items under consideration for Tier 1.</P>
                    <P>The preamble to the proposed rule stated the U.S. Government was considering whether the following ECCNs, in whole or part: 0A919, 1A002, 3A001, 3A002, 3A003, 3A201, 3A228, 3A229, 3A232, 4A001, 4A003, 5A001, 6A001, 6A002, 6A003, 6A004, 6A005, 6A006, 7A001, 7A002, 7A003, 7A004, 7A006, 8A001, 8A018, 9A001, 9A004, 9A012 and 9A018 and the technology ECCNs related to them, met the Tier 1 criteria and thus would be excluded from the scope of License Exception STA. Commenters on the proposed rule addressed 1A002, 3A001, 6A001, 6A002, 6A003, 6A005, 7A004, 8A001, 9A001, 9A004, 9A018, 1E001, 6E002, and 9E003. Generally, those comments provided support that certain specific items covered by those ECCNs are widely available from suppliers abroad, including suppliers in destinations not eligible to receive items under License Exception STA under the proposed rule.</P>
                    <P>Because planned export control tiers have not yet been established, nothing can formally be assigned to an export control tier at this time. However, after reviewing the public comments and consulting with other government agencies, BIS has concluded that the ECCNs, or portions thereof, that should be removed from the scope of STA at this time are those identified in § 740.20(b)(2) of this final rule.</P>
                    <P>Continuing efforts to improve export controls and refine License Exception STA.</P>
                    <P>As part of the President's Export Control Reform Initiative, the process of identifying the appropriate export control tier for each item on the Commerce Control List will continue. In addition, agencies will continue to study two specific issues related License Exception STA.</P>
                    <P>One issue is whether some “build to print technology” related to gas turbine engine components and controlled under ECCN 9E002 can be made eligible for License Exception STA while excluding more critical technology. In this instance, the term “build to print technology” refers to information that describes the physical and dimensional characteristics of a component, but does not reveal how to perform the processes that are used to produce a component with those physical and dimensional characteristics.</P>
                    <P>Another issue for further review is whether technology controlled under ECCN 2E003.f related to the application of certain coatings is, in whole or in part, appropriate for exclusion from License Exception STA.</P>
                    <HD SOURCE="HD3">Review of Public Comments</HD>
                    <HD SOURCE="HD2">Public Comments</HD>
                    <P>Some commenters remarked on the overall nature of License Exception STA. Many favored the concept in general and some noted that their own organizations likely would require fewer licenses as a result of STA. Others indicated that, as proposed, STA would provide little or no utility for their organizations. Some suggested specific changes or clarifications to STA or other steps that BIS could take in addition to or in lieu of License Exception STA. These ideas and BIS's responses are discussed below.</P>
                    <P>Comments related to the general utility and feasibility of License Exception STA.</P>
                    <P>
                        <E T="03">Comment 1:</E>
                         Commenters' opinions were divided on the utility of STA. 
                        <PRTPAGE P="35279"/>
                        Some believed that the license exception would substantially reduce the number of licenses needed by their organizations; others indicated that it would result in little or no change with respect to their transactions that are subject to the EAR.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         BIS recognizes that License Exception STA does not address all issues of public concern or even all issues that have been identified as pointing to a need for export control reform. As noted in the preamble to the proposed rule, License Exception STA is only one step in the Administration's Export Control Reform Initiative. Other measures will be needed to effect the remaining aspects of that initiative.
                    </P>
                    <P>
                        <E T="03">Comment 2:</E>
                         One commenter stated that STA provides no real benefit that is not already obtainable under License Exception GBS and that the latter lacks the documentation requirements and restrictions of STA. Several commenters indicated that they thought the restrictions and documentation requirements under STA would limit its utility.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         BIS agrees that parties who engage only in transactions that currently do not require licenses or that currently are eligible for License Exception GBS would not benefit from License Exception STA. A party may continue to use License Exception GBS to the extent the export at issue is within the scope of that exception. However, because License Exception STA is available for more ECCNs than is License Exception GBS, some parties will benefit from this new license exception.
                    </P>
                    <P>
                        <E T="03">Comment 3:</E>
                         Several commenters expressed concern that STA did not go far enough and cited unnamed “government officials” as having predicted that STA will replace GBS once the State and Commerce lists are merged.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         BIS currently has no plan to remove License Exception GBS from the EAR. Determining whether GBS will be needed in a regulatory scheme based on a single control list is premature and beyond the scope of the proposed rule.
                    </P>
                    <P>
                        <E T="03">Comment 4:</E>
                         Some commenters expressed concern that without broader license exceptions, BIS might be unable to handle the volume of licenses that it is likely to encounter once certain items are transferred from the United States Munitions List to the Commerce Control List. These commenters stated that although BIS's projection of License Exception STA replacing over 3,000 licenses annually is not insignificant, it is “not a large portion of the low risk licensing volume currently facing BIS.” Finally, these commenters stated that the State Department faced a 10,000 case backlog in 2007 and recommended that BIS proactively address potential increases in exports and minimize transaction-by-transaction authorization requirements in order to avoid a similar situation.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         BIS recognizes that a transfer of a large number of items from the United States Munitions List to the Commerce Control List could significantly increase BIS's workload and, without adequate preparation, could result in backlogs and delays. BIS is working to develop means for addressing those concerns. However, License Exception STA is intended to provide a more efficient method of shipping items currently subject to the EAR to destinations that present a relatively low risk of diversion. Concerns about future transfers of items from the United States Munitions List are beyond the scope of the proposed rule.
                    </P>
                    <P>
                        <E T="03">Comment 5:</E>
                         Some commenters on this topic proposed a range of changes to the EAR other than License Exception STA to address to the perceived need for fewer situations in which transaction-by-transaction authorization is required. Such proposals were: (i) Simply removing license requirements by removing X's from the boxes in the Country Chart table [Supp. No. 1 to part 738 of the EAR]; (ii) broadening the validated end-user program; (iii) creating an open general license similar to that used by the United Kingdom; and (iv) creating an intra-company transfer license that imposes fewer requirements on users than BIS's 2008 proposal on that subject.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         License Exception STA is intended as an initial step in a broad export control reform effort. It recognizes, consistent with U.S. international commitments, a limited group of destinations in which the risk of diversion to unauthorized destinations, parties or uses is low. It also imposes certain safeguards to provide reasonable assurance that  items exported, reexported, or transferred pursuant to STA will not be diverted outside that group. Each of the types of proposed revisions noted above was considered. BIS ultimately determined that a license exception approach is the best way to address the goals of this aspect of the reform effort, which primarily include reducing the licensing burden with respect to exports to a limited group of destinations, consistent with U.S. international commitments, without a wholesale revision of the EAR, creating a method of notifying foreign consignees about the prohibitions on reexports outside such destinations, avoiding unintentionally re-imposing previously removed controls, and creating records sufficient for monitoring and enforcement of parties' compliance with the conditions and obligations of STA.
                    </P>
                    <HD SOURCE="HD3">Comments Regarding Clarity</HD>
                    <P>
                        <E T="03">Comment 6:</E>
                         One commenter stated that the effects of License Exception STA on encryption are unclear and asked whether License Exception ENC reporting requirements apply to an encryption item exported under License Exception STA.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The final rule does not permit items controlled for encryption reasons to be exported, reexported or transferred under License Exception STA. Accordingly, any lack of clarity on this point that may have been present in the proposed rule need not be addressed in the final rule.
                    </P>
                    <P>
                        <E T="03">Comment 7:</E>
                         One commenter stated that BIS needs to make clear that items controlled for antiterrorism (AT) reasons are not excluded from STA. The commenter noted that a license is not required for AT reasons for any STA eligible destination.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         This commenter's observation about the lack of an AT license requirement for any STA eligible destination is correct with respect to destination-based license requirements (although Part 744 of the EAR may impose an AT license requirement for specific end uses or end users in any destination). Like other License Exceptions in the EAR, STA would be used only where a license requirement exists; if no license is required there is no need to consider STA or any other license exception. Although most ECCNs include antiterrorism as a reason for control, that reason for control currently imposes a license requirement for only five destinations, none of which is eligible for STA. Although the absence of a reference to antiterrorism controls in License Exception STA might cause some readers to conclude erroneously that 
                        <E T="03">items</E>
                         controlled for antiterrorism reasons may not be shipped under license exception STA, adding such a reference might cause some readers to conclude erroneously that exports, reexports, and in country transfers to which antiterrorism controls 
                        <E T="03">do</E>
                         apply may be consummated under License Exception STA. The latter error has greater potential for harm than the former. Therefore, BIS does not believe that a change to the regulatory text on this point is desirable.
                    </P>
                    <P>Comments regarding deemed exports.</P>
                    <P>
                        <E T="03">Comment 8:</E>
                         Two commenters addressed the applicability of License Exception STA to deemed exports. One 
                        <PRTPAGE P="35280"/>
                        indicated that it read the proposed rule as permitting License Exception STA to be used for deemed exports but suggested that specific authorizing language be added to STA for clarity. Another stated that STA would be useful for deemed exports and would be useful for some exports to some foreign subsidiary employees.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         BIS's intent in publishing the proposed rule was for License Exception STA to authorize deemed exports. However, upon further review, BIS has concluded that the requirements to furnish ECCNs, to obtain a consignee statement, and to provide a destination control statement are not likely to be relevant or useful in deemed export situations, which typically involve an employer-employee relationship or researcher collaborations. Accordingly, this final rule changes § 740.20 to address deemed exports and reexports separately from other exports and reexports. Releases of source code and technology are explicitly authorized. The authorization paragraphs explicitly refer to nationals of the destinations listed therein. Deemed exports and reexports are therefore explicitly authorized under License Exception STA. The ECCN notification, consignee statement, and destination control statement requirements are replaced with a requirement that the releaser of the technology or source code notify the recipient of the restrictions on further release. The notification must either expressly inform the recipient that the EAR impose limits on further disclosure or must be in the form of an agreement in which the recipient agrees to limits on further disclosure. Any such agreement must impose limits that are equivalent to or more restrictive than all limits on further disclosure that are imposed by the EAR. The notification must be in writing. The notification may be in a separate document or included in a document such as a contract or a nondisclosure agreement. If the document has an expiration date, it must provide that the restrictions on disclosure do not expire.
                    </P>
                    <P>Recommendation for new process for public input on eligible ECCNs for License Exception STA.</P>
                    <P>
                        <E T="03">Comment 9:</E>
                         One commenter recognized that statutory restrictions and regime controls place some restrictions on BIS. That commenter, however, recommended that BIS state in the final rule that it will conduct regular reviews of ECCNs and set up a process whereby exporters could submit a request to BIS setting forth the reasons that a particular ECCN should be eligible for STA.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         BIS is reviewing the Commerce Control List as a whole as part of the Administration's Export Control Reform Initiative. In addition, the EAR (including the Commerce Control List) will be subject to the retrospective review requirements of Executive Order 13563. Those who wish to recommend any change to License Exception STA or any other provision of the EAR may do so in a number of ways, such as: informal contacts with BIS; contacting one of the technical advisory committees that advise BIS; or petitioning BIS for issuance, amendment or repeal of a rule, as contemplated by § 756.1(a)(1) of the EAR. Although always open to suggestions, BIS does not plan to set up a special process to receive proposed changes to License Exception STA.
                    </P>
                    <P>
                        <E T="03">Comment</E>
                         on end use restrictions in § 740.20(c)(2)(ii) in the proposed rule.
                    </P>
                    <P>
                        <E T="03">Comment 10:</E>
                         One commenter stated that by including the phrase “other than a military end use as defined in § 744.21 of the EAR” in the definition of “civil end use” in proposed § 740.20(c)(2)(ii), the proposed rule essentially took the China End Use Rule and applied the foreign policy behind that rule to a much larger group of countries even though many of those countries are not subject to the same foreign policy considerations as is China.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Because the final rule does not include a civil end-use requirement, a discussion of whether the definition of civil end-use in § 744.21 is appropriate for STA is unnecessary.
                    </P>
                    <P>Proposal to expand the scope of STA.</P>
                    <P>
                        <E T="03">Comment 11:</E>
                         One commenter recommended that STA should be available for transactions where the exporter and consignee are the same organization.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         License Exception STA is available for transactions where the exporter and the consignee are the same organization, but only if they otherwise meet the requirements for use of the license exception.
                    </P>
                    <P>Eligible destination comments.</P>
                    <P>
                        <E T="03">Comment 12:</E>
                        Several commenters raised questions regarding the limitations on License Exception STA eligibility for certain countries.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                        BIS has determined that for foreign policy reasons, the lists of destinations eligible for License Exception STA shall be limited to those destinations included in this final rule.
                    </P>
                    <P>Eligible items comments.</P>
                    <P>
                        <E T="03">Comment 13:</E>
                        Two commenters recommended that items controlled for missile technology reasons should be made eligible for License Exception STA under limited circumstances. One commenter stated that such items are needed for use in public light water reactors. Another commenter stated that the eligibility of certain items, which are in Category 7 of the Commerce Control List, could be limited to equipment required for or in support of safety of flight.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                        BIS does not have the discretion to include any item controlled for export for missile technology reasons in License Exception STA. Items are controlled on the Commerce Control List for missile technology reasons because they are listed in the Missile Technology Control Regime Annex. The exclusion of items on the Missile Technology Control Regime Annex is based on Section 6(l) of the Export Administration Act and the U.S. commitment to implement the Missile Technology Control Regime Guidelines.
                    </P>
                    <P>
                        <E T="03">Comment 14:</E>
                        One commenter stated that ECCNs 2B232 and 2E001 should be eligible for STA. The commenter noted that manufacturers in China and India make comparable products.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                        ECCN 2B232 and the portion of 2E001 that addresses technology for the development of equipment controlled under 2B232 are controlled for nuclear proliferation reasons. Under both the proposed rule and this final rule, their License Exception STA eligibility is limited to the destinations in § 740.20(c)(1) for foreign policy reasons.
                    </P>
                    <P>
                        <E T="03">Comment 15:</E>
                        One commenter stated that it needs to ship items that are covered by ECCN 2B350 predominantly to Taiwan, Singapore, China and Israel. The commenter stated that it currently has about 100 licenses and that license requirements make it uncompetitive and cause it to lose business. This commenter asserted that similar parts made in South Korea can get a license in one to two weeks. A better approach than the proposed rule would be to allow less sensitive components to be exported without a license to more destinations.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                        For such destinations as Taiwan, Singapore and Israel, which are destinations listed in § 740.20(c)(2), BIS proposed that License Exception STA may be used for transactions in which the only applicable reason for control is national security. ECCN 2B350 is controlled for chemical and biological weapons reasons. BIS has retained this limit in the final rule for foreign policy reasons.
                    </P>
                    <P>
                        <E T="03">Comment 16:</E>
                        One commenter stated that exclusion of CCL Category 3 and 4 items would limit the utility of License Exception STA.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                        Commerce Control List Categories 3 and 4 are not excluded in 
                        <PRTPAGE P="35281"/>
                        their entirety from STA. All or portions of some ECCNs in Categories 3 and 4 are excluded from eligibility to the eight destinations listed in § 740.20(c)(2) because they cover items on the Wassenaar Arrangement Sensitive List. This limitation on items eligible for export to destinations listed in § 740.20(c)(2) was included in the proposed rule, and BIS has concluded that retaining the rule's limit of eligibility for License Exception STA for these destinations to non-Sensitive List items is appropriate for foreign policy reasons.
                    </P>
                    <P>
                        <E T="03">Comment 17:</E>
                        One commenter stated that ECCN 6A002.a.2 and .a.3 should be eligible for § 740.20(c)(1) destinations.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                        Under both the proposed rule and this final rule, ECCNs 6A002.a.2 and .a.3 are eligible for § 740.20(c)(1) destinations except for those portions of paragraph .a.3 that are subject to control for missile technology (MT) reasons. For the reason noted in the response to 
                        <E T="03">Comment</E>
                         13 above, BIS is not making MT controlled items eligible for License Exception STA. Portions of 6A002.a.2 and all of 6A002.a.3 are ineligible for § 740.20(a)(2) destinations because they are on the Wassenaar Arrangement Sensitive List.
                    </P>
                    <P>
                        <E T="03">Comment 18:</E>
                        Two commenters stated that ECCN 6A003.b should be eligible for the 127 destinations set forth in § 740.20(c)(2) of the proposed rule and one of those commenters also stated that ECCN 9A018.b should be eligible.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                        The STA paragraph for ECCN 6A003 excludes all of paragraphs .b.3 and .b.4 from STA eligibility if the destination is one of the destinations in paragraph (c)(2) of the proposed rule (eight destinations in this final rule). BIS developed the STA paragraphs to provide a reasonable balance between the policy of excluding items on the Sensitive List from eligibility under § 740.20(c)(2) and the need to make the regulations as clear as possible within substantive policy constraints. Rewriting the STA paragraph in 6A003 to match exactly the Sensitive List would add significantly to the length and complexity of the entry while providing relatively little change in the scope of eligible transactions. Moreover, ECCN 6A003.b.3 and .b.4.b are also controlled for regional stability reasons. Thus, even if the STA paragraph in 6A003 were rewritten to match the text of the Sensitive List exactly, the items in 6A003.b.3 and .b.4.b would continue to be excluded from eligibility under § 740.20(c)(2) because of their regional stability control. ECCN 9A018.b is also subject to a regional stability control and, consistent with the policy stated above, is not eligible for § 740.20(c)(2).
                    </P>
                    <P>
                        <E T="03">Comment 19:</E>
                        One commenter recommended that ECCN 6A001.a.2.d.1 (certain underwater heading sensors), .a.2.b.7 (certain towed hydrophone arrays) and .a.2.e.1 (certain bottom or bay cable systems) be made eligible for § 740.20(c)(2) destinations. Without such eligibility, the ability to use STA to send repair items to vessels in port is limited. These items do not require a license to go to destinations in Country Group A:1 (Supp. No. 1 to Part 740 of the EAR), which includes most of the destinations eligible under § 740.20(c)(1). This commenter stated that if License Exception STA results in the repeal of License Exception RPL, it would be at a disadvantage.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                        This final rule excludes items listed on the Wassenaar Arrangement Sensitive List from destinations listed in § 740.20(c)(2). As set forth in the response to 
                        <E T="03">Comment</E>
                         16, BIS has concluded that limiting these destinations to non-Sensitive List items is appropriate for foreign policy reasons. That said, BIS is not eliminating License Exception RPL. In addition, BIS can make one change to the 6A001 STA paragraph to track more accurately the Wassenaar Arrangement Sensitive List without adding undue length and complexity to the ECCN. Paragraph .a.2.a.4 is not on the Wassenaar Arrangement Sensitive List. Therefore, BIS is adding the phrase “except .a.2.a.4” immediately following the phrase “or 6A001.a.2 in the STA paragraph of the License Exception Section of ECCN 6A001.”
                    </P>
                    <P>
                        <E T="03">Comment 20:</E>
                        One commenter recommended that items in ECCN 8A001.c (unmanned tethered submersible vehicles) be made eligible for § 740.20(c)(2). The commenter noted that such vehicles already do not require a license for most of the 37 destinations in proposed § 740.20(c)(1) and so STA would not affect the licensing burden for these items to any great degree. This commenter stated that allowing full STA eligibility for these items would be consistent with the Wassenaar Arrangement's best practices agreed to at the 2006 Wassenaar Arrangement plenary meeting, which allows license exceptions for sensitive list items. Other Wassenaar members allow exports without an individual license. For example the United Kingdom permits such exports under an open general license. The safeguards imposed by License Exception STA allow for sensitive list items to be controlled and monitored consistent with U.S. national security interests and regime obligations. These vehicles cannot go far from their support vessel, cannot be preprogrammed and require considerable support equipment. In some cases a vessel or rig must be modified to handle the equipment and restored when the equipment is removed making diversion of such vehicles to military uses unlikely. Unmanned tethered submersible vehicles are not as sensitive from a national security perspective as untethered submersibles. Excluding 8A001.c unmanned tethered submersible vehicles while allowing 8A001.a manned tethered submersibles full STA treatment would be inconsistent.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                        Notwithstanding the arguments made in the 
                        <E T="03">Comment,</E>
                         BIS has determined that retaining the limitation set forth in the proposed rule that STA authorization for Wassenaar Arrangement Sensitive List items (as 8A001.a items are) is available only to the destinations listed in § 740.20(c)(1) of this final rule is necessary for foreign policy reasons.
                    </P>
                    <P>Comments on information and consignee statement requirements.</P>
                    <P>BIS received a number of comments on the proposed requirements to provide safeguards against diversion that were set forth in the proposed rule. Those safeguards are: the requirement to provide the consignee with the item description and ECCN; the requirement to obtain assurances from the consignee; and the requirement to furnish a special STA destination control statement. Some of the comments applied to the safeguards as a whole and others to specific safeguard measures.</P>
                    <P>Comments regarding the safeguards as a whole.</P>
                    <P>
                        <E T="03">Comment 21:</E>
                        Some commenters stated that manufacturers already have processes in place to notify consignees not to reexport in violation of the EAR and to provide ECCNs and destination control statements or that language typically found in sales contracts and purchase order agreements is a more effective means of communicating compliance obligations.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                        Although BIS encourages parties trading in items subject to the EAR to inform their customers of EAR requirements and responsibilities of parties to the transaction, in general the EAR do not require parties to do so. License Exception STA could not function in its intended manner unless all exporters, reexporters, transferors and consignees are aware of their specific responsibilities. Some form of mandatory notice is, therefore, necessary.
                    </P>
                    <P>
                        <E T="03">Comment 22:</E>
                        One commenter stated that the STA safeguards transferred 
                        <PRTPAGE P="35282"/>
                        compliance responsibilities from the exporter to the consignee.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                        BIS does not believe that the creation of License Exception STA or the specific safeguard requirements that STA imposes constitute a “transfer” of responsibilities from one party to another. All parties dealing with items that are subject to the EAR are responsible for compliance with those regulations. The safeguard requirements of License Exception STA are intended to place parties on notice of their responsibilities and to verify that they are aware of, and will comply with, such responsibilities.
                    </P>
                    <P>Comments regarding the requirement to furnish the Export Control Classification Number.</P>
                    <P>
                        <E T="03">Comment 23:</E>
                        Several commenters stated that the requirement to furnish an ECCN is unnecessary. The reasons those gave were: ECCNs are already provided on the invoice and air waybill; the EAR already require the ECCN at least for the initial export; the ECCN is required in the STA consignee statement; and it would be difficult for U.S. exporters to verify that foreign buyers pass ECCN information along to their customers.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                        Although BIS encourages parties to notify their consignees of the EAR, compliance responsibilities, and other information that would aid compliance such as ECCNs, such activities are generally not required under the EAR. License Exception STA is intended to remove the burden of applying for a license in exports, reexports and in country transfers that are limited to certain destinations where there is a relatively low risk of diversion. Requiring that consignees be notified of the ECCN provides reasonable assurance that the consignee will be on notice that the item it is receiving is sensitive and that further distribution without a U.S. license must be restricted to the destinations for which no license is required, or for which STA or some other License Exception provides authorization.
                    </P>
                    <P>The EAR do not require exporters to monitor the conduct of foreign buyers to verify that they pass on ECCN information to their customers. The EAR do, however, prohibit, among other things, selling, transferring, transporting or servicing items subject to the EAR with knowledge that a violation has, will, or is intended to take place with respect to that item.</P>
                    <P>
                        <E T="03">Comment 24:</E>
                        One commenter asked who would be responsible if an erroneous ECCN is supplied and, as a result, the consignee reexports an item using License Exception STA in a transaction that is not authorized by STA. The commenter recommended that the reexporter not be liable in such a case.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                        BIS believes that the consignee should be able to place reasonable reliance on the ECCN furnished by its supplier in License Exception STA transactions. Accordingly, the final rule states that for purposes of determining reexport or transfer eligibility under STA, the consignee may rely on the ECCN provided to it by the party required to furnish the ECCN to the consignee unless the consignee “knows” that the ECCN is in error. The term “know” has the same meaning as the term “knowledge” in § 772.1 of the EAR.
                    </P>
                    <P>Comments regarding the requirement to obtain consignee statement.</P>
                    <P>
                        <E T="03">Comment 25:</E>
                        Several commenters proposed that one consignee statement be permitted for multiple transactions. Various proposals were to allow a single statement for a specific project, a specific contract, a specific time period or for all items to be shipped to that consignee under STA. One commenter suggested that License Exception STA as proposed actually allows for a single statement to cover multiple shipments but clarification is desirable.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                        BIS agrees that a single consignee statement should be able to cover more than one transaction for the reasons provided by commenters and is revising the final rule to explicitly so state. These revisions are described more fully under the topic heading “Final Rule Revisions to License Exception STA Safeguards” below.
                    </P>
                    <P>
                        <E T="03">Comment 26:</E>
                        One commenter stated that the requirement for a consignee acknowledgement is in direct opposition to BIS's statement that the eligible destinations are “low risk.”
                    </P>
                    <P>Another commenter stated that the requirement for reexporters and transferors to obtain a statement from their consignees would impose a burden on a particular country's exporters without providing additional safeguards to U.S. export controls because that country has stringent export controls based on the same multilateral regimes as the United States. Several commenters noted that foreign customers are often reluctant or unwilling to acknowledge U.S. jurisdiction and suggested that this requirement continues a perception that dealing with U.S. companies is difficult.</P>
                    <P>
                        <E T="03">Response:</E>
                        An important purpose of the consignee statement is to ensure that the consignee is aware that the item has been shipped under a license exception that is limited to low risk destinations and agrees to take steps that will keep the item from leaving those destinations without authorization. It is integral to the overall purpose of STA, which is to provide license exception shipments throughout a group of low risk destinations. Regime membership is a key part of the overall structure for export controls in an importing country. STA is based, in part, on that structure but focuses further on actual transactions to ensure controlled items are properly exported and reexported.
                    </P>
                    <P>
                        <E T="03">Comment 27:</E>
                        One commenter suggested that the requirement to obtain a consignee statement should not be needed for destinations in § 740.20(c)(2) because the eligible items are less sensitive than those available to destinations listed in § 740.20(c)(1). This commenter noted that BIS has ample existing means of identifying violations and enforcing STA restrictions, including post shipment verifications and placing violators on the Entity List.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                        The purpose of the consignee statement is to make sure that the consignee is aware that the item has been shipped under a license exception that is limited to low risk destinations. It is integral to the overall purpose of STA, which is to provide license exception shipments throughout a group of low risk destinations. Although the items eligible to § 740.20(c)(2) destinations are less sensitive than those eligible to § 740.20(c)(1) destinations, the items are still sufficiently sensitive that obtaining the consignee's acknowledgement of the limits of STA is necessary to provide reasonable assurance that the item will not be reexported beyond the low risk group of authorized destinations.
                    </P>
                    <P>
                        <E T="03">Comment 28:</E>
                        This commenter also suggested that if the consignee statement is retained, three specific provisions are unnecessary. First, the provision in which the consignee agrees not to export, reexport or transfer in violation of the EAR is not needed because it merely duplicates the requirements of the regulations. Second, consignees in § 740.20(c)(2) destinations should not be required to acknowledge that items shipped under STA may not subsequently be shipped under License Exception APR paragraph (a) because that paragraph does not authorize reexports from any § 740.20(c)(2) country. Third, the requirement to agree that items shipped under § 740.20(c)(2)(ii) [125 destinations in the proposed rule] may be used only in a civil end use is unneeded because it repeats a restriction in part 744 of the EAR and creates an unreasonable burden on all parties in a chain of transactions who are, in effect, agreeing not to incorporate the exported item into a United States Munitions List 
                        <PRTPAGE P="35283"/>
                        defense article. This burden is particularly problematic for manufacturers of materials.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                        License exception STA authorizes exports, reexports and in country transfers in sensitive items that otherwise would require a license. As such, requiring acknowledgement of the regulations that apply to the shipment is reasonable.
                    </P>
                    <P>This commenter correctly notes that License Exception APR paragraph (a) does not directly authorize any reexport from a destination listed in § 740.20(c)(2). However License Exception STA does authorize reexports from places listed in § 740.20(c)(2) to destinations listed in § 740.20(c)(1) and License Exception APR paragraph (a) does authorize reexports from those (c)(1) destinations to other destinations that are not eligible for STA. For the safeguards of License Exception STA to function effectively, all reexporters must notify their consignees of the STA restrictions. The party in a § 740.20(c)(2) location will need to be on notice of the APR paragraph (a) restriction in order to be able to obtain the needed assurance from any party in a § 740.20(c)(1) destination to which it reexports.</P>
                    <P>Because this final rule removes the civil end use limitation from § 740.20(c)(2), the requirement to agree to that limitation is not needed and this final rule removes it from the consignee statement.</P>
                    <P>Comments regarding the destination control statement.</P>
                    <P>
                        <E T="03">Comment 29:</E>
                         Some commenters objected to the special STA destination control statement, which under the proposed rule, the exporter, reexporter, or transferor would need to place on export control documents that accompany the shipment. The stated reasons for the objections were that the requirement would be superfluous to other EAR provisions, the cost and complexity of the requirements would discourage use of License Exception STA, and that a second destination control statement is not needed or would not be effective.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         After review of the comments and further consideration, BIS has concluded that some form of notice to the consignee that the items it is receiving are subject to STA is needed. However that notice need not take the form of a destination control statement. Accordingly, BIS is replacing the destination control statement requirement with the notice requirement that is described under the heading “Final Rule Revisions to License Exception STA Safeguards” below.
                    </P>
                    <P>Final Rule Revisions to License Exception STA Safeguards.</P>
                    <P>The proposed requirements to furnish an ECCN, to obtain a consignee statement and to furnish a destination control statement were intended to operate in concert to provide assurance against diversions. To address the points raised by some of the commenters regarding those proposed requirements while maintaining their concerted nature, BIS is making the changes described below.</P>
                    <P>The final rule adds clarifying language to § 740.20(d)(1) and (2) stating that the Export Control Classification Number furnished to the consignee may be used for multiple shipments of the same item by a given exporter to a given consignee under License Exception STA so long as the information remains accurate. The final rule also provides that for purposes of determining reexport or transfer eligibility under STA, the consignee may rely on the ECCN provided to it by the party required to furnish the ECCN to the consignee unless the consignee knows that the ECCN is in error. The term “know” has the same meaning as the term “knowledge” in § 772.1 of the EAR.</P>
                    <P>The final rule revises § 740.20(d)(2) to provide that one consignee statement may be used for multiple shipments of the same item by the same exporter to the same consignee under License Exception STA provided descriptions of the item(s), ECCN(s) and names of the parties remain accurate. The final rule also removes the provision calling for the consignees' agreement that items shipped to certain destinations will be used only for civil end uses because the final rule does not impose a civil end use limitation. To facilitate verification of compliance with the consignee statement requirement, the final rule requires the exporter, reexporter, and transferor to maintain the specific consignee statement that is associated with each shipment and a log or other record that identifies each shipment made under License Exception STA and identifies the specific consignee statement that is associated with each shipment.</P>
                    <P>The final rule replaces the destination control statement with a requirement that the exporter, reexporter or transferor, as applicable, notify the consignee in writing that the shipment is made pursuant to License Exception STA. The notice must either specify which items are subject to License Exception STA or state that the entire shipment is made pursuant to License Exception STA. The notice must clearly identify the shipment to which it applies. The written notice may be conveyed by paper documents or by electronic methods such as facsimile or email.</P>
                    <P>BIS believes that with these changes, the STA safeguards provide appropriate assurances that items shipped under License Exception STA will remain within the group of low risk destinations without placing excessive and complex burdens on parties trading items subject to the EAR.</P>
                    <P>Comments regarding the License Exception STA paragraphs.</P>
                    <P>
                        <E T="03">Comment 30:</E>
                         The STA paragraphs, which appear in 49 ECCNs in this final rule, designate those ECCNs or portions thereof as ineligible for License Exception STA if the destination is listed in § 740.20(c)(2) of the EAR. Those exclusion paragraphs have no effect on the availability of STA for destinations listed in § 740.20(c)(1) of the EAR. Some commenters indicated that these exclusion paragraphs were confusing and would lead readers to conclude erroneously that the designated ECCNs or the designated portions were ineligible for License Exception STA for all destinations. In addition, some of the commenters appear to have misinterpreted the meaning of the STA exclusion paragraphs in exactly that manner. Commenters offered several suggestions to address this source of confusion.
                    </P>
                    <P>One suggestion was to employ two STA paragraphs in each ECCN on the Commerce Control List, one paragraph would state whether STA is eligible for destinations listed in § 740.20(c)(1) and the other would state whether the License Exception is eligible for destinations listed in § 740.20(c)(2). Each paragraph would take into account all of the reasons for control in the ECCN and any other relevant factors including whether the item is on the Wassenaar Arrangement Sensitive List.</P>
                    <P>Another suggestion was to use some annotation in the STA paragraphs such as STA 1 for § 740.20(c)(1) and STA 2 for § 740.20(c)(2).</P>
                    <P>A third suggestion was to reference the number of destinations that are excluded by the paragraph.</P>
                    <P>A fourth suggestion was to create a matrix that would show the STA eligibility for each ECCN and destination.</P>
                    <P>
                        <E T="03">Response:</E>
                         BIS has decided to adopt the third suggestion in this final rule. Because the number of destinations listed in § 740.20(c)(2) in the final rule is eight compared to 36 eligible destinations under § 740.20(c)(1), BIS believes that the best solution is to modify the STA paragraphs to reference the number of destinations in addition 
                        <PRTPAGE P="35284"/>
                        to referencing the relevant STA eligibility paragraph, 
                        <E T="03">i.e.</E>
                         § 740.20(c)(1) or (c)(2).
                    </P>
                    <P>Accordingly, the STA exclusion paragraphs in this final rule have the format: “License Exception STA may not be used to ship [list ineligible items] to any of the eight destinations listed in § 740.20(c)(2).” The words “or transmit” immediately follow the words “to ship” in software or technology ECCNs to be consistent with terminology used elsewhere in the EAR. BIS decided not to introduce STA paragraphs into every ECCN because ECCNs that include multiple reasons for control would require lengthy and complex STA paragraphs. This complexity would be compounded in the case of software and technology ECCNs in which one ECCN often encompasses not only multiple reasons for control but also references to multiple commodity ECCNs.</P>
                    <P>BIS decided not to adopt separate annotations such as STA1 and STA2 for the two authorizing paragraphs for two reasons. First, to be fully effective, this suggestion would require that the notations be in every ECCN, creating the same length and complexity issues noted above. Second, every License Exception paragraph in the Commerce Control List is designated by the symbol that is used to report shipments under that License Exception in the Automated Export System. All shipments under License Exception STA are to be reported under the symbol STA. Use of two different designators for a single license exception in the Commerce Control List could cause public confusion about the procedure for reporting License Exception STA shipments.</P>
                    <P>BIS decided not to attempt to describe STA eligibility in the form of a matrix because this technique also would produce an unduly complex document. Such a matrix would have to account for every destination in the world and every paragraph of every ECCN, making it far larger than the current Country Chart found at Supp. No. 1 to part 738 of the EAR. The STA paragraphs apply to only eight destinations and to 49 ECCNs. BIS believes that revising the STA paragraphs themselves is a more practical way to reduce the possibility of confusion pointed out by these commenters.</P>
                    <HD SOURCE="HD2">Specific License Exception Provisions</HD>
                    <HD SOURCE="HD2">Scope</HD>
                    <P>The license exception applies only to Commerce Control List based license requirements. Transactions in which a license is required because of an end-use—such as a proliferation end use described in part 744 of the EAR or a proscribed end user (such as a party on the Entity List in part 744 of the EAR)—or because the destination is subject to an embargo or special restrictions in part 746 of the EAR, are not eligible for License Exception STA. Items on the Commerce Control List that are subject to the encryption items (EI), short supply (SS), surreptitious listening (SL), missile technology (MT), or chemical weapons (CW) reasons for control are not eligible for License Exception STA because of various requirements imposed by statutes, treaties or U.S. implementation of international commitments. Items in ECCNs 0A981, 0A982, 0A983, 0A985 or 0E982 are not eligible. Those ECCNs apply to equipment designed for the execution of human beings, specially designed implements of torture, law enforcement restraint devices, discharge type arms and devices designed to administer electric shocks and certain related technology. The human rights concerns associated with those items are sufficiently great to justify precluding use of License Exception STA.</P>
                    <P>Items in ECCNs 1C351.a, .b, .c, .d.5, .d.6 or .e; 1C352; 1C353; 1C354; 1C360; 1E001 (for 1C351.a, .b, .c, .d.5, .d.6 or .e, 1C352, 1C353, 1C354 or 1C360) or in ECCN 1E351 may not be shipped pursuant to License Exception STA because those ECCNs cover certain pathogens and toxins that have potential uses in developing chemical or biological weapons. Commodities in ECCN 1C351.d.1, .2, .3, .4, .7, .8, .9, or .10 are eligible for License Exception STA so long as the exports, reexports or transfers are limited to no more than 100 milligrams of any one toxin per shipment and no more than six shipments are sent to any one end user in any one calendar year.</P>
                    <P>License Exception STA may not be used for certain software and technology in Category 9 of the Commerce Control List as noted below.</P>
                    <P>(A) License Exception STA may not be used for 9D001 or 9D002 “software” that is specially designed or modified for the “development” or “production” of:</P>
                    <P>(1) Components of engines controlled by ECCN 9A001 if such components incorporate any of the “technologies” controlled by 9E003.a.1, 9E003.a.2, 9E003.a.3, 9E003.a.4, 9E003.a.5, 9E003.c, 9E003.i (other than technology for fan or power turbines), 9E003.h; or</P>
                    <P>(2) Equipment controlled by 9B001; or</P>
                    <P>(B) License Exception STA may not be used for 9D001 “software” that is specially designed or modified for the “development” of “technology” controlled by 9E003.a.1, 9E003.a.2, 9E003.a.3, 9E003.a.4, 9E003.a.5, 9E003.c, 9E003.i (other than technology for fan or power turbines) or 9E003.h.</P>
                    <P>(C) License Exception STA may not be used for 9D004.f or 9D004.g “software”.</P>
                    <P>(D) License Exception STA may not be used for 9E001 “technology” according to the General Technology Note for the “development” of 9A001.b engines or components of engines controlled by 9A001.b if such components incorporate:</P>
                    <P>(1) Any of the “technologies” controlled by 9E003.a.1, 9E003.a.2, 9E003.a.3, 9E003.a.4, 9E003.a.5, 9E003.c, 9E003.i (other than technology for fan or power turbines) or 9E003.h;</P>
                    <P>(2) Any of the 9D001 or 9D002 software in paragraphs (A) or (B) above.</P>
                    <P>(E) License Exception STA may not be used for 9E002 “technology” according to the General Technology Note for the “production” of components of engines controlled by 9A001.b if such components incorporate any of the “technologies” controlled by 9E003.a.1, 9E003.a.2, 9E003.a.3, 9E003.a.4, 9E003.a.5, 9E003.c, 9E003.i (other than technology for fan or power turbines) or 9E003.h.</P>
                    <P>(F) License Exception STA may not be used for “technology” in 9E003.a.1, 9E003.a.2, 9E003.a.3, 9E003.a.4, 9E003.a.5, 9E003.c, 9E003.i (other than technology for fan or power turbines), 9E003.h.</P>
                    <P>Authorizations.</P>
                    <P>This license exception provides two distinct authorizations. One authorization allows exports, reexports or in country transfers to which any (or all) of six reasons for control apply to go to 36 destinations. Another authorization allows less sensitive items where exports, reexports and in country transfers subject to only national security reasons for control to go to eight additional destinations. National security-controlled items that are ineligible for the latter authorization are identified by the new STA paragraphs in the “License Exceptions” sections of 49 ECCNs on the Commerce Control List. Thus, the STA exclusion paragraph serves the opposite function of a typical list-based license exception paragraph. The typical license exception paragraph in an ECCN identifies items that are eligible for a license exception rather than those that are ineligible.</P>
                    <P>Authorization for Items Controlled for Multiple Reasons to 36 Destinations.</P>
                    <P>
                        If the only reason(s) for control that impose(s) a license requirement on the export, reexport or in country transfer is (are) national security (NS); chemical or biological weapons (CB); nuclear nonproliferation (NP); regional stability (RS); crime control (CC); or significant 
                        <PRTPAGE P="35285"/>
                        items (SI), exports, reexports and transfers (in-country) to 36 destinations as well as releases within a single country of software source code and technology to nationals of the same 36 destinations are authorized, unless otherwise excluded from License Exception STA.
                    </P>
                    <P>On April 29, 2011, the Under Secretary of Commerce for Industry and Security, pursuant to the authority delegated to him under section 6(n)(2) of the EAA, designated Argentina, Austria, Finland, Ireland, South Korea, Sweden, and Switzerland as eligible destinations for export and re-export of items controlled for crime control (CC), not including ECCNs 0A981, 0A982, 0A983, 0A985 or 0E982, without a license under License Exception Strategic Trade Authorization.</P>
                    <P>Authorization for Less Sensitive National Security Items to Eight Additional Destinations.</P>
                    <P>If the only reason for control that imposes a license requirement on the export, reexport or in country transfer is national security (NS) and the item is not designated in the STA sensitive items exclusion paragraph in its ECCN, eight destinations (and nationals thereof) in addition to the 36 noted above are authorized. The STA exclusion paragraphs closely track the Sensitive List of the Wassenaar Arrangement. This rule adds such paragraphs to 49 ECCNs.</P>
                    <P>Limitations on Subsequent Use of License Exception APR.</P>
                    <P>Use of License Exception STA precludes subsequent use of License Exception APR paragraphs (a) and (b) (§ 740.16(a) and (b) of the EAR) for items shipped pursuant to License Exception STA.</P>
                    <P>Conditions That Apply to License Exception STA.</P>
                    <P>Section 740.20(d) imposes three conditions on exports, reexports and transfers and an alternative set of conditions on deemed exports and deemed reexports made pursuant to License Exception STA.</P>
                    <P>(1) Exporters must furnish the consignee with the ECCN that applies to each item transferred under License Exception STA. Reexporters and transferors must provide subsequent consignees with the ECCN provided by the exporter or by prior reexporters or transferors. The ECCN need be furnished to each consignee only once for each item to be shipped under License Exception STA. So long as the furnished ECCN remains accurate, it need not be refurnished for subsequent shipments.</P>
                    <P>(2) Exporters, reexporters and transferors must obtain from their consignees, prior to the shipment, a written statement identifying the items to be shipped and restating the ECCN(s) provided to the consignees by the exporters, reexporters or transferors. The exporter, reexporter and transferor must maintain the consignee's written statement as well as a log or other written record that identifies each shipment associated with a particular statement.</P>
                    <P>The statement must also acknowledge that the consignee:</P>
                    <P>• Is aware that items will be shipped pursuant to License Exception STA;</P>
                    <P>• Has been informed of the description of the items and their ECCN(s) by the exporter, reexporter or transferor;</P>
                    <P>• Understands that shipment pursuant to License Exception STA precludes subsequent use of paragraphs (a) or (b) of License Exception APR for the items;</P>
                    <P>• Agrees not to export, reexport or transfer these items to any destination, end use or end user prohibited by the EAR; and</P>
                    <P>• Agrees to produce copies of this document and all other export, reexport or transfer records (i.e., the documents described in part 762 of the EAR) relevant to the items referenced in this statement to the U.S. Government, upon request, as set forth in § 762.7.</P>
                    <P>(3) With each shipment under License Exception STA, the exporter (or reexporter or transferor as applicable) must notify the consignee in writing that the shipment is made pursuant to License Exception STA. The notice must either specify which items are subject to License Exception STA or state that the entire shipment is made pursuant to License Exception STA. The notice must clearly identify the shipment to which it refers. The written notice may be conveyed by paper documents or by electronic methods such as facsimile or email.</P>
                    <P>Recognizing that the foregoing requirements are not relevant or workable with respect to releases within a single country of software source code or technology to foreign nationals, § 740.20(d) imposes a different set of requirements on them. The releaser of the technology or source code must notify the recipient of the technology or source code of the restrictions on further release. The notification must either expressly inform the recipient that the EAR impose limits on further disclosure or must be in the form of an agreement in which the recipient agrees to limits on further disclosure. Any such agreement must impose limits that are equivalent to or more restrictive than all limits on further disclosure that are imposed by the EAR. The notification must be in writing and a copy of it must be retained by the releaser and the recipient. The notification may be in a separate document or included in a document such as a contract or a nondisclosure agreement. If the document has an expiration date, it must provide that the restrictions on disclosure do not expire.</P>
                    <P>Addition of License Exception STA Paragraphs to 49 ECCNs.</P>
                    <P>This rule adds License Exception STA paragraphs to 49 ECCNs. These paragraphs, which closely track the Wassenaar Arrangement Sensitive List, designate certain items that are not eligible for License Exception STA to the eight destinations in § 740.20(c)(2).</P>
                    <HD SOURCE="HD3">Incidental Changes Necessary To Implement License Exception STA</HD>
                    <HD SOURCE="HD3">Cross Reference to Wassenaar Arrangement Reporting Requirements</HD>
                    <P>Section 740.20 cross references the Wassenaar Arrangement reporting requirements in § 743.1 of the EAR because Wassenaar Arrangement Sensitive List items exported to Wassenaar Arrangement non-members pursuant to License Exception STA are subject to the reporting requirements of § 743.1.</P>
                    <HD SOURCE="HD3">Revisions to § 732.4</HD>
                    <P>Section 732.4 of the EAR explains how to identify and use license exceptions. This rule revises that section to note the License Exception STA exclusion paragraphs in ECCNs and to add License Exception STA to the list of license exceptions that are subject to the Wassenaar Arrangement reporting requirements of § 743.1 of the EAR.</P>
                    <HD SOURCE="HD3">Revision to § 738.2(d)(2)(ii) Explaining the Use of the License Exception STA Exclusion Paragraphs in ECCNs</HD>
                    <P>
                        Section 738.2 of the EAR explains the workings of the Commerce Control List, and paragraph (d)(2)(ii) of that section explains the “License Exception” paragraph of an ECCN. This rule revises that paragraph to explain the role of the STA exclusion paragraphs, which is different from that of the other license exception paragraphs that appear in ECCNs. The other license exception paragraphs signal eligibility to use a license exception and the limits of that eligibility. The STA paragraphs identify items for which the second of the two authorizing paragraphs of License Exception STA (
                        <E T="03">i.e.,</E>
                         § 740.20(c)(2)) may not be used.
                    </P>
                    <HD SOURCE="HD3">Revision to § 743.1 Wassenaar Arrangement Reporting</HD>
                    <P>Wassenaar Arrangement member states, including the United States, are required to report to the Wassenaar Arrangement exports of Wassenaar Arrangement Sensitive List items to non-member states for which a license was not issued. Section 743.1 of the EAR requires exporters using certain license exceptions for such exports to report the export to BIS. The information reported by the exporters is used to compile a report that the United States submits to the Wassenaar Arrangement. To enable the United States to meet its reporting obligations to the Wassenaar Arrangement, this rule adds a reference to License Exception STA in § 743.1. The reporting requirement in § 743.1 is based on exports of Wassenaar Arrangement Sensitive List items to non-Wassenaar member states. The only non-Wassenaar member state to which License Exception STA authorizes Wassenaar Arrangement Sensitive List items is Iceland, a country with which the United States has a relatively small volume of trade. Therefore, BIS believes that this rule will not have any material impact on volume of reports required by § 743.1.</P>
                    <HD SOURCE="HD3">Other Incidental Changes</HD>
                    <P>The restriction on using license exceptions for items controlled for crime controlled reasons is modified by adding a paragraph to § 740.2 exempting transactions authorized by License Exception STA from the restriction.</P>
                    <P>The prohibition on using License Exception GOV to export or reexport items controlled for chemical or biological weapons (CB) to the agencies of cooperating governments (as defined in § 740.11(b)(3)(ii) of the EAR) and certain diplomatic and consular missions of cooperating governments (as defined in § 740.11(b)(2)(iv) of the EAR) is removed by revisions to paragraphs (a)(2) and (b)(2) of Supplement No. 1 to § 740.11 for the reasons noted above.</P>
                    <HD SOURCE="HD3">Rulemaking Requirements</HD>
                    <P>1. Executive Orders 13563 and 12866 direct agencies to assess all costs and benefits of available regulatory alternatives and, if regulation is necessary, to select regulatory approaches that maximize net benefits (including potential economic, environmental, public health and safety effects, distribute impacts, and equity). Executive Order 13563 emphasizes the importance of quantifying both costs and benefits, of reducing costs, of harmonizing rules, and of promoting flexibility. This rule has been designated a “significant regulatory action,” although not economically significant, under section 3(f) of Executive Order 12866. Accordingly, the rule has been reviewed by the Office of Management and Budget.</P>
                    <P>
                        2. Notwithstanding any other provision of law, no person is required to respond to, nor is subject to a penalty for failure to comply with, a collection of information, subject to the requirements of the Paperwork Reduction Act of 1995 (44 U.S.C. 3501 et seq.) (PRA), unless that collection of information displays a currently valid Office of Management and Budget (OMB) Control Number. The rule affects a collection of information approved by OMB under control number 0607-0152 (the Automated Export System or AES). That collection is administered by the Census Bureau. For most exports of items subject to the EAR, the export license number, a license exception symbol or the designator NLR (no license required) must be entered into AES. BIS believes that this rule will have no material impact on the burden imposed by that collection because this rule merely replaces an existing requirement to enter the license number with a requirement to enter a license exception symbol instead. This rule also 
                        <PRTPAGE P="35286"/>
                        amends a collection of information approved by OMB under control number 0694-0137 (License Exemptions and Exclusions). This control number is being amended to add the requirement for exporters, reexporters and transferors to furnish ECCNs, to obtain a statement of assurance from the consignee before shipping pursuant to the license exception and to notify the consignee of shipments pursuant to the License Exception and the requirement to maintain records identifying shipments associated with each statement created by this rule (safeguards requirements). BIS expects the safeguards requirements are likely to increase the burden associated with control number 0694-0137 by about 3,387 hours (2,903 instances of complying with transactions subject to the safeguards requirements @ 1 hour and 10 minutes each). BIS believes that, in most instances, this new burden will be wholly or partially offset by a reduction in burden under control number 0694-0088 (Simplified Network Application Processing System) which authorizes, among other things, export license applications.
                    </P>
                    <P>3. This rule does not contain policies with Federalism implications as that term is defined under E.O. 13132.</P>
                    <P>4. The Chief Counsel for Regulation of the Department of Commerce has certified to the Chief Counsel for Advocacy of the Small Business Administration that the proposed rule, if adopted in final form, would not have a significant economic impact on a substantial number of small entities. The basis for that certification was published in the preamble to the proposed rule and is not repeated here. BIS received no comments regarding the certification. As a result, a final regulatory flexibility analysis is not required and none has been prepared.</P>
                    <P>5. The Department finds that there is good cause to exempt this rule from the requirement of 5 U.S.C. 553(d) to publish a substantive rule not less than 30 days before its effective date. This rule creates an exception to some export license requirements and requires users of that exception to provide certain information to their consignees and to obtain certain assurances from their consignees. In doing so, this rule allows international trade transactions to proceed without the delay needed to obtain a license. Such delays give international customers an incentive to purchase foreign made products and reduce the competiveness of American made products in the marketplace. Moreover, this rule does not require any person to use the new license exception that it creates. Any person may continue to use any other license exceptions that exist or may continue to apply for licenses. Thus no person is required to alter existing practices as a result of this rule. Because a delayed effective date would continue a disincentive to purchase American products and an immediate effective date would not require a change in existing practices, any delay in implementation would not be in the public interest.</P>
                    <LSTSUB>
                        <HD SOURCE="HED">List of Subjects</HD>
                        <CFR>15 CFR Parts 732 and 740</CFR>
                        <P>Administrative practice and procedure, Exports, Reporting and recordkeeping requirements.</P>
                        <CFR>15 CFR Part 738</CFR>
                        <P>Exports.</P>
                        <CFR>15 CFR Part 743</CFR>
                        <P>Administrative practice and procedure, Reporting and recordkeeping requirements.</P>
                        <CFR>15 CFR Part 774</CFR>
                        <P>Exports, Reporting and recordkeeping requirements. </P>
                    </LSTSUB>
                    <P>Accordingly, the Export Administration Regulations (15 CFR parts 730-774) are amended as follows:</P>
                    <REGTEXT TITLE="15" PART="732">
                        <PART>
                            <HD SOURCE="HED">PART 732—[AMENDED]</HD>
                        </PART>
                        <AMDPAR>1. The authority citation for part 732 continues to read as follows:</AMDPAR>
                        <AUTH>
                            <HD SOURCE="HED">Authority:</HD>
                            <P>
                                 50 U.S.C. app. 2401 
                                <E T="03">et seq.;</E>
                                 50 U.S.C. 1701 
                                <E T="03">et seq.;</E>
                                 E.O. 13026, 61 FR 58767, 3 CFR, 1996 Comp., p. 228; E.O. 13222, 66 FR 44025, 3 CFR, 2001 Comp., p. 783; Notice of August 12, 2010, 75 FR 50681 (August 16, 2010).
                            </P>
                        </AUTH>
                    </REGTEXT>
                    <REGTEXT TITLE="15" PART="732">
                        <AMDPAR>2. Section 732.4 is amended by:</AMDPAR>
                        <AMDPAR>a. Adding two sentences immediately following the existing third sentence in paragraph (b)(3)(iii); and</AMDPAR>
                        <AMDPAR>b. Revising paragraph (b)(3)(iv) to read as follows:</AMDPAR>
                        <SECTION>
                            <SECTNO>§ 732.4 </SECTNO>
                            <SUBJECT>Steps regarding License Exceptions.</SUBJECT>
                            <STARS/>
                            <P>(b) * * *</P>
                            <P>(iii) * * * Some ECCNs contain License Exception STA exclusion paragraphs. Those paragraphs delineate items excluded from the License Exception STA provisions in § 740.20(c)(2) of the EAR. * * *</P>
                            <P>(iv) If you are exporting under License Exceptions GBS, CIV, LVS, STA, APP, TSR or GOV, you should review § 743.1 of the EAR to determine the applicability of certain reporting requirements.</P>
                            <STARS/>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="15" PART="738">
                        <PART>
                            <HD SOURCE="HED">PART 738—[AMENDED]</HD>
                        </PART>
                        <AMDPAR>3. The authority citation for part 738 continues to read as follows:</AMDPAR>
                        <AUTH>
                            <HD SOURCE="HED">Authority:</HD>
                            <P>
                                 50 U.S.C. app. 2401 
                                <E T="03">et seq.;</E>
                                 50 U.S.C. 1701 
                                <E T="03">et seq.;</E>
                                 10 U.S.C. 7420; 10 U.S.C. 7430(e); 22 U.S.C. 287c; 22 U.S.C. 3201 
                                <E T="03">et seq.;</E>
                                 22 U.S.C. 6004; 30 U.S.C. 185(s), 185(u); 42 U.S.C. 2139a; 42 U.S.C. 6212; 43 U.S.C. 1354; 15 U.S.C. 1824a; 50 U.S.C. app. 5; 22 U.S.C. 7201 
                                <E T="03">et seq.;</E>
                                 22 U.S.C. 7210; E.O. 13026, 61 FR 58767, 3 CFR, 1996 Comp., p. 228; E.O. 13222, 66 FR 44025, 3 CFR, 2001 Comp., p. 783; Notice of August 12, 2010, 75 FR 50681 (August 16, 2010).
                            </P>
                        </AUTH>
                    </REGTEXT>
                    <REGTEXT TITLE="15" PART="738">
                        <AMDPAR>4. Section 738.2 is amended by adding two sentences immediately following the existing third sentence in paragraph (d)(2)(ii) to read as follows:</AMDPAR>
                        <SECTION>
                            <SECTNO>§ 738.2 </SECTNO>
                            <SUBJECT>Commerce Control List structure.</SUBJECT>
                            <STARS/>
                            <P>(d) * * *</P>
                            <P>(2) * * *</P>
                            <P>(ii) * * * Some ECCNs have License Exception STA exclusion paragraphs. These paragraphs identify items for which the License Exception STA provisions in § 740.20(c)(2) of the EAR may not be used, but do not otherwise affect License Exception STA availability. * * *</P>
                            <STARS/>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="15" PART="740">
                        <PART>
                            <HD SOURCE="HED">PART 740—[AMENDED]</HD>
                        </PART>
                        <AMDPAR>5. The authority citation for part 740 continues to read as follows:</AMDPAR>
                        <AUTH>
                            <HD SOURCE="HED">Authority: </HD>
                            <P>
                                50 U.S.C. app. 2401 
                                <E T="03">et seq.;</E>
                                 50 U.S.C. 1701 
                                <E T="03">et seq.;</E>
                                 22 U.S.C. 7201 
                                <E T="03">et seq.;</E>
                                 E.O. 13026, 61 FR 58767, 3 CFR, 1996 Comp., p. 228; E.O. 13222, 66 FR 44025, 3 CFR, 2001 Comp., p. 783; Notice of August 12, 2010, 75 FR 50681 (August 16, 2010).
                            </P>
                        </AUTH>
                    </REGTEXT>
                    <REGTEXT TITLE="15" PART="740">
                        <AMDPAR>6. Section 740.2 is amended by revising paragraphs (a)(4)(ii) and (iii) and by adding paragraph (a)(4)(iv) to read as follows:</AMDPAR>
                        <SECTION>
                            <SECTNO>§ 740.2 </SECTNO>
                            <SUBJECT>Restrictions on all License Exceptions.</SUBJECT>
                            <P>(a) * * *</P>
                            <P>(4) * * *</P>
                            <P>(ii) Authorized by § 740.11(b)(2)(ii) (official use by personnel and agencies of the U.S. government);</P>
                            <P>(iii) Authorized by § 740.14(e) of the EAR (certain shotguns and shotgun shells for personal use); or</P>
                            <P>(iv) Authorized by § 740.20 of the EAR (License Exception STA).</P>
                            <STARS/>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="15" PART="740">
                        <AMDPAR>7. Supplement No. 1 to § 740.11 is amended by revising paragraphs (a)(2) and (b)(2) to read as follows:</AMDPAR>
                        <SECTION>
                            <PRTPAGE P="35287"/>
                            <SECTNO>§ 740.11 </SECTNO>
                            <SUBJECT>Governments, international organizations, international inspections under the Chemical Weapons Convention, and the International Space Station (GOV).</SUBJECT>
                            <STARS/>
                            <HD SOURCE="HD1">Supplement No. 1 to § 740.11—Additional Restrictions on Use of License Exception GOV</HD>
                            <EXTRACT>
                                <P>(a) * * *</P>
                                <P>(2) Items identified on the Commerce Control List as controlled for missile technology (MT) or nuclear nonproliferation (NP) reasons;</P>
                                <STARS/>
                                <P>(b) * * *</P>
                                <P>(2) Items identified on the Commerce Control List as controlled for missile technology (MT) or nuclear nonproliferation (NP) reasons;</P>
                                <STARS/>
                            </EXTRACT>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="15" PART="740">
                        <AMDPAR>8. Add § 740.20 to read as follows:</AMDPAR>
                        <SECTION>
                            <SECTNO>§ 740.20 </SECTNO>
                            <SUBJECT>License Exception Strategic Trade Authorization (STA).</SUBJECT>
                            <P>
                                (a) 
                                <E T="03">Introduction.</E>
                                 This section authorizes exports, reexports and in country transfers, including releases within a single country of software source code and technology to foreign nationals in lieu of a license that would otherwise be required pursuant to part 742 of the EAR.
                            </P>
                            <P>
                                (b) 
                                <E T="03">Requirements and Limitations</E>
                                —(1) 
                                <E T="03">Requirements for Using License Exception STA.</E>
                                 (i) 
                                <E T="03">All</E>
                                 of the reasons for control that impose a part 742 license requirement on the
                                <E T="03"> export, reexport or in country transfer</E>
                                 must be addressed in at least one authorizing paragraph of this section.
                            </P>
                            <P>(ii) The party using License Exception STA must comply with all of the requirements in paragraph (d) of this section.</P>
                            <P>
                                (2) 
                                <E T="03">Limitations on Use of License Exception STA.</E>
                                 The prohibitions and limits of this paragraph (b)(2) apply notwithstanding the authorizations in paragraph (c) of this section.
                            </P>
                            <P>(i) License Exception STA may not be used in lieu of any license requirement imposed by “Part 744—Control Policy: End User and End Use Based” or by “Part 746—Embargoes and Other Special Controls” of the EAR.</P>
                            <P>(ii) License Exception STA may not be used for any item controlled under ECCNs 0A981, 0A982, 0A983, 0A985 or 0E982.</P>
                            <P>(iii) License Exception STA may not be used for any item that is controlled for reason of encryption items (EI), short supply (SS), surreptitious listening (SL), missile technology (MT) or chemical weapons (CW).</P>
                            <P>(iv) License Exception STA may not be used for any item identified on the CCL as being subject to the exclusive export control jurisdiction of another agency, such as the Department of State, the Department of Energy, or the Nuclear Regulatory Commission.</P>
                            <P>(v) License Exception STA may not be used for any item controlled by ECCNs 1C351.a, .b, .c, .d.5, .d.6 or .e; 1C352; 1C353; 1C354; 1C360; 1E001 (for 1C351.a, .b, .c, .d.5, .d.6 or .e, 1C352, 1C353, 1C354 or 1C360) or ECCN 1E351.</P>
                            <P>(vi) Toxins controlled by ECCN 1C351.d.1, .2, .3, .4, .7, .8, .9, and .10 are authorized to destinations in paragraph (c)(1) of this section under License Exception STA subject to the following limits. For purposes of this paragraph all ECCN 1C351.d.1, .2, .3, .4, .7, .8, .9, or .10 toxins sent from one exporter, reexporter or transferor to one end user on the same day constitute one shipment.</P>
                            <P>(A) The maximum amount of any one toxin in any one shipment may not exceed 100 milligrams. </P>
                            <P>(B) No exporter, reexporter or transferor may send more than six shipments of any one toxin to any one end user in a single calendar year.</P>
                            <P>(vii) Commerce Control List Category 9 limitations on use of License Exception STA.</P>
                            <P>(A) License Exception STA may not be used for 9D001 or 9D002 “software” that is specially designed or modified for the “development” or “production” of:</P>
                            <P>
                                (
                                <E T="03">1</E>
                                ) Components of engines controlled by ECCN 9A001 if such components incorporate any of the “technologies” controlled by 9E003.a.1, 9E003.a.2, 9E003.a.3, 9E003.a.4, 9E003.a.5, 9E003.c, 9E003.i (other than technology for fan or power turbines), 9E003.h; or
                            </P>
                            <P>
                                (
                                <E T="03">2</E>
                                ) Equipment controlled by 9B001.
                            </P>
                            <P>(B) License Exception STA may not be used for 9D001 “software” that is specially designed or modified for the “development” of “technology” controlled by 9E003.a.1, 9E003.a.2, 9E003.a.3, 9E003.a.4, 9E003.a.5, 9E003.c, 9E003.i (other than technology for fan or power turbines) or 9E003.h.</P>
                            <P>(C) License Exception STA may not be used for 9D004.f or 9D004.g “software”.</P>
                            <P>(D) License Exception STA may not be used for 9E001 “technology” according to the General Technology Note for the “development” of 9A001.b engines or components of engines controlled by 9A001.b if such components incorporate:</P>
                            <P>
                                (
                                <E T="03">1</E>
                                ) Any of the “technologies” controlled by 9E003.a.1, 9E003.a.2, 9E003.a.3, 9E003.a.4, 9E003.a.5, 9E003.c, 9E003.i (other than technology for fan or power turbines) or 9E003.h;
                            </P>
                            <P>
                                (
                                <E T="03">2</E>
                                ) Any of the 9D001 or 9D002 software in paragraphs (b)(2)(viii)(A) or (B) of this section.
                            </P>
                            <P>(E) License Exception STA may not be used for 9E002 “technology” according to the General Technology Note for the “production” of components of engines controlled by 9A001.b if such components incorporate any of the “technologies” controlled by 9E003.a.1, 9E003.a.2, 9E003.a.3, 9E003.a.4, 9E003.a.5, 9E003.c, 9E003.i (other than technology for fan or power turbines) 9E003.h.</P>
                            <P>(F) License Exception STA may not be used for “technology” in 9E003.a.1, 9E003.a.2, 9E003.a.3, 9E003.a.4, 9E003.a.5, 9E003.c, 9E003.i (other than technology for fan or power turbines) 9E003.h.</P>
                            <P>
                                (c) 
                                <E T="03">Authorizing paragraphs</E>
                                —(1) 
                                <E T="03">Multiple reasons for control.</E>
                                 Exports, reexports, and in country transfers in which the only applicable reason(s) for control is (are) national security (NS); chemical or biological weapons (CB); nuclear nonproliferation (NP); regional stability (RS); crime control (CC), and/or significant items (SI) are authorized for destinations in or nationals of Argentina, Australia, Austria, Belgium, Bulgaria, Canada, Croatia, Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Japan, Latvia, Lithuania, Luxembourg, Netherlands, New Zealand, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, South Korea, Spain, Sweden, Switzerland, Turkey, or the United Kingdom.
                            </P>
                            <P>
                                (2) 
                                <E T="03">Controls of lesser sensitivity.</E>
                                 Exports, reexports and in country transfers in which the only applicable reason for control 
                                <E T="03">is</E>
                                 national security (NS) and the 
                                <E T="03">item</E>
                                 being exported, reexported or transferred (in country) 
                                <E T="03">is not</E>
                                 designated in the STA paragraph in the License Exception section of the ECCN that lists the item are authorized for destinations in or nationals of Albania, Hong Kong, India, Israel, Malta, Singapore, South Africa, or Taiwan.
                            </P>
                            <P>
                                (d) 
                                <E T="03">Conditions</E>
                                —(1) 
                                <E T="03">Requirement to furnish Export Control Classification Number.</E>
                                 (i) The exporter must furnish to the consignee the ECCN of each item to be shipped pursuant to this section. Once furnished to a particular consignee, the ECCN that applies to any item need not be refurnished to that consignee at the time the same exporter makes an additional shipment of the same item, if the information remains accurate at the time of the additional shipment.
                            </P>
                            <P>
                                (ii) A reexporter or transferor must furnish to subsequent consignees the ECCN, provided by the exporter or a prior reexporter or transferor, of each item to be shipped pursuant to this 
                                <PRTPAGE P="35288"/>
                                section. Once furnished to a particular consignee, the ECCN that applies to any item need not be refurnished to that consignee at the time the same reexporter or transferor makes an additional shipment of the same item, if the information remains accurate at the time of the additional shipment.
                            </P>
                            <P>(iii) For purposes of determining reexport or transfer eligibility under this section, the consignee may rely on the ECCN provided to it by the party required to furnish the ECCN under paragraph (d)(1)(i) or (ii) of this section unless the consignee knows that the ECCN is incorrect or has changed. The word “knows” has the same meaning as the term “knowledge” in § 772.1 of the EAR.</P>
                            <P>
                                (2) 
                                <E T="03">Prior Consignee Statement.</E>
                                 The exporter, reexporter and transferor must obtain the following statement in writing from its consignee prior to shipping the item and must retain the statement in accordance with part 762 of the EAR. One statement may be used for multiple shipments of the same items between the same parties so long as the party names, the description(s) of the item(s) and the ECCNs are correct. The exporter, reexporter, and transferor must maintain a log or other record that identifies each shipment made pursuant to this section and the specific consignee statement that is associated with each shipment.
                            </P>
                            <FP>[INSERT NAME OF CONSIGNEE]:</FP>
                            <P>(i) Is aware that [INSERT DESCRIPTION AND APPLICABLE ECCNS OF ITEMS TO BE SHIPPED] will be shipped pursuant to License Exception Strategic Trade Authorization (STA) in § 740.20 of the United States Export Administration Regulations (15 CFR 740.20);</P>
                            <P>(ii) Has been informed of the ECCNs noted above by [INSERT NAME OF EXPORTER, REEXPORTER OR TRANSFEROR];</P>
                            <P>(iii) Understands that items shipped pursuant to License Exception STA may not subsequently be reexported pursuant to paragraphs (a) or (b) of License Exception APR (15 CFR 740.16(a) or (b));</P>
                            <P>(iv) Agrees not to export, reexport or transfer these items to any destination, use or user prohibited by the United States Export Administration Regulations; and</P>
                            <P>
                                (v) Agrees to provide copies of this document and all other export, reexport or transfer records (
                                <E T="03">i.e.,</E>
                                 the documents described in 15 CFR part 762) relevant to the items referenced in this statement to the U.S. Government as set forth in 15 CFR 762.7.
                            </P>
                            <P>
                                (3) 
                                <E T="03">Notification to consignee of STA shipment.</E>
                                 With each shipment under License Exception STA, the exporter (or reexporter or transferor as applicable), must notify the consignee in writing that the shipment is made pursuant to License Exception STA. The notice must either specify which items are subject to License Exception STA or state that the entire shipment is made pursuant to License Exception STA. The notice must clearly identify the shipment to which it applies. The written notice may be conveyed by paper documents or by electronic methods such as facsimile or email.
                            </P>
                            <P>
                                (4) 
                                <E T="03">Requirements for releases of software source code or technology within a single country.</E>
                                 Instead of the requirement of paragraphs (d)(1) through (d)(3) of this section, the party releasing software source code or technology to a national of a country listed in paragraph (c)(1) or (c)(2) of this section must notify the recipient of the software source code or technology of the restrictions upon further release of the software source code or technology. The notification must either expressly inform the recipient that the EAR impose limits on further disclosure or must be in the form of an agreement in which the recipient agrees to limits on further disclosure. Any such agreement must impose limits that are equivalent to or more restrictive than all limits on further disclosure that are imposed by the EAR. The notification must be in writing and a copy of it must be retained by the party making the release and the recipient of the release. The notification may be in a separate document or included in a document such as a contract or a nondisclosure agreement. If the document has an expiration date, it must provide that the restrictions on disclosure do not expire.
                            </P>
                            <P>
                                (e) 
                                <E T="03">Limitation on subsequent exports, reexports or in country transfers.</E>
                                 If a commodity has been exported, reexported or transferred in-country pursuant to this section, it may not be subsequently exported, reexported or transferred in-country pursuant to paragraphs (a) or (b) of License Exception APR (§ 740.16(a) or (b) of the EAR). Paragraphs (a) and (b) of License Exception APR do not authorize exports of software or technology.
                            </P>
                            <P>
                                (f) 
                                <E T="03">Applicability of Wassenaar Arrangement reporting requirements.</E>
                                 See § 743.1 of the EAR for special reporting requirements that apply to some exports made pursuant to this section.
                            </P>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="15" PART="743">
                        <PART>
                            <HD SOURCE="HED">PART 743—[AMENDED]</HD>
                        </PART>
                        <AMDPAR>9. The authority citation for part 743 continues to read as follows:</AMDPAR>
                        <AUTH>
                            <HD SOURCE="HED">Authority:</HD>
                            <P>
                                 50 U.S.C. app. 2401 
                                <E T="03">et seq.;</E>
                                 50 U.S.C. 1701 
                                <E T="03">et seq.;</E>
                                 E.O. 13222, 66 FR 44025, 3 CFR, 2001 Comp., p. 783; Notice of August 12, 2010, 75 FR 50681 (August 16, 2010).
                            </P>
                        </AUTH>
                    </REGTEXT>
                    <REGTEXT TITLE="15" PART="743">
                        <AMDPAR>10. Section 743.1 is amended by adding a paragraph (b)(4) to read as follows:</AMDPAR>
                        <SECTION>
                            <SECTNO>§ 743.1 </SECTNO>
                            <SUBJECT>Wassenaar Arrangement.</SUBJECT>
                            <STARS/>
                            <P>(b) * * *</P>
                            <P>(4) Exports authorized under License Exception STA (See § 740.20 of the EAR).</P>
                            <STARS/>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="15" PART="774">
                        <PART>
                            <HD SOURCE="HED">PART 774—[AMENDED]</HD>
                        </PART>
                        <AMDPAR>11. The authority citation for part 774 continues to read as follows:</AMDPAR>
                        <AUTH>
                            <HD SOURCE="HED">Authority:</HD>
                            <P>
                                 50 U.S.C. app. 2401 
                                <E T="03">et seq.;</E>
                                 50 U.S.C. 1701 
                                <E T="03">et seq.;</E>
                                 10 U.S.C. 7420; 10 U.S.C. 7430(e); 22 U.S.C. 287c, 22 U.S.C. 3201 
                                <E T="03">et seq.,</E>
                                 22 U.S.C. 6004; 30 U.S.C. 185(s), 185(u); 42 U.S.C. 2139a; 42 U.S.C. 6212; 43 U.S.C. 1354; 15 U.S.C. 1824a; 50 U.S.C. app. 5; 22 U.S.C. 7201 
                                <E T="03">et seq.;</E>
                                 22 U.S.C. 7210; E.O. 13026, 61 FR 58767, 3 CFR, 1996 Comp., p. 228; E.O. 13222, 66 FR 44025, 3 CFR, 2001 Comp., p. 783; Notice of August 12, 2010, 75 FR 50681 (August 16, 2010).
                            </P>
                        </AUTH>
                    </REGTEXT>
                    <REGTEXT TITLE="15" PART="774">
                        <AMDPAR>12. In Supplement No. 1 to Part 774 (the Commerce Control List), Category 1, ECCN 1A002 is amended by adding at the end of the License Exception section, a new License Exception STA paragraph to read as follows:</AMDPAR>
                        <HD SOURCE="HD1">Supplement No. 1 to Part 774—The Commerce Control List</HD>
                        <EXTRACT>
                            <STARS/>
                            <HD SOURCE="HD1">1A002 “Composite” structures or laminates, having any of the following (see List of Items Controlled).</HD>
                            <STARS/>
                            <HD SOURCE="HD2">License Exceptions</HD>
                            <STARS/>
                            <P>
                                <E T="03">STA:</E>
                                 License Exception STA may not be used to ship any item in this entry to any of the eight destinations listed in § 740.20(c)(2) of the EAR.
                            </P>
                            <STARS/>
                        </EXTRACT>
                        <AMDPAR>13. In Supplement No. 1 to Part 774 (the Commerce Control List), Category 1, ECCN 1C001 is amended by adding at the end of the License Exception section, a new License Exception STA paragraph to read as follows:</AMDPAR>
                        <EXTRACT>
                            <HD SOURCE="HD1">1C001 Materials specially designed for use as absorbers of electromagnetic waves, or intrinsically conductive polymers, as follows (see List of Items Controlled).</HD>
                            <STARS/>
                            <PRTPAGE P="35289"/>
                            <HD SOURCE="HD2">License Exceptions</HD>
                            <STARS/>
                            <P>
                                <E T="03">STA:</E>
                                 License Exception STA may not be used to ship any item in this entry to any of the eight destinations listed in § 740.20(c)(2) of the EAR.
                            </P>
                            <STARS/>
                        </EXTRACT>
                        <AMDPAR>14. In Supplement No. 1 to Part 774 (the Commerce Control List), Category 1, ECCN 1C007 is amended by adding at the end of the License Exception section, a new License Exception STA paragraph to read as follows:</AMDPAR>
                        <EXTRACT>
                            <HD SOURCE="HD1">1C007 Ceramic base materials, non- “composite” ceramic materials, ceramic- “matrix” “composite” materials and precursor materials, as follows (see List of Items Controlled).</HD>
                            <STARS/>
                            <HD SOURCE="HD2">License Exceptions</HD>
                            <STARS/>
                            <P>
                                <E T="03">STA:</E>
                                 License Exception STA may not be used to ship any item in 1C007.c or d to any of the eight destinations listed in § 740.20(c)(2) of the EAR.
                            </P>
                            <STARS/>
                        </EXTRACT>
                    </REGTEXT>
                    <REGTEXT TITLE="15" PART="774">
                        <AMDPAR>15. In Supplement No. 1 to Part 774 (the Commerce Control List), Category 1, ECCN 1C010 is amended by adding at the end of the License Exception section, a new License Exception STA paragraph to read as follows:</AMDPAR>
                        <EXTRACT>
                            <HD SOURCE="HD1">1C010 “Fibrous or filamentary materials” as follows (see List of Items Controlled).</HD>
                            <STARS/>
                            <HD SOURCE="HD2">License Exceptions</HD>
                            <STARS/>
                            <P>
                                <E T="03">STA:</E>
                                 License Exception STA may not be used to ship any item in 1C010.c or d to any of the eight destinations listed in § 740.20(c)(2) of the EAR.
                            </P>
                            <STARS/>
                        </EXTRACT>
                    </REGTEXT>
                    <REGTEXT TITLE="15" PART="774">
                        <AMDPAR>16. In Supplement No. 1 to Part 774 (the Commerce Control List), Category 1, ECCN 1C012 is amended by adding at the end of the License Exception section, a new License Exception STA paragraph to read as follows:</AMDPAR>
                        <EXTRACT>
                            <HD SOURCE="HD1">1C012 Materials, as follows (see List of Items Controlled).</HD>
                            <STARS/>
                            <HD SOURCE="HD2">License Exceptions</HD>
                            <STARS/>
                            <P>
                                <E T="03">STA:</E>
                                 License Exception STA may not be used to ship any item in this entry to any of the eight destinations listed in § 740.20(c)(2) of the EAR.
                            </P>
                            <STARS/>
                        </EXTRACT>
                    </REGTEXT>
                    <REGTEXT TITLE="15" PART="774">
                        <AMDPAR>17. In Supplement No. 1 to Part 774 (the Commerce Control List), Category 1, ECCN 1D002 is amended by adding at the end of the License Exception section, a new License Exception STA paragraph to read as follows:</AMDPAR>
                        <EXTRACT>
                            <HD SOURCE="HD1">1D002 “Software” for the “development” of organic “matrix”, metal “matrix” or carbon “matrix” laminates or “composites”.</HD>
                            <STARS/>
                            <HD SOURCE="HD2">License Exceptions</HD>
                            <STARS/>
                            <P>
                                <E T="03">STA:</E>
                                 License Exception STA may not be used to ship or transmit “software” for the “development” of organic “matrix”, metal “matrix” or carbon “matrix” laminates or “composites” specified in ECCN 1A002 to any of the eight destinations listed in § 740.20(c)(2) of the EAR.
                            </P>
                            <STARS/>
                        </EXTRACT>
                    </REGTEXT>
                    <REGTEXT TITLE="15" PART="774">
                        <AMDPAR>18. In Supplement No. 1 to Part 774 (the Commerce Control List), Category 1, ECCN 1E001 is amended by adding at the end of the License Exception section, a new License Exception STA paragraph to read as follows:</AMDPAR>
                        <EXTRACT>
                            <HD SOURCE="HD1">1E001 “Technology” according to the General Technology Note for the “development” or “production” of items controlled by 1A001.b, 1A001.c, 1A002, 1A003, 1A004, 1A005, 1A006.b, 1A007, 1A008, 1A101, 1B (except 1B999), or 1C (except 1C355, 1C980 to 1C984, 1C988, 1C990, 1C991, 1C995 to 1C999).</HD>
                            <STARS/>
                            <HD SOURCE="HD2">License Exceptions</HD>
                            <STARS/>
                            <P>
                                <E T="03">STA:</E>
                                 License Exception STA may not be used to ship or transmit “technology” according to the General Technology Note for the “development” or “production” of equipment and materials specified by ECCNs 1A002, 1C001, 1C007.c or d, 1C010.c or d or 1C012 to any of the eight destinations listed in § 740.20(c)(2) of the EAR.
                            </P>
                            <STARS/>
                        </EXTRACT>
                    </REGTEXT>
                    <REGTEXT TITLE="15" PART="774">
                        <AMDPAR>19. In Supplement No. 1 to Part 774 (the Commerce Control List), Category 1, ECCN 1E002 is amended by adding at the end of the License Exception section, a new License Exception STA paragraph to read as follows:</AMDPAR>
                        <EXTRACT>
                            <HD SOURCE="HD1">1E002 Other “technology” as follows (see List of Items Controlled).</HD>
                            <STARS/>
                            <HD SOURCE="HD2">License Exceptions</HD>
                            <STARS/>
                            <P>
                                <E T="03">STA:</E>
                                 License Exception STA may not be used to ship or transmit any item in 1E002.e or .f to any of the eight destinations listed in § 740.20(c)(2) of the EAR.
                            </P>
                            <STARS/>
                        </EXTRACT>
                    </REGTEXT>
                    <REGTEXT TITLE="15" PART="774">
                        <AMDPAR>20. In Supplement No. 1 to Part 774 (the Commerce Control List), Category 2, ECCN 2D001 is amended by adding at the end of the License Exception section, a new License Exception STA paragraph to read as follows:</AMDPAR>
                        <EXTRACT>
                            <HD SOURCE="HD1">2D001 “Software”, other than that controlled by 2D002, specially designed or modified for the “development”, “production” or “use” of equipment controlled by 2A001 or 2B001 to 2B009.</HD>
                            <STARS/>
                            <HD SOURCE="HD2">License Exceptions</HD>
                            <STARS/>
                            <P>
                                <E T="03">STA:</E>
                                 License Exception STA may not be used to ship or transmit “software”, other than that specified by ECCN 2D002, specially designed for the “development” or “production” of equipment as follows: ECCN 2B001 entire entry; or “Numerically controlled” or manual machine tools as specified in 2B003 to any of the eight destinations listed in § 740.20(c)(2) of the EAR.
                            </P>
                            <STARS/>
                        </EXTRACT>
                    </REGTEXT>
                    <REGTEXT TITLE="15" PART="774">
                        <AMDPAR>21. In Supplement No. 1 to Part 774 (the Commerce Control List), Category 2, ECCN 2E001 is amended by adding at the end of the License Exception section, a new License Exception STA paragraph to read as follows: </AMDPAR>
                        <EXTRACT>
                            <HD SOURCE="HD1">2E001 “Technology” according to the General Technology Note for the “development” of equipment or “software” controlled by 2A (except 2A983, 2A984, 2A991, or 2A994), 2B (except 2B991, 2B993, 2B996, 2B997, or 2B998), or 2D (except 2D983, 2D984, 2D991, 2D992, or 2D994).</HD>
                            <STARS/>
                            <HD SOURCE="HD2">License Exceptions</HD>
                            <STARS/>
                            <P>
                                <E T="03">STA:</E>
                                 License Exception STA may not be used to ship or transmit “technology” according to the General Technology Note for the “development” of “software” specified in the License Exception STA paragraph in the License Exception section of ECCN 2D001 or for the “development” of equipment as follows: ECCN 2B001 entire entry; or “Numerically controlled” or manual machine tools as specified in 2B003 to any of the eight destinations listed in § 740.20(c)(2) of the EAR.
                            </P>
                            <STARS/>
                        </EXTRACT>
                    </REGTEXT>
                    <REGTEXT TITLE="15" PART="774">
                        <AMDPAR>22. In Supplement No. 1 to Part 774 (the Commerce Control List), Category 2, ECCN 2E002 is amended by adding at the end of the License Exception section, a new License Exception STA paragraph to read as follows:</AMDPAR>
                        <EXTRACT>
                            <HD SOURCE="HD1">2E002 “Technology” according to the General Technology Note for the “production” of equipment controlled by 2A (except 2A983, 2A984, 2A991, or 2A994), or 2B (except 2B991, 2B993, 2B996, 2B997, or 2B998).</HD>
                            <STARS/>
                            <HD SOURCE="HD2">License Exceptions</HD>
                            <STARS/>
                            <P>
                                <E T="03">STA:</E>
                                 License Exception STA may not be used to ship or transmit “technology” according to the General Technology Note for the “production” of equipment as follows: ECCN 2B001 entire entry; or “Numerically controlled” or manual machine tools as 
                                <PRTPAGE P="35290"/>
                                specified in 2B003 to any of the eight destinations listed in § 740.20(c)(2) of the EAR.
                            </P>
                            <STARS/>
                        </EXTRACT>
                    </REGTEXT>
                    <REGTEXT TITLE="15" PART="774">
                        <AMDPAR>23. In Supplement No. 1 to Part 774 (the Commerce Control List), Category 3, ECCN 3A002 is amended by adding at the end of the License Exception section, a new License Exception STA paragraph to read as follows:</AMDPAR>
                        <EXTRACT>
                            <HD SOURCE="HD1">3A002 General purpose electronic equipment and accessories therefor, as follows (see List of Items Controlled).</HD>
                            <STARS/>
                            <HD SOURCE="HD2">License Exceptions</HD>
                            <STARS/>
                            <P>
                                <E T="03">STA:</E>
                                 License Exception STA may not be used to ship any item in 3A002.g.1 to any of the eight destinations listed in § 740.20(c)(2) of the EAR.
                            </P>
                            <STARS/>
                        </EXTRACT>
                    </REGTEXT>
                    <REGTEXT TITLE="15" PART="774">
                        <AMDPAR>24. In Supplement No. 1 to Part 774 (the Commerce Control List), Category 3, ECCN 3B001 is amended by adding at the end of the License Exception section, a new License Exception STA paragraph to read as follows:</AMDPAR>
                        <EXTRACT>
                            <HD SOURCE="HD1">3B001 Equipment for the manufacturing of semiconductor devices or materials, as follows (see List of Items Controlled) and specially designed components and accessories therefor.</HD>
                            <STARS/>
                            <HD SOURCE="HD2">License Exceptions</HD>
                            <STARS/>
                            <P>
                                <E T="03">STA:</E>
                                 License Exception STA may not be used to ship any item in 3B001.a.2 to any of the eight destinations listed in § 740.20(c)(2) of the EAR.
                            </P>
                            <STARS/>
                        </EXTRACT>
                    </REGTEXT>
                    <REGTEXT TITLE="15" PART="774">
                        <AMDPAR>25. In Supplement No. 1 to Part 774 (the Commerce Control List), Category 3, ECCN 3D001 is amended by adding at the end of the License Exception section, a new License Exception STA paragraph to read as follows:</AMDPAR>
                        <EXTRACT>
                            <HD SOURCE="HD1">3D001 “Software” specially designed for the “development” or “production” of equipment controlled by 3A001.b to 3A002.g or 3B (except 3B991 and 3B992).</HD>
                            <STARS/>
                            <HD SOURCE="HD2">License Exceptions</HD>
                            <STARS/>
                            <P>
                                <E T="03">STA:</E>
                                 License Exception STA may not be used to ship or transmit “software” specially designed for the “development” or “production” of equipment specified by 3A002.g.1 or 3B001.a.2 to any of the eight destinations listed in § 740.20(c)(2) of the EAR.
                            </P>
                            <STARS/>
                        </EXTRACT>
                    </REGTEXT>
                    <REGTEXT TITLE="15" PART="774">
                        <AMDPAR>26. In Supplement No. 1 to Part 774 (the Commerce Control List), Category 3, ECCN 3E001 is amended by adding at the end of the License Exception section, a new License Exception STA paragraph to read as follows:</AMDPAR>
                        <EXTRACT>
                            <HD SOURCE="HD1">3E001 “Technology” according to the General Technology Note for the “development” or “production” of equipment or materials controlled by 3A (except 3A292, 3A980, 3A981, 3A991 3A992, or 3A999), 3B (except 3B991 or 3B992) or 3C (except 3C992).</HD>
                            <STARS/>
                            <HD SOURCE="HD2">License Exceptions</HD>
                            <STARS/>
                            <P>
                                <E T="03">STA:</E>
                                 License Exception STA may not be used to ship or transmit “technology” according to the General Technology Note for the “development” or “production” of equipment specified by ECCNs 3A002.g.1 or 3B001.a.2 to any of the eight destinations listed in § 740.20(c)(2) of the EAR.
                            </P>
                            <STARS/>
                        </EXTRACT>
                    </REGTEXT>
                    <REGTEXT TITLE="15" PART="774">
                        <AMDPAR>27. In Supplement No. 1 to Part 774 (the Commerce Control List), Category 4, ECCN 4A001 is amended by adding at the end of the License Exception section, a new License Exception STA paragraph to read as follows: </AMDPAR>
                        <EXTRACT>
                            <HD SOURCE="HD1">4A001 Electronic computers and related equipment, having any of the following (see List of Items Controlled), and “electronic assemblies” and specially designed components therefor.</HD>
                            <STARS/>
                            <HD SOURCE="HD2">License Exceptions</HD>
                            <STARS/>
                            <P>
                                <E T="03">STA:</E>
                                 License Exception STA may not be used to ship any commodity in 4A001.a.2 to any of the eight destinations listed in § 740.20(c)(2) of the EAR.
                            </P>
                            <STARS/>
                        </EXTRACT>
                    </REGTEXT>
                    <REGTEXT TITLE="15" PART="774">
                        <AMDPAR>28. In Supplement No. 1 to Part 774 (the Commerce Control List), Category 4, ECCN 4D001 is amended by adding at the end of the License Exception section, a new License Exception STA paragraph to read as follows: </AMDPAR>
                        <EXTRACT>
                            <HD SOURCE="HD1">4D001 “Software” as follows (see List of Items Controlled).</HD>
                            <STARS/>
                            <HD SOURCE="HD2">License Exceptions</HD>
                            <STARS/>
                            <P>
                                <E T="03">STA:</E>
                                 License Exception STA may not be used to ship or transmit “software” specially designed for the “development” or “production” of equipment specified by ECCN 4A001.a.2 or for the “development” or “production” of “digital computers” having an ‘Adjusted Peak Performance’ (‘APP’) exceeding 0.5 Weighted TeraFLOPS (WT) to any of the eight destinations listed in § 740.20(c)(2) of the EAR.
                            </P>
                            <STARS/>
                        </EXTRACT>
                    </REGTEXT>
                    <REGTEXT TITLE="15" PART="774">
                        <AMDPAR>29. In Supplement No. 1 to Part 774 (the Commerce Control List), Category 4, ECCN 4E001 is amended by adding at the end of the License Exception section, a new License Exception STA paragraph to read as follows:</AMDPAR>
                        <EXTRACT>
                            <HD SOURCE="HD1">4E001 “Technology” as follows (see List of Items Controlled).</HD>
                            <STARS/>
                            <HD SOURCE="HD2">License Exceptions</HD>
                            <STARS/>
                            <P>
                                <E T="03">STA:</E>
                                 License Exception STA may not be used to ship or transmit “technology” according to the General Technology Note for the “development” or “production” of any of the following equipment or “software”: a. Equipment specified by ECCN 4A001.a.2; b. “Digital computers” having an ‘Adjusted Peak Performance’ (‘APP’) exceeding 0.5 Weighted TeraFLOPS (WT); or c. “software” specified in the License Exception STA paragraph found in the License Exception section of ECCN 4D001 to any of the eight destinations listed in § 740.20(c)(2) of the EAR.
                            </P>
                        </EXTRACT>
                    </REGTEXT>
                    <REGTEXT TITLE="15" PART="774">
                        <AMDPAR>30. In Supplement No. 1 to Part 774 (the Commerce Control List), Category 5, Part 1, ECCN 5A001 is amended by adding at the end of the License Exception section, a new License Exception STA paragraph to read as follows:</AMDPAR>
                        <EXTRACT>
                            <HD SOURCE="HD1">5A001 Telecommunications systems, equipment, components and accessories, as follows (see List of Items Controlled).</HD>
                            <STARS/>
                            <HD SOURCE="HD2">License Exceptions</HD>
                            <STARS/>
                            <P>
                                <E T="03">STA:</E>
                                 License Exception STA may not be used to ship any commodity in 5A001.b.3, .b.5 or .h to any of the eight destinations listed in § 740.20(c)(2) of the EAR.
                            </P>
                            <STARS/>
                        </EXTRACT>
                    </REGTEXT>
                    <REGTEXT TITLE="15" PART="774">
                        <AMDPAR>31. In Supplement No. 1 to Part 774 (the Commerce Control List), Category 5, Part 1, ECCN 5B001 is amended by adding at the end of the License Exception section, a new License Exception STA paragraph to read as follows:</AMDPAR>
                        <EXTRACT>
                            <HD SOURCE="HD1">5B001 Telecommunication test, inspection and production equipment, components and accessories, as follows (See List of Items Controlled).</HD>
                            <STARS/>
                            <HD SOURCE="HD2">License Exceptions</HD>
                            <STARS/>
                            <P>
                                <E T="03">STA:</E>
                                 License Exception STA may not be used to ship 5B001.a equipment and specially designed components or accessories therefor, specially designed for the “development”, “production” or “use” of equipment, functions or features specified by in ECCN 5A001.b.3, .b.5 or .h to any of the eight destinations listed in § 740.20(c)(2) of the EAR.
                            </P>
                            <STARS/>
                        </EXTRACT>
                    </REGTEXT>
                    <REGTEXT TITLE="15" PART="774">
                        <AMDPAR>32. In Supplement No. 1 to Part 774 (the Commerce Control List), Category 5, Part 1, ECCN 5D001 is amended by adding at the end of the License Exception section, a new License Exception STA paragraph to read as follows:</AMDPAR>
                        <EXTRACT>
                            <PRTPAGE P="35291"/>
                            <HD SOURCE="HD1">5D001 “Software” as follows (see List of Items Controlled).</HD>
                            <STARS/>
                            <HD SOURCE="HD2">License Exceptions</HD>
                            <STARS/>
                            <P>
                                <E T="03">STA:</E>
                                 License Exception STA may not be used to ship or transmit 5D001.a “software” specially designed for the “development” or “production” of equipment, functions or features, specified by ECCN 5A001.b.3, .b.5 or .h; and for 5D001.b. for “software” specially designed or modified to support “technology” specified by the STA paragraph in the License Exception section of ECCN 5E001 to any of the eight destinations listed in § 740.20(c)(2) of the EAR.
                            </P>
                            <STARS/>
                        </EXTRACT>
                    </REGTEXT>
                    <REGTEXT TITLE="15" PART="774">
                        <AMDPAR>33. In Supplement No. 1 to Part 774 (the Commerce Control List), Category 5, Part 1, ECCN 5E001 is amended by adding at the end of the License Exception section, a new License Exception STA paragraph to read as follows:</AMDPAR>
                        <EXTRACT>
                            <HD SOURCE="HD1">5E001 “Technology” as follows (see List of Items Controlled).</HD>
                            <STARS/>
                            <HD SOURCE="HD2">License Exceptions</HD>
                            <STARS/>
                            <P>
                                <E T="03">STA:</E>
                                 License Exception STA may not be used to ship or transmit “technology” according to the General Technology Note for the “development” or “production” of equipment, functions or features specified by 5A001.b.3, .b.5 or .h; or for “software” in 5D001.a that is specified in the STA paragraph in the License Exception section of ECCN 5D001 to any of the eight destinations listed in § 740.20(c)(2) of the EAR.
                            </P>
                            <STARS/>
                        </EXTRACT>
                    </REGTEXT>
                    <REGTEXT TITLE="15" PART="774">
                        <AMDPAR>34. In Supplement No. 1 to Part 774 (the Commerce Control List), Category 6, ECCN 6A001 is amended by adding at the end of the License Exception section, a new License Exception STA paragraph to read as follows: </AMDPAR>
                        <EXTRACT>
                            <HD SOURCE="HD1">6A001 Acoustic systems, equipment and components, as follows (see List of Items Controlled).</HD>
                            <STARS/>
                            <HD SOURCE="HD2">License Exceptions</HD>
                            <STARS/>
                            <P>
                                <E T="03">STA:</E>
                                 License Exception STA may not be used to ship commodities in 6A001.a.1.b, 6A001.a.1.e or 6A001.a.2 (except .a.2.a.4) to any of the eight destinations listed in § 740.20(c)(2) of the EAR.
                            </P>
                            <STARS/>
                        </EXTRACT>
                    </REGTEXT>
                    <REGTEXT TITLE="15" PART="774">
                        <AMDPAR>35. In Supplement No. 1 to Part 774 (the Commerce Control List), Category 6, ECCN 6A002 is amended by revising the ECCN heading and by adding at the end of the License Exception section, a new License Exception STA paragraph to read as follows:</AMDPAR>
                        <EXTRACT>
                            <HD SOURCE="HD1">6A002 Optical sensors or equipment and components therefore, as follows (see List of Items Controlled).</HD>
                            <STARS/>
                            <HD SOURCE="HD2">License Exceptions</HD>
                            <STARS/>
                            <P>
                                <E T="03">STA:</E>
                                 License Exception STA may not be used to ship any commodity in: 6A002.a.1.a, b. or c; or 6A002.a.2.a in which the photocathode in described in 6A002.a.2.a 3.a is a Multialkali photocathode (e.g., S-20 and S-25) having a luminous sensitivity exceeding 700 µA/lm; or
                            </P>
                            <P>6A002.a.3; or</P>
                            <P>6A002.b; or</P>
                            <P>6A002.c “Direct view” imaging equipment incorporating any of the following:</P>
                            <P>1. Image intensifier tubes having the characteristics listed in the description of 6A002.a.2.a earlier in this STA paragraph of License Exception section to this ECCN; or</P>
                            <P>2. “Focal plane arrays” having the characteristics listed in the description of 6A002.a.3; or 6A002.e to any of the eight destinations listed in § 740.20(c)(2) of the EAR</P>
                            <STARS/>
                        </EXTRACT>
                    </REGTEXT>
                    <REGTEXT TITLE="15" PART="774">
                        <AMDPAR>36. In Supplement No. 1 to Part 774 (the Commerce Control List), Category 6, ECCN 6A003 is amended by adding at the end of the License Exception section, a new License Exception STA paragraph to read as follows:</AMDPAR>
                        <EXTRACT>
                            <HD SOURCE="HD1">6A003 Cameras.</HD>
                            <STARS/>
                            <HD SOURCE="HD2">License Exceptions</HD>
                            <STARS/>
                            <P>
                                <E T="03">STA:</E>
                                 License Exception STA may not be used to ship any commodity in 6A003.b.3 or b.4 to any of the eight destinations listed in § 740.20(c)(2) of the EAR.
                            </P>
                            <STARS/>
                        </EXTRACT>
                    </REGTEXT>
                    <REGTEXT TITLE="15" PART="774">
                        <AMDPAR>37. In Supplement No. 1 to Part 774 (the Commerce Control List), Category 6, ECCN 6A004 is amended by adding at the end of the License Exception section, a new License Exception STA paragraph to read as follows: </AMDPAR>
                        <EXTRACT>
                            <HD SOURCE="HD1">6A004 Optical equipment and components, as follows (see List of Items Controlled).</HD>
                            <STARS/>
                            <HD SOURCE="HD2">License Exceptions</HD>
                            <STARS/>
                            <P>
                                <E T="03">STA:</E>
                                 Paragraph (c)(2) of License Exception STA may not be used to ship any commodity in 6A004.c or .d to any of the eight destinations in § 740.20(c)(2) of the EAR.
                            </P>
                            <STARS/>
                        </EXTRACT>
                    </REGTEXT>
                    <REGTEXT TITLE="15" PART="774">
                        <AMDPAR>38. In Supplement No. 1 to Part 774 (the Commerce Control List), Category 6, ECCN 6A006 is amended by adding at the end of the License Exception section, a new License Exception STA paragraph to read as follows:</AMDPAR>
                        <EXTRACT>
                            <HD SOURCE="HD1">6A006 “Magnetometers”, “magnetic gradiometers”, “intrinsic magnetic gradiometers”, underwater electric field sensors, “compensation systems”, and specially designed components therefor, as follows (see List of Items Controlled).</HD>
                            <STARS/>
                            <HD SOURCE="HD2">License Exceptions</HD>
                            <STARS/>
                            <P>
                                <E T="03">STA:</E>
                                 License Exception STA may not be used to ship any commodity in:
                            </P>
                            <P>6A006.a.1; or</P>
                            <P>6A006.a.2; or</P>
                            <P>6A006.c.1 “Magnetic gradiometers” using multiple “magnetometers” specified by 6A006.a.1 or 6.A006.a.2; or 6A006.d or .e (only for underwater receivers incorporating magnetometers specified in 6A006.a.1 or 6A006.a.2) to any of the eight destinations listed in § 740.20(c)(2) of the EAR</P>
                            <STARS/>
                        </EXTRACT>
                    </REGTEXT>
                    <REGTEXT TITLE="15" PART="774">
                        <AMDPAR>39. In Supplement No. 1 to Part 774 (the Commerce Control List), Category 6, ECCN 6A008 is amended by adding at the end of the License Exception section, a new License Exception STA paragraph to read as follows:</AMDPAR>
                        <EXTRACT>
                            <HD SOURCE="HD1">6A008 Radar systems, equipment and assemblies, having any of the following (see List of Items Controlled), and specially designed components therefor.</HD>
                            <STARS/>
                            <HD SOURCE="HD2">License Exceptions</HD>
                            <STARS/>
                            <P>
                                <E T="03">STA:</E>
                                 License Exception STA may not be used to ship any commodity in 6A008.d, 6A008.h or 6A008.k to any of the eight destinations listed in § 740.20(c)(2) of the EAR.
                            </P>
                            <STARS/>
                        </EXTRACT>
                    </REGTEXT>
                    <REGTEXT TITLE="15" PART="774">
                        <AMDPAR>40. In Supplement No. 1 to Part 774 (the Commerce Control List), Category 6, ECCN 6B008 is amended by adding at the end of the License Exception section, a new License Exception STA paragraph to read as follows:</AMDPAR>
                        <EXTRACT>
                            <HD SOURCE="HD1">6B008 Pulse radar cross-section measurement systems having transmit pulse widths of 100 ns or less, and specially designed components therefor.</HD>
                            <STARS/>
                            <HD SOURCE="HD2">License Exceptions</HD>
                            <STARS/>
                            <P>
                                <E T="03">STA:</E>
                                 License Exception STA may not be used to ship any commodity in this entry to any of the eight destinations listed in § 740.20(c)(2) of the EAR.
                            </P>
                            <STARS/>
                        </EXTRACT>
                    </REGTEXT>
                    <REGTEXT TITLE="15" PART="774">
                        <AMDPAR>41. In Supplement No. 1 to Part 774 (the Commerce Control List), Category 6, ECCN 6D001 is amended by adding at the end of the License Exception section, a new License Exception STA paragraph to read as follows:</AMDPAR>
                        <EXTRACT>
                            <PRTPAGE P="35292"/>
                            <HD SOURCE="HD1">6D001 “Software” specially designed for the “development” or “production” of equipment controlled by 6A004, 6A005, 6A008 or 6B008.</HD>
                            <STARS/>
                            <HD SOURCE="HD2">License Exceptions</HD>
                            <STARS/>
                            <P>
                                <E T="03">STA:</E>
                                 License Exception STA may not be used to ship or transmit “software” specially designed for the “development” or “production” of equipment specified by ECCNs 6A004.c, 6A004.d, 6A008.d, 6A008.h, 6A008.k, or 6B008 to any of the eight destinations listed in § 740.20(c)(2) of the EAR
                            </P>
                            <STARS/>
                        </EXTRACT>
                    </REGTEXT>
                    <REGTEXT TITLE="15" PART="774">
                        <AMDPAR>42. In Supplement No. 1 to Part 774 (the Commerce Control List), Category 6, ECCN 6D003 is amended by adding at the end of the License Exception section, a new License Exception STA paragraph to read as follows:</AMDPAR>
                        <EXTRACT>
                            <HD SOURCE="HD1">6D003  Other “software” as follows (see List of Items Controlled).</HD>
                            <STARS/>
                            <HD SOURCE="HD2">License Exceptions</HD>
                            <STARS/>
                            <P>
                                <E T="03">STA:</E>
                                 License Exception STA may not be used to ship transmit software in 6D003.a to any of the eight destinations listed in § 740.20(c)(2) of the EAR.
                            </P>
                            <STARS/>
                        </EXTRACT>
                    </REGTEXT>
                    <REGTEXT TITLE="15" PART="774">
                        <AMDPAR>43. In Supplement No. 1 to Part 774 (the Commerce Control List), Category 6, ECCN 6E001 is amended by adding at the end of the License Exception section, a new License Exception STA paragraph to read as follows:</AMDPAR>
                        <EXTRACT>
                            <HD SOURCE="HD1">6E001 “Technology” according to the General Technology Note for the “development” of equipment, materials or “software” controlled by 6A (except 6A991, 6A992, 6A994, 6A995, 6A996, 6A997, or 6A998), 6B (except 6B995), 6C (except 6C992 or 6C994), or 6D (except 6D991, 6D992, or 6D993).</HD>
                            <STARS/>
                            <HD SOURCE="HD2">License Exceptions</HD>
                            <STARS/>
                            <P>
                                <E T="03">STA:</E>
                                 License Exception STA may not be used to ship or transmit any technology in this entry to any of the eight destinations listed in § 740.20(c)(2) of the EAR.
                            </P>
                            <STARS/>
                        </EXTRACT>
                    </REGTEXT>
                    <REGTEXT TITLE="15" PART="774">
                        <AMDPAR>44. In Supplement No. 1 to Part 774 (the Commerce Control List), Category 6, ECCN 6E002 is amended by adding at the end of the License Exception section, a new License Exception STA paragraph to read as follows:</AMDPAR>
                        <EXTRACT>
                            <HD SOURCE="HD1">6E002 “Technology” according to the General Technology Note for the “production” of equipment or materials controlled by 6A (except 6A991, 6A992, 6A994, 6A995, 6A996, 6A997 or 6A998), 6B (except 6B995) or 6C (except 6C992 or 6C994).</HD>
                            <STARS/>
                            <HD SOURCE="HD2">License Exceptions</HD>
                            <STARS/>
                            <P>
                                <E T="03">STA:</E>
                                 License Exception STA may not be used to ship or transmit “technology” according to the General Technology Note for the “production” of equipment specified in the STA exclusion paragraphs found in the License Exception sections of by ECCNs 6A001, 6A002, 6A003, 6A004, 6A006, 6A008, or 6B008 to any of the eight destinations listed in § 740.20(c)(2) of the EAR.
                            </P>
                            <STARS/>
                        </EXTRACT>
                    </REGTEXT>
                    <REGTEXT TITLE="15" PART="774">
                        <AMDPAR>45. In Supplement No. 1 to Part 774 (the Commerce Control List), Category 7, ECCN 7D003 is amended by adding at the end of the License Exception section, a new License Exception STA paragraph to read as follows:</AMDPAR>
                        <EXTRACT>
                            <HD SOURCE="HD1">7D003 Other “software” as follows (see List of Items Controlled).</HD>
                            <STARS/>
                            <HD SOURCE="HD2">License Exceptions</HD>
                            <STARS/>
                            <P>
                                <E T="03">STA:</E>
                                 License Exception STA may not be used to ship or transmit software in 7D003.a, b, c, d.1 to d.4 or d.7 to any of the eight destinations listed in § 740.20(c)(2) of the EAR.
                            </P>
                            <STARS/>
                        </EXTRACT>
                    </REGTEXT>
                    <REGTEXT TITLE="15" PART="774">
                        <AMDPAR>46. In Supplement No. 1 to Part 774 (the Commerce Control List), Category 7, ECCN 7E001 is amended by:</AMDPAR>
                        <AMDPAR>a. Revising the MT paragraph in the License Requirements section; and</AMDPAR>
                        <AMDPAR>b. Adding at the end of the License Exception section, a new License Exception STA paragraph to read as follows:</AMDPAR>
                        <EXTRACT>
                            <HD SOURCE="HD1">7E001 “Technology” according to the General Technology Note for the “development” of equipment or “software”, controlled by 7A (except 7A994), 7B (except 7B994) or 7D (except 7D994).</HD>
                            <HD SOURCE="HD2">License Requirements</HD>
                            <STARS/>
                            <GPOTABLE COLS="2" OPTS="L1,tp0,i1" CDEF="s120,r60">
                                <TTITLE> </TTITLE>
                                <BOXHD>
                                    <CHED H="1">Controls</CHED>
                                    <CHED H="1">Country chart</CHED>
                                </BOXHD>
                                <ROW>
                                    <ENT I="22"> </ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="28">*         *         *         *         *         *         *</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="01">
                                        MT applies to technology for equipment controlled for MT reasons. MT 
                                        <E T="03">does not</E>
                                         apply to “technology” for equipment controlled by 7A008. MT 
                                        <E T="03">does</E>
                                         apply to “technology” for equipment specified in 7A001, 7A002 or 7A003.d that meets or exceeds parameters of 7A101, 7A102 or 7A103
                                    </ENT>
                                    <ENT>MT Column 1.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="22"> </ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="28">*         *         *         *         *         *         *</ENT>
                                </ROW>
                            </GPOTABLE>
                            <HD SOURCE="HD2">License Exceptions</HD>
                            <STARS/>
                            <P>
                                <E T="03">STA:</E>
                                 License Exception STA may not be used to ship or transmit any technology in this entry to any of the eight destinations listed in § 740.20(c)(2) of the EAR.
                            </P>
                            <STARS/>
                        </EXTRACT>
                    </REGTEXT>
                    <REGTEXT TITLE="15" PART="774">
                        <AMDPAR>47. In Supplement No. 1 to Part 774 (the Commerce Control List), Category 7, ECCN 7E002 is amended by:</AMDPAR>
                        <AMDPAR>a. Revising the MT paragraph in the License Requirements section; and</AMDPAR>
                        <AMDPAR>b. Adding at the end of the License Exception section, a new License Exception STA paragraph to read as follows:</AMDPAR>
                        <EXTRACT>
                            <HD SOURCE="HD1">7E002 “Technology” according to the General Technology Note for the “production” of equipment controlled by 7A (except 7A994) or 7B (except 7B994).</HD>
                            <HD SOURCE="HD2">License Requirements</HD>
                            <STARS/>
                            <GPOTABLE COLS="2" OPTS="L1,tp0,i1" CDEF="s120,r60">
                                <TTITLE> </TTITLE>
                                <BOXHD>
                                    <CHED H="1">Controls</CHED>
                                    <CHED H="1">Country chart</CHED>
                                </BOXHD>
                                <ROW>
                                    <ENT I="22"> </ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="28">*         *         *         *         *         *         *</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="01">
                                        MT applies to technology for equipment controlled for MT reasons. MT 
                                        <E T="03">does not</E>
                                         apply to “technology” for equipment controlled by 7A008. MT 
                                        <E T="03">does</E>
                                         apply to “technology” for equipment specified in 7A001, 7A002 or 7A003.d that meets or exceeds parameters of 7A101, 7A102 or 7A103
                                    </ENT>
                                    <ENT>MT Column 1.</ENT>
                                </ROW>
                                <ROW>
                                    <PRTPAGE P="35293"/>
                                    <ENT I="22"> </ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="28">*         *         *         *         *         *         *</ENT>
                                </ROW>
                            </GPOTABLE>
                            <HD SOURCE="HD2">License Exceptions</HD>
                            <STARS/>
                            <P>
                                <E T="03">STA:</E>
                                 License Exception STA may not be used to ship or transmit any technology in this entry to any of the eight destinations listed in § 740.20(c)(2) of the EAR.
                            </P>
                            <STARS/>
                        </EXTRACT>
                    </REGTEXT>
                    <REGTEXT TITLE="15" PART="774">
                        <AMDPAR>48. In Supplement No. 1 to Part 774 (the Commerce Control List), Category 8, ECCN 8A001 is amended by adding at the end of the License Exception section, a new License Exception STA paragraph to read as follows:</AMDPAR>
                        <EXTRACT>
                            <HD SOURCE="HD1">8A001 Submersible vehicles and surface vessels, as follows (see List of Items Controlled).</HD>
                            <STARS/>
                            <HD SOURCE="HD2">License Exceptions</HD>
                            <STARS/>
                            <P>
                                <E T="03">STA:</E>
                                 License Exception STA may not be used to ship any commodity in 8A001.b, 8A001.c or 8A001.d to any of the eight destinations listed in § 740.20(c)(2) of the EAR.
                            </P>
                            <STARS/>
                        </EXTRACT>
                    </REGTEXT>
                    <REGTEXT TITLE="15" PART="774">
                        <AMDPAR>49. In Supplement No. 1 to Part 774 (the Commerce Control List), Category 8, ECCN 8A002 is amended by adding at the end of the License Exception section, a new License Exception STA paragraph to read as follows:</AMDPAR>
                        <EXTRACT>
                            <HD SOURCE="HD1">8A002 Marine systems, equipment and components, as follows (see List of Items Controlled).</HD>
                            <STARS/>
                            <HD SOURCE="HD2">License Exceptions</HD>
                            <STARS/>
                            <P>
                                <E T="03">STA:</E>
                                 License Exception STA may not be used to ship any commodity in 8A002.b, h, j, o.3, or p to any of the eight destinations listed in § 740.20(c)(2) of the EAR.
                            </P>
                            <STARS/>
                        </EXTRACT>
                    </REGTEXT>
                    <REGTEXT TITLE="15" PART="774">
                        <AMDPAR>50. In Supplement No. 1 to Part 774 (the Commerce Control List), Category 8, ECCN 8D001 is amended by adding at the end of the License Exception section, a new License Exception STA paragraph to read as follows:</AMDPAR>
                        <EXTRACT>
                            <HD SOURCE="HD1">8D001 “Software” specially designed or modified for the “development”, “production” or “use” of equipment or materials, controlled by 8A (except 8A018 or 8A992), 8B or 8C.</HD>
                            <STARS/>
                            <HD SOURCE="HD2">License Exceptions</HD>
                            <STARS/>
                            <P>
                                <E T="03">STA:</E>
                                 License Exception STA may not be used to ship or transmit “software” specially designed for the “development” or “production” of equipment in 8A001.b, 8A001.c, 8A001.d, 8A002.b, 8A002.h, 8A002.j, 8A002.o.3 or 8A002.p to any of the eight destinations listed in § 740.20(c)(2) of the EAR.
                            </P>
                            <STARS/>
                        </EXTRACT>
                        <AMDPAR>51. In Supplement No. 1 to Part 774 (the Commerce Control List), Category 8, ECCN 8D002 is amended by adding at the end of the License Exception section, a new License Exception STA paragraph to read as follows:</AMDPAR>
                        <EXTRACT>
                            <HD SOURCE="HD1">8D002 Specific “software” specially designed or modified for the “development”, “production”, repair, overhaul or refurbishing (re-machining) of propellers specially designed for underwater noise reduction.</HD>
                            <STARS/>
                            <HD SOURCE="HD2">License Exceptions</HD>
                            <STARS/>
                            <P>
                                <E T="03">STA:</E>
                                 License Exception STA may not be used to ship or transmit any software in this entry to any of the eight destinations listed in § 740.20(c)(2) of the EAR.
                            </P>
                            <STARS/>
                        </EXTRACT>
                        <AMDPAR>52. In Supplement No. 1 to Part 774 (the Commerce Control List), Category 8, ECCN 8E001 is amended by adding at the end of the License Exception section, a new License Exception STA paragraph to read as follows:</AMDPAR>
                        <EXTRACT>
                            <HD SOURCE="HD1">8E001 “Technology” according to the General Technology Note for the “development” or “production” of equipment or materials, controlled by 8A (except 8A018 or 8A992), 8B or 8C.</HD>
                            <STARS/>
                            <HD SOURCE="HD2">License Exceptions</HD>
                            <STARS/>
                            <P>
                                <E T="03">STA:</E>
                                 License Exception STA may not be used to ship or transmit “technology” according to the General Technology Note for the “development” or “production” of equipment specified by 8A001.b, 8A001.c, 8A001.d, 8A002.b, 8A002.h, 8A002.j, 8A002.o.3 or 8A002.p to any of the eight destinations listed in § 740.20(c)(2) of the EAR.
                            </P>
                            <STARS/>
                        </EXTRACT>
                    </REGTEXT>
                    <REGTEXT TITLE="15" PART="774">
                        <AMDPAR>53. In Supplement No. 1 to Part 774 (the Commerce Control List), Category 8, ECCN 8E002 is amended by adding at the end of the License Exception section, a new License Exception STA paragraph to read as follows:</AMDPAR>
                        <EXTRACT>
                            <HD SOURCE="HD1">8E002 Other “technology” as follows (see List of Items Controlled).</HD>
                            <STARS/>
                            <HD SOURCE="HD2">License Exceptions</HD>
                            <STARS/>
                            <P>
                                <E T="03">STA:</E>
                                 License Exception STA may not be used to ship or transmit technology in 8E002.a to any of the eight destinations listed in § 740.20(c)(2) of the EAR.
                            </P>
                            <STARS/>
                        </EXTRACT>
                    </REGTEXT>
                    <REGTEXT TITLE="15" PART="774">
                        <AMDPAR>54. In Supplement No. 1 to Part 774 (the Commerce Control List), Category 9, ECCN 9B001 is amended by adding at the end of the License Exception section, a new License Exception STA paragraph to read as follows:</AMDPAR>
                        <EXTRACT>
                            <HD SOURCE="HD1">9B001 Equipment, tooling and fixtures, specially designed for manufacturing gas turbine blades, vanes or tip shroud castings, as follows (see List of Items Controlled).</HD>
                            <STARS/>
                            <HD SOURCE="HD2">License Exceptions</HD>
                            <STARS/>
                            <P>
                                <E T="03">STA:</E>
                                 License Exception STA may not be used to ship commodities in 9B001.b to any of the eight destinations listed in § 740.20(c)(2) of the EAR.
                            </P>
                            <STARS/>
                        </EXTRACT>
                    </REGTEXT>
                    <REGTEXT TITLE="15" PART="774">
                        <AMDPAR>55. In Supplement No. 1 to Part 774 (the Commerce Control List), Category 9, ECCN 9D001 is amended by adding at the end of the License Exception section, a new License Exception STA paragraph to read as follows:</AMDPAR>
                        <EXTRACT>
                            <HD SOURCE="HD1">9D001 “Software” specially designed or modified for the “development” of equipment or “technology”, controlled by 9A (except 9A018, 9A990 or 9A991), 9B (except 9B990 or 9B991) or 9E003.</HD>
                            <STARS/>
                            <HD SOURCE="HD2">License Exceptions</HD>
                            <STARS/>
                            <P>
                                <E T="03">STA:</E>
                                 License Exception STA may not be used to ship or transmit “software” specially designed or modified for the “development” of equipment or “technology”, specified by ECCNs 9B001.b. or 9E003.a.1, 9E003.a.2 to a.5, 9E003.a.8, or 9E003.h to any of the eight destinations listed in § 740.20(c)(2) of the EAR.
                            </P>
                            <STARS/>
                        </EXTRACT>
                    </REGTEXT>
                    <REGTEXT TITLE="15" PART="774">
                        <AMDPAR>56. In Supplement No. 1 to Part 774 (the Commerce Control List), Category 9, ECCN 9D002 is amended by adding at the end of the License Exception section, a new License Exception STA paragraph to read as follows:</AMDPAR>
                        <EXTRACT>
                            <HD SOURCE="HD1">9D002 “Software” specially designed or modified for the “production” of equipment controlled by 9A (except 9A018, 9A990, or 9A991) or 9B (except 9B990 or 9B991).</HD>
                            <STARS/>
                            <HD SOURCE="HD2">License Exceptions</HD>
                            <STARS/>
                            <P>
                                <E T="03">STA:</E>
                                 License Exception STA may not be used to ship or transmit “software” specially 
                                <PRTPAGE P="35294"/>
                                designed or modified for the “production” of equipment specified by 9B001.b to any of the eight destinations listed in § 740.20(c)(2) of the EAR.
                            </P>
                            <STARS/>
                        </EXTRACT>
                    </REGTEXT>
                    <REGTEXT TITLE="15" PART="774">
                        <AMDPAR>57. In Supplement No. 1 to Part 774 (the Commerce Control List), Category 9, ECCN 9D004 is amended by adding at the end of the License Exception section, a new License Exception STA paragraph to read as follows:</AMDPAR>
                        <EXTRACT>
                            <HD SOURCE="HD1">9D004 Other “software” as follows (see List of Items Controlled).</HD>
                            <STARS/>
                            <HD SOURCE="HD2">License Exceptions</HD>
                            <STARS/>
                            <P>
                                <E T="03">STA:</E>
                                 License Exception STA may not be used to ship or transmit software in 9D004.a and 9D004.c to any of the eight destinations listed in § 740.20(c)(2) of the EAR.
                            </P>
                            <STARS/>
                        </EXTRACT>
                    </REGTEXT>
                    <REGTEXT TITLE="15" PART="774">
                        <AMDPAR>58. In Supplement No. 1 to Part 774 (the Commerce Control List), Category 9, ECCN 9E001 is amended by adding at the end of the License Exception section, a new License Exception STA paragraph to read as follows:</AMDPAR>
                        <EXTRACT>
                            <HD SOURCE="HD1">9E001 “Technology” according to the General Technology Note for the “development” of equipment or “software”, controlled by 9A001.b, 9A004 to 9A012, 9B (except 9B990 or 9B991), or 9D (except 9D990 or 9D991).</HD>
                            <STARS/>
                            <HD SOURCE="HD2">License Exceptions</HD>
                            <STARS/>
                            <P>
                                <E T="03">STA:</E>
                                 License Exception STA may not be used to ship or transmit any technology in this entry to any of the eight destinations listed in § 740.20(c)(2) of the EAR.
                            </P>
                            <STARS/>
                        </EXTRACT>
                    </REGTEXT>
                    <REGTEXT TITLE="15" PART="774">
                        <AMDPAR>59. In Supplement No. 1 to Part 774 (the Commerce Control List), Category 9, ECCN 9E002 is amended by adding at the end of the License Exception section, a new License Exception STA paragraph to read as follows: </AMDPAR>
                        <EXTRACT>
                            <HD SOURCE="HD1">9E002 “Technology” according to the General Technology Note for the “production” of equipment controlled by 9A001.b, 9A004 to 9A011 or 9B (except 9B990 or 9B991).</HD>
                            <STARS/>
                            <HD SOURCE="HD2">License Exceptions</HD>
                            <STARS/>
                            <P>
                                <E T="03">STA:</E>
                                 License Exception STA may not be used to ship or transmit any technology in this entry to any of the eight destinations listed in § 740.20(c)(2) of the EAR.
                            </P>
                            <STARS/>
                        </EXTRACT>
                    </REGTEXT>
                    <REGTEXT TITLE="15" PART="774">
                        <AMDPAR>60. In Supplement No. 1 to Part 774 (the Commerce Control List), Category 9, ECCN 9E003 is amended by adding at the end of the License Exception section, a new License Exception STA paragraph to read as follows:</AMDPAR>
                        <EXTRACT>
                            <HD SOURCE="HD1">9E003 Other “technology” as follows (see List of Items Controlled).</HD>
                            <STARS/>
                            <HD SOURCE="HD2">License Exceptions</HD>
                            <STARS/>
                            <P>
                                <E T="03">STA:</E>
                                 License Exception STA may not be used to ship or transmit any technology in 9E003.a.1, 9E003.a.2 to a.5, 9E003.a.8, or 9E003.h to any of the eight destinations listed in § 740.20(c)(2) of the EAR.
                            </P>
                            <STARS/>
                        </EXTRACT>
                    </REGTEXT>
                    <SIG>
                        <DATED>Dated: June 8, 2011.</DATED>
                        <NAME>Gary Locke,</NAME>
                        <TITLE>Secretary of Commerce.</TITLE>
                    </SIG>
                </SUPLINF>
                <FRDOC>[FR Doc. 2011-14705 Filed 6-15-11; 8:45 am]</FRDOC>
                <BILCOD>BILLING CODE 4910-13-P</BILCOD>
            </RULE>
        </RULES>
    </NEWPART>
    <VOL>76</VOL>
    <NO>116</NO>
    <DATE>Thursday, June 16, 2011</DATE>
    <UNITNAME>Presidential Documents</UNITNAME>
    <NEWPART>
        <PTITLE>
            <PRTPAGE P="35295"/>
            <PARTNO>Part III</PARTNO>
            <PRES>The President</PRES>
            <EXECORDR>Executive Order 13576—Delivering an Efficient, Effective, and Accountable Government</EXECORDR>
        </PTITLE>
        <PRESDOCS>
            <PRESDOCU>
                <EXECORD>
                    <TITLE3>Title 3—</TITLE3>
                    <PRES>
                        The President
                        <PRTPAGE P="35297"/>
                    </PRES>
                    <EXECORDR>Executive Order 13576 of June 13, 2011</EXECORDR>
                    <HD SOURCE="HED">Delivering an Efficient, Effective, and Accountable Government</HD>
                    <FP>By the authority vested in me as President by the Constitution and the laws of the United States of America, and in order to cut waste, streamline Government operations, and reinforce the performance and management reform gains my Administration has achieved, it is hereby ordered as follows:</FP>
                    <FP>
                        <E T="04">Section 1.</E>
                          
                        <E T="03">Policy. </E>
                        My Administration is committed to ensuring that the Federal Government serves the American people with the utmost effectiveness and efficiency.  Over the last 2 years, we have made good progress and have saved taxpayer dollars by cutting waste and increasing the efficiency of Government operations by curbing uncontrolled growth in contract spending, terminating poorly performing information technology projects, deploying state of the art fraud detection tools to crack down on waste, focusing agency leaders on achieving ambitious improvements in high priority areas, and opening Government up to the public to increase accountability and accelerate innovation.
                    </FP>
                    <FP>The American people must be able to trust that their Government is doing everything in its power to stop wasteful practices and earn a high return on every tax dollar that is spent.  To strengthen that trust and deliver a smarter and leaner Government, my Administration will reinforce the performance and management reform gains achieved thus far; systematically identify additional reforms necessary to eliminate wasteful, duplicative, or otherwise inefficient programs; and publicize these reforms so that they may serve as a model across the Federal Government.</FP>
                    <FP>The implementation of the American Recovery and Reinvestment Act of 2009 (Public Law 111-5) (Recovery Act) has seen unprecedented transparency.  The Recovery Accountability and Transparency Board (RATB) has developed innovative technologies and approaches for preventing and identifying fraud and abuse that have the potential to improve performance across all of Government spending.</FP>
                    <FP>
                        <E T="04">Sec. 2.</E>
                          
                        <E T="03">Accountable Government Initiative. </E>
                        (a)  On September 14, 2010, in a Memorandum to the Senior Executive Service, my Administration introduced goals for the Accountable Government Initiative (Initiative).  The mission of the Initiative is to monitor and promote agency progress in making Government work better, faster, and more efficiently.  To hold executive departments and agencies (agencies) accountable for obtaining results consistent with this mission, the Vice President shall convene periodic meetings in which Cabinet members and the Director of the Office of Management and Budget (OMB) report to him on improvements implemented under their direction.
                    </FP>
                    <P>
                        (b)  The Federal Chief Performance Officer (CPO), who also serves as the Deputy Director for Management of OMB and the Chair of the President's Management Council (PMC), shall work with the PMC to support agencies' performance and management reform and cost-cutting efforts.  The CPO will lead OMB and the PMC in identifying practices that should be adopted across agencies and in facilitating reforms that require cross-agency coordination and cooperation.  The CPO shall work with agencies to ensure that each area identified as critical to performance improvement has robust performance metrics in place, and that these metrics are frequently analyzed 
                        <PRTPAGE P="35298"/>
                        and reviewed by agency leadership.  Agencies shall update these metrics quarterly, as appropriate, on the website performance.gov.
                    </P>
                    <P>
                        (c)  In accordance with the GPRA Modernization Act of 2010 (31 U.S.C. 1115 
                        <E T="03">et seq</E>
                        .), each agency's Chief Operating Officer (COO) shall be designated as the Senior Accountable Official responsible for leading performance and management reform efforts, and for reducing wasteful or ineffective programs, policies, and procedures.  In discharging this responsibility, this official shall be accountable for conducting frequent data-driven reviews of agency progress toward goals in the areas that OMB identifies as being critical to performance improvement across agencies or that the agency head identifies as top near-term priorities.  These goals may include reforming information technology, reducing improper payments, leveraging the Federal Government's purchasing scale, reducing high-risk contracting practices, improving the management of Federal real estate, enhancing customer service, and achieving agency and Federal Government priority goals identified pursuant to the GPRA Modernization Act of 2010.
                    </P>
                    <P>(d)  The Director of OMB shall provide guidance to agencies as part of the Fiscal Year 2013 budget process for identifying areas of program overlap and duplication within and across agencies, and for proposing consolidations and reductions to address those inefficiencies.</P>
                    <P>(e)  The Chief Financial Officers (CFOs) at all agencies shall be responsible for achieving agency cost savings.  This will include each agency's share of the $2.1 billion in administrative cost savings identified in my Fiscal Year 2012 Budget, and for achieving those savings as quickly as possible.  The CFOs are encouraged to realize these cost savings by targeting wasteful practices and by reducing, and identifying alternatives to, discretionary travel, the use of consultants, and other administrative expenses.  The Federal CFO Council shall provide a monthly report on these efforts to the PMC, with relevant findings and progress reported on performance.gov.</P>
                    <FP>
                        <E T="04">Sec. 3.</E>
                          
                        <E T="03">Government Accountability and Transparency Board. </E>
                        (a)  There is hereby established a Government Accountability and Transparency Board (Board) to provide strategic direction for enhancing the transparency of Federal spending and advance efforts to detect and remediate fraud, waste, and abuse in Federal programs.  The Board shall be composed of 11 members designated by the President from among agency Inspectors General, agency Chief Financial Officers or Deputy Secretaries, a senior official of OMB, and such other members as the President shall designate.  The President shall designate a Chair from among the members.  Building on the lessons learned from the successful implementation of the Recovery Act, the Board shall work with the RATB to apply the approaches developed by the RATB across Government spending.
                    </FP>
                    <P>(b)  Not later than 6 months after the date of this order, the Board shall submit a report to the President that identifies implementation guidelines for integrating systems that support the collection and display of Government spending data, ensuring the reliability of those data, and broadening the deployment of fraud detection technologies, including those proven successful during the implementation of the Recovery Act.</P>
                    <P>(c)  The Director of OMB, in consultation with the Board, shall be responsible for assisting executive agencies in achieving objectives in the guidelines identified in subsection (b) above.</P>
                    <P>(d)  The Chair of the Board, in consultation with the Director of OMB, shall provide monthly updates to the Vice President on the progress obtained under this order.</P>
                    <FP>
                        <E T="04">Sec. 4.</E>
                          
                        <E T="03">General Provisions. </E>
                        (a)  Nothing in this order shall be construed to impair or otherwise affect:
                    </FP>
                    <FP SOURCE="FP1">(i)   authority granted by law to a department or agency, or the head thereof; or </FP>
                    <FP SOURCE="FP1">
                        (ii)  functions of the Director of the Office of Management and Budget related to budgetary, administrative, or legislative proposals.
                        <PRTPAGE P="35299"/>
                    </FP>
                    <P>(b)  This order shall be implemented consistent with applicable law and subject to the availability of appropriations.</P>
                    <P>(c)  This order is not intended to, and does not, create any right or benefit, substantive or procedural, enforceable at law or in equity by any party against the United States, its departments, agencies, or entities, its officers, employees, or agents, or any other person.</P>
                    <GPH SPAN="1" DEEP="62" HTYPE="RIGHT">
                        <GID>OB#1.EPS</GID>
                    </GPH>
                    <PSIG> </PSIG>
                    <PLACE>THE WHITE HOUSE,</PLACE>
                    <DATE>June 13, 2011.</DATE>
                    <FRDOC>[FR Doc. 2011-15181</FRDOC>
                    <FILED>Filed 6-15-11; 11:15 am]</FILED>
                    <BILCOD>Billing code 3195-W1-P</BILCOD>
                </EXECORD>
            </PRESDOCU>
        </PRESDOCS>
    </NEWPART>
</FEDREG>
